[Mailman-Users] Mailman vs OSX vs launchd

[Larry Stone]

On 6/26/09 6:22 AM, Matthias Schmidt at beta at admilon.net wrote:

> Am/On Thu, 18 Jun 2009 19:22:02 -0500 schrieb/wrote Larry Stone:
> 
>> On 6/18/09 7:11 PM, Bryan Harrison at bryan at bryanharrison.com wrote:
>> 
>>> I've built and installed Mailman 2.12 from current source code and
>>> have it running just fine under OS X Server 10.5.7, with on exception,
>>> which is not properly speaking a Mailman problem at all.
>>> 
>>> If I start Mailman from the CLI, using /usr/share/mailman/bin/
>>> mailmanctl -s start, all is well.
>>> 
>>> If I allow launchd to start it
>>> S<caron>I get an endless succession ofS<caron>
>>> 
>>> Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master
>>> qrunner.
>>> Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]):
>>> Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python
>>> Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling
>>> respawn: Will start in 9 seconds
>> 
>> Known issue, no idea why. I've been running Mailman on Client OS X since the
>> Tiger days. As soon as I upgraded to Leopard, I started seeing this happen
>> intermittently. I have a launchd plist almost identical to yours.
>> 
>> It is intermittent for me. Probably happens about 1 in 3 boots. I try to
>> remember to check that it's running after reboots. If not, I have a cron job
>> that runs hourly to check for the proper number of qrunners and send me
>> e-mail if any or all are missing.
> 
> I have the same issue as Bryan (and my plist looks simular) and find
> this in my logs, when I start mailman via launchd, if I start it by CLI,
> I don't see this issue:
> 
> Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: The master qrunner
> lock could not be acquired because it appears as if another
> Jun 26 20:16:29 myMac org.list.mailmanctl[40673]: master qrunner is
> already running.
> Jun 26 20:16:29 myMac com.apple.launchd[1] (org.list.mailmanctl):
> Throttling respawn: Will start in 9 seconds
> Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: The master qrunner
> lock could not be acquired because it appears as if another
> Jun 26 20:16:41 myMac org.list.mailmanctl[40675]: master qrunner is
> already running.
> Jun 26 20:16:41 myMac com.apple.launchd[1] (org.list.mailmanctl):
> Throttling respawn: Will start in 8 seconds
> Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: The master qrunner
> lock could not be acquired because it appears as if another
> Jun 26 20:16:52 myMac org.list.mailmanctl[40680]: master qrunner is
> already running.
> Jun 26 20:16:52 myMac com.apple.launchd[1] (org.list.mailmanctl):
> Throttling respawn: Will start in 8 seconds
> Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: The master qrunner
> lock could not be acquired because it appears as if another
> Jun 26 20:17:02 myMac org.list.mailmanctl[40757]: master qrunner is
> already running.
> Jun 26 20:17:03 myMac com.apple.launchd[1] (org.list.mailmanctl):
> Throttling respawn: Will start in 8 seconds
> Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: The master qrunner
> lock could not be acquired because it appears as if another
> Jun 26 20:17:13 myMac org.list.mailmanctl[40760]: master qrunner is
> already running.
> Jun 26 20:17:13 myMac com.apple.launchd[1] (org.list.mailmanctl):
> Throttling respawn: Will start in 8 seconds

This is not the same issue as Bryan and I have. The log entries you have
posted indicate that you are trying to start Mailman twice (the issue Bryan
and I have is Mailman dying with the "stray process" message). Perhaps you
have two different launchd scripts that try to to start Mailman. Launchd
looks in both /System/Library/LaunchDaemons and /Library/LaunchDaemons. The
former is supposed to be for Apple provided scripts with the latter for
user/3rd party application scripts. My "mailman.plist" is in
/Library/LaunchDaemons but you should check both and grep for mailmanctl.

-- 
Larry Stone
lstone19 at stonejongleux.com
http://www.stonejongleux.com/