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 not started after reboot

Discussion in 'E-mail Discussions' started by nicklas, Aug 2, 2010.

  1. nicklas

    nicklas Well-Known Member

    Joined:
    Dec 22, 2005
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    Root Administrator
    Hi,

    I discovered that the mailman is not started after a server reboot, how to fix this?

    Thanks.
     
  2. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    What is your full cPanel version number? Please use the following command to obtain this information:
    Code:
    # cat /usr/local/cpanel/version && echo
    Does your mailman installation have any active lists setup for cPanel accounts? Please use the following command to determine this information:
    Code:
    # find /usr/local/cpanel/3rdparty/mailman/lists -maxdepth 1 -mindepth 1 ! -name "mailman" | wc -l
    The above command will display a count for the number of mailman lists other than the stock-default test list named "mailman"; to see the output without a count, you may use the following command:
    Code:
    # find /usr/local/cpanel/3rdparty/mailman/lists -maxdepth 1 -mindepth 1 ! -name "mailman"
     
  3. nicklas

    nicklas Well-Known Member

    Joined:
    Dec 22, 2005
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    Root Administrator
    11.25.0-RELEASE_46156

    find /usr/local/cpanel/3rdparty/mailman/lists -maxdepth 1 -mindepth 1 ! -name "mailman" | wc -l

    Output is 7

    Because of the privacy for the account i can tell you that it shows the exact amount of lists (7) with path and name for this user account, thank you.

    It works fine when i manual start the mailman, but because i had to reboot once the mailman stopped working and customer contacted me about this.

    Kind regards,
     
  4. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Thank you for the information. What command is being used to start or restart mailman? Are you using "mailmanctl" or a different script?

    Any one of the following commands will stop Mailman:
    Code:
    # /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl -s stop
    # /usr/local/cpanel/etc/init/stopmailman
    # /scripts/restartsrv_mailman --stop
    Conversely, any one of the following commands will start Mailman:
    Code:
    # /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl -s start
    # /usr/local/cpanel/etc/init/startmailman
    # /scripts/restartsrv_mailman
    You may use the following command to check the status of Mailman, before and after stopping or starting:
    Code:
    # /scripts/restartsrv_mailman --status
    Please let us know the output from the following commands, entered one-at-a-time in the order listed:
    Code:
    # stat /etc/mailmandisable
    # /scripts/restartsrv_mailman --status
    # /usr/local/cpanel/etc/init/stopmailman
    # /usr/local/cpanel/etc/init/startmailman
    # /scripts/restartsrv_mailman --status
    # /scripts/restartsrv_mailman --stop
    # /scripts/restartsrv_mailman
    # /scripts/restartsrv_mailman --status
    
    I'm looking to know if there are any errors when Mailman is stopped and started as seen above.
     
  5. nicklas

    nicklas Well-Known Member

    Joined:
    Dec 22, 2005
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    Root Administrator
    Thanks, I use the following commands to check status and start it.

    #ps auxfw |grep mailman
    #/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl start

    Here is the output in the order you wanted it, hope you can find out how to get the mailman keep running on my server even after a reboot :)

    Kind regards,

    Code:
    root@server [~]# stat /etc/mailmandisable
    stat: cannot stat `/etc/mailmandisable': No such file or directory
    root@server [~]# /scripts/restartsrv_mailman --status
    mailmanctl (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl start) running as mailman with PID 21894
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=ArchRunner:0:1 -s) running as mailman with PID 21895
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=BounceRunner:0:1 -s) running as mailman with PID 21896
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=CommandRunner:0:1 -s) running as mailman with PID 21897
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s) running as mailman with PID 21898
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=NewsRunner:0:1 -s) running as mailman with PID 21899
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s) running as mailman with PID 21900
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=VirginRunner:0:1 -s) running as mailman with PID 21901
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=RetryRunner:0:1 -s) running as mailman with PID 21902
    root@server [~]# /usr/local/cpanel/etc/init/stopmailman
    Shutting down Mailman's master qrunner
    mailmanctl: no process killed
    root@server [~]# /usr/local/cpanel/etc/init/startmailman
    Starting Mailman's master qrunner.
    root@server [~]# /scripts/restartsrv_mailman --status
    mailmanctl (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl -s start) running as mailman with PID 7580
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=ArchRunner:0:1 -s) running as mailman with PID 7585
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=BounceRunner:0:1 -s) running as mailman with PID 7586
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=CommandRunner:0:1 -s) running as mailman with PID 7587
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s) running as mailman with PID 7588
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=NewsRunner:0:1 -s) running as mailman with PID 7589
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s) running as mailman with PID 7590
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=VirginRunner:0:1 -s) running as mailman with PID 7591
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=RetryRunner:0:1 -s) running as mailman with PID 7592
    root@server [~]# /scripts/restartsrv_mailman --stop
    root@server [~]# /scripts/restartsrv_mailman
    root@server [~]# /scripts/restartsrv_mailman --status
    mailmanctl (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl --stale-lock-cleanup start) running as mailman with PID 7918
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=ArchRunner:0:1 -s) running as mailman with PID 7921
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=BounceRunner:0:1 -s) running as mailman with PID 7922
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=CommandRunner:0:1 -s) running as mailman with PID 7923
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s) running as mailman with PID 7924
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=NewsRunner:0:1 -s) running as mailman with PID 7925
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s) running as mailman with PID 7926
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=VirginRunner:0:1 -s) running as mailman with PID 7927
    3rdparty/mailman/bin/qrunner (/usr/local/cpanel/3rdparty/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runner=RetryRunner:0:1 -s) running as mailman with PID 7928
    root@server [~]#
     
    #5 nicklas, Aug 3, 2010
    Last edited by a moderator: Aug 3, 2010
  6. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Thank you for the verbose information; that is greatly appreciated. I do not see an immediate indication of any problem based on the provided output.

    If the difficulty is persistently occurring, where mailman is not automatically starting after each time the system is power-cycled, I recommend submitting a support request so that we may assist with more thorough, in-depth investigation that is only possible via direct root SSH access. You may submit a complimentary support request directly to cPanel or you may submit a ticket through your cPanel license provider, which might be your data center, who can ensure your request receives higher priority.
     
Loading...

Share This Page