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
