Mailinglist Archive: opensuse (3336 mails)

< Previous Next >
Re: [SLE] Mysterious cron problem with Suse 9.3
  • From: Bruce Marshall <bmarsh@xxxxxxxxxx>
  • Date: Fri, 2 Dec 2005 13:38:27 -0500
  • Message-id: <200512021338.27528.bmarsh@xxxxxxxxxx>
On Friday 02 December 2005 01:22 pm, Eric E wrote:
> Hi all,
> I'm running Suse Linux 9.3, and I'm having problems with cron not
> actually running cron jobs. I suspect this is the kind of profile issue
> that commonly happens with cron jobs, but I don't have any idea how to
> debug it.
>
> For example, if as root, I run crontab -e and enter the following very
> simple cron job:
>
> 22 12 * * * /usr/bin/touch /root/hello.root
>
> In /var/log/messages, I have the following output:
>
> Dec 2 12:21:23 hypervisor1 crontab[7015]: (root) BEGIN EDIT (root)
> Dec 2 12:21:25 hypervisor1 crontab[7015]: (root) REPLACE (root)
> Dec 2 12:21:25 hypervisor1 crontab[7015]: (root) END EDIT (root)
> Dec 2 12:22:01 hypervisor1 /usr/sbin/cron[6536]: (root) RELOAD (tabs/root)
>
> so it sure seems like cron is waking up, finding the job, and then going
> back to sleep. However, the file that should be touch-ed
> is not there, and there are no error messages, either in
> /var/log/messages or as an email.
>
> Can anyone give me advice on how to debug this problem, or why cron does
> not appear to be actually running the job?
>
> Thanks,
>
> Eric

Well for starters, I looked in /var/log/messages and all of the cron jobs I
run in the same manner have log entries that look like the below:


Nov 27 22:10:01 linux1 /usr/sbin/cron[15239]: (root) CMD
(/usr/local/bin/putwx)


Notice the CMD that follows the userid.... Yours shows RELOAD which to me
indicates that the RELOAD was due to your changing the crontab, and did not
have anything to do with running the command. (cron is reloading the file)

Was there any log message after the above?

Perhaps you just missed it on the timing.... I tried the same thing here,
with a few minutes to lapse first, and it worked fine. (and it did the
reload on the next minute after I ran crontab -e.


< Previous Next >
References