Zabbix Proxy failing to start

[Parasin]

Hi all,

I am trying to create a new Zabbix Proxy server on CentOS7 and I am having problems getting it to start after yum install. when using

systemctl start zabbix-proxy

I get the following error:

[root@localhost ~]# systemctl status zabbix-proxy
zabbix-proxy.service - Zabbix Proxy
   Loaded: loaded (/usr/lib/systemd/system/zabbix-proxy.service; enabled)
   Active: failed (Result: start-limit) since Mon 2015-02-16 12:13:28 EST; 5s ago
  Process: 11069 ExecStart=/usr/sbin/zabbix_proxy -c /etc/zabbix/zabbix_proxy.conf (code=exited, status=0/SUCCESS)
 Main PID: 1787 (code=exited, status=1/FAILURE)

Feb 16 12:13:28 localhost.localdomain systemd[1]: zabbix-proxy.service never wrote its PID file. Failing.
Feb 16 12:13:28 localhost.localdomain systemd[1]: Failed to start Zabbix Proxy.
Feb 16 12:13:28 localhost.localdomain systemd[1]: Unit zabbix-proxy.service entered failed state.
Feb 16 12:13:28 localhost.localdomain systemd[1]: zabbix-proxy.service holdoff time over, scheduling restart.
Feb 16 12:13:28 localhost.localdomain systemd[1]: Stopping Zabbix Proxy...
Feb 16 12:13:28 localhost.localdomain systemd[1]: Starting Zabbix Proxy...
Feb 16 12:13:28 localhost.localdomain systemd[1]: zabbix-proxy.service start request repeated too quickly...art.
Feb 16 12:13:28 localhost.localdomain systemd[1]: Failed to start Zabbix Proxy.

I tried to change the zabbix-proxy.service file to this, per another thread in the forum:

ExecStart=/usr/sbin/zabbix_proxy -c /etc/zabbix/zabbix_proxy.conf

UPDATE: Upon debugging a bit more, I found this gem:

Feb 16 12:23:23 localhost.localdomain systemd[1]: PID file /run/zabbix/zabbix_proxy.pid not readable (yet?) afte
Feb 16 12:23:23 localhost.localdomain systemd[1]: zabbix-proxy.service never wrote its PID file. Failing.
Feb 16 12:23:23 localhost.localdomain systemd[1]: Failed to start Zabbix Proxy.
-- Subject: Unit zabbix-proxy.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

I believe that the proxy is not able to create a PID file... Any ideas on how to resolve?

[Parasin]

Adding PID data from zabbix_proxy.conf

Here is the pidFile option from the zabbix_proxy.conf file.

### Option: PidFile
#       Name of PID file.
#
# Mandatory: no
# Default:
# PidFile=/tmp/zabbix_proxy.pid

# PidFile=/var/run/zabbix/zabbix_proxy.pid

UPDATE:

I went ahead an started up the agent for this server, and it works correctly and is talking to the Zabbix server. however, the Zabbix proxy is still experiencing the same error.


***Possible bug present when installing zabbix proxy on RHEL7***
using yum install zabbix-proxy after installing the erel repository and updating all dependencies, Zabbix proxy is not writing the PID file for zabbix-proxy.service

[monjwf]

Can you post your zabbix_agent and zabbix_proxy config files.

I am having issues starting zabbix_agent (v 2.4) on centos 7. Same thing for the proxy.

Looks like the systemd unit file has changed since zabbix 2.2

[Parasin]

Unfortunately, I do not have this server anymore; it was a VM and after having so much trouble with using CentOS7 I decided to downgrade to CentOS6.

I can report that my CentOS6 Proxy works perfectly. I think that there may have been changes to the OS that impact certain filesystem operations, which Zabbix has not yet accounted for.

If you'd like, I can post my working proxy and agent config from my CentOS6 setup.

[monjwf]

@parasin

thanks. I have 6.x working fine but I am testing 7.1 which is to be deployed in the near future. Thank you though !

[Atsushi]

If you install by using the repository by Zabbix SIA, you can start up normally on CentOS 7.
not epel.

If you use on CentOS 7.1.1503, you must update trousers package to trousers-0.3.11.2-4.el7_1 or newer.