[Mailman-Users] mailman no longer working
Mark Sapiro
msapiro at value.net
Sat Oct 7 20:14:02 CEST 2006
Please copy your replise to the list.
Noah wrote:
>Mark Sapiro wrote:
>
>> Where are the messages ('ls -lR /usr/local/mailman/qfiles/')?
>>
>
>yes
>
># ls -lR /usr/local/mailman/qfiles/ | wc -l
> 14430
># ls /usr/local/mailman/qfiles/
>archive bounces in out shunt
>bad commands news retry virgin
And in which of the ten queues are the 14,000+ entries and are they all
current entries?
>> What's in Mailman's 'error' log?
>>
>>
>
>here is a tail of /usr/local/mailman/logs/error
>
>
>Oct 05 21:15:46 2006 (80775) Ignoring unparseable message:
>1160108146.3305931+690c58fe518535018e9efa2e62f34e6956e6c1e9
>Oct 06 19:45:15 2006 (75058) Uncaught runner exception: No terminating
>boundary and no trailing empty line
>Oct 06 19:45:15 2006 (75058) Traceback (most recent call last):
> File "/usr/local/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
> msg, msgdata = self._switchboard.dequeue(filebase)
> File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 151, in
>dequeue
> msg = email.message_from_string(msg, Message.Message)
> File "/usr/local/mailman/pythonlib/email/__init__.py", line 51, in
>message_from_string
> return Parser(_class, strict=strict).parsestr(s)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr
> return self.parse(StringIO(text), headersonly=headersonly)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse
> self._parsebody(root, fp, firstbodyline)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 240, in
>_parsebody
> msgobj = self.parsestr(part)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 75, in parsestr
> return self.parse(StringIO(text), headersonly=headersonly)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse
> self._parsebody(root, fp, firstbodyline)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 265, in
>_parsebody
> msg = self.parse(fp)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 64, in parse
> self._parsebody(root, fp, firstbodyline)
> File "/usr/local/mailman/pythonlib/email/Parser.py", line 206, in
>_parsebody
> raise Errors.BoundaryError(
>BoundaryError: No terminating boundary and no trailing empty line
>
>Oct 06 19:45:15 2006 (75058) Ignoring unparseable message:
>1160189115.47842+18be24324dc17289fa21a0eba9728ad56f13d0d2
This entry and the fragment of the Oct 5 entry are from malformed MIME
messages, almost certainly spam, that were ignored.
This is probably not related to your current problem.
>Oct 06 21:56:25 2006 mailmanctl(87639): No child with pid: 78979
>Oct 06 21:56:25 2006 mailmanctl(87639): [Errno 3] No such process
>Oct 06 21:56:25 2006 mailmanctl(87639): Stale pid file removed.
>Oct 06 21:57:20 2006 mailmanctl(87734): No child with pid: 87677
>Oct 06 21:57:20 2006 mailmanctl(87734): [Errno 3] No such process
>Oct 06 21:57:20 2006 mailmanctl(87734): Stale pid file removed.
These may indicate that qrunners died. Is there anything about this in
the 'qrunner' log?
>Oct 06 22:33:46 2006 mailmanctl(90876): The master qrunner lock could
>not be acquired because it appears as if another
>master qrunner is already running.
>Oct 06 22:33:46 2006 mailmanctl(90876):
These indicate you are doing 'mailmanctl start' or 'mailmanctl -s
start' without first doing 'mailmanctl stop' and verifying that all
Mailman processes are stopped. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.068.htp>.
--
Mark Sapiro <msapiro at value.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