Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 9 subscribers
  • Views 4906 views
  • Users 0 members are here
Options
Suggested
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

Failed to install savxp: setup error causing servers to crash due to memory exhaustion

Rohan Dwyer

We are finding Sophos is causing our servers to lockup/freeze due to memory exhaustion. The event seems to correlate with errors in sophos central console for:

 

Failed to install savxp: setup error.
One or more Sophos services are missing or not running

In windows event viewer it shows at the same time as the above error in the sophos central console

Resource Exhaustion-Detector: Event 2004, Windows sucesfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: SavService.exe (8080) consumed 269762560 bytes, Norskale Broker Service.exe (6060) consumed 61325312 bytes etc. "

Whilst there were gigabytes of memory allocated to the VM the consistent thing we are seeing is that sophos is consuming a lot of memory just before the crash behavior. In this case the server is running Windows Server 2016 Std.

We have had about 5 of our servers with this issue now. They are running server advanced licenses with encryption protection enabled.

I have tried disabling automatic product updates and created a test group for server updates but it is still happening?



This thread was automatically locked due to age.
Parents
  • 0

    Hello Rohan Dwyer,

    might be that setup crashes due to memory exhaustion - not the other way round.

    sophos is consuming a lot of memory
    the 269762560 bytes are just a quarter Gig and around 250MB is the normal end expected value. And with the second most having a mere 60MB it'd take a lot of processes to fill gigabytes of memory.
    Neverhteless it seems to be related to Sophos in some way. I'd suggest that you collect the logs and open a Support ticket.

    Christian

Reply
  • 0

    Hello Rohan Dwyer,

    might be that setup crashes due to memory exhaustion - not the other way round.

    sophos is consuming a lot of memory
    the 269762560 bytes are just a quarter Gig and around 250MB is the normal end expected value. And with the second most having a mere 60MB it'd take a lot of processes to fill gigabytes of memory.
    Neverhteless it seems to be related to Sophos in some way. I'd suggest that you collect the logs and open a Support ticket.

    Christian

Children
No Data
Unfiltered HTML