Extreme High CPU Usage

Dear all,

 

I am using Sohpos Antivirus for Linux on a Univention Corporate Server (based on Debian 7 using talpa). I have been using SAV for more than a year without facing any problems.

After an update yesterday evening I experienced an extremely high CPU load caused by the on access scan engine. As soon as I diable the on access scanning the CPU load drops to a normal level again. For further clarification please see the following screenshot from the gui task manager.

As far as I can tell there are no unusual entries/ warnings displayed in the log files. I have already tried to reinstall Sophos AV for Linux and diabled archive scanning, however this did not resolve the issue.

 

Any suggestions would be highly appreciated.

 

Kindest regards,

 

Tom Derryl

  • Hello  

    Are you still getting this issue? (apologies that no one has replied to this thread)

    If you are still seeing the CPU spike can you please use the links below to send the logs to our support team. We have not seen any unusual spikes in CPU usage in the current and previous releases but we will certainly help to see if we can pinpoint the issue and cause of the spike when running an on access scan. 

     

    thanks 

     

    Mark 

  • In reply to MarkToshack:

    I am having the same problem with my MACPro (OS X 10.11.6 (El Capitan),  64 GB RAM, dual Xeon quad-core CPUs).  CPU usage varies from 90% to 50 % under the following circumstances:  When I restart the system and log n to an account; When I  start up from up a shutdown;'  when I change user accounts (i.e., whenever I log into a user account from sleep mode).  The CPU usage is caused by the Sophos scan process.   I can kill the scan in the activity monitor, but then the scan just restarts and monopolizes the CPUs.   This really ties up my system and is most annoying.  

  • In reply to John Pessagno:

    Hi  

    Would you please suggest what is the version of the Sophos Antivirus installed? Please follow the steps listed in this article to find the exact component causing the issue.