Tend to pending moderator requests - Bug in Mailman version 2.1.18-1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Invalid
|
Undecided
|
Mark Sapiro |
Bug Description
I get an error when trying to login to view pending moderator requests.
Error says
Bug in Mailman version 2.1.18-1 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.
The trace is as follows - can you help with a solution?
admin(2117): [----- Mailman Version: 2.1.18-1 -----]
admin(2117): [----- Traceback ------]
admin(2117): Traceback (most recent call last):
admin(2117): File "/usr/local/
admin(2117): main()
admin(2117): File "/usr/local/
admin(2117): num += show_helds_
admin(2117): File "/usr/local/
admin(2117): t.AddRow(
admin(2117): TypeError: %d format: a number is required, not str
admin(2117): [----- Python Information -----]
admin(2117): sys.version = 2.6.6 (r266:84292, Jan 22 2014, 09:42:36)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)]
admin(2117): sys.executable = /usr/local/
admin(2117): sys.prefix = /usr
admin(2117): sys.exec_prefix = /usr
admin(2117): sys.path = ['/usr/
admin(2117): sys.platform = linux2
Thank you.
This is apparently a cPanel bug. I don't think it can occur in standard GNU Mailman. This needs to be reported to, diagnosed and fixed by cPanel.
I think the underlying problem is the /usr/local/ cpanel/ 3rdparty/ mailman/ lists/LISTNAME/ request. pck file is corrupt, but how did it get that way? It could be a cPanel bug, or possibly a hardware, power failure or similar issue.
If you do
/usr/local/ cpanel/ 3rdparty/ mailman/ bin/dumpdb /usr/local/ cpanel/ 3rdparty/ mailman/ lists/LISTNAME/ request. pck
and post the output, I may be able to say what the corruption is. The output should be a dictionary with only one entry
'version': (0, 1)
having a non-numeric key and all other entries having integers as keys and values of the form (type, data) where type is one of 1, 2 or 3 indicating a held message, subscription or unsubscription respectively and data depends on type.