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.
Maybe I spoke too soon...
It looks like setting ccMaxBytes:=1 does not help.
Just had a long 8 minute episode, then a 4 minute one about 15
minutes later.
Maybe heading back to 1.3.2 this evening when traffic dies down.
Having another episode right now.
It's like having a mail server with epilepsy.
Waiting for it to clear so I can send this -- Arrggghh...
-------------------------------------------------------------------------
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
