Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
2.3.4
Description
maxctrl stops working after trying a switchover:
|
|
[root@server_a ~]# maxctrl list servers
|
┌─────────┬───────────────┬──────┬─────────────┬─────────────────┬────────────────┐
|
│ Server │ Address │ Port │ Connections │ State │ GTID │
|
├─────────┼───────────────┼──────┼─────────────┼─────────────────┼────────────────┤
|
│ server1 │ 192.168.1.97 │ 3306 │ 0 │ Slave, Running │ 1-1-77,2-2-189 │
|
├─────────┼───────────────┼──────┼─────────────┼─────────────────┼────────────────┤
|
│ server2 │ 192.168.1.98 │ 3306 │ 0 │ Master, Running │ 1-1-77,2-2-189 │
|
└─────────┴───────────────┴──────┴─────────────┴─────────────────┴────────────────┘
|
|
|
[root@server_a ~]# maxctrl call command mariadbmon switchover MariaDB-Monitor server1 server2
|
Error: {
|
"code": "ESOCKETTIMEDOUT",
|
"connect": false
|
}
|
|
|
[root@server_a ~]# maxctrl list servers
|
Error: {
|
"code": "ESOCKETTIMEDOUT",
|
"connect": false
|
}
|
|
|
|
|
|
|
|
|
[root@server_a ~]# systemctl stop maxscale
|
|
|
[root@server_a ~]# systemctl start maxscale
|
|
|
[root@server_a ~]# maxctrl list servers
|
┌─────────┬───────────────┬──────┬─────────────┬─────────────────┬────────────────┐
|
│ Server │ Address │ Port │ Connections │ State │ GTID │
|
├─────────┼───────────────┼──────┼─────────────┼─────────────────┼────────────────┤
|
│ server1 │ 192.168.1.97 │ 3306 │ 0 │ Slave, Running │ 1-1-77,2-2-189 │
|
├─────────┼───────────────┼──────┼─────────────┼─────────────────┼────────────────┤
|
│ server2 │ 192.168.1.98 │ 3306 │ 0 │ Master, Running │ 1-1-77,2-2-189 │
|
└─────────┴───────────────┴──────┴─────────────┴─────────────────┴────────────────┘
|
|
|
[root@server_a ~]# maxctrl call command mariadbmon switchover MariaDB-Monitor server1 server2
|
Error: {
|
"code": "ESOCKETTIMEDOUT",
|
"connect": false
|
}
|