-
Incident report
-
Resolution: Fixed
-
Critical
-
3.0.0
-
uname -a: Linux zabbix.communitake.com 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/redhat-release: CentOS Linux release 7.2.1511 (Core)
I've upgraded to zabbix 3.0 (server and agent)
I try to use net.tcp.listen to check if a port is listening and I always get 0 as an anwser
for example.
on one of the machines I have the following output for netstat -nlpt
tcp 0 0 0.0.0.0:9234 0.0.0.0:* LISTEN 1155/python tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 806/sshd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 882/master tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN 18514/zabbix_agentd tcp 0 0 :::22 :::* LISTEN 806/sshd tcp 0 0 ::1:25 :::* LISTEN 882/master tcp 0 0 :::443 :::* LISTEN 1900/docker-proxy tcp 0 0 :::8443 :::* LISTEN 1881/docker-proxy tcp 0 0 :::10050 :::* LISTEN 18514/zabbix_agentd
this is the output from running zabbix_get on the zabbix server for all available ports.
[root@zabbix ~]# zabbix_get -s r5.communitake.com -k net.tcp.listen[9234] 0 [root@zabbix ~]# zabbix_get -s r5.communitake.com -k net.tcp.listen[22] 0 [root@zabbix ~]# zabbix_get -s r5.communitake.com -k net.tcp.listen[25] 0 [root@zabbix ~]# zabbix_get -s r5.communitake.com -k net.tcp.listen[10050] 0 [root@zabbix ~]# zabbix_get -s r5.communitake.com -k net.tcp.listen[443] 0 [root@zabbix ~]# zabbix_get -s r5.communitake.com -k net.tcp.listen[8443] 0
- is duplicated by
-
-
- Closed
-