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. This problem started 2 days ago after updating: SA-2.60 -> 2.61 Last night, I updated to SA-2.63 -- problem continued and server rebooted every few hours, being overwhelmed I guess. This morning, I disabled the auto_whitelist DB process and the problem has ceased. I always read the docs and saw nothing about this, nor any posts here about other having this problem. I had synced the DB back in the version where the format was changed and it had been working fine thereafter. I did see that this function could become "flaky" if using NFS, but I am not using NFS. If I missed something in the docs, then shame on me. Theo and/or anyone -- please help if you know the answer. I would like to keep using this function now disabled. BTW: here are a few of the errors that appeared every few mins: Jan 22 04:59:54 sage-american /kernel: pid 810 (perl5.00503), uid 2: exited on signal 10 Jan 22 05:10:03 sage-american /kernel: pid 916 (perl5.00503), uid 2: exited on signal 10 Jan 22 05:21:30 sage-american /kernel: pid 985 (perl5.00503), uid 2: exited on signal 10 Jan 22 05:31:38 sage-american /kernel: pid 1089 (perl5.00503), uid 2: exited on signal 10 Jan 22 05:41:39 sage-american /kernel: pid 1129 (perl5.00503), uid 2: exited on signal 10 Jan 22 05:51:41 sage-american /kernel: pid 1189 (perl5.00503), uid 2: exited on signal 10 Jan 22 06:09:27 sage-american /kernel: pid 1298 (perl5.00503), uid 2: exited on signal 10 Jan 22 06:21:02 sage-american /kernel: pid 1381 (perl5.00503), uid 2: exited on signal 10 Jan 22 06:37:22 sage-american /kernel: pid 1540 (perl5.00503), uid 2: exited on signal 10 Jan 22 06:52:49 sage-american /kernel: pid 1661 (perl5.00503), uid 2: exited on signal 10 Jan 22 07:03:27 sage-american /kernel: pid 1884 (perl5.00503), uid 2: exited on signal 10 Jan 22 07:13:31 sage-american /kernel: pid 1968 (perl5.00503), uid 2: exited on signal 10 Jan 22 07:23:59 sage-american /kernel: pid 2101 (perl5.00503), uid 2: exited on signal 10 Best regards, Jack L. Stone, Administrator Sage American http://www.sage-american.com [EMAIL PROTECTED] ------------------------------------------------------- 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
