Internal metrics gathering impacted by network discovery

XMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Zabbix server 7.0.3 with 1500 discovery rules.

      Discovery rules were created in automed way following this pattern: create 20 rules, wait 1 minute, repeat. Every rule covers /28 subnet and runs every 24 hours.

      When Zabbix starts executing all these rules internal metrics gathering is affected (effectively stops -  see screenshot)

      In logs I see:

      1053621:20241021:224026.649 item "Zabbix server:zabbix[process,discovery worker,avg,busy]" became not supported: Timeout while waiting for response
      1053618:20241021:224127.306 cannot write to IPC socket: Broken pipe
      1053618:20241021:235441.346 cannot write to IPC socket: Broken pipe
      1053618:20241022:004022.334 cannot write to IPC socket: Broken pipe
      1053618:20241022:015015.698 cannot write to IPC socket: Broken pipe
      1053618:20241022:025915.657 cannot write to IPC socket: Broken pipe
      1053618:20241022:040853.700 cannot write to IPC socket: Broken pipe
      1053618:20241022:051813.078 cannot write to IPC socket: Broken pipe
      1053618:20241022:062757.094 cannot write to IPC socket: Broken pipe
      1053618:20241022:073610.741 cannot write to IPC socket: Broken pipe
      1053618:20241022:084414.796 cannot write to IPC socket: Broken pipe
      1053618:20241022:094256.931 cannot write to IPC socket: Broken pipe
      1053618:20241022:094256.932 cannot write to IPC socket: Broken pipe
      1053621:20241022:094256.958 item "Zabbix server:zabbix[process,discovery worker,avg,busy]" became supported
      
      # Here is the processes from above
      zabbix   1053618 1053587  1 Oct03 ?        07:59:31 /usr/sbin/zabbix_server: discovery manager #1 [processing 0 rules, 0 unsaved checks]
      zabbix   1053621 1053587 11 Oct03 ?        2-05:12:25 /usr/sbin/zabbix_server: history syncer #1 [processed 1 values, 0 triggers in 0.004099 sec, idle 1 sec]

      When Zabbix starts it does not report "insufficient file descriptors", Zabbix server service configured with

      LimitNOFILE=65536 

      I start 30 discoverers

      StartDiscoverers=30 
      
      

      Expected:
      Internal metrics gathering always works.

            Assignee:
            Tomasz Grzechulski
            Reporter:
            Evgeny Yurchenko
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: