[Mailman-Users] log errors after restart
Mark Sapiro
mark at msapiro.net
Fri Dec 21 21:32:31 CET 2012
Con Wieland wrote:
>We recently had an electrical issue and had to shutdown our mailman server. It know is looping this log error. Seems like it mail be a malformed message but I am not sure how to clear it.
It is a corrupt queue entry.
>Dec 21 07:56:02 2012 (5770) Traceback (most recent call last):
5770 is the PID of the queue runner that is encountering this error.
The entry is in the queue of that runner. I.e. if it is
IncomingRunner, the queue is qfiles/in.
ps -fwp 5770
will show you the cammand that started the runner including its name.
The queue entry is the first *.pck file in name sequence in the
directory.
> File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop
> msg, msgdata = self._switchboard.dequeue(filebase)
> File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 164, in dequeue
> msg = email.message_from_string(msg, Message.Message)
Since the runner got this far, you should be able to see the actual
message via
bin/show_qfiles qfiles/x/y.pck
or
bin/dumpdb qfiles/x/y.pck
where x is the queue and y.pck is the entry.
--
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