[Mailman-Users] mailman giving a 500 error when trying to opentheadministartor web page for a list.

[Mark Sapiro]

Steven Jones wrote:
>
>No such files under /var/mailman/data/ Doing a find under /var/mailman/
>reveals none....


Then there aren't any held messages waiting moderation.


>Another thing you could try is just bin/dumpdb on the
>lists/listname/request.pck file to be sure it can be read.
>
>========
>Looks like it can be read.
>
>[root at vuwunicosmtp004 bin]# ls -l ../lists/mailerdaemon/request.pck
>-rw-rw-r--    1 mailman  mailman        20 Feb  2 08:15
>../lists/mailerdaemon/request.pck
>[root at vuwunicosmtp004 bin]# ./dumpdb -n
>../lists/mailerdaemon/request.pck
>[----- start pickle file -----]
><----- start object 1 ----->
>{'version': (0, 1)}
>[----- end pickle file -----]


This confirms it. There aren't any requests in request.pck



>I get this from the mailman error log,
>
>[root at vuwunicosmtp004 bin]# more /var/log/mailman/error
>Feb 01 13:05:33 2006 (16068) Uncaught runner exception: No terminating
>boundary and no trailing empty line
>Feb 01 13:05:33 2006 (16068) Traceback (most recent call last):
>  File "/var/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
>    msg, msgdata = self._switchboard.dequeue(filebase)
>  File "/var/mailman/Mailman/Queue/Switchboard.py", line 151, in dequeue
>    msg = email.message_from_string(msg, Message.Message)
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/__init
>__.py", line 52, in message_from_string
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 75, in parsestr
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 64, in parse
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 240, in _parsebody
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 75, in parsestr
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 64, in parse
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 265, in _parsebody
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 64, in parse
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 240, in _parsebody
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 75, in parsestr
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 64, in parse
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 265, in _parsebody
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 64, in parse
>  File
>"/usr/src/build/526417-x86_64/install/var/mailman/pythonlib/email/Parser
>.py", line 206, in _parsebody
>BoundaryError: No terminating boundary and no trailing empty line


There is a malformed, unparseable MIME format message (probably spam)
in the 'in' queue (I'm assuming the 'in' queue, because normally only
the 'in' queue contains unparsed messages). This is wierd though
because BoundaryError is a subclass of MessageParseError which should
be caught in runner and logged in the error log as "Ignoring
unparseable message: filename"



>=========
>
>And I get this from the httpd log,
>
>[Thu Feb 02 09:33:34 2006] [error] [client 130.195.20.33] Premature end
>of script headers: admindb
>[Thu Feb 02 09:34:12 2006] [error] [client 130.195.20.33] Premature end
>of script headers: admindb
>[Thu Feb 02 09:35:38 2006] [error] [client 130.195.20.33] Premature end
>of script headers: admin, referer: http://lists.vuw.ac.nz/mailman/admin
>[Thu Feb 02 10:28:13 2006] [error] [client 130.195.20.33] Premature end
>of script headers: admin, referer: http://lists.vuw.ac.nz/mailman/admin
>[Thu Feb 02 10:36:14 2006] [error] [client 130.195.20.33] Premature end
>of script headers: admin, referer: http://lists.vuw.ac.nz/mailman/admin
>[Thu Feb 02 10:40:36 2006] [error] [client 130.195.62.121] Directory
>index forbidden by rule: /var/www/html/


These say the script ended without producing output. Maybe because the
list is locked looping on the above error or ? But there seems to be
only one such error in the error log, so I don't know what's going on.

Perhaps the above left the list locked. Look in mailman's locks/
directory for files with names mailerdaemon.lock* that were created
around Feb 01 13:05:33 2006. If there are two, one named
'mailerdaemon.lock' and one with name beginning with
'mailerdaemon.lock', it's probably safe to remove them. Also, you
might check Mailman's 'locks' log.

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