1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

'Bug in Mailman version 2.1.12'

Discussion in 'Plesk 10.x for Linux Issues, Fixes, How-To' started by davorg, Jan 24, 2012.

  1. davorg

    davorg Basic Pleskian

    24
     
    Joined:
    Aug 7, 2005
    Messages:
    33
    Likes Received:
    0
    I'm working on setting up a server running Plesk 10.4.4 Update #13 on Centos 6.2.

    I've configured Mailman and now I want to set up some mailing lists. I've created a list in the Plesk control panel, but when I try to administer the new list (by visiting http://lists.[domain].com/mailman/admin/[listname] I see the following error:

    Bug in Mailman version 2.1.12

    We're sorry, we hit a bug!

    Please inform the webmaster for this site of this problem. Printing of traceback and other system information has
    been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.

    I see exactly the same error if I try to go to the list info page at http://lists.[domain].com/mailman/listinfo/[listname].

    I would follow the instructions and look in the error logs, but I can't find them. I would expect to find a file at /var/log/mailman/error, but there's nothing there.

    Has anyone else seen this? Any suggestions for tracking down and fixing the problem?

    Cheers,

    Dave...

    p.s. Just one other piece of information - my test list seems to work correctly. It sends all the expected email. It's just the web pages for the list that seem to be broken.

    Update: I got to the bottom of this, so I'm documenting the answer in case anyone else has the same problem.

    The fact that I couldn't find the error log was the clue. The problem was that the Mailman process didn't have permissions to create an error log. And it seems that if Mailman can't create an error log then it will respond to any web request with this error page. Creating an error log file (in /var/log/mailman/error) and giving it the correct permissions fixed the problem.
     
    Last edited: Feb 19, 2012
  2. RubénV

    RubénV New Pleskian

    12
    55%
    Joined:
    Feb 21, 2012
    Messages:
    1
    Likes Received:
    0
    Re: Bug in Mailman version 2.1.12

    It Works!!!!!

    Thank you
     
  3. PrasenjeetP

    PrasenjeetP New Pleskian

    10
     
    Joined:
    Jul 13, 2012
    Messages:
    3
    Likes Received:
    0
    This worked

    I created the file and things worked fine, with a chmod 777 to the file.
     
  4. FloydH

    FloydH New Pleskian

    10
     
    Joined:
    Jul 17, 2012
    Messages:
    3
    Likes Received:
    0
    I created the directories /var/log/mailman/error because all I had was /var/log
    The file I created in the /error directory is error.log and I chmod 777
    I still get the same error.
    Do I need to chmod the directories? Is the filename error.log the right file name?
    Any help will be appreciated. I host at 1and1 and they offer zero support and I am not the brightest bulb.
    Thanks in advance.
    Floyd
     
  5. PrasenjeetP

    PrasenjeetP New Pleskian

    10
     
    Joined:
    Jul 13, 2012
    Messages:
    3
    Likes Received:
    0
    Here are the steps that I did and it worked .. hope they help your case. Please post back what you find.


    1) mkdir /var/log/mailman
    2) touch /var/log/mailman/error
    3) chmod 777 /var/log/mailman/error
     
  6. FloydH

    FloydH New Pleskian

    10
     
    Joined:
    Jul 17, 2012
    Messages:
    3
    Likes Received:
    0
    Thanks, works perfect!

    You guys are great!
     
  7. dorkus

    dorkus New Pleskian

    10
     
    Joined:
    Aug 9, 2012
    Messages:
    4
    Likes Received:
    0
    have the same problem with 2.14

    tried adding a error log but still get the error. i use plesk 10.4.4. on a suse 11.4 system....

    any help apprechiated as there are no log files anywhere....
     
  8. Aldricd

    Aldricd New Pleskian

    13
    85%
    Joined:
    Dec 4, 2011
    Messages:
    10
    Likes Received:
    0
    davorg answer worked for me.
    Thanks a lot.
     
Loading...