SV: [Mimedefang] Help with slave died unexpectedly

Kimmo Jaskari kimmo.jaskari at eget.fi
Mon Sep 15 10:53:00 EDT 2003


> Normally adding '-l' flag to the mimdefang-multiplexor will 
> tell you what's
> wrong. Just add it to yor startup script and wait fot the 
> error to happen again
> then check your syslog logs.

Thanks. I did check my syslog and this is what happens:

Sep 15 17:34:55 mlmsg02 mimedefang-multiplexor: [ID 731849 mail.info] stats
1063636495.348 ReapSlave slave=0 nslaves=0 nbusy=0
Sep 15 17:34:58 mlmsg02 mimedefang-multiplexor: [ID 778059 mail.info]
Starting slave 0 (pid 6182) (1 running): Bringing slaves up to minSlaves (2)
Sep 15 17:34:58 mlmsg02 mimedefang-multiplexor: [ID 731849 mail.info] stats
1063636498.356 StartSlave slave=0 nslaves=1 nbusy=0 reason="Bringing slaves
up to minSlaves (2)"
Sep 15 17:34:58 mlmsg02 mimedefang-multiplexor: [ID 260045 mail.error] Reap:
Idle slave 0 (pid 6182) exited normally with status 1 (SLAVE DIED
UNEXPECTEDLY)
Sep 15 17:34:58 mlmsg02 mimedefang-multiplexor: [ID 638987 mail.info] Slave
0 resource usage: req=0, scans=0, user=0.000, sys=0.000, nswap=0, majflt=0,
minflt=0, maxrss=0, bi=0, bo=0
Sep 15 17:34:58 mlmsg02 mimedefang-multiplexor: [ID 731849 mail.info] stats
1063636498.358 ReapSlave slave=0 nslaves=0 nbusy=0
Sep 15 17:35:00 mlmsg02 mimedefang-multiplexor: [ID 685023 mail.info]
Received SIGTERM: Killing slaves and terminating

The last line is from me doing ./mimedefang stop, obviously.

Doesn't tell me much except that it keeps trying to restart a slave and it
keeps failing. :(

-- 

 ___________________________
|              
| European Game & Entertainment Technology Ltd Ab
| Kimmo Jaskari, Systems Administrator
| Torggatan 13 A, FIN-22100 Mariehamn, Åland, Finland
| Phone: +358 (0)18 24158, Mobile +358 (0)4575 759 158
|______________________________________________________  




More information about the MIMEDefang mailing list