Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
2.1.2
-
None
-
ubuntu server 16.04
mysql server 5.7.7
Description
I configure the maxscale like:
[maxscale]
|
threads=1
|
enable_root_user=true
|
|
|
[server1]
|
type=server
|
address=127.0.0.1
|
port=3306
|
protocol=MySQLBackend
|
|
|
[MySQL Monitor]
|
type=monitor
|
module=mysqlmon
|
servers=server1
|
user=root
|
passwd=123456
|
monitor_interval=10000
|
|
|
[Read-Only Service]
|
type=service
|
router=readconnroute
|
servers=server1
|
user=root
|
passwd=123456
|
router_options=slave
|
|
|
[Read-Write Service]
|
type=service
|
router=readwritesplit
|
servers=server1
|
user=root
|
passwd=123456
|
max_slave_connections=100%
|
|
|
[MaxAdmin Service]
|
type=service
|
router=cli
|
|
|
[Read-Only Listener]
|
type=listener
|
service=Read-Only Service
|
protocol=MySQLClient
|
port=4008
|
|
|
[Read-Write Listener]
|
type=listener
|
service=Read-Write Service
|
protocol=MySQLClient
|
port=4006
|
|
|
[MaxAdmin Listener]
|
type=listener
|
service=MaxAdmin Service
|
protocol=maxscaled
|
socket=default
|
then I run the:
bin/maxscale --user=maxscale -d & |
I can see maxscale is ready from the log:
2018-11-27 00:16:37 notice : Listening for connections at ::|4008 with protocol MySQL
|
2018-11-27 00:16:37 notice : [MySQLAuth] [Read-Write Service] Loaded 2 MySQL users for listener Read-Write Listener.
|
2018-11-27 00:16:37 notice : Listening for connections at ::|4006 with protocol MySQL
|
2018-11-27 00:16:37 notice : Listening for connections at /tmp/maxadmin.sock with protocol MaxScale Admin
|
2018-11-27 00:16:37 notice : MaxScale started with 1 server threads.
|
2018-11-27 00:16:37 notice : Started MaxScale log flusher.
|
2018-11-27 00:16:38 notice : Server changed state: server1[127.0.0.1:3306]: new_master. [Running] -> [Master, Running]
|
2018-11-27 00:16:38 notice : [mysqlmon] A Master Server is now available: 127.0.0.1:3306
|
However, when I run:
./bin/mysql -uroot -p123456 -h127.0.0.1 -P4006 |
the terminal only shows:
mysql: [Warning] Using a password on the command line interface can be insecure. |
and nothing else happens until I send a Ctr+C to terminate the mysql client.
Then the cpu usage remains 100% until I send kill -9 to the maxscale.
What did I miss? Please help.
Thanks