Cron Error

[John Peace]

I have a cron that is erroring with rc=126. @ questions.

1. What is error 126?
2. Where can I find the errors that relate to the numbers?

[harry d brown jr · Accepted solution]

John,

using the SEARCH feature using

+cron +126

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc1895220af9bd5118ff10090279cd0f9,00.html


live free or die
harry

[Mark Vollmers]

John-

Here is a thread with that number
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc1895220af9bd5118ff10090279cd0f9,00.html

is there anything is root email? have you looked at the script itself to make sure there are no errors? also, can you run the script manually?

Mark

[John Peace]

DUH!!! Right in front of my face. I had one too many * in the crontab. Thanks. Now can anyone tell me where I could have looked up the error code for 126?

[James R. Ferguson]

Hi John:

The Technical Knowledge Base (document #HPUXKBRC00001849) offers further insight:

rc=101 no at command file
rc=102 (stat(at_cmdfile,&buf)) was true, so stat(2) returned an error
rc=103 if set uid bit off, original owner has given file to someone else
rc=104 bad job open
rc=105 no audit id
rc=106 couldn't set group /user ids, exiting
rc=107 couldn't open stdin
rc=108 no stdin
rc=109 couldn't open tmp as stdin to sh
rc=110 couldn't open output file or /dev/null
rc=111 testing
rc=112 can't exec sh
rc=113 file locking problem
rc=127 can't fork (this might also be return code from the shell)

Regards!

...JRF...

[Michael R. Monteith]

I couldn't find HPUXKBRC00001849. Anyone post an updated link, attach it, or send it to me?

Michael

[Pete Randall]

http://www1.itrc.hp.com/service/cki/search.do?searchString=HPUXKBRC00001849&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty&searchCrit=allwords&search.x=18&admit=-682735245+1160761149282+28353475&category=c0&mode=id&dateRange=all&prevQueryString=&search.y=10


Pete

[Bill Hassell]

Here's an updated version of my errno script. I've added the codes for cron returns (ie, 101-127) and will update it for LVM code (126 and up) when I find the files. Run it like this:

errno 12
errno enomem
errno 102
errno 126

[rachelgomez_123]

If you can't find your job but believe it was previously scheduled double check that you are on the correct server.

Validate your job schedule. Once you have found your job, verify that it's scheduled correctly. 
Check your permissions.
Check that your cron job is running by finding the attempted execution in syslog.

Greeting,

Rachel Gomez