Con Wieland wrote:
>
>The system got restarted again to return ait to it;s original power
>source before I got the original error tracked down. So when it
>restarted this time I got this error. I was assuming I would find it in
>the in queue and just remove it but there was nothing in the in
>dire
Con Wieland wrote:
>In addition I just received this error:
>
>Dec 21 13:01:56 2012 qrunner(683): Traceback (most recent call last):
>Dec 21 13:01:56 2012 qrunner(683): File =
>"/usr/local/mailman/bin/qrunner", line 278, in ?
>Dec 21 13:01:56 2012 qrunner(683): main()
>Dec 21 13:01:56 2012
In addition I just received this error:
Dec 21 13:01:56 2012 qrunner(683): Traceback (most recent call last):
Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/bin/qrunner",
line 278, in ?
Dec 21 13:01:56 2012 qrunner(683): main()
Dec 21 13:01:56 2012 qrunner(683): File "/usr/l
Mark Sapiro wrote:
>
>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.
I forgot to add, and maybe it's obvious anyway, but once you find the
offendi
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
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.
Any ideas?
thanks
Con Wieland
Office of Information Technology
University of California at Irvine
Dec 2
