Cachet and Zabbix-cachet run inside containers, deployed in a Kubernetes cluster. Zabbix runs on a VM.
Problem
We have an automatic patch process that stops the Zabbix server before upgrading our MySQL cluster. This process is executed on a monthly basis. After the cluster has been upgraded and Zabbix is started again, Zabbix-cachet is no longer restoring the connection to Zabbix. The result of this is that no new incidents are created until the zabbix-cachet container is restarted.
Environment:
Cachet: 2.3.18 Zabbix-cachet: 1.3.7 Zabbix: 4.0.29
Cachet and Zabbix-cachet run inside containers, deployed in a Kubernetes cluster. Zabbix runs on a VM.
Problem
We have an automatic patch process that stops the Zabbix server before upgrading our MySQL cluster. This process is executed on a monthly basis. After the cluster has been upgraded and Zabbix is started again, Zabbix-cachet is no longer restoring the connection to Zabbix. The result of this is that no new incidents are created until the zabbix-cachet container is restarted.
The following message occurs every 2 minutes:
2021-04-09 07:18:49 DEBUG: (Trigger Watcher) Resetting dropped connection: <hostname>
Full log:
Once the zabbix-cachet container is restarted past incidents are updated in Cachet.