improper shutdown causes mailman not to start?
Hello,
I rebooted my machine today and mailman wouldn't start.
Feb 27 06:46:56 2008 mailmanctl(692): 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.
Now could the reason be that mailman startup script did not have the -s flag?
mailman_start() { /usr/local/mailman/bin/mailmanctl -q start }
I removed it recently because I was having problem with two instances of mailman at startup. But I then realized I had two different scripts to start mailman so I removed one. I did not however change the main (and now only) startup script in /usr/local/etc/rc.d/ to have the -s flag included.
Many thanks!
-- Zbigniew Szalbot
Zbigniew Szalbot wrote:
I rebooted my machine today and mailman wouldn't start.
Feb 27 06:46:56 2008 mailmanctl(692): 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.
Now could the reason be that mailman startup script did not have the -s flag?
Yes. You generally want that flag in a startup script. After a reboot, it is guaranteed that all locks are stale as all the processes that set them are gone, so you want the -s flag. I suggested removing it as a debugging aid, not as a permanent change.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Zbigniew Szalbot