-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 7.0.24rc1, 7.4.8rc1, 8.0.0beta1 (master)
-
Component/s: Proxy (P), Server (S)
Zabbix Server fails to log the final shutdown message when it terminates due to a read-only database error. While the server correctly identifies the issue and attempts to reconnect, the standard "stopped" signature is missing from the logs upon exit.
Steps to reproduce:
- Set the PostgreSQL database to read-only mode.
- Start zabbix_server and observe the log output.
Result:
133123:20260224:090232.392 Starting Zabbix Server. Zabbix 8.0.0beta1 (revision {ZABBIX_REVISION}).
133123:20260224:090232.393 ****** Enabled features ******
133123:20260224:090232.393 SNMP monitoring: YES
133123:20260224:090232.393 IPMI monitoring: NO
133123:20260224:090232.393 Web monitoring: YES
133123:20260224:090232.393 VMware monitoring: YES
133123:20260224:090232.393 SMTP authentication: YES
133123:20260224:090232.393 ODBC: NO
133123:20260224:090232.393 SSH support: NO
133123:20260224:090232.393 IPv6 support: YES
133123:20260224:090232.393 TLS support: NO
133123:20260224:090232.393 ******************************
133123:20260224:090232.393 using configuration file: /home/zabbix/workspace/master/etc/zabbix_server.conf
133123:20260224:090232.439 database is read-only: reconnecting in 10 seconds
133123:20260224:090242.453 database is read-only: reconnecting in 10 seconds
133123:20260224:090252.507 database is read-only: reconnecting in 10 seconds
133123:20260224:090302.521 database is read-only: reconnecting in 10 seconds
133123:20260224:090312.535 database is read-only: reconnecting in 10 seconds
133123:20260224:090322.548 database is read-only: reconnecting in 10 seconds
133123:20260224:090332.560 database is read-only: Exiting...
Expected:
134982:20260224:092258.556 Zabbix Server stopped. Zabbix 8.0.0beta1 (revision {ZABBIX_REVISION}).
