Regarding at command queuing up the job and not running the job , I have killed the cron daemon by using kill <process-id-cron-daemon (/usr/sbin/cron) > and jobs started running so that problem is solved.

But at jobs sometimes doesn't run , that problem still persist.Application user is running at jobs. It does't seem to be file permission problem as it runs the at jobs sometimes with the same userid and sometimes it doesnt run and throws an error 0481-103 Cannot open a file in the /var/spool/cron/atjobs directory.

So that leaves file system issues as possible causes. Have you checked the availability of free disk space and/or inodes? The directory in question will (by default) be served by LV "hd9var".

I hope this helps.

bakunin

Hunch based on googling the error message. The error message is normally associated with issuing "crontab -l" when there is no crontab for that user.

Listing the queued "at" jobs is of course "at -l".

Assuming that the error message did not come from issuing "crontab -l" instead of "at -l", and if there is definitely no crontab for the user of the "at" jobs, try creating a crontab for that user containing only comment lines.

ok does that mean when we are out of disk space on hd9var , this issue may occur ? this sounds logical although..

---------- Post updated at 09:12 AM ---------- Previous update was at 09:10 AM ----------

I already have some crontab entries...this is not an empty file...

---------- Post updated at 09:13 AM ---------- Previous update was at 09:12 AM ----------

I would like to thank you all....Although i didnt get to the exact issue yet...but each one of you helped me to get onto the next step...I hope i solve it soon and post it back ....