This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[bug ?] pop3 proxy/cssd cpu usage

Hi.

Just upgraded from ASG V8 to UTM 9.000 (fresh iso + backup file).
All was then fine.

This night, upgraded from UTM 9.000 to UTM 9.001-18.

pop3 proxy is now not working anymore :-(

I got this (UTM pop3 proxy log) for each message using pop3 proxy
..
2012:08:11-07:47:01 firewall pop3proxy[3960]: Connect to cssd failed: Connection refused
2012:08:11-07:47:08 firewall pop3proxy[3960]: Connect to cssd failed: Connection refused
2012:08:11-07:47:16 firewall pop3proxy[3960]: Connect to cssd failed: Connection refused
2012:08:11-07:47:23 firewall pop3proxy[3960]: Fatal: Scan failed due to some weird reason
...

I've try with single or both engines. 
Message size doesn't impact problem.

I also notice that cpu usage is now very high with 9.001 : average above 70% with summit at 100%. consumer is cssd...

Just before, with 9.000, average CPU was less that 15/20% with very rare and short summits to 90/100%

My CPU is AMD Duron socket A @1.7Ghz with 2G RAM.
Home usage (3 users max).

only workaround now : disable pop3 proxy :-(((


This thread was automatically locked due to age.
  • In fact disabling/re-enabling the POP3 proxy antivirus feature solve the problem.
  • In fact disabling/re-enabling the POP3 proxy antivirus feature solve the problem. 


    Super!  Thanks for letting us know.  I would have suggested a reboot, but your solution is a better one to know for environments where a reboot is undesirable.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA