[Bug 610454] [NEW] Bug in Mailman version 2.1.7
Public bug reported: i have install Zimbra open source 6.0.7 and integrate mailman version 2.1.7, after complete installation of mailman when i acess my link i get this error, Bug in Mailman version 2.1.7 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. ** Affects: mailman Importance: Undecided Status: New -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Without the traceback from Mailman's error log, there's no way we can begin to diagnose or fix this. Please find the full error report including traceback in Mailman's error log and attach it to this report. -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Dear Mark, Error Log is [root@mailserver cron]# tail -200000 /var/log/mailman/error Jul 28 12:14:14 2010 mailmanctl(3446): Site list is missing: mailman Jul 28 12:14:14 2010 (3446) Site list is missing: mailman [root@mailserver cron]# tail -20000000 /var/log/mailman/error Jul 28 12:14:14 2010 mailmanctl(3446): Site list is missing: mailman Jul 28 12:14:14 2010 (3446) Site list is missing: mailman [root@mailserver cron]# /etc/init.d/mailman restart PID unreadable in: /usr/local/mailman/data/master-qrunner.pid [Errno 2] No such file or directory: '/usr/local/mailman/data/master-qrunner.pid' Is qrunner even running? [root@mailserver cron]# tail -f /var/log/mailman/error Jul 28 12:14:14 2010 mailmanctl(3446): Site list is missing: mailman Jul 28 12:14:14 2010 (3446) Site list is missing: mailman On Tue, Jul 27, 2010 at 7:52 PM, Mark Sapiro <mark@msapiro.net> wrote:
Without the traceback from Mailman's error log, there's no way we can begin to diagnose or fix this. Please find the full error report including traceback in Mailman's error log and attach it to this report.
-- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a direct subscriber of the bug.
Status in GNU Mailman: New
Bug description: i have install Zimbra open source 6.0.7 and integrate mailman version 2.1.7, after complete installation of mailman when i acess my link i get this error,
Bug in Mailman version 2.1.7
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.
To unsubscribe from this bug, go to: https://bugs.launchpad.net/mailman/+bug/610454/+subscribe
-- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Dear Mark, i check the log and restart mailman service i got this error. [root@mailserver cron]# tail -200000 /var/log/mailman/error Jul 28 12:14:14 2010 mailmanctl(3446): Site list is missing: mailman Jul 28 12:14:14 2010 (3446) Site list is missing: mailman [root@mailserver cron]# tail -20000000 /var/log/mailman/error Jul 28 12:14:14 2010 mailmanctl(3446): Site list is missing: mailman Jul 28 12:14:14 2010 (3446) Site list is missing: mailman [root@mailserver cron]# /etc/init.d/mailman restart PID unreadable in: /usr/local/mailman/data/master-qrunner.pid [Errno 2] No such file or directory: '/usr/local/mailman/data/master-qrunner.pid' Is qrunner even running? [root@mailserver cron]# tail -f /v ar/log/mailman/error Jul 28 12:14:14 2010 mailmanctl(3446): Site list is missing: mailman Jul 28 12:14:14 2010 (3446) Site list is missing: mailman Even i remove 2.1.7 and reinstall with 2.1.6 still same error. MTA is postfix -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
You can't run Mailman until you create the site list named 'mailman'. You can create this list with Mailman's bin/newlist (give the --help option for information), and then you will be able to start Mailman. None of this has anything to do with the "we hit a bug" error. Perhaps the log containing that error has rotated to /var/log/mailman/error.1 or /var/log/mailman/error.2 or ... or perhaps you have more that one Mailman installation and the one accessed by the web interface logs somewhere else. -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Dear Mark Sapiro, thanks for your kind response, mailman was created. i already create that on this path. [root@mailserver bin]# pwd /usr/local/mailman/bin ./newlist mailman and also fellow these command. bin/config_list -i data/sitelist.cfg mailman bin/newlist --emailhost=virtual-domain1.com --urlhost=<your zimbra host> <listname> <admin-email-address> <admin-password> # This is just to make sure that aliases and virtual-mailman files get generated. Until you add a virtual-domain based list, virtual-mailman won't be generated. /usr/local/mailman/bin/genaliases # aliases and virtual-mailman must be owned by mailman. chown mailman:mailman /usr/local/mailman/data/aliases* chown mailman:mailman /usr/local/mailman/data/virtual-mailman* -------------------------------------------------------- second time i have only one log in my var directory, that is error log -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Do you have a problem or not? Can you visit Mailman's web interface without the "We hit a bug" response? If you cannot, and you don't have any message in Mailman's error log, either the log is not where you think it is or there are permissions issues in writing it. Try running Mailman's bin/check_perms. -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Dear Mark sapiro, i already fixed all permissions and also change permissions, still no effect. second this mailman web page is not accessable. i simply check it. On Fri, Jul 30, 2010 at 6:28 AM, Mark Sapiro <mark@msapiro.net> wrote:
Do you have a problem or not?
Can you visit Mailman's web interface without the "We hit a bug" response?
If you cannot, and you don't have any message in Mailman's error log, either the log is not where you think it is or there are permissions issues in writing it.
Try running Mailman's bin/check_perms.
-- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a direct subscriber of the bug.
Status in GNU Mailman: New
Bug description: i have install Zimbra open source 6.0.7 and integrate mailman version 2.1.7, after complete installation of mailman when i acess my link i get this error,
Bug in Mailman version 2.1.7
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.
To unsubscribe from this bug, go to: https://bugs.launchpad.net/mailman/+bug/610454/+subscribe
-- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
I have marked this report invalid because Mailman 2.1.7 is out of date (current is 2.1.13 and 2.1.14 will be released soon), and because I think your Mailman installation is not done correctly and I am unable to get information from you to determine what might be wrong. In any case, I don't think there is an actual Mailman bug, but if you can provide more information to determine what is actually happening, I will be happy to investigate further. For example, what steps are you following to install Mailman (note that Zimbra would have nothing to do with "we hit a bug" in the web interface)? Why are you installing such an old version? ** Changed in: mailman Status: New => Invalid -- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
Dear Mark Sapiro, thanks for your kindly support, i will check it myself and get any positive result then i will share with you all. again thanks,,,,,,, On Fri, Jul 30, 2010 at 7:39 PM, Mark Sapiro <mark@msapiro.net> wrote:
I have marked this report invalid because Mailman 2.1.7 is out of date (current is 2.1.13 and 2.1.14 will be released soon), and because I think your Mailman installation is not done correctly and I am unable to get information from you to determine what might be wrong.
In any case, I don't think there is an actual Mailman bug, but if you can provide more information to determine what is actually happening, I will be happy to investigate further. For example, what steps are you following to install Mailman (note that Zimbra would have nothing to do with "we hit a bug" in the web interface)? Why are you installing such an old version?
** Changed in: mailman Status: New => Invalid
-- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a direct subscriber of the bug.
Status in GNU Mailman: Invalid
Bug description: i have install Zimbra open source 6.0.7 and integrate mailman version 2.1.7, after complete installation of mailman when i acess my link i get this error,
Bug in Mailman version 2.1.7
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.
To unsubscribe from this bug, go to: https://bugs.launchpad.net/mailman/+bug/610454/+subscribe
-- Bug in Mailman version 2.1.7 https://bugs.launchpad.net/bugs/610454 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.
participants (2)
-
Mark Sapiro -
Rashid Rasheed