-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 22 January 2004 07:53, Jack L. Stone wrote: > Perhaps this question needs to be directed to Theo Van Dinter who most > likely knows the answer I need. My server is going down frequently and has > been traced to SA. > > Yesterday I posted a question about a perl5 function breaking and > apparently doing so on just about every message processed by SA. It is so > bad that it is causing my mail server to crash/reboot -- twice last night. > > The time to process a message jumped to over 30 secs from the usual 1 sec > or less. I don't use rbls, so it's not related to any outside server > services. -- a 30x jump! > > I spent the whole day yesterday tracing the problem and finally to the > auto_whitelist DB -- which appeared to be creating numerous lock files and > leaving them there after each break in the process. The PIDs were compared > to those being displayed in top when the perl500503 processes (numerous) > appeared. They were the same that were appended to the lock files left > behind in /root/.spamassassin.
I would upgrade perl for spamassassin to at least 5.6X. You should also clean out the white list DB. See if you have the problem with a fresh WhiteList DB. Douglas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAEAvoSpWn8R0Z08URAoTSAKDBc9nQWWNzN9VdupbbhxY4fphJ5QCgtIOQ 7AU1xRYyE1Agnu4llbi/NFQ= =4W08 -----END PGP SIGNATURE----- ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
