Hello
We've just migrate Zabbix 3.2 to 3.4 on a Debian 8.
It works for one day and then the zabbix-server process stop and start.
In /var/log/syslog :
Can you help us ?
Thanks.
We've just migrate Zabbix 3.2 to 3.4 on a Debian 8.
It works for one day and then the zabbix-server process stop and start.
In /var/log/syslog :
Code:
Aug 31 14:57:02 naboo systemd[1]: Starting Zabbix Server... Aug 31 14:57:02 naboo systemd[1]: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start. Aug 31 14:57:02 naboo systemd[1]: Started Zabbix Server. Aug 31 14:57:02 naboo systemd[1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE Aug 31 14:57:02 naboo kill[8440]: kill: invalid argument S Aug 31 14:57:02 naboo kill[8440]: Usage: Aug 31 14:57:02 naboo kill[8440]: kill [options] <pid> [...] Aug 31 14:57:02 naboo kill[8440]: Options: Aug 31 14:57:02 naboo kill[8440]: <pid> [...] send signal to every <pid> listed Aug 31 14:57:02 naboo kill[8440]: -<signal>, -s, --signal <signal> Aug 31 14:57:02 naboo kill[8440]: specify the <signal> to be sent Aug 31 14:57:02 naboo kill[8440]: -l, --list=[<signal>] list all signal names, or convert one to a name Aug 31 14:57:02 naboo kill[8440]: -L, --table list all signal names in a nice table Aug 31 14:57:02 naboo kill[8440]: -h, --help display this help and exit Aug 31 14:57:02 naboo kill[8440]: -V, --version output version information and exit Aug 31 14:57:02 naboo kill[8440]: For more details see kill(1). Aug 31 14:57:02 naboo systemd[1]: zabbix-server.service: control process exited, code=exited status=1 Aug 31 14:57:02 naboo systemd[1]: Unit zabbix-server.service entered failed state. Aug 31 14:57:13 naboo systemd[1]: zabbix-server.service holdoff time over, scheduling restart. Aug 31 14:57:13 naboo systemd[1]: Stopping Zabbix Server... Aug 31 14:57:13 naboo systemd[1]: Starting Zabbix Server... Aug 31 14:57:13 naboo systemd[1]: PID file /run/zabbix/zabbix_server.pid not readable (yet?) after start. Aug 31 14:57:13 naboo systemd[1]: zabbix-server.service: Supervising process 8445 which is not our child. We'll most likely not notice when it exits. Aug 31 14:57:13 naboo systemd[1]: Started Zabbix Server. Aug 31 14:57:13 naboo systemd[1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE Aug 31 14:57:13 naboo kill[8447]: kill: invalid argument S Aug 31 14:57:13 naboo kill[8447]: Usage: Aug 31 14:57:13 naboo kill[8447]: kill [options] <pid> [...] Aug 31 14:57:13 naboo kill[8447]: Options: Aug 31 14:57:13 naboo kill[8447]: <pid> [...] send signal to every <pid> listed Aug 31 14:57:13 naboo kill[8447]: -<signal>, -s, --signal <signal> Aug 31 14:57:13 naboo kill[8447]: specify the <signal> to be sent Aug 31 14:57:13 naboo kill[8447]: -l, --list=[<signal>] list all signal names, or convert one to a name Aug 31 14:57:13 naboo kill[8447]: -L, --table list all signal names in a nice table Aug 31 14:57:13 naboo kill[8447]: -h, --help display this help and exit Aug 31 14:57:13 naboo kill[8447]: -V, --version output version information and exit Aug 31 14:57:13 naboo kill[8447]: For more details see kill(1). Aug 31 14:57:13 naboo systemd[1]: zabbix-server.service: control process exited, code=exited status=1 Aug 31 14:57:13 naboo systemd[1]: Unit zabbix-server.service entered failed state. Aug 31 14:57:23 naboo systemd[1]: zabbix-server.service holdoff time over, scheduling restart. Aug 31 14:57:23 naboo systemd[1]: Stopping Zabbix Server... Aug 31 14:57:23 naboo systemd[1]: Starting Zabbix Server...
Thanks.