I run several mailing lists under Mailman 2.1.6. Recently one of my mailing lists received 2 spam messages, I was able to delete one of them using the moderator admindb interface, but when I tried to delete the second message, I got the "hit a bug" page (traceback is listed below).
At that point I: ran check_db and check_perms, restarted the daemon, cleared out the locks. No luck.
I found the heldmsg in data/ and deleted the message manually, which seems to have made matters worse. Now when I access the admindb web page for the mailing list, it throws the error right away before displaying the admindb page (same traceback as before).
I suspect I may have not deleted everything I need to delete. I have considered upgrading to 2.1.7, but thought I should resolve this issue first.
Any advice would be greatly appreciated, thanks,
-Tom
admin(24303): [----- Traceback ------] admin(24303): Traceback (most recent call last): admin(24303): File "/usr/local/mailman-2.1.6//scripts/driver", line 101, in run_main admin(24303): main() admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Cgi/admindb.py", line 2 34, in main admin(24303): num += show_helds_overview(mlist, form) admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Cgi/admindb.py", line 4 85, in show_helds_overview admin(24303): mlist.HandleRequest(id, mm_cfg.DISCARD) admin(24303): File "/usr/local/mailman-2.1.6/Mailman/ListAdmin.py", line 167 , in HandleRequest admin(24303): forward, addr) admin(24303): File "/usr/local/mailman-2.1.6/Mailman/ListAdmin.py", line 353 , in __handlepost admin(24303): syslog('vette', note) admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/Syslog.py", lin e 40, in write admin(24303): self.write_ex(kind, msg, args, kws) admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/Syslog.py", lin e 58, in write_ex admin(24303): logf.write(msg + '\n') admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/StampedLogger.p y", line 73, in write admin(24303): Logger.write(self, "%s %s" % (prefix, msg)) admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/Logger.py", lin e 91, in write admin(24303): f.write(msg) admin(24303): UnicodeError: ASCII encoding error: ordinal not in range(128) admin(24303): [----- Python Information -----] admin(24303): sys.version = 2.2.3 (#1, Mar 9 2006, 18:16:14) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-53)] admin(24303): sys.executable = /usr/bin/python admin(24303): sys.prefix = /usr admin(24303): sys.exec_prefix = /usr admin(24303): sys.path = /usr admin(24303): sys.platform = linux2 admin(24303): [----- Environment Variables -----]
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
ts North wrote:
I run several mailing lists under Mailman 2.1.6. Recently one of my mailing lists received 2 spam messages, I was able to delete one of them using the moderator admindb interface, but when I tried to delete the second message, I got the "hit a bug" page (traceback is listed below).
At that point I: ran check_db and check_perms, restarted the daemon, cleared out the locks. No luck.
Restarting mailman shouldn't have been required. If you 'cleared locks' you may now have multiple instances of the same qrunners running. This needs to be addressed - see <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.068.htp>.
I found the heldmsg in data/ and deleted the message manually, which seems to have made matters worse. Now when I access the admindb web page for the mailing list, it throws the error right away before displaying the admindb page (same traceback as before).
I suspect I may have not deleted everything I need to delete.
That's right. You also need to delete the lists/listname/request.pck that contains the request and points to the now non-existent heldmsg file.
I have considered upgrading to 2.1.7, but thought I should resolve this issue first.
I'm not sure if the underlying issue is fixed in 2.1.7 or not. At this point, I would advise going to 2.1.8 (rc1 should be released this weekend).
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro <msapiro@value.net> wrote:
>> I run several mailing lists under Mailman 2.1.6. Recently one
>> of my mailing lists received 2 spam messages, I was able to
>> delete one of them using the moderator admindb interface, but
>> when I tried to delete the second message, I got the "hit a
>> bug" page (traceback is listed below).
>>
>> At that point I: ran check_db and check_perms, restarted the
>> daemon, cleared out the locks. No luck.
MS> Restarting mailman shouldn't have been required. If you
MS> 'cleared locks' you may now have multiple instances of the
MS> same qrunners running. This needs to be addressed - see
MS> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.068.htp>.
>> I found the heldmsg in data/ and deleted the message manually,
>> which seems to have made matters worse. Now when I access the
>> admindb web page for the mailing list, it throws the error
>> right away
>> before displaying the admindb page (same traceback as before).
>> I suspect I may have not deleted everything I need to delete.
MS> That's right. You also need to delete the
MS> lists/listname/request.pck that contains the request and
MS> points to the now non-existent heldmsg file.Mark,
This did the trick. Thanks!
>> I have considered upgrading to 2.1.7, but thought I should
>> resolve this issue first.
MS> I'm not sure if the underlying issue is fixed in 2.1.7 or
MS> not. At this point, I would advise going to 2.1.8 (rc1 should
MS> be released this weekend).Will monitor if any additional spam cause the unicode error again and, if so, will test under 2.1.8rc1.
Thanks,
-Tom
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.
participants (2)
-
Mark Sapiro -
ts North