If you have configured Disaster Recovery DR for Gateway, or database you may notice that the replication keeps breaking during patch updates or rebooting.
All Supported versions of Gateway.
The secondary DB may have the my.cnf setting log_slave_updates=OFF. Per Mysql docs log_slave_updates must be ON for this scenario.
You can further review the documentation on the mysql site.
1) Stop slave on all database nodes.
2) Update the /etc/my.cnf file on secondary database server "log_slave_updates=ON"
3) restart mysql service.
4) On the Primary and DR node, run "start slave;" to restart replication.
5) Check the status of the replication on all nodes.
Note: If replication is not running / starting at this time you can restart replication using the "restart_replication.sh" script .