On Sat November 4 2006 02:29, Marc Haber wrote: > On Fri, Nov 03, 2006 at 01:06:01PM -0700, Bruce Sass wrote: > > ...would seem to indicate that it is a transitory situation caused > > by the upgrade process. > > Probably. Did killing the existing daemon manually help with starting > the new daemon?
I did not need to restart exim4. I saw the message in the INBOX associated with /var/mail/spool, then ran the ps|grep command you saw the output of. The mainlog just prior to the paniclog entry I included shows periodic Start and End queue run messages, 10 socket bind() failures at 30s intervals, then more Start/End queue runs. > > The result is daily... > > > > -e Subject: exim paniclog on onegee has non-zero size > > To: root > > > > exim paniclog /var/log/exim4/paniclog on onegee has non-zero size, > > mail system might be broken > > > > ...messages when there is no problem. > > Yes, you'll need to rotate the paniclog away manually. See > /usr/share/doc/exim4-base/README.Debian.gz chapter 2.5.1 > > If the message is continuously being written again and again over and > over, you have probably still an old daemon running. I understand that, but it doesn't seem right to have to do it after an upgrade if all is well... hence the report. Unfortunately I can not reliably reproduce this bug. Nine attempts at: #apt-get --reinstall install exim4-daemon-light got me two failures initially then seven successes. I have another box running the light daemon and one running the heavy daemon, neither of them have had a panic. :-/ - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]