-
Problem report
-
Resolution: Unresolved
-
Major
-
None
-
5.4.2
-
Zabbix installation "All In One" VM
==============================
CentOS Linux release 8.1.1911 (Core)
==============================
mariadb.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
mariadb-backup.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
mariadb-common.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
mariadb-connector-c.x86_64 3.0.7-1.el8
mariadb-connector-c-config.noarch 3.0.7-1.el8
mariadb-errmsg.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
mariadb-gssapi-server.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
mariadb-server.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
mariadb-server-utils.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839
net-snmp.x86_64 1:5.8-20.el8
zabbix-agent.x86_64 5.4.2-1.el8
zabbix-nginx-conf.noarch 5.4.2-1.el8
zabbix-server-mysql.x86_64 5.4.2-1.el8
zabbix-sql-scripts.noarch 5.4.2-1.el8
zabbix-web.noarch 5.4.2-1.el8
zabbix-web-deps.noarch 5.4.2-1.el8
zabbix-web-mysql.noarch 5.4.2-1.el8Zabbix installation "All In One" VM ============================== CentOS Linux release 8.1.1911 (Core) ============================== mariadb.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 mariadb-backup.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 mariadb-common.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 mariadb-connector-c.x86_64 3.0.7-1.el8 mariadb-connector-c-config.noarch 3.0.7-1.el8 mariadb-errmsg.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 mariadb-gssapi-server.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 mariadb-server.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 mariadb-server-utils.x86_64 3:10.3.17-1.module_el8.1.0+217+4d875839 net-snmp.x86_64 1:5.8-20.el8 zabbix-agent.x86_64 5.4.2-1.el8 zabbix-nginx-conf.noarch 5.4.2-1.el8 zabbix-server-mysql.x86_64 5.4.2-1.el8 zabbix-sql-scripts.noarch 5.4.2-1.el8 zabbix-web.noarch 5.4.2-1.el8 zabbix-web-deps.noarch 5.4.2-1.el8 zabbix-web-mysql.noarch 5.4.2-1.el8
I'm new to Zabbix, but my first impression is that you do a very good job. Bulk processing is a great feature ! 
Steps to reproduce:
Difficult to reproduce : I'm polling a Cisco device with "Use bulk requests" configured and every hour I got a log message on my Cisco device like this one :
2021 Aug 3 01:00:16 switch %SNMPD-3-ERROR: SNMP log error : SNMP Operation (GET) failed. Reason:1 reqId (904207711) errno (2) error index (0)
It seems to be related to the bulk processing mecanism which try to determine the maximum SNMP items Zabbix can retreive in one SNMP request for a device.
For my device, it seems that max_succeed=59 works most part of the time but every hour for a specific get-resquest, related to network discovry rule, it fails.
Result:
Cisco device's log file spammed every hour with a log message like :
2021 Aug 3 01:00:16 switch %SNMPD-3-ERROR: SNMP log error : SNMP Operation (GET) failed. Reason:1 reqId (904207711) errno (2) error index (0)
Expected:
I don't understand when "max_succeed" is calculated but it should not oscillating between two values. Some margin/historical data should prevent such oscillation.
- part of
-
ZBXNEXT-4428 internal logic of SNMP bulk processing
-
- Closed
-