pay db:
jrhdpt11:/root/sbin# mysql -uroot -p'R00t,uHagt.0511' -e "show processlist" | grep backup
Warning: Using a password on the command line interface can be insecure.
832734 backup 121.43.153.147:37873 NULL Binlog Dump 129384 Master has sent all binlog to slave; waiting for binlog to be updated NULL
832752 backup dr-mysql01.zjcap.com:38021 NULL Binlog Dump 129321 Master has sent all binlog to slave; waiting for binlog to be updated NULL
mysql> show grants for backup@'%';
+-------------------------------------------------------------------------------------------------------------------+
| Grants for backup@% |
+-------------------------------------------------------------------------------------------------------------------+
| GRANT REPLICATION SLAVE ON *.* TO 'backup'@'%' IDENTIFIED BY PASSWORD '*93CCED77A19FA43FCA335E99889F351FABDA1320' |
+-------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
ZJZC数据库从120.26.57.101:
jrhdpt02:/root# set -o vi
jrhdpt02:/root# mysql -ubackup -pxxxxxxxx -h121.43.153.146
Warning: Using a password on the command line interface can be insecure.
GRANT REPLICATION SLAVE ON *.* TO 'backup'@'121.43.153.147' identified by 'xxxxxxxx';
GRANT REPLICATION SLAVE ON *.* TO 'backup'@'115.236.160.82' identified by 'xxxxxxxx';
mysql> delete from mysql.user where user='backup' and host='%';
Query OK, 1 row affected (0.01 sec)
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
mysql> flush privileges;
Query OK, 0 rows affected (0.04 sec)
mysql> select host,user from mysql.user where user='backup';
+----------------+--------+
| host | user |
+----------------+--------+
| 115.236.160.82 | backup |
| 121.43.153.147 | backup |
+----------------+--------+
2 rows in set (0.00 sec)
ZJZC数据库从120.26.57.101,已经连接不上
jrhdpt02:/root# mysql -ubackup -pxxxxxxxx -h121.43.153.146
Warning: Using a password on the command line interface can be insecure.
ERROR 1045 (28000): Access denied for user 'backup'@'120.26.57.101' (using password: YES)
mysql> show grants for backup@'115.236.160.82';
+--------------------------------------------------------------------------------------------------------------------------------+
| Grants for backup@115.236.160.82 |
+--------------------------------------------------------------------------------------------------------------------------------+
| GRANT REPLICATION SLAVE ON *.* TO 'backup'@'115.236.160.82' IDENTIFIED BY PASSWORD '*93CCED77A19FA43FCA335E99889F351FABDA1320' |
+--------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
mysql> show grants for backup@'121.43.153.147';
+--------------------------------------------------------------------------------------------------------------------------------+
| Grants for backup@121.43.153.147 |
+--------------------------------------------------------------------------------------------------------------------------------+
| GRANT REPLICATION SLAVE ON *.* TO 'backup'@'121.43.153.147' IDENTIFIED BY PASSWORD '*93CCED77A19FA43FCA335E99889F351FABDA1320' |
+--------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
mysql 主从复制用户权限限制
转载本文章为转载内容,我们尊重原作者对文章享有的著作权。如有内容错误或侵权问题,欢迎原作者联系我们进行内容更正或删除文章。
提问和评论都可以,用心的回复会被更多人看到
评论
发布评论
相关文章
-
mysql 主从复制测试 mysql主从复制问题
Mysql主从复制以及常见错误问题分析一、主从复制简
mysql 主从复制测试 数据库 mysql 服务器 sql -
mysql 主从复制频率 mysql 主从复制模式
0、为什么需要主从复制?1、在业务复杂的系统中,有这么一个情景,有一句sql语句需要锁表,导致暂时不能使用读的服务,那么就很影响运行中的业务,使用主从复制,让主库负责写,从库负责读,这样,即使主库出现了锁表的情景,通过读从库也可以保证业务的正常运作。2、做数据的热备3、架构的扩展。业务量越来越大,I/O访问频率过高,单机无法满足,此时做多库的存储,降低磁盘I/O访问的频率,提高单个机器的I/O性能
mysql 主从复制频率 mysql 主从复制 mysql 锁表 mysql主从复制 mysql主从复制原理详解