+ "Chris Garrigues" <[EMAIL PROTECTED]>:
| > From: "Chris Garrigues" <[EMAIL PROTECTED]>
| > Date: Wed, 09 Jun 1999 09:26:11 -0500
| >
| > I've got a system on which cron keeps dying.
| >
| > Would it work to run cron under supervise?
|
| As I worked on tracking this problem down, I found that the last log entries for
| vixie-cron were:
|
| root (06/06-00:00:15-15757) MAIL (mailed 11060 bytes of output but got status 0x006f
| )
| root (06/06-00:00:15-30191) MAIL (mailed 11839 bytes of output but got status 0x006f
| )
| root (06/06-00:00:15-17528) MAIL (mailed 7360 bytes of output but got status 0x006f
| )
| root (06/06-00:00:15-4607) MAIL (mailed 13738 bytes of output but got status 0x006f
| )
|
| and Vixie asked me why qmail was sending a non-zero error code.
Hmmm. 0x006f=111 is the usual exit code for temporary errors in the
qmail suite of programs.
| here's the qmail log from that time (run through tailocal):
Probably irrelevant. If qmail-queue did not manage to complete
delivery, the message will not show up in the queue, and hence there
should not be any trace of it in the qmail log.
If you see these messages only once in a while, I would assume some
resource is temporarily exhausted, causing the mailing operation to
fail. If it happens every time cron tries to send mail, maybe it's
time to start tracing system calls to find out what is going on.
- Harald
