Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-18256

SNMPv3 Network discovery check does not start on active proxy

    XMLWordPrintable

Details

    • Problem report
    • Status: Closed
    • Trivial
    • Resolution: Cannot Reproduce
    • 5.0.2
    • None
    • Proxy (P)
    • None
    • zabbix-agent.x86_64 5.0.2-1.el7 @zabbix
      zabbix-proxy-mysql.x86_64 5.0.2-1.el7 @zabbix

    Description

      I have the problem that one of our network discoveries on our active proxy just doesn't start and I have no idea why that happens. Other network discoveries on that proxy work just fine. The rule of the never running discovery is correctly propagated from our server to the proxy.

       

      +---------+--------------+-----------------------------------+--------------------------------+-------+------------+--------+
      | druleid | proxy_hostid | name                              | iprange                        | delay | nextcheck  | status |
      +---------+--------------+-----------------------------------+--------------------------------+-------+------------+--------+
      |      37 |         NULL | Discovery Core 3/3                | xx.xx.xxx.x/24,xx.xx.yyy.yy/27 | 37m   | 1597325915 |      0 |
      +---------+--------------+-----------------------------------+--------------------------------+-------+------------+--------+
      

       

      # date [email protected]
      Thu Aug 13 15:38:35 CEST 2020
      # date
      Thu Aug 13 18:21:43 CEST 2020
      
      +----------+---------+------+---------------------------+----------------+-------+---------------------+----------------------+-----------------------+-----------------------+------+---------------------+---------------------+--------------------+-------------+-------------+
      | dcheckid | druleid | type | key_                      | snmp_community | ports | snmpv3_securityname | snmpv3_securitylevel | snmpv3_authpassphrase | snmpv3_privpassphrase | uniq | snmpv3_authprotocol | snmpv3_privprotocol | snmpv3_contextname | host_source | name_source |
      +----------+---------+------+---------------------------+----------------+-------+---------------------+----------------------+-----------------------+-----------------------+------+---------------------+---------------------+--------------------+-------------+-------------+
      |       77 |      37 |   13 | SNMPv2-MIB::sysObjectID.0 |                | 161   | <User>              |                    2 | <Secret>              | <Secret>              |    0 |                   1 |                   0 | <Context>          |           1 |           0 |
      +----------+---------+------+---------------------------+----------------+-------+---------------------+----------------------+-----------------------+-----------------------+------+---------------------+---------------------+--------------------+-------------+-------------+
      

      I increased the loglevel of the discoverer and of course stopped and started the zabbix-proxy several times. But I never see any discovery for dcheckid 77.

       

      # grep "insert into proxy_dhistory " /var/log/zabbix/zabbix_proxy.log | grep dcheckid | grep ",77," | wc -l
      0
      

       

      Other discoveries are running as expected and there are enough discoverer processes available:

      ● zabbix-proxy.service - Zabbix Proxy
         Loaded: loaded (/usr/lib/systemd/system/zabbix-proxy.service; enabled; vendor preset: disabled)
         Active: active (running) since Thu 2020-08-13 18:13:57 CEST; 47min ago
        Process: 53962 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=0/SUCCESS)
        Process: 53972 ExecStart=/usr/sbin/zabbix_proxy -c $CONFFILE (code=exited, status=0/SUCCESS)
       Main PID: 53974 (zabbix_proxy)
         CGroup: /system.slice/zabbix-proxy.service
                 ├─53974 /usr/sbin/zabbix_proxy -c /etc/zabbix/zabbix_proxy.conf
                 ├─53979 /usr/sbin/zabbix_proxy: configuration syncer [synced config 6571743 bytes in 2.156553 sec, idle 600 sec]
                 ├─53981 /usr/sbin/zabbix_proxy: trapper #1 [processed data in 0.001736 sec, waiting for connection]
                 ├─53982 /usr/sbin/zabbix_proxy: trapper #2 [processed data in 0.001711 sec, waiting for connection]
                 ├─53983 /usr/sbin/zabbix_proxy: trapper #3 [processed data in 0.001894 sec, waiting for connection]
                 ├─53984 /usr/sbin/zabbix_proxy: heartbeat sender [sending heartbeat message success in 0.003479 sec, idle 60 sec]
                 ├─53985 /usr/sbin/zabbix_proxy: data sender [sent 99 values in 0.009317 sec, idle 1 sec]
                 ├─53986 /usr/sbin/zabbix_proxy: housekeeper [deleted 663732 records in 8.563912 sec, idle for 1 hour(s)]
                 ├─53987 /usr/sbin/zabbix_proxy: http poller #1 [got 0 values in 0.000315 sec, idle 5 sec]
                 ├─53988 /usr/sbin/zabbix_proxy: http poller #2 [got 0 values in 0.000443 sec, idle 5 sec]
                 ├─53989 /usr/sbin/zabbix_proxy: discoverer #1 [processed 0 rules in 0.000525 sec, idle 60 sec]
                 ├─53990 /usr/sbin/zabbix_proxy: discoverer #2 [processed 0 rules in 0.000438 sec, idle 60 sec]
                 ├─53991 /usr/sbin/zabbix_proxy: discoverer #3 [processed 0 rules in 0.000493 sec, idle 60 sec]
                 ├─53992 /usr/sbin/zabbix_proxy: discoverer #4 [processed 0 rules in 0.000862 sec, idle 60 sec]
                 ├─53993 /usr/sbin/zabbix_proxy: discoverer #5 [processed 0 rules in 0.000829 sec, idle 60 sec]
                 ├─53994 /usr/sbin/zabbix_proxy: discoverer #6 [processed 0 rules in 0.000335 sec, idle 60 sec]
                 ├─53995 /usr/sbin/zabbix_proxy: discoverer #7 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─53996 /usr/sbin/zabbix_proxy: discoverer #8 [processed 0 rules in 0.000640 sec, idle 60 sec]
                 ├─53997 /usr/sbin/zabbix_proxy: discoverer #9 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─53998 /usr/sbin/zabbix_proxy: discoverer #10 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─53999 /usr/sbin/zabbix_proxy: discoverer #11 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54000 /usr/sbin/zabbix_proxy: discoverer #12 [processed 0 rules in 0.000370 sec, idle 60 sec]
                 ├─54001 /usr/sbin/zabbix_proxy: discoverer #13 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54002 /usr/sbin/zabbix_proxy: discoverer #14 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54003 /usr/sbin/zabbix_proxy: discoverer #15 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54004 /usr/sbin/zabbix_proxy: discoverer #16 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54005 /usr/sbin/zabbix_proxy: discoverer #17 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54006 /usr/sbin/zabbix_proxy: discoverer #18 [processed 0 rules in 0.000000 sec, performing discovery]
                 ├─54007 /usr/sbin/zabbix_proxy: discoverer #19 [processed 0 rules in 0.000605 sec, idle 60 sec]
                 ├─54008 /usr/sbin/zabbix_proxy: discoverer #20 [processed 0 rules in 0.000648 sec, idle 60 sec]
                 ├─54009 /usr/sbin/zabbix_proxy: history syncer #1 [processed 0 values in 0.000020 sec, idle 1 sec]
                 ├─54010 /usr/sbin/zabbix_proxy: history syncer #2 [processed 0 values in 0.000017 sec, idle 1 sec]
                 ├─54011 /usr/sbin/zabbix_proxy: history syncer #3 [processed 0 values in 0.000022 sec, idle 1 sec]
                 ├─54012 /usr/sbin/zabbix_proxy: history syncer #4 [processed 26 values in 0.001630 sec, idle 1 sec]
                 ├─54013 /usr/sbin/zabbix_proxy: snmp trapper [processed data in 0.000025 sec, idle 1 sec]
                 ├─54014 /usr/sbin/zabbix_proxy: self-monitoring [processed data in 0.000023 sec, idle 1 sec]
                 ├─54015 /usr/sbin/zabbix_proxy: task manager [processed 0 task(s) in 0.000377 sec, idle 5 sec]
                 ├─54016 /usr/sbin/zabbix_proxy: poller #1 [got 0 values in 0.000019 sec, idle 1 sec]
                 ├─54017 /usr/sbin/zabbix_proxy: poller #2 [got 1 values in 0.001327 sec, idle 1 sec]
                 ├─54018 /usr/sbin/zabbix_proxy: poller #3 [got 0 values in 0.000021 sec, getting values]
                 ├─54019 /usr/sbin/zabbix_proxy: poller #4 [got 0 values in 0.000016 sec, idle 1 sec]
                 ├─54020 /usr/sbin/zabbix_proxy: poller #5 [got 0 values in 0.000014 sec, getting values]
                 ├─54023 /usr/sbin/zabbix_proxy: poller #6 [got 0 values in 0.000016 sec, getting values]
                 ├─54024 /usr/sbin/zabbix_proxy: poller #7 [got 0 values in 0.000019 sec, getting values]
                 ├─54025 /usr/sbin/zabbix_proxy: poller #8 [got 0 values in 0.000017 sec, getting values]
                 ├─54026 /usr/sbin/zabbix_proxy: poller #9 [got 0 values in 0.000016 sec, idle 1 sec]
      

      Please tell me how to track the reason for this behaviour since I can't find any corresponding errors in our logfiles.

      Thank you!

      Holger

      Steps to reproduce:
      I seriously don't know.

      Result:
      discovery check is never executed.
      Expected:
      discovery check should run as any other discovery.

      Attachments

        Activity

          People

            aigars.kadikis Aigars Kadikis
            h.l. H.L.
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: