Birmingham mumbai

[
 347 
]
The output should be similar to the following:
tcp   LISTEN 0      80                               0.0.0.0:3306       
0.0.0.0:*            users:(("mysqld",pid=9768,fd=23)) 
If you see that the service is listening on 
127.0.0.1:3306
 instead, that means it's only 
accepting connections from localhost. Earlier in this section, I mentioned changing 
the 
bind
 address in the 
/etc/mysql/mariadb.conf.d/50-server.cnf
 file. Make sure 
you've already done that and restart 
mariadb
. During my tests, I've actually had one 
situation where the 
mariadb
 service became locked after I made this change, and 
attempting to restart the process did nothing (I ended up having to reboot the entire 
server, which is not typically something you'd have to do). Once the server came 
back up, it was listening for connections from the network.
If you receive errors on the secondary server when you run 
SHOW SLAVE STATUS \G
, 
with regards to authentication, make sure you've run 
FLUSH PRIVILEGES
 on the 
primary server. Even if you have, run it again to be sure. Also, double-check that 
you're synchronizing with the correct username, IP address, and password. For your 
convenience, here's the command we ran on the primary server to grant replication 
permissions:
GRANT REPLICATION SLAVE ON *.* to 'replicate'@'192.168.1.204' 
identified by 'password'; 
FLUSH PRIVILEGES 
Here's the command that we ran on the secondary server:
CHANGE MASTER TO MASTER_HOST="192.168.1.184", MASTER_USER='replicate', 
MASTER_PASSWORD='password'; 
Finally, make sure that your primary database and the secondary database both 
contain the same databases and tables. The primary server won't be able to update 
a database on the secondary server if it doesn't exist there. Flip back to my example 
usage on 
mysqldump
 if you need a refresher. You should only need to use 
mysqldump
 
and import the database onto the secondary server once, since after you get the 
replication going, any changes made to the database on the primary server should 
follow over to the secondary. If you have any difficulties with the 
mysqldump
 
command, you can manually create 
mysampledb
 and the 
Employees
 table on the 
secondary server, which is really all it needs for synchronization to start.
Synchronization should then begin within a minute, but you can execute 
STOP SLAVE
, 
followed by 
START SLAVE
, on the secondary server to force it to try to synchronize 
again without waiting.

---

Managing Databases