用实例管理器轻松管理多个MySQL实例
一、MySQL数据库的实例管理器概述:
1、MySQL数据库的实例管理器(IM)是通过TCP/IP端口运行的后台程序,用来监视和管理MySQL数据库服务器实例。
2、假如IM挂了,则所有的实例都会挂掉;假如实例挂了,IM会尝试重新来启动它。
3、IM读取配置文件比如MY.CNF的[manager]段。
4、本文中的示例依据LINUX环境下试验。
二、配置说明:
1、配置文件如下:
|
[manager] user=mysql default-mysqld-path = /usr/local/mysql/bin/mysqld socket=/tmp/manager.sock pid-file=/tmp/manager.pid password-file = /etc/mysqlmanager.passwd monitoring-interval = 2 port = 1999 bind-address = 192.168.0.231 log = /usr/local/mysql/bin/mysqlmanager.log run-as-service = true [mysqld1] … [mysqld2] … |
这个有两个配置实例,具体就不说了。见我的安装多个实例的文章。
具体含义查看mysqlmanager –help
2、密码文件
IM将用户信息保存到密码文件中。密码文件的默认位置为/etc/mysqlmanager.passwd。
密码应类似于:
| petr:*35110DC9B4D8140F5DE667E28C72DD2597B5C848 |
我的mysqlmanager.passwd内容
|
user_all:*6BB4837EB74329105EE4568DDA7DC67ED2CA2AD9 |
3、启动IM
|
[root@localhost tmp]# /usr/local/mysql/bin/mysqlmanager WARNING: This program is deprecated and will be removed in 6.0. [2483/3086632640] [08/04/24 14:24:50] [INFO] IM: started. [2483/3086632640] [08/04/24 14:24:50] [INFO] Loading config file ‘my.cnf’… [2483/3086632640] [08/04/24 14:24:50] [INFO] Manager: initializing… [2483/3086632640] [08/04/24 14:24:50] [INFO] Manager: detected threads model: POSIX threads. [2483/3086632640] [08/04/24 14:24:50] [INFO] Loading the password database… [2483/3086632640] [08/04/24 14:24:50] [INFO] Loaded user ‘user_all’. [2483/3086632640] [08/04/24 14:24:50] [INFO] The password database loaded successfully. [2483/3086632640] [08/04/24 14:24:50] [INFO] Manager: pid file (/tmp/manager.pid) created. [2483/3086632640] [08/04/24 14:24:50] [INFO] mysqld instance ‘mysqld1′ has been added successfully. [2483/3086632640] [08/04/24 14:24:50] [INFO] mysqld instance ‘mysqld2′ has been added successfully. [2483/3076139920] [08/04/24 14:24:50] [INFO] Guardian: started. [2483/3076139920] [08/04/24 14:24:50] [INFO] Guardian: starting ‘mysqld1′… [2483/3076058000] [08/04/24 14:24:50] [INFO] Instance ‘mysqld1′: Monitor: started. [2483/3076058000] [08/04/24 14:24:50] [INFO] Instance ‘mysqld1′: Monitor: starting mysqld… [2483/3076139920] [08/04/24 14:24:50] [INFO] Guardian: starting ‘mysqld2′… [2483/3076058000] [08/04/24 14:24:50] [INFO] Instance ‘mysqld1′: Monitor: waiting for mysqld to stop… [2483/3075894160] [08/04/24 14:24:50] [INFO] Instance ‘mysqld2′: Monitor: started. [2483/3075894160] [08/04/24 14:24:50] [INFO] Instance ‘mysqld2′: Monitor: starting mysqld… [2483/3075894160] [08/04/24 14:24:50] [INFO] Instance ‘mysqld2′: Monitor: waiting for mysqld to stop… [2483/3086632640] [08/04/24 14:24:50] [INFO] Manager: started. [2483/3075976080] [08/04/24 14:24:50] [INFO] Listener: started. [2483/3075976080] [08/04/24 14:24:50] [INFO] Listener: accepting connections on ip socket (port: 1999)… [2483/3075976080] [08/04/24 14:24:50] [INFO] Listener: accepting connections on unix socket ‘/tmp/manager.sock’… … InnoDB: than specified in the .cnf file 0 5242880 bytes! 080424 14:24:50 InnoDB: Started; log sequence number 0 46409 080424 14:24:50 [Note] Event Scheduler: Loaded 0 events 080424 14:24:50 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: ‘5.1.23a-maria-alpha-log’ socket: ‘/tmp/mysql1.sock’ port: 3306 MySQL Community Server [Maria] (GPL) 080424 14:24:50 [Warning] ‘user’ entry ‘root@localhost.localdomain’ ignored in –skip-name-resolve mode. 080424 14:24:50 [Warning] ‘user’ entry ‘@localhost.localdomain’ ignored in –skip-name-resolve mode. 080424 14:24:50 [Note] Event Scheduler: Loaded 0 events 080424 14:24:50 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: ‘5.1.23a-maria-alpha-log’ socket: ‘/tmp/mysql2.sock’ port: 3309 MySQL Community Server [Maria] (GPL) [2483/3076139920] [08/04/24 14:24:52] [INFO] Guardian: ‘mysqld1′ is running, set state to STARTED. |
