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 Errors and no log files

Discussion in 'E-mail Discussions' started by sparek-3, Aug 26, 2010.

  1. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,381
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    I am starting to see a lot of:

    Bug in Mailman version 2.1.13

    errors from the users on our servers.

    I have tried everything that I know to try.

    I have tried running:

    /usr/local/cpanel/3rdparty/mailman/bin/check_db
    /usr/local/cpanel/3rdparty/mailman/bin/check_perms


    As well as reinstalling mailman with:

    /usr/local/cpanel/bin/mailman-install --force

    And it does nothing.

    I'm not seeing anything in any of the logs at:

    /usr/local/cpanel/3rdparty/mailman/logs

    that would help to point in the right direction. I am at a complete loss.

    This is on 11.25.0-RELEASE_46156
     
  2. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,381
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Looks like the permissions in the cgi-bin were not correct. Not sure why the check_perms script did not correct this.

    chmod 2755 /usr/local/cpanel/3rdparty/mailman/cgi-bin/*
    chmod 0000 /usr/local/cpanel/3rdparty/mailman/cgi-bin/create


    Seemed to correct the issue for me.
     
  3. 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 follow-up. The described permission corrections are valid as you have found; it is also correct that the file named "create" should be chmod 0000 and all other files in the mailman cgi-bin directory should be chmod 2755.

    If the access permissions are an issue in the mailman cgi-bin directory, I recommend the following steps to inspect the status and apply corrections:
    • The following command will simply list the directory contents:
      Code:
      # ls -Ahl /usr/local/cpanel/3rdparty/mailman/cgi-bin
    • The following command using "find" will list files that do not have a permissions value of 2755 and that are not named "create":
      Code:
      # find /usr/local/cpanel/3rdparty/mailman/cgi-bin -type f ! -perm 2755 ! -name create -exec ls -Ahl '{}' \;
    • For applicable files that require permissions of 2755 the following command will apply corrections with verbose output:
      Code:
      # find /usr/local/cpanel/3rdparty/mailman/cgi-bin -type f ! -perm 2755 ! -name create -exec chmod -vv 2755 '{}' \;
     
  4. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hi there Don. I experienced the same issue but the solutions proposed in this thread didn't make it work. What logs can I check to trace the source of this error? what other possible upgrade problems may be involved? This issue originated when the last Stable version was applied.
     
  5. Kent Brockman

    Kent Brockman Well-Known Member

    Joined:
    Jan 20, 2008
    Messages:
    1,130
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Buenos Aires, Argentina
    cPanel Access Level:
    Root Administrator
    Twitter:
    I reinstalled mailman with --force twice. The second time I reinstalled it magically started to work..... Why may this have happened?
     
  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:
    I'm not certain what would trigger that scenario; it is difficult to know without being able to investigate the issue and monitor the command-line output during the installation process.
     
Loading...

Share This Page