MySQL active/standby hot standby and mysql active/standby

Source: Internet
Author: User

MySQL active/standby hot standby and mysql active/standby

1. Slave_IO_Running: No

mysql> show slave status\G*************************** 1. row ***************************               Slave_IO_State:                  Master_Host: 192.16.10.21                  Master_User: cahms                  Master_Port: 3306                Connect_Retry: 60              Master_Log_File: mysql-bin.000003          Read_Master_Log_Pos: 20398               Relay_Log_File: mysqld-relay-bin.000001                Relay_Log_Pos: 4        Relay_Master_Log_File: mysql-bin.000003             Slave_IO_Running: No            Slave_SQL_Running: Yes              Replicate_Do_DB:          Replicate_Ignore_DB:           Replicate_Do_Table:       Replicate_Ignore_Table:      Replicate_Wild_Do_Table:  Replicate_Wild_Ignore_Table:                   Last_Errno: 0                   Last_Error:                 Skip_Counter: 0          Exec_Master_Log_Pos: 20398              Relay_Log_Space: 106              Until_Condition: None               Until_Log_File:                Until_Log_Pos: 0           Master_SSL_Allowed: No           Master_SSL_CA_File:           Master_SSL_CA_Path:              Master_SSL_Cert:            Master_SSL_Cipher:               Master_SSL_Key:        Seconds_Behind_Master: NULLMaster_SSL_Verify_Server_Cert: No                Last_IO_Errno: 1593                Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have                                equal MySQL server ids; these ids must be different for replication to                                work (or the --replicate-same-server-id option must be used on slave but                                this does not always make sense; please check the manual before using                               it).               Last_SQL_Errno: 0               Last_SQL_Error:1 row in set (0.00 sec)

(1) master and slave have equal MySQL server ids
[Solution]
Modify the server-id value under/etc/my. cnf to ensure that the server-id of master and slave is different;

(2) Error reading packet from server:

Access denied; you need the replication slave privilege for this operation (server_errno = 1227)

[Solution] The master server does not have enough replication permissions to re-grant permissions.

> Grant replication slave on *. * to 'uname' @ 'peer ip address 'identified by 'Password';> flush privileges;
== e.g ==
> grant replication slave on *.* to 'root'@'192.16.10.21'     identified by 'root';> grant replication slave on *.* to 'root'@'192.16.10.23'   identified by 'root';

2. Slave_IO_State:

Waiting to reconnect after a failed master event readmysql> show slave status\G*************************** 1. row ***************************               Slave_IO_State: Waiting to reconnect after a failed master event read                  Master_Host: 192.16.10.231                  Master_User: cahms                  Master_Port: 3306                Connect_Retry: 60              Master_Log_File: mysql-bin.000003          Read_Master_Log_Pos: 106               Relay_Log_File: mysqld-relay-bin.000001                Relay_Log_Pos: 4        Relay_Master_Log_File: mysql-bin.000003             Slave_IO_Running: No            Slave_SQL_Running: Yes              Replicate_Do_DB:          Replicate_Ignore_DB:           Replicate_Do_Table:       Replicate_Ignore_Table:      Replicate_Wild_Do_Table:  Replicate_Wild_Ignore_Table:                   Last_Errno: 0                   Last_Error:                 Skip_Counter: 0          Exec_Master_Log_Pos: 106              Relay_Log_Space: 106              Until_Condition: None               Until_Log_File:                Until_Log_Pos: 0           Master_SSL_Allowed: No           Master_SSL_CA_File:           Master_SSL_CA_Path:              Master_SSL_Cert:            Master_SSL_Cipher:               Master_SSL_Key:        Seconds_Behind_Master: NULLMaster_SSL_Verify_Server_Cert: No                Last_IO_Errno: 0                Last_IO_Error:               Last_SQL_Errno: 0               Last_SQL_Error:1 row in set (0.00 sec)

[Solution]

> grant replication slave on *.* to 'root'@'192.16.10.228'  identified by 'root';> grant replication slave on *.* to 'root'@'192.16.10.231'     identified by 'root';> flush privileges;

3. Another MySQL daemon already running with the same unix socket.

The reason is that multiple Mysql processes use the same socket. Two solutions:

The first is to immediately shut down and use the command shutdown-h now to shut down. After the shutdown is started, the process stops.

The second one is to rename the mysql. sock file directly. You can also delete it. We recommend that you rename it.
Then you can start mysql.

Below are the original foreign documents

To prevent the problem from occurring, you must perform a graceful
Shutdown of the server from the command line rather than powering off
The server.

# shutdown -h now

This will stop the running services before powering down the machine.
Based on Centos, an additional method for getting it back up again when you run into this problem is to move mysql. sock:

# mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak# service mysqld start

Restarting the service creates a new entry called mqsql. sock

Hot recommendations

  • LNMP environment setup-Nginx

  • Configure the local YUM source in RHEL6.5

  • Installing and using Zabbix in Ubuntu

  • Troubleshooting of MySQL dual-master hot standby

  • Rsync synchronization error handling
  • Fix Elementary Boot Screen (plymouth UTH)
    After Installing Nvidia Drivers
  • LNMP environment setup-MySQL
  • Shell Step by Step (3) -- Stdin & if
  • Shell Step by Step (4) -- Cron & Echo

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger | Copyright©2011-2015, Kallen Ding, All Rights Reserved.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.