problems with "net.tcp.listen"

[ZehEmEe]

Hi,

i monitor some service (bacula-fd) for listen state via "net.tcp.listen". All works fine but not on two machines. Here i get wrong info for this item.

It doen't matter if bacula-fd i bound to a single ip or to all ips of this server

# lsof -nPi :9102
COMMAND    PID USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME
bacula-fd 2471 root    3u  IPv4 400971953      0t0  TCP *:9102 (LISTEN)

if it try this on proxy:

# zabbix_get -s host -k net.tcp.listen[9102]
0

these lines shown in zabbix_agent.log with loglevel 4:

  2324:20140415:085828.719 Requested [net.tcp.listen[9102]]
  2324:20140415:085828.722 Sending back [0]
  2324:20140415:085828.722 listener #1 [waiting for connection]

Another system which is configured the same way works fine and i get right values.

Any ideas?

Zabbix 2.2.3 (Server, Proxy, Agent)

Cheers

Zeh

[dyegomb]

I noticed the same problem, it's happening only with high values ports... a bug??

[Molinero]

Me too !

I have the same problem !

In zabbix agent 2.4 the key "net.tcp.listen" returns the correct value
In zabbix agent 3 the value is always 0

bug ?!?