Cron: can't access your crontab file. Resubmit it.

[sekar parthasarathy]

This mesg from root, maybe permission problem ?
Server : k580 - HP-UX 11.00

Thanks in Advance

sekar.

[Patrick Wallek]

What are the permissions on root's crontab file?

Mine are:

# ll /var/spool/cron/crontabs/root
-r-------- 1 root sys 214 Jan 23 14:27 /var/spool/cron/crontabs/root

[Helen French]

Hi Sekar,

Check this out:

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=e8ccc3181220300c5e/screen=ckiDisplayDocument?docId=200000006433534

HTH,
Shiju

[Krishnan Viswanathan]

It is also likely that your root crontab must have got corrupted if you edited the /var/../root crontab file using "vi" instead of crontab -l". In that case you have to do crontab -e and add the entries all over again or restore from a backup copy

[Darrell Allen]

Hi Sekar,

What were you doing that caused you to get the error message?

Darrell

[Bill Hassell]

Make sure no one has 'improved' the standard HP-UX permissions on / (very important) and /var. They should look like this:

ll -d / /var /var/spool /var/spool/cron /var/spool/cron/crontabs
drwxr-xr-x 31 root root 5120 Dec 6 03:32 /
drwxr-xr-x 20 bin bin 1024 Apr 18 1999 /var
dr-xr-xr-x 14 bin bin 1024 Jul 21 1999 /var/spool
dr-xr-xr-x 7 bin bin 1024 Jan 4 2001 /var/spool/cron
dr-xr-xr-x 2 bin bin 1024 Jan 28 13:34 /var/spool/cron/crontabs

[Manohar Joshi]

I corrected by doing chmod +x on the cron job file.

[Steven Sim Kok Leong]

Hi Sekar,

I believe Bill is right.

Btw, if you already have your problem resolved, can you at least assign points to the correct solution above so that the rest of the forumers would know that this problem has already been resolved. If not, at least respond to say that your problem has been fixed by so-and-so solution (please describe the solution or point to it). If it has not yet been resolved, please also feedback by responding.

If you have problems locating this post of yours, you can use the search engine at https://www.beepz.com/cgi-bin/itrc.cgi.

Hope this helps. Regards.

Steven Sim Kok Leong

[sekar parthasarathy]

Sorry Bill I was totaly forget to inform,
the problem resolved that day itselt, one the
DBA admin edit the crontab using vi and not
done properly. Thanks to everyone.

sekar.

[Sanjay_6]

Hi Sekar,

You get this message when there is no crontab file for root or for that user.

Probably root does not have a crontab file. Check if the file exist in /var/spool/cron/crontabs. The file name should be root. If it does not exist, you can create a new crontab file, just do a "crontab -e" and it will open a new file in vi mode. you can add your cron jobs to this file in and then save the file. The file will automatically be scheduled by cron. Do "man crontab" for more info on how to add cron jobs to the system.

Hope this helps.

Regds

[Peter Kloetgen]

Hi,

you told us that the DBA edited the crontab file with vi- editor and did it not "properly". Does this mean he closed his connection to the computer without saving the file? This would generate a temporary file with the option to repair it in future.

vi -r file_name should show you that file, remove it and this error should leave.

Allways stay on the bright side of life!

Peter