Test in environment:

1. VMware Workstation 17 Pro v17.6.3
2. zabbix-server-mysql 7.4.3; zabbix-proxy-mysql 7.4.7, zabbix-agent 7.4.7
3. agent monitored with proxy
4. In my case proxy and server were ion separate machines
5. I didn't catch such effect on proxy until started monitoring with it.

Steps to reproduce:

1. Connect to machines from the VMware
2. Disable mysql

   systemctl stop mysqld
   

3. Make sure that server/proxy tries to connect to DB

   # tail /var/log/zabbix/zabbix_server.log
   1729485:20251125:211208.621 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local server through socket '/var/lib/mysql/mysql.sock' (2)
   1729485:20251125:211208.621 database is down: reconnecting in 10 seconds
   

4. Reboot OS from command line:

   # reboot
   

5. Try this steps for both server and proxy - the behaviour the same

6. Result:
   Machines start rebooting but can't:
   

Expected:
After 60min unsuccessful connection to DB zabbix server/proxy should be stopped itself.