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/local/mailman/bin/qrunner", line 238, in main Dec 21 13:01:56 2012 qrunner(683): qrunner.run() Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Dec 21 13:01:56 2012 qrunner(683): filecnt = self._oneloop() Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop Dec 21 13:01:56 2012 qrunner(683): msg, msgdata = self._switchboard.dequeue(filebase) Dec 21 13:01:56 2012 qrunner(683): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 150, in dequeue Dec 21 13:01:56 2012 qrunner(683): fp = open(filename) Dec 21 13:01:56 2012 qrunner(683): IOError : [Errno 2] No such file or directory: '/usr/local/mailman/qfiles/out/1356123714.5592401+1ec0a1f9ab8fdab3f923b9eb39d706046ac42b7b.pck'

since it says there is no file I am not clear what I'm looking for here

On Dec 21, 2012, at 1:01 PM, Con Wieland wrote:

Hi Mark,

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 directory

con

Dec 21 12:57:12 2012 (826) Ignoring unparseable message: 1350498399.3898871+2cdf0127ff3b85695d03ea16c34571045d928788 Dec 21 12:57:12 2012 (826) Uncaught runner exception: No terminating boundary and no trailing empty line Dec 21 12:57:12 2012 (826) Traceback (most recent call last): 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) 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

On Dec 21, 2012, at 12:55 PM, Mark Sapiro wrote:

...

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 offending queue entry, you can just remove it or move it aside.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan