Sometimes Zabbix can be a real pain to troubleshoot if you don't know where to look. Here are some pointers:
/var/log/zabbix/
file. If something fails, this is probably the second place to look at.setsebool -P zabbix_can_network on
sealert -a /var/log/audit/audit.log
SELinux will tell you what it has blocked and why, and it will also try to tell you how to undo this. Most of the time this will work however it's not perfect and sometimes you have to investigate further. To make the sealert
parameter working you probably have to install the setroubleshoot
package.
For example, creating your own fping
module could be done like this:
grep fping /var/log/audit/audit.log | audit2allow -M zabbix_fping semodule -i zabbix_fping.pp
log
file. However, be careful as increasing the log
level will give you a lot of information. Since Zabbix 2.4, it is possible to do this without restarting the Zabbix server:zabbix_server -c /etc/zabbix/zabbix_server.conf -R log_level_increase
zabbix_server -c /etc/zabbix/zabbix_server.conf -R log_level_increase="http poller"
With the decrease
option instead of the increase
option you can return back to log level 3.
telnet <ip> <port>
.msgAuthoritativeEngineID
(also known as snmpEngineID
or "Engine ID
") is never shared by two devices as this will give rise to problems.