Zabbix Agent and Proxy one Debian Jessie server

[Dexoid]

Hello.
I have Zabbix Agent and proxy on one server Debian Jessie.
I use http://repo.zabbix.com/zabbix/2.4/debian jessie main.
There is a problem at startup:
Sep 24 06:31:53 gw zabbix-agent[855]: mkdir: cannot create directory «/var/run/zabbix»: File exists
Sep 24 06:31:53 gw systemd[1]: zabbix-agent.service: control process exited, code=exited status=1
Sep 24 06:31:53 gw systemd[1]: Failed to start LSB: Start zabbix-agent daemon.
Sep 24 06:31:53 gw systemd[1]: Unit zabbix-agent.service entered failed state.
Sep 24 06:31:56 gw zabbix-proxy[858]: Starting Zabbix proxy daemon: zabbix_proxy.
Sep 24 07:59:46 gw zabbix-proxy[892]: mkdir: cannot create directory «/var/run/zabbix»: File exists
Sep 24 07:59:46 gw systemd[1]: zabbix-proxy.service: control process exited, code=exited status=1
Sep 24 07:59:46 gw systemd[1]: Failed to start LSB: Start zabbix-proxy daemon.
Sep 24 07:59:46 gw systemd[1]: Unit zabbix-proxy.service entered failed state.

perhaps because that systemd run in parallel?

[Stefan_D]

Hi,

does your problem still exist?

I had something similar with a 2.4.6 installation on SLES12.
I simply commented out the pidfile parts in the configuration files, because
systemd calls zabbix-server and I didn't see what I would need it for. :-)

Regards

SD

[adamdcorus]

Hello

I am also having this experience.

One of my servers simply refuses to restart zabbix agent. I have tried everything.

sudo /etc/init.d/zabbix-agent restart

[....] Restarting zabbix-agent (via systemctl): zabbix-agent.serviceJob for zabbix-agent.service failed because the control process exited with error code. See "systemctl status zabbix-agent.service" and "journalctl -xe" for details.
 failed!

systemctl status zabbix-agent.service -l

May 26 11:12:46 ops1 systemd[1]: Starting LSB: Start zabbix-agent daemon...
May 26 11:12:46 ops1 systemd[1]: zabbix-agent.service: Control process exited, code=exited status=1
May 26 11:12:46 ops1 systemd[1]: Failed to start LSB: Start zabbix-agent daemon.
May 26 11:12:46 ops1 systemd[1]: zabbix-agent.service: Unit entered failed state.
May 26 11:12:46 ops1 systemd[1]: zabbix-agent.service: Failed with result 'exit-code'.
May 26 11:12:46 ops1 zabbix-agent[7567]: * Starting Zabbix agent zabbix_agentd

The only thing that has fixed this in previous weeks is a full server restart, which is unfeasible in the long term.

How can I troubleshoot and fix this issue?

Adam D.

[adamdcorus]

Does anybody from Zabbix.com actually participate in this forum?

This issue still remains. A little help would be appreciated.

ad

[scriptracer]

Hello!

Problem may be in zabbix_agentd.conf
Please show cat

[Jeevananthan]

Hi, I am also facing the same while start zabbiz-agent "Job for zabbix-agent.service failed because the control process exited with error code. See "systemctl status zabbix-agent.service" and "journalctl -xe" for details"

Any one can help us to fix.

[dimir]

Dexoid , do you use multiple agent/proxy/server instances on the same host?

[Jeevananthan]

alamin ,I remove older version of zabbix client and installed new version now working fine. Thanks

[dimir]

Yeah, noticed this is an old issue only after posting. Good luck with new Zabbix! ;-)