Error 126

vadirajcs · 09-25-2007, 12:34 AM

Hey folks,

I get an error 126 for the command " mkdir -p" this command fails( as far as I'm aware) if the path already exists and is a file or a link.

On further digging into error.h and google. found that this is ENOKEY number. Thrown when kernel gets invalid key for a shared memory access.

And what happens to me is not consistent. You try to execute the command again everything works fine. I do hit this sometime.
Any geeks here to help me out on this?

Thanks in advance.

matthewg42 · 09-25-2007, 04:24 AM

Can you reliably replicate the problem? If so, please post your procedure here so that others can replicate it. Can you copy-paste the exact output of mkdir when the error occurs (and the command which caused it)?

vadirajcs · 09-25-2007, 04:37 AM

Quote:

Originally Posted by matthewg42

Can you reliably replicate the problem? If so, please post your procedure here so that others can replicate it. Can you copy-paste the exact output of mkdir when the error occurs (and the command which caused it)?

Actually this step is part of script. It does not print any message. Modified the script to capture the return status and
also put an strace command.

When this is hit, strace too fails with output too man arguments.

this is how my script is.

mkdir -p /var/run/tmp
if [ $? -ne 0 ];
then
echo " unable to create dir. Return status $?";
strace -o /tmp/mkdir.debug mkdir -p /var/run/tmp;
exit -1;
fi

tweek the code to just see if strace is a problem.. it executes properly. For my bad luck this error is causing strace to throw and error too

matthewg42 · 09-25-2007, 05:18 AM

When I try to create a directory which already exists as a file, I get error level = 1 and error message:

Code:

mkdir: `a/test/file' exists but is not a directory

According to the EXIT STATUS section of the bash manual page,

Quote:

If a command is found but is not executable, the return status is 126.

This might also explain which strace is not executing.

Find out where mkdir and strace are being found using these commands:

Code:

which mkdir
which strace

Check the permissions of the files is such that your user can read and execute the files. If they ar not executable then I think you have a serious system state issue - your files have been messed up somehow, and you are probably going to be glad of that full system backup you made.

Another (easier to fix, but less likely) possibility is that the filesystem on which the files reside is mounted with the noexec flag set. In this case, you really need to find out why and resolve the issue.

vadirajcs · 09-25-2007, 05:40 AM

Quote:

Originally Posted by matthewg42

When I try to create a directory which already exists as a file, I get error level = 1 and error message:

Code:

mkdir: `a/test/file' exists but is not a directory

According to the EXIT STATUS section of the bash manual page,

This might also explain which strace is not executing.

Find out where mkdir and strace are being found using these commands:

Code:

which mkdir
which strace

Check the permissions of the files is such that your user can read and execute the files. If they ar not executable then I think you have a serious system state issue - your files have been messed up somehow, and you are probably going to be glad of that full system backup you made.

Another (easier to fix, but less likely) possibility is that the filesystem on which the files reside is mounted with the noexec flag set. In this case, you really need to find out why and resolve the issue.

Thanks a lot matt that was helpful.

1. Its not mounted filesystem.
2. which mkdir is /bin/mkdir
3. This does not fail everytime. Run the script again and it succeeds. Have no clue why at that perticular time it fails.

4. Another point, this directory /var/run/tmp does contain files
these files are socket file and fifo files. Does this make a difference.

5. And one more thing, mkdir -p on other directories have not been throwing. I have same command for different directory path.. ex mkdir -p /var/run/log and they dont crib any time.

matthewg42 · 09-25-2007, 05:51 AM

Perhaps your system is operating near capacity, and sometimes a new process cannot be spawned because of some system limit (max number of processes or max number of files open or something like that)?

I would expect a more meaningful error message in this case however.

Apart from that I'm out of ideas, sorry - it's hard without access to the system to get inspiration.