zabbix agent security upgrade 1.8.20

[foru]

Hi,

I'm currently using zabbix 1.8.8 with agent 1.8.17 and 1.8.18 deployed on my servers.

I choosed to deploy upgraded version (1.8.20-1.el6) of those agents from epel-release-6-8.noarch (with yum)

As soon as the agent has been upgraded on some servers, the number of running processes is considered as 0 by the server, (except for zabbix_agentd).

Do you have any idea if there is a something to reconfigure, or if this is an incompability between the server and the agent?

Thanks for your eventuals answers

[bsdtux]

Can you check through your logs on the zabbix server. The Logs should located at /var/log/zabbix/zabbix_agentd.log and post any new errors since the upgrade.

This will be a starting point. Also I read through this blog from zabbix and it does state that all agents are backwards compatible. http://blog.zabbix.com/zabbix-interv...vladishev/792/

[foru]

Thanks for your answer !
/var/log/zabbix/zabbix.log is empty on the monitoring server.
On the monitored server, everything seems normal :

  1706:20140311:101057.188 Starting Zabbix Agent [SPVCOWEB01]. Zabbix 1.8.20 (revision 42524).
  1713:20140311:101057.206 agent #2 started[listener]
  1714:20140311:101057.207 agent #3 started[listener]
  1715:20140311:101057.208 agent #4 started [active checks]
  1712:20140311:101057.208 agent #1 started[listener]
  1711:20140311:101057.208 agent #0 started [collector]

When I try to look the running processes with zabbix agent, it's working :

 zabbix_agentd -t "proc.num[httpd]"
proc.num[httpd]                               [u|9]

but still 0 running process detected on my monitoring server

Edit : The problem comes from SELinux : if disabled, everything is working find. I'm trying to find a solution to make them work together.

Edit 2 : Fixed the problem with Joshua Preston's solution :

https://support.zabbix.com/browse/ZBX-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel#issue-tabs

I don't like this solution, but this works

[bsdtux]

Yeah I have always done the bad thing and just disabled SELINUX because it is a pain in the neck to deal with.