[Bug 238224] net-mgmt/zabbix4-server ipmi poller eats all CPU

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed May 29 21:05:45 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238224

            Bug ID: 238224
           Summary: net-mgmt/zabbix4-server ipmi poller eats all CPU
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: 000.fbsd at quip.cz
                CC: pg at pakhom.spb.ru
                CC: pg at pakhom.spb.ru
             Flags: maintainer-feedback?(pg at pakhom.spb.ru)

After upgrade of zabbix4-server from 4.0.4 to 4.0.7 I noticed  CPU overload.
This host (VM) vas almost idle with version 4.0.4 (monitoring 2 hosts only) but
now zabbix_server process (ipmi poller) eats all CPU.

last pid:  4696;  load averages:  2.11,  2.39,  2.24    up 0+00:35:43  14:00:17
84 processes:  2 running, 82 sleeping
CPU: 32.7% user,  0.0% nice, 67.3% system,  0.0% interrupt,  0.0% idle
Mem: 312M Active, 126M Inact, 281M Wired, 200M Buf, 1243M Free
Swap: 1024M Total, 1024M Free

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    TIME    WCPU COMMAND
  899 zabbix        1  81    0 63268K 14008K RUN     10:40  98.85%
zabbix_server: ipmi poller #2 [polled 5 values, idle 5.055918 sec during
5.080817 sec] (zabbix_server)
  769 mysql        57  20    0   540M   202M select   0:09   0.25% [mysqld]
  675 zabbix        1  20    0 11584K  6324K select   0:00   0.04%
zabbix_agentd: listener #1 [waiting for connection] (zabbix_agentd)

I tired to restart zabbix_server but it instantly starts to eat all CPU again.

My Zabbix server was built with following options

Options        :
        CURL           : on
        FPING          : on
        GNUTLS         : off
        IPMI           : on
        IPV6           : on
        JABBER         : off
        LDAP           : off
        LIBXML2        : off
        MYSQL          : on
        NMAP           : off
        OPENSSL        : on
        ORACLE         : off
        PGSQL          : off
        SSH            : on
        UNIXODBC       : off



Details about "pkg ugprade" after which the problem occurred:

pcre upgraded: 8.42_1 -> 8.43_1
png upgraded: 1.6.36 -> 1.6.37
php71 upgraded: 7.1.26_1 -> 7.1.29
perl5 upgraded: 5.28.1 -> 5.28.2
icu upgraded: 63.1_1,1 -> 64.2,1
readline upgraded: 7.0.5 -> 8.0.0
php71-dom upgraded: 7.1.26_1 -> 7.1.29
oniguruma upgraded: 6.9.0 -> 6.9.2
libnghttp2 upgraded: 1.36.0 -> 1.38.0
ca_root_nss upgraded: 3.42.1 -> 3.44
boost-libs upgraded: 1.69.0_1 -> 1.70.0_2
php71-xmlwriter upgraded: 7.1.26_1 -> 7.1.29
php71-xmlreader upgraded: 7.1.26_1 -> 7.1.29
php71-xml upgraded: 7.1.26_1 -> 7.1.29
php71-sockets upgraded: 7.1.26_1 -> 7.1.29
php71-snmp upgraded: 7.1.26_1 -> 7.1.29
php71-simplexml upgraded: 7.1.26_1 -> 7.1.29
php71-session upgraded: 7.1.26_1 -> 7.1.29
php71-mysqli upgraded: 7.1.26_1 -> 7.1.29
php71-mbstring upgraded: 7.1.26_1 -> 7.1.29
php71-ldap upgraded: 7.1.26_1 -> 7.1.29
php71-json upgraded: 7.1.26_1 -> 7.1.29
php71-gettext upgraded: 7.1.26_1 -> 7.1.29
php71-gd upgraded: 7.1.26_1 -> 7.1.29
php71-filter upgraded: 7.1.26_1 -> 7.1.29
php71-ctype upgraded: 7.1.26_1 -> 7.1.29
php71-bcmath upgraded: 7.1.26_1 -> 7.1.29
openipmi upgraded: 2.0.26_1 -> 2.0.27_2
mariadb103-client upgraded: 10.3.13_1 -> 10.3.15
libssh2 upgraded: 1.8.0_1,3 -> 1.8.2,3
liblz4 upgraded: 1.8.3,1 -> 1.9.1,1
libevent upgraded: 2.1.8_2 -> 2.1.8_3
galera upgraded: 25.3.25_1 -> 25.3.26
fping upgraded: 4.0_1 -> 4.2
curl upgraded: 7.64.0_1 -> 7.65.0_1
zabbix4-server upgraded: 4.0.4 -> 4.0.7
zabbix4-frontend upgraded: 4.0.4 -> 4.0.7
zabbix4-agent upgraded: 4.0.4 -> 4.0.7
vim-console upgraded: 8.1.0865 -> 8.1.1248
python27 upgraded: 2.7.16 -> 2.7.16_1
nginx upgraded: 1.14.2_8,2 -> 1.16.0,2
mariadb103-server upgraded: 10.3.13 -> 10.3.15
gawk upgraded: 4.1.4_3 -> 5.0.0
base-audit upgraded: 0.3 -> 0.4

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list