I did an upgrade on a server and one proxy, the server runs no issue but the proxy will not start. Both of these systems are PI 4 with 8gb ram for the server and 4gb ram on the proxy.
On the proxy I am not getting the logging to start I am getting a message in the journal I see this error:
pi@proxy1:/etc/zabbix $ journalctl -xe
-- Support: https://www.debian.org/support
--
-- The unit zabbix-proxy.service has entered the 'failed' state with result 'signal'.
Sep 30 09:22:18 proxy1.thewayiseeit.net systemd[1]: Failed to start Zabbix Proxy.
-- Subject: A start job for unit zabbix-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zabbix-proxy.service has finished with a failure.
--
-- The job identifier is 4378 and the job result is failed.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: zabbix-proxy.service: Scheduled restart job, restart counter is at 47.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit zabbix-proxy.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: Stopped Zabbix Proxy.
-- Subject: A stop job for unit zabbix-proxy.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit zabbix-proxy.service has finished.
--
-- The job identifier is 4443 and the job result is done.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: Starting Zabbix Proxy...
-- Subject: A start job for unit zabbix-proxy.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zabbix-proxy.service has begun execution.
--
-- The job identifier is 4443.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: zabbix-proxy.service: Control process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zabbix-proxy.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: zabbix-proxy.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zabbix-proxy.service has entered the 'failed' state with result 'signal'.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: Failed to start Zabbix Proxy.
-- Subject: A start job for unit zabbix-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zabbix-proxy.service has finished with a failure.
--
-- The job identifier is 4443 and the job result is failed.
I have dropped the database and recreated it.
These were running zabbix 6.4 till the upgrade with no issues.
On the proxy I am not getting the logging to start I am getting a message in the journal I see this error:
pi@proxy1:/etc/zabbix $ journalctl -xe
-- Support: https://www.debian.org/support
--
-- The unit zabbix-proxy.service has entered the 'failed' state with result 'signal'.
Sep 30 09:22:18 proxy1.thewayiseeit.net systemd[1]: Failed to start Zabbix Proxy.
-- Subject: A start job for unit zabbix-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zabbix-proxy.service has finished with a failure.
--
-- The job identifier is 4378 and the job result is failed.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: zabbix-proxy.service: Scheduled restart job, restart counter is at 47.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit zabbix-proxy.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: Stopped Zabbix Proxy.
-- Subject: A stop job for unit zabbix-proxy.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit zabbix-proxy.service has finished.
--
-- The job identifier is 4443 and the job result is done.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: Starting Zabbix Proxy...
-- Subject: A start job for unit zabbix-proxy.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zabbix-proxy.service has begun execution.
--
-- The job identifier is 4443.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: zabbix-proxy.service: Control process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zabbix-proxy.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: zabbix-proxy.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zabbix-proxy.service has entered the 'failed' state with result 'signal'.
Sep 30 09:22:28 proxy1.thewayiseeit.net systemd[1]: Failed to start Zabbix Proxy.
-- Subject: A start job for unit zabbix-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zabbix-proxy.service has finished with a failure.
--
-- The job identifier is 4443 and the job result is failed.
I have dropped the database and recreated it.
These were running zabbix 6.4 till the upgrade with no issues.