Project scenario:
Master slave connection method
Problem Description:
Last_IO_Errno: 2003 Last_IO_Error: error connecting to master '[email protected]:3306' - retry-time: 60 retries: 7
Cause analysis:
-
- when trying to log in to the master database to copy users from the server, an error of 113 is found
[ [email protected] mysql]# mysql -urepl -p123 -h 192.168.8.131 -P 3306 mysql: [Warning] Using a password on the command line interface can be insecure. Error 2003 (HY000): can't connect to MySQL server on '192.168.8.131' (113)
-
- check whether the main server firewall is closed. It is found that it is closed. It is speculated that the port is not open
systemctl status firewalld service
-
- 3. Check whether the 3306 port of the main database is open to the public. It is found that it is no
firewall CMD -- zone = public -- Query port = 3306/TCP
-
- 4 Open 3306 port
firewall CMD -- zone = public -- add port = 3306/TCP -- permanent
-
- 5 Update firewall
firewall CMD -- reload
Solution:
The master-slave replication connecting problem is mainly caused by the master and slave libraries can not be connected, after this problem found that although the firewall has been closed, but the port is not necessarily open to the public state, you need to set their own.
Read More:
- SSH Connect Service Error: Could not connect to ‘xxx.xxx.xx.xx‘ (port 22): Connection failed.
- Linux: How to Solve Rabbitmq Plug-in Install Error
- Error Running Context: The server unexpectedly closed the connection
- [Solved] Centos7 firewalld startup error: Failed to start firewalld.service: Unit is masked.
- [Solved] Node uploads files to FTP server error: timed out while making data connection
- [Solved] minio Failed to Upload File Error: The difference between the request time and the server‘s time is too large.
- Install and start the tftp-server server and possible solutions to Redirecting to /bin/systemctl restart xinetd.service problems
- [Solved] Keepalived Configurate Error: Unicast peers are not supported in strict mode
- The solution to the crash loop back off error of coredns in k8s deployment
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code
- Firewall Status View Error: service iptables status [How to Solve]
- Centos6.8vnc error: connect: Connection refused 10061
- [Solved] docker Error: System has not been booted with systemd as init system (PID 1). Can‘t operate. Failed to con
- [Solved] Web server failed to start. Port 8080 was already in use.
- Job for network.service failed [How to Solve]
- How to Solve NPM Error: listen EADDRINUSE 127.0.0.1:8080
- Linux Install Docker Error: Failed to restart docker.service: Unit docker.service not found.
- See system logs and ‘systemctl status docker.service‘ for details
- U-boot NFS download file error: loading: * * * error: File lookup fail solution
- [Solved] Gbase Install Error: service cgconfig is not exist on hosts