When I said "crashed" I was referring to the spamchk script, which, once it gave an error, continued to do so for the next 8 hours.
> The description of the problem was logged by process 74861. Yes, I did note that I saw that. (But it makes no sense to repeat over and over; it's a call to sendmail. I'm trying to understand wy sendmail would suddenly stp accepting mail at 02:38.) >Enhance that script to log its failures & capture the stderr of what it calls >rather than just tossing back to Postfix. yeah... :-( > On Nov 17, 2015, at 16:16, Wietse Venema <wie...@porcupine.org> wrote: > > Vicki Brown: >> Log sections looked like this when it was working: >> >> Nov 17 02:35:37 g3po postfix/qmgr[70628]: 91D742F5FFD8: >> from=<...@googlegroups.com>, size=7252, nrcpt=1 (queue active) > ... >> >> Then it crashed. >> >> /var/log/mail.log shows >> >> Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: private/spamchk socket: >> malformed response >> Nov 17 02:38:29 g3po postfix/qmgr[70628]: warning: transport spamchk failure >> -- see a previous warning/fatal/panic logfile record for the problem >> description >> Nov 17 02:38:29 g3po postfix/master[69788]: warning: process >> /usr/libexec/postfix/pipe pid 74861 exit status 1 > > You're still running the same qmgr daemon process, so it has not crashed. > > However the pipe daemon that you configured for the spamchk service > is terminating with a fatal error (exit status 1). > > The description of the problem was logged by process 74861. > > Some Linux distros unhelpfully log different messages to different > files, so you may have to look in more than one place. > > Wietse >
