[Mailman-Users] Mailmanctl not starting : OSError: [Errno 1]Operation not permitted

Mark Sapiro msapiro at value.net
Thu Apr 7 04:43:19 CEST 2005


Charles de Noyelle wrote:

>Big Problem with mailman : mailmanctl refuses to start.
>
>Mailman used to work fine, and I changed a few times from
>disks and motherboards, and had quite some problems taking
>it back, but managed to have it yesterday.
>
>Since I rebooted, mailmanctl does not start anymore :/
>
>here is the error :
>
>---- (as root) /path/to/mailman/bin/mailmanctl start ----
>Traceback (most recent call last):
>   File "./bin/mailmanctl", line 547, in ?
>     main()
>   File "./bin/mailmanctl", line 389, in main
>     lock = acquire_lock(force)
>   File "./bin/mailmanctl", line 216, in acquire_lock
>     status = qrunner_state()
>   File "./bin/mailmanctl", line 186, in qrunner_state
>     os.kill(pid, 0)
>OSError: [Errno 1] Operation not permitted
>------------------------------------------------------
>I cannot understand *what* precisely is not permitted :/
>and of course, ./bin/check_perms is OK ...
>
>I used mailman 2.1.6 beta and downgraded to 2.1.5 to be sure, and the 
>problem persists.
>
>I am running an AMD 64, it might have a role on the bug :-)
>
>I donno what to add to help people willing to help, so please
>ask for more details !

Mailmanctl has found an existing lock file, extracted a pid from it and
is trying to signal that pid to see if it is still running. The signal
attempt is being denied by the OS.

If you're sure no mailmanctl is running, you can just manually remove
the locks/master-qrunner* files (you could first check the pid with ps
to be sure) as a workaround.

--
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan




More information about the Mailman-Users mailing list