Help - Search - Members - Calendar
Full Version: cron issues
Linuxhelp > Support > Technical Support
Music
Im running the 2.6.14.5 Kernel using Trustix, and I noticed that none
of roots cronjobs (like logrotate) were running. I restarted the fcron
daemon, but didnt seem to fix the problem. To verify this, I used the
fcrondyn program, which allows you do things dynamically with cronjobs.
So I ran fcrondyn in debug mode and here is what I saw:

#fcrondyn -d
08:58:50 fcronconf=/etc/fcron.conf
08:58:50 called with echo='OFF', prompt='password for root :'.
password for root :
fcrondyn>


At this point I ran a listing (ls root)


fcrondyn>ls root
command : ls
uid = 0
ID SCHEDULE CMD
No corresponding job found.


Yet, my roots crontab file reads:


SHELL=/bin/bash
PATH=/sbin:/bin:/usr/bin:/usr/sbin


#run parts
01 * * * * run-parts /etc/cron.hourly
02 0 * * * run-parts /etc/cron.daily
22 0 * * 0 run-parts /etc/cron.weekly
42 0 1 * * run-parts /etc/cron.monthly


On other machines which are running the same software, the results of
the 'ls root' command in the fcrondyn prompt should have produced a
listing of the complete contents of root's crontab, along with job ID's
and other identifying notations.


Ive done a lot of troubleshooting on this issue, including matching up
file permissions, verifying packages, googling a lot and nothing was
come close to working.


Any help whatsoever would be greatly appreciated! I will watch this
thread like a hawk and respond asap to any questions.


Thanks,


Eric
markjr
QUOTE (Music @ Jul 27 2006, 11:06 AM) *
Im running the 2.6.14.5 Kernel using Trustix, and I noticed that none
of roots cronjobs (like logrotate) were running. I restarted the fcron
daemon, but didnt seem to fix the problem. To verify this, I used the
fcrondyn program, which allows you do things dynamically with cronjobs.
So I ran fcrondyn in debug mode and here is what I saw:


Probably not the answer you are looking for, but everytime I setup a box, I do two things to cron:

1. add this to the crontab

<code>
* * * * * touch /tmp/cron.running
</code>

and

2. edit syslogd.conf and have cron.all log to a separate system log

The first just lets me do a quick visual check to make sure crond is always running, and he second splits out all the cron output to its own logfile so they don't get buried in the other system logs.

I'm not that familiar with fcron tho, sorry
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2017 Invision Power Services, Inc.