Hey, I found some more info on my problem, but haven't cracked the case yet:
in ~mailman/logs/error, since Aug 31 qrunner has been choking as follows: Aug 31 16:18:01 2004 qrunner(11238): Traceback (most recent call last): Aug 31 16:18:01 2004 qrunner(11238): File "/usr/lib/mailman/cron/qrunner", line 283, in ? Aug 31 16:18:01 2004 qrunner(11238): kids = main(lock) Aug 31 16:18:01 2004 qrunner(11238): File "/usr/lib/mailman/cron/qrunner", line 253, in main Aug 31 16:18:01 2004 qrunner(11238): keepqueued = dispose_message(mlist, msg, msgdata) Aug 31 16:18:01 2004 qrunner(11238): File "/usr/lib/mailman/cron/qrunner", line 157, in dispose_message Aug 31 16:18:01 2004 qrunner(11238): mlist.ParseMailCommands(msg) Aug 31 16:18:01 2004 qrunner(11238): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 163, in ParseMailCommands Aug 31 16:18:01 2004 qrunner(11238): splitsubj = string.split(subject) Aug 31 16:18:01 2004 qrunner(11238): File "/usr/lib/python2.2/string.py", line 117, in split Aug 31 16:18:01 2004 qrunner(11238): return s.split(sep, maxsplit) Aug 31 16:18:01 2004 qrunner(11238): AttributeError : 'NoneType' object has no attribute 'split' Any help is greatly appreciated. Thanks > -----Original Message----- > From: Hurley, Michael [mailto:[EMAIL PROTECTED] > Sent: Friday, September 03, 2004 1:30 PM > To: '[EMAIL PROTECTED]' > Subject: [Mailman-Users] Messages stuck in qfiles > > > I'm experiencing some odd behavior with Mailman. All was > working fine or so > I thought. I maintain >180 lists and >1000 subscribers. > > The system: > SuSE Linux Standard Server 8 > Sendmail 8.12.6-159 > Mailman 2.0.14-18 (yes, I know it's old, it's what SuSE likes) > > The symptoms: > Sendmail passes incoming messages off to the Mailman wrapper, > which does > nothing with them. They are piling up (.msg and .db files) in the > ~mailman/qfiles dir. There are about three days worth in there. > > Anybody know what is up? The qrunner cronjob seems to be > running normally, I > can't remember making any changes that would have affected mailman > operations around 3 days ago. > > Alternately, is there a way I can flush these messages out > manually so they > don't back up too far? > > Thanks > > > /*************************************** .-"""-. > Michael Hurley ' \ > Webmaster/SysAdmin |,. ,-. | > University of Connecticut School of Law |()L( ()| | > [EMAIL PROTECTED] |,' `".| | > (860) 570-5233 |.___.',| ` > ***************************************/ .j `--"' ` `. > / ' ' \ > / / ` `. > / / ` . > / / l | > . , | | > ,"`. .| | > _.' ``. | `..-'l > | `.`, | `. > | `. __.j ) > |__ |--""___| ,-' > `"--...,+"""" `._,.-' mh > ------------------------------------------------------ > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
