[Mailman-Users] shunt dir and "Uncaught runner exception"
spork at bway.net
Sun May 15 01:43:05 CEST 2005
On Sat, 14 May 2005, Brad Knowles wrote:
> At 5:14 PM -0400 2005-05-14, Charles Sprickman wrote:
>> Now, does anyone have any clue what the error messages below mean?
>> Judging by the number of shunted messages, this happens fairly often. The
>> "I/O error" leads me towards permsissions, but on what?
> I'd have to check the code, but from reading the traceback it seems
> to me like there was some sort of error writing to the log files. What is
> the ownership and permissions for the Mailman "logs" directory, all the log
> files within that directory, etc...? How full is that filesystem? How large
> are those log files?
The perms look OK, but I do remember many months ago that the "smtp"
logfile would sometimes revert to being owned by root rather than mailman.
If it is a permissions problem on a log, should that actually cause the
message to get shunted? If that is what's happening, perhaps I should put
that in the SF bug tracker...
>> Lastly, what are ".pck" files? How can I examine these as they show up?
> Those are the Python "pickle" files which contain binary data
> regarding the message. Use the "show_qfiles" program in
> /usr/local/mailman/bin. For example, from the /usr/local/mailman directory,
> do the following:
> % bin/show_qfiles qfiles/shunt/*.pck
> However, if the "pickle" file is causing errors of this sort, then
> show_qfiles may come back with errors as well -- you'll just have to give it
> a try.
Excellent! Thanks for that info, I appreciate it.
> Brad Knowles, <brad at stop.mail-abuse.org>
> "Those who would give up essential Liberty, to purchase a little
> temporary Safety, deserve neither Liberty nor Safety."
> -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
> Assembly to the Governor, November 11, 1755
> SAGE member since 1995. See <http://www.sage.org/> for more info.
More information about the Mailman-Users