The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Mailman error after mdbox upgrade

Discussion in 'E-mail Discussions' started by WebHostPro, Jul 3, 2017.

Tags:
  1. WebHostPro

    WebHostPro Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,612
    Likes Received:
    11
    Trophy Points:
    318
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    Twitter:
    I upgraded my server to mdbox and now mailman is failing over and over.

    The error is:90
    Code:
    Waiting for “mailman” to start ……Job for mailman.service failed because a configured resource limit was exceeded. See "systemctl status mailman.service" and "journalctl -xe" for details. …Waiting for mailman,qrunner to shutdown ... not running. Job for mailman.service failed because a configured resource limit was exceeded. See "systemctl status mailman.service" and "journalctl -xe" for details. …failed.
    
    Cpanel::Exception::Services::StartError Service Error
    (XID 453urg) The “mailman” service failed to start.
    
    Startup Log
    Jul 03 16:26:24 dwhslvxx.example.net restartsrv_mailman[28357]: process on some other host may have acquired it. We can't test for stale
    Jul 03 16:26:24 dwhslvxx.example.net restartsrv_mailman[28357]: locks across host boundaries, so you'll have to do this manually. Or, if you
    Jul 03 16:26:24 dwhslvxx.example.net restartsrv_mailman[28357]: know the lock is stale, re-run mailmanctl with the -s flag.
    Jul 03 16:26:24 dwhslvxx.example.net restartsrv_mailman[28357]: Lock file: /usr/local/cpanel/3rdparty/mailman/locks/master-qrunner
    Jul 03 16:26:24 dwhslvxx.example.net restartsrv_mailman[28357]: Lock host: lvxx.example.pro
    Jul 03 16:26:24 dwhslvxx.example.net restartsrv_mailman[28357]: Exiting.
    Jul 03 16:26:24 dwhslvxx.example.net systemd[1]: PID file /usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid not readable (yet?) after start.
    Jul 03 16:26:24 dwhslvxx.example.net systemd[1]: Failed to start mailman services.
    Jul 03 16:26:24 dwhslvxx.example.net systemd[1]: Unit mailman.service entered failed state.
    Jul 03 16:26:24 dwhslvxx.example.net systemd[1]: mailman.service failed.
    
    mailman has failed. Contact your system administrator if the service does not automagically recover.
    
     
    #1 WebHostPro, Jul 3, 2017
    Last edited by a moderator: Jul 3, 2017
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    37,204
    Likes Received:
    1,297
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    This is typically fixed by removing any stale lock files from the "/usr/local/cpanel/3rdparty/mailman/locks/" directory and then restarting Mailman. EX:

    Code:
    mv /usr/local/cpanel/3rdparty/mailman/locks/master-qrunner /usr/local/cpanel/3rdparty/mailman/locks/master-qrunner.BACKUP1
    /scripts/restartsrv_mailman
    However, I'd see to make sure there's no defect with the mailbox conversion process. Could you verify the specific steps you took when converting mailboxes to mdbox?

    Thank you.
     
Loading...

Share This Page