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 updating hostname

Discussion in 'E-mail Discussions' started by Asif Nawaz, Aug 12, 2012.

  1. Asif Nawaz

    Asif Nawaz Member

    Joined:
    Jul 30, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    London, United Kingdom, United Kingdom
    cPanel Access Level:
    Root Administrator
    So I just updated the hostname to a FQDN (should have done it before, but realised it wasn't set when I got some HELO errors when sending emails).

    This might be of use to someone!

    The hostname changed successfully, I could also see it in /etc/hosts, but after the change, cPanel thrrew up the following:

    Code:
    Updating Apache configuration
    Updating cPanel license...Done. Update succeeded. Building global cache for cpanel...Done
    Traceback (most recent call last):
    File "/usr/local/cpanel/bin/reset_mailman_hostname", line 44, in ?
    raise SystemExit(main(sys.argv))
    File "/usr/local/cpanel/bin/reset_mailman_hostname", line 31, in main
    file=open('/usr/local/cpanel/3rdparty/mailman/lists/' + list + '/config.pck','r')
    IOError: [Errno 2] No such file or directory: '/usr/local/cpanel/3rdparty/mailman/lists/mailman/config.pck'
    I attempted to reboot mailman, but it failed with the following:

    Code:
    mailman has failed, please contact the sysadmin (result was "mailmanctl is not running").
    Then I looked around and the forum and tried to start it via the
    Code:
    /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl start
    command.

    It said mailman wasn't running so obviously couldn't be restarted (in retrospect this wasn't the smartest move).

    I then checked if mailman was enabled under WHM > Tweam settings, and it was.

    So then I attempted to do a forced reinstall of mailman with the following:

    Code:
    /usr/local/cpanel/scripts/reinstallmailman --force
    This command is deprecated, so the system gave me a new one.

    That command took a few minutes to run and displayed a whole bunch of things with (fixing) at the end. Once it was run, it said:

    Code:
    Problems found: 85
    Re-run as mailman (or root) with -f flag to fix
    Non-standard property restored: personalize
    
    Interestingly enough, though, I attempted to restart mailman and it seemed to restart without any problems.

    I've seen this issue on this ticket here: http://forums.cpanel.net/f34/cpanel-chkservd-service-monitor-212612.html

    So, the question is, before I open a ticket, how do I make sure mailman is working exactly the way it should? Any diagnostics I can run?

    Thanks!
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    675
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    The following command may be useful:

    Code:
    # /scripts/fixmailman
    However, if you continue to experience the same problem, feel free to submit a ticket as suggested in the other thread.

    Thank you.
     
  3. Asif Nawaz

    Asif Nawaz Member

    Joined:
    Jul 30, 2012
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    London, United Kingdom, United Kingdom
    cPanel Access Level:
    Root Administrator
    No problems found, apparently :).

    Thank you.
     
Loading...

Share This Page