[Mailman-Users] Interesting "Bug in Mailman version 2.1.12"

Mark Sapiro mark at msapiro.net
Wed Nov 11 15:33:57 CET 2009

Tomasz Chmielewski wrote:

>Mark Sapiro wrote:
>> Tomasz Chmielewski wrote:
>>> It exited with "Bug in Mailman version 2.1.12".
>>> Webserver nor Mailman logs didn't give me a clue.
>> Mailman's 'error' log should have a a complete traceback and other
>> information about the error.
>Here is a sample log - it doesn't give me any clue about the nature of the problem, though:
>Nov 09 11:09:55 2009 admin(7664): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
>admin(7664): [----- Mailman Version: 2.1.12 -----]                             
>admin(7664): [----- Traceback ------]                                          
>admin(7664): Traceback (most recent call last):                                
>admin(7664):   File "/srv/www/vhosts/wpkg.org/mailman//scripts/driver", line 112, in run_main
>admin(7664):     main()                                                                      
>admin(7664):   File "/srv/www/vhosts/wpkg.org/mailman/Mailman/Cgi/listinfo.py", line 42, in main
>admin(7664):     listinfo_overview()                                                            
>admin(7664):   File "/srv/www/vhosts/wpkg.org/mailman/Mailman/Cgi/listinfo.py", line 88, in listinfo_overview
>admin(7664):     if mlist.advertised:                                                                        
>admin(7664):   File "/srv/www/vhosts/wpkg.org/mailman//Mailman/MailList.py", line 146, in __getattr__        
>admin(7664):     raise AttributeError, name                                                                  
>admin(7664): AttributeError: advertised                                                                      

It says that the listinfo CGI was building the overview page, and was
going through the lists, instantiating each one to check it's domain
and advertised attribute to see if it should be listed.

In this process it encountered one list whose preserved state as loaded
from lists/LISTNAME/config.pck had no 'advertised' attribute.

I don't know why this occurred, or why 'touch'ing the config.pck would
have any effect on this. If the problem were still occurring, there
are ways to find out which is the problem list, but since it no longer
occurs, I think there's nothing further that can be done.

Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

More information about the Mailman-Users mailing list