[Mailman-Developers] Problem with MM after power outage

[Barry Warsaw]

On Fri, 2003-08-15 at 12:52, Bill Bradford wrote:
> Looks like the problem resolved itself after a few minutes.
> 
> Bill
> 
> On Fri, Aug 15, 2003 at 09:58:39AM -0500, Bill Bradford wrote:
> > After power was restored and the machine came up, Mailman (2.1.2) is now
> > spitting out errors:
> > Traceback (most recent call last):
> >   File "/usr/local/mailman/bin/qrunner", line 270, in ?
> >     main()
> >   File "/usr/local/mailman/bin/qrunner", line 230, in main
> >     qrunner.run()
> >   File "/usr/local/mailman/Mailman/Queue/Runner.py", line 59, in run
> >     filecnt = self._oneloop()
> >   File "/usr/local/mailman/Mailman/Queue/Runner.py", line 88, in _oneloop
> >     msg, msgdata = self._switchboard.dequeue(filebase)
> >   File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 144, in dequeue
> >     data = self._ext_read(dbfile)
> >   File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 246, in _ext_read
> >     dict = marshal.load(fp)
> > ValueError: bad marshal data

Hmm, weird.  The switchboard is written such that this shouldn't happen
(i.e. you shouldn't get a corrupt message.db file).  It's supposed to
write the message first to .db.tmp and then rename it to .db in an
atomic operation.

Do you have any .db.tmp turds in your qfiles directories?

all-problems-should-fix-themselves-ly y'rs,
-Barry