I've never seen this before, but I have seen in the code that some of
the daemons are set to stop themselves if it's taking too long to run a
process. I suggest that you look at the virtual server and see if you
are getting enough cycles while Mailman is running.
The daemon that is most sensitive
Someone asked about the content of the qrunner log and another some other
questions about processes and such, as well as the status of the archives.
The archives are a bit behind. The last seven messages to the list have
yet to appear in the archive pages. In fact, I notice a huge time lag
betwe
What are your system resources while running Mailmanctl? How much
memory do you have in use? How much swap are you using? How much drive
space do you have on each volume?
And for an off-beat question: Are your archives updating properly?
On Sun, 2003-02-02 at 12:26, VLists.Net Support wrote:
>
We've had several instances lately where Mailman 2.1 just dies silently and
no more mail goes out. I've resorted to putting a cron job in that
restarts mailmanctl but when that happens I get the following returned...
Shutting down Mailman's master qrunner
PID unreadable in: /usr/home/circle/usr/l
