Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 26 replies
  • Subscribers 4 subscribers
  • Views 18095 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

High CPU After 9.310-11 Update

CWanamaker
Has anyone else noticed a much high CPU usage after this update? Most of the time, our UTM's will hover around 15-20% but every once in a while, they will spike up to 85%+ and stay that way for a period of time. We also noticed that it's happening across multiple UTMs at the exact same time. Different clients, different network but a number of them spike at the same time. Anyone else had this experience as well?


This thread was automatically locked due to age.
Parents
  • 0
    I think this is a bug/idiosyncrasy in cssd's rebuilding of the AV database immediately after a pattern update.  If you are using single-scan, switch to dual - that worked for me in the one instance I encountered.  William made that suggestion remembering an old bug.

    Cheers - Bob
    PS If you have a paid subscription, please get Sophos Support involved.  I think the bug in cssd is that it tries to use all possible memory to rebuild the database, causing all of the CPU to be used to manage swapping.
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    I think this is a bug/idiosyncrasy in cssd's rebuilding of the AV database immediately after a pattern update.  If you are using single-scan, switch to dual - that worked for me in the one instance I encountered.  William made that suggestion remembering an old bug.

    Cheers - Bob
    PS If you have a paid subscription, please get Sophos Support involved.  I think the bug in cssd is that it tries to use all possible memory to rebuild the database, causing all of the CPU to be used to manage swapping.
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    I think this is a bug/idiosyncrasy in cssd's rebuilding of the AV database immediately after a pattern update.  If you are using single-scan, switch to dual - that worked for me in the one instance I encountered.  William made that suggestion remembering an old bug.

    Cheers - Bob
    PS If you have a paid subscription, please get Sophos Support involved.  I think the bug in cssd is that it tries to use all possible memory to rebuild the database, causing all of the CPU to be used to manage swapping.


    That's the funny part wtih mine, mine was always single scan, but I had to change ENGINES from Avira to Sophos to stop the high CPU usage.  That was a problem for me since 9.3 released I believe.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

Unfiltered HTML