[ZBX-23963] When zabbix connects to a read-only database instance, the zabbix service immediately stops Created: 2024 Jan 19  Updated: 2024 Jan 22

Status: Open
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: roy_li Assignee: Tomass Janis Bross
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: AmazonLinux2
Zabbix Server Version: 6.0.6
Database: AWS RDS for MySQL
Deployment Architecture: 2 Zabbix server + RDS for MySQL


Attachments: JPEG File image-2024-01-19-14-36-41-415.png     JPEG File image-2024-01-19-14-36-53-733.png    

 Description   

Steps to reproduce:

  1. RDS MySQL Database Minor Version Upgrades via Blue-Green Deployment
  2. When the upgrade is complete and there is an instance switchover, the old instance becomes a read-only instance
  3. Zabbix servers still connects to old instance due to DNS caching
  4. Zabbix servers configured with ha mode stopped the zabbix service at the same time due to connected read-only instances

Result:
See screenshot...

**

Expected:
The zabbix server should stop the service when it detects that the database cannot be inserted and continues to fail to execute for several minutes before stopping the service.

Otherwise, this Zabbix high availability means nothing. Because this problem connecting to a read-only instance could probably be recovered after 1 minute, and it's so weird that the zabbix service actually just stops when it detects the anomaly.

 Comments   
Comment by roy_li [ 2024 Jan 22 ]

Hi Tomass Janis Bross 

 

How can this problem be avoided?

For me, as the zabbix server has been configured for high availability, it shouldn't all be down at the same time when it faces these kinds of exceptions.

Generated at Sat Apr 12 10:57:27 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.