Speed up your computer in minutes
Last week some of our users reported bugs on com_register_slave.
We are suffering from an existing master copy of a server to a master copy on two servers, and we may notwhere did not mention IP address 188.8.131.52 but we get the exact below error as.
Last_IO_Error: COM_REGISTER_SLAVE main command error: Permission denied 'user'@'11 for user.12.13.Password: 18' (using YES) (Errno: 1045)
Set up replication and see if it works.
Create an SSH tunnel with stunnel.All
test tunnel works with:
main mysql -u 10 -h.0.0.-P 1 -p
mysql -usa 3310 -h root 127.0.0.1 -P -p
This 3310 is NOT working
mysql -u root -t localhost -P 3310 -p
stop becoming an expert on master_host=’10.0.0.1′, master_user=’xxxx’, master_port=3310 … ;
Last IO=… error.Access.denied.for.user.’xxxx’@’localhost’….
The problem seems to be that it is trying to connect to the localhost, not the IP address to the server (10.0.0.1).
Localhost can be a problem similar to this article:
If instead of the IP address of the localhost (192.168.5.In we 45) we use the above mysql connection string, we will get good errors:
I believe Mariadb is trying to use plocal working socket, not 127.0.01 in addition to 10.0.0.1
error: no packages available at. : received 1 2 expected: At parser.write (/vagrant/zongji/node_modules/mysql/lib/protocol/Parser.js:39:19) protocol at.write(/vagrant/zongji/node_modules/mysql/lib/protocol/Protocol.js:39:16) In Socket.
(/vagrant/zongji/node_modules/mysql/lib/Connection.js:96:28) In EmitOne (events.js:96:13) Worry Socket.emitter (events.js:188:7) readableAddChunk(_stream_readable in.js:172:18) socket only for .Readable.push(_stream_readable.js:130:10) In TCP.onread (net.js:542:20) -------------------- in Protocol._enqueue (/vagrant/zongji/node_modules/mysql/lib/protocol/Protocol.js:141:48) at immediately._start [as _onImmediate] (/vagrant/zongji/index.js:203:31) In tryOnImmediate(timers.js:543:15) Process [as passed to Immediate(_immediatecallback timers].js:523:5)
This article explains how to add a new slave to an existing MySQL processing. It is possible to add a new standby server, which will allow MySQL replication without controlling the master server and without shutting down the existing cleanup server. At this time, you must stop replication of the website in order to create a current data snapshot. On the other hand, if you need to set up a new MySQL replication read dev.mysql.com – How to set up replication before replication and
- Stop at Slave
- Export found existing slave databases
- Relay-log.info and master.Copy from existing info to new slave
- Start real slave replication
- Import the mysqld dump to the new appropriate slave and continue to stop mysqld
- Edit the relay-log.info file
- Add server permission development increment
- Copy from my.cnf matrix and server id
- Start any slave new server
1. Stop replication if existing slave
Cloning virtually all downstream servers from scratch is necessary if you want to temporarily stop replication on existing downstream servers. Why? While you are eating, take a picture of the dates. Connect to the slave using the MySQL consumer and run the following command:
An existing standby server is nearly stalled and switched off the master until you start replication with the start standby command. Standby servers can usually execute SQL queries, and unless data changes are used frequently, no one will notice the push going on in the background. With Show slave status you can preview the status message and stop searching for slaves.
2. Exporting existing slave databases
Once the slave becomes available for disconnection, you can create your own snapshot of the data. With mysqldump information (or a set of databases) can usually be exported to a file.
Before running mysqldump, make sure you have enough disk space. Move my_database.sql as a new slave running scp, ftp, wget…
3. Copy relay-log.info as well as master.info from the existing server to the slave modern server
The slave replication server hasva additional small files in our data directory. Status hot These files are usually relay-log.info and go offending master.info. relay-log.info contains relay_log, filenames, relay_log location, corresponding Master name.log and corresponding master.log location, although master.info contains parameters that are logged by main server address: from server, user to make sure you are connecting to the main web (with clear password), port…Here is an example of how you can send relay-log.info and master.info to different servers:< slaves /p>
Com Register Slave 오류
Fout Op Com Register Slave
Erreur Sur Com Register Slave
Errore Su Com Register Slave
Oshibka Na Com Register Slave
Error En Com Register Slave
Fel Pa Com Register Slave
Fehler Auf Com Register Slave
Blad W Com Register Slave
Erro Em Com Register Slave