Zabbix 6.2.9 has been working fine for months, but now suddenly won't start.

[[email protected]]

We're running Zabbix 6.2.9 on Rocky 8.6. It's been running great for a long time. Suddenly the service won't start.

Here's a snippet of the system log showing the service continually restarting and failing.

Sep 26 19:48:56 mgt03.mycharts.md systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
Sep 26 19:48:56 mgt03.mycharts.md systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 3.
Sep 26 19:48:56 mgt03.mycharts.md systemd[1]: Stopped Zabbix Server.
Sep 26 19:48:56 mgt03.mycharts.md systemd[1]: Starting Zabbix Server...
Sep 26 19:48:56 mgt03.mycharts.md systemd[1]: Started Zabbix Server.
Sep 26 19:48:59 mgt03.mycharts.md kill[3194]: kill: not enough arguments
Sep 26 19:48:59 mgt03.mycharts.md systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
Sep 26 19:48:59 mgt03.mycharts.md systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
Sep 26 19:49:09 mgt03.mycharts.md systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
Sep 26 19:49:09 mgt03.mycharts.md systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 4.
Sep 26 19:49:09 mgt03.mycharts.md systemd[1]: Stopped Zabbix Server.
Sep 26 19:49:09 mgt03.mycharts.md systemd[1]: Starting Zabbix Server...
Sep 26 19:49:09 mgt03.mycharts.md systemd[1]: Started Zabbix Server.
Sep 26 19:49:11 mgt03.mycharts.md kill[3296]: kill: not enough arguments
Sep 26 19:49:11 mgt03.mycharts.md systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
Sep 26 19:49:11 mgt03.mycharts.md systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
Sep 26 19:49:21 mgt03.mycharts.md systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
Sep 26 19:49:21 mgt03.mycharts.md systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 5.
Sep 26 19:49:21 mgt03.mycharts.md systemd[1]: Stopped Zabbix Server.
Sep 26 19:49:21 mgt03.mycharts.md systemd[1]: Starting Zabbix Server...
Sep 26 19:49:21 mgt03.mycharts.md systemd[1]: Started Zabbix Server.
Sep 26 19:49:23 mgt03.mycharts.md kill[3458]: kill: not enough arguments
Sep 26 19:49:23 mgt03.mycharts.md systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
Sep 26 19:49:23 mgt03.mycharts.md systemd[1]: zabbix-server.service: Failed with result 'exit-code'.

We keep getting these messages in the zabbix server log:

47196:20230926:201355.360 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x7feb0000008d]. Crashing ...

(The full zipped zabbix server log is attached.)

The only thing that may have changed is that I migrated the VM to a different Proxmox host. That was done recently, but I don't know if it was exactly when Zabbix stopped working.

I have searched for solutions and have noticed that lots of people have encountered this issue, but the fix was usually to disable VMWare monitoring or upgrade to a new version of zabbix, but we don't do VMWare monitoring, and we're on the latest version of zabbix.

Help will be greatly appreciated.

[[email protected]]

Have I provided enough information? Looking forward to a response.

[vijayk]

Did you check the database? Is it working and connection is okay?

[[email protected]]

Did you check the database? Is it working and connection is okay?

The database is up and listening. There are no relevant errors in the error log, no hung queries, and no corrupted tables.