SOLVED mailman failed; won't restart

jndawson

Well-Known Member
Aug 27, 2014
303
32
78
Western US
cPanel Access Level
DataCenter Provider
Running v.64.0.15.

Got an alert that mailman failed. Logged into whm > restart services and got this result, several times:
Code:
Waiting for “mailman” to start …………failed.

Cpanel::Exception::Services::StartError Service Error
(XID r4bdu9) The “mailman” service failed to start.

Startup Log
Traceback (most recent call last):
File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 556, in <module>
main()
File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 391, in main
lock = acquire_lock(force)
File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 215, in acquire_lock
lock = acquire_lock_1(force)
File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 203, in acquire_lock_1
if not force or qrunner_state():
File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 187, in qrunner_state
os.kill(pid, 0)
OSError: [Errno 1] Operation not permitted

mailman has failed. Contact your system administrator if the service does not automagically recover.
/usr/local/cpanel/scripts/fixmailman had no effect. Logs just show restart attempts; prior to 07:56, mailman appears normal:
Code:
Apr 24 07:56:18 2017 mailmanctl(3016): 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.
Apr 24 07:56:18 2017 mailmanctl(3016):
Apr 24 07:58:47 2017 mailmanctl(4499): No child with pid: 5813
Apr 24 07:58:47 2017 mailmanctl(4499): [Errno 3] No such process
Apr 24 07:58:47 2017 mailmanctl(4499): Stale pid file removed.
Apr 24 08:26:41 2017 mailmanctl(7830): Traceback (most recent call last):
Apr 24 08:26:41 2017 mailmanctl(7830):   File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 556, in <module>
Apr 24 08:26:41 2017 mailmanctl(7830):      main()
Apr 24 08:26:41 2017 mailmanctl(7830):   File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 391, in main
Apr 24 08:26:41 2017 mailmanctl(7830):      lock = acquire_lock(force)
Apr 24 08:26:41 2017 mailmanctl(7830):   File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 215, in acquire_lock
Apr 24 08:26:41 2017 mailmanctl(7830):      lock = acquire_lock_1(force)
Apr 24 08:26:41 2017 mailmanctl(7830):   File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 203, in acquire_lock_1
Apr 24 08:26:41 2017 mailmanctl(7830):      if not force or qrunner_state():
Apr 24 08:26:41 2017 mailmanctl(7830):   File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 187, in qrunner_state
Apr 24 08:26:41 2017 mailmanctl(7830):      os.kill(pid, 0)
Apr 24 08:26:41 2017 mailmanctl(7830): OSError :  [Errno 1] Operation not permitted
Tried cli using -s:

Code:
[ [email protected] ~># /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl -s start
Traceback (most recent call last):
  File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 556, in <module>
    main()
  File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 391, in main
    lock = acquire_lock(force)
  File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 215, in acquire_lock
    lock = acquire_lock_1(force)
  File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 203, in acquire_lock_1
    if not force or qrunner_state():
  File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 187, in qrunner_state
    os.kill(pid, 0)
OSError: [Errno 1] Operation not permitted
What are we missing?
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,909
2,228
463
Hello,

You can try moving the existing Mailman lock files out of the way and then restarting Mailman to see if the issue persists. EX:

Code:
# mkdir /root/mailman-locks
# mv /usr/local/cpanel/3rdparty/mailman/locks/* /root/mailman-locks/
# /scripts/restartsrv_mailman
Thank you.
 
  • Like
Reactions: EneTar
Thread starter Similar threads Forum Replies Date
S Email 1
M Email 1
T Email 1
R Email 2
G Email 8