Simple check tcp

[rsterenb]

Well, yes, I'm fully aware and that's exactly what I want.
I'm against using the Zabbix Agent to check a local port, when I can easily use the Zabbix Server to check a remote port and at the same time have the full network path for that specific port tested.

On the first page of this thread I also posted the results of an nmap scan. Network connectivity is fine.

- The Zabbix Server and the Salt server are in the same subnet. There is no local firewall configured on neither the Zabbix Server nor the Salt server.
- An nmap scan from the Zabbix Server to the (Salt) [server]:[port] I want to monitor says the port is open.
- zabbix_get says the Salt service is open/active (result: 1). This is the expected result.
- Zabbix GUI (Latest data) says the port is closed/inactive (result: 0). I do not expect this result. The result from the SQL statements I executed earlier shows that a value of 0 is stored. You can find this in a previous reply I wrote.

(Edit: getting rid of the unintended smiley..)

[mobarrio]

Hi rsterenb,
I have the same issue, do you resolve it?

Mariano

[Rectifier]

Hi All,

Maybe it's not up to date topic but I had a similar issue. Problem was with selinux (CentOS7) which denied boolean zabbix_can_network

getsebool -a | grep zabbix
setsebool zabbix_can_network on
setsebool -P zabbix_can_network on

[rsterenb]

Unfortunately that is not the issue I experienced because we have SELinux is disabled. This was almost 2 years ago, and IIRC we never got this fixed.
However, we want to upgrade to Zabbix-4 somewhere in the upcoming months and maybe that fixes it, although I'm not having high hopes..

[coffee]

Thank you very much for reminding us to check SELinux. It has indeed solved our problem. There are really several server problems because of this！

[Barnilla]

Hello everyone.

I'm not sure, that this topic still actual, but I spend few last hours for resolving this issue, and I'm here.

There is a problem with type of item. I chose the Simple check and this is wrong.
After changing to type Zabbix agent everything became fine.

I think, when you choose type Simple check , this means, that check will be work from Zabbix Server.
In my case, I needed to check net.tcp.service[tcp,192.168.54.20,4052] on another host. When I used type Simple check, probably, Zabbix server tried to check port 4052 in ip-address 192.168.54.20. But it doesn't have connectivity with this network and was searching in ownself local network.

[Bdolnik]

After intensive search I found the solution. By default Zabbix server blocks all the ports except some (22,80,433). To change the behavior in RH8 you need to grant it permission to the can_network by doing following:
setsebool -P zabbix_can_network on
Works like a charm after this !