Allan Trick wrote:
>
>There's nothing in the error log. But qrunner's might have a
>clue. I'm not sure how to read this:
>
>Jan 31 11:38:51 2007 (1541) Master qrunner detected subprocess exit
>(pid: 29673, sig: None, sts: 1, class: OutgoingRunner, slice: 1/1) [restarting]
This says OutgoingRun
At 11:15 AM 2/2/2007, Mark Sapiro wrote:
>Look at Mailman's error and qrunner logs from the time that the
>lists stopped for clues as to why the other seven qrunners died (or
>why they all died and only RetryRunner was restarted).
There's nothing in the error log. But qrunner's might have a
c
Allan Trick wrote:
>
>So I'm back in business. Any follow-up thoughts on why this happened?
Look at Mailman's error and qrunner logs from the time that the lists
stopped for clues as to why the other seven qrunners died (or why they
all died and only RetryRunner was restarted).
--
Mark Sapiro
Our Mailman 2.1.5 system (on a Red Hat Linux server w/sendmail)
hasn't been working all week. I just discovered it, and the first
thing I did was ./mailmanctl restart ---
It appears to have done what I told it:
Feb 02 09:43:31 2007 (1541) Master watcher caught SIGINT. Restarting.
Feb 02 09:43
I think I solved my own problem. Instead of just restarting qrunner,
I did a stop and then a start. That did it.
The clue was when I ran
ps auxww | egrep 'p[y]thon'
as FAQ 3.14 suggests, instead of there being eight processes there,
there were only two.
So I'm back in business. Any foll
