I don't know how to properly set up my system so that mailman restarts after a crash. I've just experienced one a few minutes ago, and here's the situation
# /etc/init.d/mailman start Starting list server: mailman. The master qrunner lock could not be acquired. It appears as though there is a stale master qrunner lock. Try re-running mailmanctl with the -s flag.
# /home/mailman/bin/mailmanctl -s start Starting Mailman's master qrunner. Traceback (most recent call last): File "/home/mailman/bin/mailmanctl", line 492, in ? main() File "/home/mailman/bin/mailmanctl", line 364, in main lock._transfer_to(pid) File "/home/mailman/Mailman/LockFile.py", line 357, in _transfer_to os.link(self.__lockfile, self.__tmpfname) OSError: [Errno 2] No such file or directory
# ps aux | grep mailman mailman 924 0.0 0.3 4440 2968 pts/1 S 11:22 0:00 /usr/local/bin/python2.1 /home/mailman/bin/mailmanctl -s start
So the process has failed but is still running?
By the way, I've set things up so that :
in mm_cfg.py: PIDFILE = '/var/run/mailman/mailman.pid'
/var/run/mailman/ is emptied as startup (I've checked, it's empty now, and permissions seem to be correct: drwxr-xr-x 2 mailman mailman 4096 jan 9 11:15 /var/run/mailman/
I've got a /etc/init.d/mailman script that just does not much more than call /home/mailman/bin/mailmanctl start
(Using the most recent CVS version, I prefer to post this to the -dev list)
-- Fil