On Fri, 2004-08-20 at 09:49, Mike DeCleene wrote: > Hi, > > I'm running FC2, and I'm having some strange issues with cron. I updated > a fairly large number of package via up2date in mid-July, and for some > reason cron appears to no longer be functioning properly. i.e. it's not > executing anything. The logs are telling me "getfilecron FAILED"--see > below. > > I do have what appears to be a properly formatted /etc/crontab, and I've > verified I can manually execute "run-parts cron.hourly" and such. But > cron won't run them, and I'm out of ideas. > > Any help greatly appreciated. Some hopefully relevant detail follows. > > I've verified crond is in fact running: > [root@home root]# service crond status > crond (pid 5526) is running... > > Relevant installed rpm's are: > anacron-2.3-30 > crontabs-1.10-6 > vixie-cron-3.0.1-87 > > The end of the current /var/log/cron looks like this: > Aug 18 22:40:14 localhost crond[5502]: (CRON) STARTUP (fork ok) > Aug 18 22:40:14 localhost crond[5503]: (system_u) getfilecon FAILED > (/etc/crontab) > Aug 18 22:43:00 localhost crond[5503]: (system_u) getfilecon FAILED > (/etc/crontab) > Aug 18 22:43:11 localhost crond[5525]: (CRON) STARTUP (fork ok) > Aug 18 22:43:11 localhost crond[5526]: (system_u) getfilecon FAILED > (/etc/crontab) > Followed by nothing for the last 2 days (2 start statements because I > restarted cron hoping to see something useful in the logs...) > > Mike > Mike, Be careful, you hijacked a thread by replying to an existing message and just changing the topic (there are internal tags that aid in threading). I seem to have the same set of cron packages, so I can only assume that perhaps there is a problem in your /etc/crontab file... Here is mine as an example (it's the default): # cat /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root HOME=/ # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly The other place I just thought of looking is that crond will also hunt through the directory /etc/cron.d, so perhaps there is an extraneous file there with a bad format (files should have the same format as the /etc/crontab). Also, not that permissions should get in the way but: # ls -l /etc/crontab -rw-r--r-- 1 root root 255 Feb 15 2004 /etc/crontab HTH a little, --Rob
