On 12/24/2012 12:31 PM, Con Wieland wrote:
> Thanks Mark, that did the trick, ArchRunner started right up without any
> errors. Fingers crossed the only thing left are the 542 messages in
> qfiles/bad. They mostly seem to just be message headers that were bounces or
> the body was omitted
Thanks Mark, that did the trick, ArchRunner started right up without any
errors. Fingers crossed the only thing left are the 542 messages in
qfiles/bad. They mostly seem to just be message headers that were bounces or
the body was omitted Can they safely be deleted?
con
On Dec 24, 2012
On 12/24/2012 9:19 AM, Con Wieland wrote:
> so the other thing I just noticed, which I think is what your getting at is
> that
>
> --runner=ArchRunner:0:1 -s
>
> is not running and I notice it is on another install of mailman that I have.
> But I can't find any thing error wise other than the
so the other thing I just noticed, which I think is what your getting at is
that
--runner=ArchRunner:0:1 -s
is not running and I notice it is on another install of mailman that I have.
But I can't find any thing error wise other than the below. Is there a way to
start it manually (maybe that
On Dec 24, 2012, at 8:58 AM, Mark Sapiro wrote:
> On 12/24/2012 8:53 AM, Con Wieland wrote:
>>
>> On Dec 24, 2012, at 8:46 AM, Mark Sapiro wrote:
>>>
>>> Is ArchRunner running? What are the extensions on the names of these 153
>>> entries.
>>
>> looks to be:
>>
>> ps -ef |grep -i qrunner
>> m
On 12/24/2012 8:53 AM, Con Wieland wrote:
>
> On Dec 24, 2012, at 8:46 AM, Mark Sapiro wrote:
>>
>> Is ArchRunner running? What are the extensions on the names of these 153
>> entries.
>
> looks to be:
>
> ps -ef |grep -i qrunner
> mailman 17786 17123 0 07:41:53 ?0:00 /usr/local/bin/py
On Dec 24, 2012, at 8:46 AM, Mark Sapiro wrote:
> On 12/24/2012 7:48 AM, Con Wieland wrote:
>> More issues. I had several of these messages:
>>
>> Dec 24 06:57:23 2012 (17125) Ignoring unparseable message:
>> 1354049125.0870931+f5e280e91f2ed298fb5
>> 62d3690311d1e47d24dee
>>
>> I found them i
On 12/24/2012 7:48 AM, Con Wieland wrote:
> More issues. I had several of these messages:
>
> Dec 24 06:57:23 2012 (17125) Ignoring unparseable message:
> 1354049125.0870931+f5e280e91f2ed298fb5
> 62d3690311d1e47d24dee
>
> I found them in the bounce directory and removed them. I then restarted
More issues. I had several of these messages:
Dec 24 06:57:23 2012 (17125) Ignoring unparseable message:
1354049125.0870931+f5e280e91f2ed298fb5
62d3690311d1e47d24dee
I found them in the bounce directory and removed them. I then restarted mailman
with no errors but I noticed that I now have a l
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
15 matches
Mail list logo
