So far... >>> When this happens, CPU usage jumps to 100% during the period, it's >>> usually 4% to 8%. >>> During that time, the ASSP GUI will not respond, and local outgoing >>> SMTP fails (through ASSP). >>> During that time, the POP and IMAP DOES respond (on same machine) >>> TOP shows PERL using most of the CPU cycles. >>> Have examined the logs following episodes, haven't noticed anything >>> unusual. >> >> set this: >> # grep -i ccmaxbytes /opt/assp/assp.cfg >> ccMaxBytes:=1 > > I had exactly the same problem, even with ccMaxBytes:=1. Now I am > running version 1.3.2(53) and its gone. Thats why I am not really > willing to update to version 1.3.3.1. Is the security problem also > present in version 1.3.2(53)? Never change a running system you > know;-) > > Hans
Rainer - Thanks for the ccMacBytes info. I've set ccMaxBytes:=1 It DOES seem to help some, the episodes still happen - but not as often. Just watched two (2) episodes occur, only 75 seconds and 60 seconds. Hans - Thanks for your input, guess I'm not alone. If my server doesn't clear up, I'll have to go back to 1.3.2 like you did. Fritz wrote: > I am worried about these reports. Are there more of this experiences? > Please test and test fast, so that we can react. Fritz - Looking at logs, I've noticed these in the logs Aug-6-07 07:24:53 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:25:12 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:26:33 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:26:51 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:28:05 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:28:24 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:30:43 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:31:01 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:37:08 Cache reset (/usr/local/assp/spamdb) Aug-6-07 07:37:27 Cache reset (/usr/local/assp/spamdb) Each one takes about 20 seconds - should I see this many? Probably not related to my problem? Doug wrote: > I think we have come to the conclusion in the past that long pauses in > responding are caused by ASSP trying to connect to an outside lookup > source either URIBL, RBL, etc. Doug - checking my logs, looks like the lookups are happening pretty quickly: Aug-6-07 08:29:20 Commencing DNSBL checks on 89.149.139.181 Aug-6-07 08:29:20 Completed DNSBL checks on 89.149.139.181 Aug-6-07 08:29:21 Commencing DNSBL checks on 206.132.3.184 Aug-6-07 08:29:21 Completed DNSBL checks on 206.132.3.184 Aug-6-07 08:29:22 Commencing DNSBL checks on citicards.com Aug-6-07 08:29:22 Completed DNSBL checks on citicards.com Aug-6-07 08:29:22 Commencing DNSBL checks on aa.com Aug-6-07 08:29:23 Completed DNSBL checks on aa.com and URIBL looks similar - seems OK Thanks for your suggestions guys, Donald at Lorian Network ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
