Noah wrote: > >okay well there were no relevant "SHUNT" messages in logs/error . how >else could I have figure this out from bin/dumpdb ?
You can't. In general, there may be nothing at all wrong with the message that was shunted. It may be shunted due to a software error or some other condition not directly related to the message itself. But, if you don't find out what the error was and do something about it, unshunting will likely just cause the message to encounter the same error and be shunted again. The mystery here is where the error log entries went. The code (at least our code, I can't speak for FreeBSD) always writes the error log when shunting a message (unless permissions prevent writing the error log in which case, that exception kills the runner). I would as root do find / -name error and see which of the resultant files look like Mailman error logs and whether any of those contain the 'missing' log entries. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
