Could not connect to remote node database, primary server down in cluster
"Could not connect to remote node database" Primary server is down. I get the above error with cluster enabled.
synopsis: This article provides troubleshooting steps to resolve the "Could not connect to remote node database" error in a MySQL cluster by verifying port accessibility, SELinux settings, and reviewing application logs.
step 1. Ensure that the MySQL ports are open in firewall and that secondary is able to connect to primary on the MySQL port and is able to log in as the user specified in /usr/local/etc/ezlogin/ez.conf. This should work from primary to secondary and vice versa.
Use the following command to check that the MySQL ports are open in the firewall:
sudo firewall-cmd --permanent --list-ports | grep 3306
To check the MySQL Connection:
Primary to Secondary:
mysql -h secondary_server_ip -u username -p
Secondary to Primary:
mysql -h primary_server_ip -u username -p
step 2. Ensure that SELinux is not interfering.
root@gateway ~]# sestatus
SELinux status: enabled
If SELinux is enabled, try disabling it and reboot then test again
root@gateway ~]# vim /etc/sysconfig/selinux
SELINUX=disabled
step 3. Check for the error messages in the application logs on the server.
- The logs files are stored in the /{system folder specified at the time of installation}. You can find the path by checking the system_folder variable in /usr/local/etc/ezlogin/ez.conf.
- The web application log file path would be /{system folder}/applicaton/logs/
Related Articles
Basic MySQL commands for troubleshooting database related issues in Ezeelogin