Here's what one of our lists' moderators receive, once in a while, since we updated Mailman to the current CVS.
So there's "bad marshal data", but in which file? What to do? (I guess it's people trying to unsubscribe.)
MailCommandHandler.ParseMailCommand()
Traceback (most recent call last): File "/home/mailman/Mailman/MailCommandHandler.py", line 261, in ParseMailC self.__dispatch[cmd](args, line, msg) File "/home/mailman/Mailman/MailCommandHandler.py", line 601, in ProcessUns self.ConfirmUnsubscription(cpaddr) File "/home/mailman/Mailman/MailList.py", line 1011, in ConfirmUnsubscripti cookie = Pending.new(Pending.UNSUBSCRIPTION, addr) File "/home/mailman/Mailman/Pending.py", line 62, in new db = _load() File "/home/mailman/Mailman/Pending.py", line 115, in _load return marshal.load(fp) ValueError: bad marshal data
-- Fil
In fact it was happening with all lists. I traced the problem to data/pending.db, which I removed, and the Mailman went on fine thereafter. Maybe it was because this file was mistakenly with permissions root.mailman 640 ? The trace error message was not very helpful, but I'm OK now.
@ Fil <fil@rezo.net> :
Here's what one of our lists' moderators receive, once in a while, since we updated Mailman to the current CVS.
So there's "bad marshal data", but in which file? What to do? (I guess it's people trying to unsubscribe.)
-- Fil
"F" == Fil <fil@rezo.net> writes:
F> In fact it was happening with all lists. I traced the problem
F> to data/pending.db, which I removed, and the Mailman went on
F> fine thereafter. Maybe it was because this file was mistakenly
F> with permissions root.mailman 640 ? The trace error message was
F> not very helpful, but I'm OK now.I'm not so sure, because your file was readable by the mailman process and you wouldn't get a marshal error if there was a permission problem, you'd get an IOError on the file open.
But it's definitely possible that there was a permission problem when the file was written, although that shouldn't truncate the file. If there was some kind of disk problem that caused the file to get truncated though, the save may not write the entire marshaled dictionary, and then you could get that error when reading it back.
Watch for other disk problems on the same filesystem.
-Barry
participants (2)
-
barry＠zope.com -
Fil