Ad Widget

Collapse

High CPU on server 2019 DC's

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jeremy.flaugh
    Junior Member
    • Jun 2022
    • 3

    #1

    High CPU on server 2019 DC's

    Hello,

    I'm running Zabbix appliance Ver. 5.4 and on our windows server 2019 DC's were seeing high CPU from SVC host:windows event log, we found that if you stop the Zabbix service the CPU will settle back down. Sometimes the CPU fluctuates every 5 minutes and sometimes it a solid 100%
    I upgraded one the agents from 5.4.8.2400 to 5.4.12.2400 and had no change. I also removed and reinstalled the agent but the symptoms continued.
    This is similar to the issues in this thread. https://www.zabbix.com/forum/zabbix-...ent-collecting
    We do have templates applied that has triggers set for every 5 minutes I tried removing the templates but the issue continued.


    Thanks
    Attached Files
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    The triggers probably aren't relevant here, since trigger processing is going to happen on the Zabbix server, not a client system.

    I think you're on the right track: one or more of the items that are being collected are resource-intensive, and that's what's causing the high CPU utilization on the client systems.

    Since you're only seeing this on your domain controllers, it very likely is one (or more) of the items that are being collected only on your domain controllers. If you have one template that was only applied to your domain controllers, it's one or more of the items from that template.

    You indicated that you removed the templates, but did that actually remove all the items (and triggers, etc.) from the client system? I'm guessing not.

    In Configuration->Hosts, if you drill down to one of the hosts that's having CPU utilization issues, try systematically disabling the DC-specific items one by one and run for a while with one item disabled before trying the next one. This should help you identify which item(s) is/are resource intensive to collect. You may also have to disable triggers for each item, not sure if that's necessary or not.

    Comment

    • LenR
      Senior Member
      • Sep 2009
      • 1005

      #3
      Some M$ antimalware can cause this, we had to add some exe paths to it's white list.

      Comment

      Working...