Re: [Mailman-Users] log errors after restart
Con Wieland wrote:
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):
Even in 2.1.9, these messages are removed when you see the "Ignoring unparseable message:" entry. If you continue to see these, they are probably malformed spam messages tha have nothing to do with the outage and restart.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Con Wieland
-
Mark Sapiro