Zabbix agent no longer able to listen on apache's new port 81

[snetadmin]

Hi guys,

We've updated the apache2 port to listen to 81 today and since then, our Zabbix agent is reporting it down even though the service is up and running on the server.

Has anyone seen this issue and what fix should be implemented for this?

[tim.mooney]

That depends upon what item(s) and trigger(s) you're using to monitor Apache httpd. If you're using a pre-defined template then you need to examine the documentation for that template to see if there's a way (likely via a macro) to adjust the port that the template uses for monitoring httpd.

[snetadmin]

Thank you for the information.

However, I'm running into a strange issue. We have two ubuntu servers that we changed the apache2 port to 81 and the zabbix agent is only reporting one of them as down while the other one is reporting as up which doesn't make sense.

I compared both servers and they are both identical on the port configuration setup.

They are both using same template.

[vladimir_lv]

Check the macros {$APACHE.STATUS.PORT} on the host.

[cyber]

selinux? https://www.systutorials.com/docs/li...abbix_selinux/

If you want to determine whether zabbix can connect to all TCP ports, you must turn on the zabbix_can_network boolean. Disabled by default.

setsebool -P zabbix_can_network 1

[snetadmin]

Hi Cyber,

When I run the command setsebool -P zabbix_can_network 1, I'm seeing the following error message below.

sudo setsebool -P zabbix_can_network 1
Cannot set persistent booleans without managed policy.

How can I resolve this issue?

Also, regarding to checking the macro for {$APACHE.STATUS.PORT}, I do not see that zabbix item listed on the host.
Does this need to be created? In comparison between the two Ubuntu servers running on the same Apache port 81, this Zabbix Item is not listed on either host.