net.udp.listen key on 2.2.2

[asenci]

Hello,

Anybody noticing erratic behavior on the net.udp.listen key on version 2.2.2?

I get from the release notes that the method used to read /proc/net/udp has changed, but the weird thing is I'm receiving 0 on a port witch is open.

net.tcp.listen seems to behave fine.


On one of the hosts (the same happens on other hosts):
$ /usr/sbin/zabbix_agentd -t 'net.udp.listen[5060]'
net.udp.listen[5060] [u|0]

$ sudo netstat -tupln | grep 5060
udp 0 0 X.X.X.X:5060 0.0.0.0:* 30623/asterisk

$ cat /proc/net/udp | grep ':13C4'
127: XXXXXXXX:13C4 00000000:0000 07 00000000:00000000 00:00000000 00000000 0 0 16188625 2 ffff8800581db840 0


On the item history:
2014-03-07 10:38:00 1394199480 0
2014-03-07 10:37:00 1394199420 1
2014-03-07 10:36:00 1394199360 0
2014-03-07 10:35:00 1394199300 0
2014-03-07 10:34:00 1394199240 1
2014-03-07 10:33:00 1394199180 1
2014-03-07 10:32:00 1394199120 1

[unnikrishnan]

Seems the issue is there for tcp also.

# netstat -plan | grep :25
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 58156/master


However, the key is returning '0'

# /usr/sbin/zabbix_agentd -t net.tcp.listen[25]
net.tcp.listen[25] [u|0]


It would be really helpful if someone can look into this.

[OKyHb]

Confirm excact the same issue. Had to downgrade to 2.2.1 because of that.

P.S. By the way, zabbix20-agent-2.0.11-1.el6.x86_64.rpm has the same problem.

[unnikrishnan]

mm...



Seems the key 'net.tcp.port' will return the correct value even for version 2.2.2.

# /usr/sbin/zabbix_agentd -t net.tcp.listen[25]
net.tcp.listen[25] [u|0]
# /usr/sbin/zabbix_agentd -t net.tcp.port[,25]
net.tcp.port[,25] [u|1]

[asenci]

Both net.tcp.port and net.tcp.listen works fine for me on 2.2.2.
Only the net.udp.listen key is returning the wrong value on my hosts.

[Bsabbath66]

I am also having this problem with version 2.2.2. I am monitoring port 53/udp my DNS server and is returning as down, even though the service is functioning properly. This needs to be fixed by the development team Zabbix (seems to be a bug).

[ebonweaver]

Still no UDP in 2.4.3

net.udp.listen is for some reason not supported on the Windows agent and never has been. Shame, not sure why they can't make this work after several years. I find no way of monitoring a service on Windows that only uses UDP and not TCP.