On Sunday, August 21, 2005 at 12:15AM, Javier Fern?ndez-Sanguino Pe?a wrote:
I'm sorry but I can't reproduce this and you're the only one seeing this.
I'm pretty sure that if 3.0pl1-88 introduce a bug of this kind I would
be flooded with similar bug reports already since it is a base package.
Could you please send a trace of the cron daemon _before_ a cronjob
starts so we can actually determine why it's dying? You can do this
with 'strace' (use the -p option to tell it which pid to trace and the -f
option to follow forks)
I'm having this problem also, but haven't tried 3.0pl1-87. I'm also having
problems with my clock running too fast, so I'm frequently running ntpdate
until I can figure out what's going on when I get back to work on Monday. Not
sure if that would have anything to do with it...
I've rebuilt the cron daemon with -g to try and get something good out of the
core, but now it's not crashing. :/
A strace I captured earlier looks like this:
[snip]
1523 open("/etc/cron.d", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
1523 fstat64(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
1523 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
1523 getdents64(4, /* 5 entries */, 4096) = 136
1523 lstat64("/etc/cron.d/sendmail", {st_mode=S_IFREG|0644, st_size=7, ...}) = 0
1523 open("/etc/cron.d/sendmail", O_RDONLY) = 5
1523 fstat64(5, {st_mode=S_IFREG|0644, st_size=7, ...}) = 0
1523 close(5) = 0
1523 lstat64("/etc/cron.d/php4", {st_mode=S_IFREG|0644, st_size=456, ...}) = 0
1523 open("/etc/cron.d/php4", O_RDONLY) = 5
1523 fstat64(5, {st_mode=S_IFREG|0644, st_size=456, ...}) = 0
1523 close(5) = 0
1523 getdents64(4, /* 0 entries */, 4096) = 0
1523 close(4) = 0
1523 open("crontabs", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
1523 fstat64(4, {st_mode=S_IFDIR|S_ISVTX|0730, st_size=4096, ...}) = 0
1523 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
1523 getdents64(4, /* 4 entries */, 4096) = 104
1523 open("crontabs/root", O_RDONLY|O_NOFOLLOW) = 5
1523 fstat64(5, {st_mode=S_IFREG|0600, st_size=1011, ...}) = 0
1523 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
It seemed stable when I commented everyone's crontabs.
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
