> Am 18.10.2016 um 22:50 schrieb mailman-admin <mailman-ad...@uni-konstanz.de>:
> Am 18.10.2016 um 10:57 schrieb Matthias Schmidt via Mailman-Users:
>> Hello,
>> I’m trying to start mailman on startup with ElCapitan.
>> I tried a plist in LaunchDaemons - that was working in the past with the 
>> command:
>> /usr/local/mailman/bin/mailmanctl -s start
>> this produces now the error:
>> Service only ran for 2 seconds. Pushing respawn out by 8 seconds
>> the error log says:
>> The master qrunner lock could not be acquired because it appears as if 
>> another
>> master qrunner is already running
>> So it starts, creates a lock as localhost … and then it tries to start again.
>> than I created a startup script as described here:
>> https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html#//apple_ref/doc/uid/10000172i-SW9-CJBBHDII
>> and it does … nothing
>> the only thing which works currently is starting it manually with sudo
>> and this is kind of inconvenient
>> I installed mailman manually without using macports or something like that.
>> I hope someone on the list can share some insight here.
> Do you shutdown mailman cleanly?

mailman was not running before startup and for the test I made sure that there 
are no pid files present

> If not, you leave a pid file behind, which will prevent mailman from
> starting.

the -s option should fix that problem ;-)
but if mailman is started as local then -s doesn’t remove a stray pid file.


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Mailman-Users mailing list Mailman-Users@python.org
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Reply via email to