On Wednesday 09 October 2002 14:27 CET Jost Krieger wrote: > On Wed, Oct 09, 2002 at 03:01:43AM -0700, Quinn Vallance wrote: > > I maintain two relatively high volume mail servers both of which have > > been using Spamassassin for some time mow. Everything has always worked > > fine and I have always upgraded to the newest stable versions when > > released. I upgraded to 2.42 on both of my servers (one is running > > postfix with postbox the other sendmail with procmail) and on both > > server the spamd daemon died after several hours for no apparent reason > > leaving nothing in the logs as to indicate why. Has anybody else been > > having similar problems? I have updated numerous times with no problems > > so I am confused as to what may have caused this with such a small > > version increment (2.41->2.42). I have switched back to 2.41 for the > > time being but would love any suggestions or to hear from people having > > similar issues. > > Same problem here. I switched yesterday and got 4 restarts between > 12:13 and midnight, while processing 38494 connections. > > I can live with that, as spamd runs under supervise, but I'm now going to > switch from syslog to daemontools logging and hope to find something in > stderr. > > BTW: Solaris 8 and perl 5.6.1.
This sounds like a really grave problem. Could you please open a bug in bugzilla.spamassassin.org? Quinn, do you run on Solaris, too? And there's really nothing in the syslog? If it's possible, could you please run spamd with debugging enabled (-D)? (This will probably fill up your logs quickly, so don't do this if you're low on disk space.) Malte -- --- Coding is art. -- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
