-
Incident report
-
Resolution: Fixed
-
Blocker
-
3.2.0
-
Solaris 10
After upgrading the agent to 3.2.0, we see issues with discovery (some hosts discover no interfaces, others discover correctly).
Also seeing net.if.in/out returning an error.
Running the zabbix_agent as root has no effect on the behaviour.
Agent 3.0.0:
[user@server01 ~]$ /opt/zabbix/bin/zabbix_get -s localhost -k net.if.discovery
{"data":[{"{#IFNAME}":"lo0"},{"{#IFNAME}":"igb1"}]}
[user@server01 ~]$ /opt/zabbix/bin/zabbix_get -s localhost -k net.if.in[igb1]
18025317092167
Agent 3.2.0:
[user@server01 ~]$ sudo /opt/zabbix/bin/zabbix_get -s localhost -k net.if.discovery
{"data":[{"{#IFNAME}":"lo0"},{"{#IFNAME}":"igb1"}]}
[user@server01 ~]$ sudo /opt/zabbix/bin/zabbix_get -s localhost -k net.if.in[igb1]
ZBX_NOTSUPPORTED: Cannot look up interface "igb1" in kernel statistics facility
[user@server01 ~]$ sudo /opt/zabbix/bin/zabbix_get -s localhost -k net.if.out[igb1]
ZBX_NOTSUPPORTED: Cannot look up interface "igb1" in kernel statistics facility
Although it does appear that igb1 is in kstat:
[[email protected] ~]$ kstat | grep igb module: igb instance: 0 module: igb instance: 0 name: igb0 class: net module: igb instance: 0 module: igb instance: 0 module: igb instance: 1 module: igb instance: 1 name: igb1 class: net module: igb instance: 1 module: igb instance: 1 module: igb instance: 2 module: igb instance: 2 module: igb instance: 2 module: igb instance: 3 module: igb instance: 3 module: igb instance: 3
Agent 3.2.0 failing to return interfaces in discovery:
[user@server02 ~]$ /opt/zabbix/bin/zabbix_get -s localhost -k net.if.discovery
{"data":[]}
[user@server02 ~]$ ifconfig -a
lo0:4: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bnx532002:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 6
inet 10.0.0.1 netmask ffffff00 broadcast 10.0.0.255
I believe this is somehow related to ZBX-10372