Hiya, thanks for that Wil, gives me some ideas. I notice the Bad file descriptor error in there, I've pasted the part there it starts to run it below (I'm only using touch as a basic test as other cron entries don't work, touch outside of cron works fine). I'm a bit clueless looking at the rest really though, is it definitely the bad file descriptor thats causing it, and any ideas why as its fine outside of cron?
read(6, "03 11 * * * /bin/touch /home/log"..., 4096) = 47 lseek(6, 47, SEEK_SET) = 47 read(6, "", 4096) = 0 read(6, "", 4096) = 0 close(6) = 0 munmap(0x2a9556c000, 4096) = 0 close(6) = -1 EBADF (Bad file descriptor) getdents64(5, /* 0 entries */, 4096) = 0 close(5) = 0 time(NULL) = 1159179661 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 rt_sigaction(SIGCHLD, NULL, {0x552aaad780, [], SA_RESTORER|SA_RESTART, 0x2a959b7410}, 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 nanosleep({60, 0}, <unfinished ...>
On 9/25/06, Will McDonald wmcdonald@gmail.com wrote:
On 25/09/06, Ian mu mu.llamas@gmail.com wrote:
Hiya all,
just found an odd one on one of our boxes, cron isnt working (for a
user
anyway, but can't seem to get it running properly at all), i.e if I do a crontab -e as a user (who is in /var/spool/cron) and add 19 10 * * * /bin/touch /home/logadmin/testfile (has permission) its never created.
Also
I get no mails from cron to /var/spool/mail/root so guessing maybe cron
not
working at all, can't find any errors in logfiles relating to it either.
ps -ef shows crond running however, have tried restarting it via service crond restart which shows fine in logs as started
Not sure what else to check?
Is there an entry in /etc/cron.deny for the user? Does /var/spool/cron/logadmin look OK?
You could try attaching strace to the running crond process with -f to see if that provides any insights.
Will. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos