Ad Widget

Collapse

Upgrade to 7.4.4 zabbix_agent2 results in 100% CPU usage

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ams047
    Junior Member
    • Oct 2025
    • 1

    #1

    Upgrade to 7.4.4 zabbix_agent2 results in 100% CPU usage

    I upgraded zabbix_agent2 from 7.4.3-1 to 7.4.4-1 on my Debian 11 and 12 hosts, and openSUSE 15.6 and within a minute it claimed 100%+ CPU usage across all hosts providing databases (mysql and postgresql). Those that are not running databases were unaffected.

    My solution was to downgrade back down to 7.4.3-1 on the affected hosts and all is well again.

    Anyone else affected by this issue - is there something in their cfg that needed upgrading, or should I just file a bug?
  • jonad2002
    Junior Member
    • Oct 2025
    • 3

    #2
    I too am seeing precisely this behavior. 100% CPU for zabbix_agent2 7.4.4 and MySQL. I can state that this occurs for a fresh uncustomized configuration of MySQL as well as an uncustomized agent2 .conf. I bumped up debug = 4 and did not see anything in that output that was unexpected. Just the agent2 process pegged for CPU.

    Comment

    • d2inco
      Junior Member
      • Jul 2020
      • 1

      #3
      Hate to add a "me too", but: me too. Zabbix-agent2, on a host with only Mysql and Redis running. Running as an "active agent".

      Comment

      • stoege
        Junior Member
        • Oct 2025
        • 1

        #4
        same here ... downgrade to 7.4.3 solved the problem. server is running on debian 12 with mariadb 10.11.14.

        Comment

        • cerealx
          Junior Member
          • Sep 2024
          • 2

          #5
          Same here on 2 hosts with mariadb 11.8.3 on debian 12 and debian 13

          Comment

          • manusfreedom
            Junior Member
            • Aug 2017
            • 4

            #6
            Same here with Zabbix-agent2 and MariaDB (11.4), but on Zabbix 7.0.20.

            Comment

            • brechsteiner
              Junior Member
              • Nov 2025
              • 2

              #7
              Same here with zabbix-agent2
              • Zabbix Agent2 7.0.20-1+debian12
              • MariaDB Server 10.11.14+maria~deb12

              Comment

              • brechsteiner
                Junior Member
                • Nov 2025
                • 2

                #8
                Has anyone already created a ticket on support.zabbix.com?

                Comment

              • Calypso
                Junior Member
                • Mar 2007
                • 29

                #9
                Just got zabbix agent 2 v 7.4.5 on the affected hosts and the issue is still present

                Comment

                • jonad2002
                  Junior Member
                  • Oct 2025
                  • 3

                  #10
                  Confirmed. I tried 7.4.5-1. Agent2 still pegged 100%. Rolled back again to 7.4.3-1.

                  Comment

                  • aaxvig
                    Junior Member
                    • Nov 2025
                    • 3

                    #11
                    Same on 7.0.21, Debian 13. PostgreSQL and MariaDB are installed--both from stock Debian packages. `apt install zabbix-agent2=1:7.0.19-1+debian13` seems to have fixed it.

                    Comment

                    • cerealx
                      Junior Member
                      • Sep 2024
                      • 2

                      #12
                      Fixed for me with the latest minor version update

                      Comment

                      • jonad2002
                        Junior Member
                        • Oct 2025
                        • 3

                        #13
                        Confirmed: 7.0.21-2, 7.4.5-2 -- I didn't test 7.0.21, but the -2 iteration of 7.4.5 resolved for my environments.

                        Comment

                        • aaxvig
                          Junior Member
                          • Nov 2025
                          • 3

                          #14
                          Relevant bug is ZBX-27156.

                          Comment

                          Working...