MariaDB MaxScale /var/log/maxscale/maxscale.log Wed Feb 21 12:09:49 2018 ---------------------------------------------------------------------------- 2018-02-21 12:09:49 notice : Working directory: /var/log/maxscale 2018-02-21 12:09:49 notice : The collection of SQLite memory allocation statistics turned off. 2018-02-21 12:09:49 notice : Threading mode of SQLite set to Multi-thread. 2018-02-21 12:09:49 notice : MariaDB MaxScale 2.2.2 started 2018-02-21 12:09:49 notice : MaxScale is running in process 21180 2018-02-21 12:09:49 notice : Commit: 6c6baebc65ece637fa8f1ab1fa1cad5bfe794c9e 2018-02-21 12:09:49 notice : Configuration file: /etc/maxscale.cnf 2018-02-21 12:09:49 notice : Log directory: /var/log/maxscale 2018-02-21 12:09:49 notice : Data directory: /var/lib/maxscale 2018-02-21 12:09:49 notice : Module directory: /usr/lib64/maxscale 2018-02-21 12:09:49 notice : Service cache: /var/cache/maxscale 2018-02-21 12:09:49 notice : Loading /etc/maxscale.cnf. 2018-02-21 12:09:49 warning: Number of threads set to 4, which is greater than the number of processors available: 1 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: MySQL Monitor 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: RW Split Router 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: Read Connection Router Slave 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: Read Connection Router Master 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: RW Split Listener 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: Read Connection Listener Slave 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: Read Connection Listener Master 2018-02-21 12:09:49 warning: Whitespace in object names is deprecated, converting to hyphens: CLI Listener 2018-02-21 12:09:49 notice : /etc/maxscale.cnf.d does not exist, not reading. 2018-02-21 12:09:49 notice : [cli] Initialise CLI router module 2018-02-21 12:09:49 notice : Loaded module cli: V1.0.0 from /usr/lib64/maxscale/libcli.so 2018-02-21 12:09:49 notice : [readconnroute] Initialise readconnroute router module. 2018-02-21 12:09:49 notice : Loaded module readconnroute: V1.1.0 from /usr/lib64/maxscale/libreadconnroute.so 2018-02-21 12:09:49 notice : [readwritesplit] Initializing statement-based read/write split router module. 2018-02-21 12:09:49 notice : Loaded module readwritesplit: V1.1.0 from /usr/lib64/maxscale/libreadwritesplit.so 2018-02-21 12:09:49 notice : [mariadbmon] Initialise the MariaDB Monitor module. 2018-02-21 12:09:49 notice : Loaded module mariadbmon: V1.5.0 from /usr/lib64/maxscale/libmariadbmon.so 2018-02-21 12:09:49 warning: Protocol module 'mysqlbackend' has been deprecated, use 'mariadbbackend' instead. 2018-02-21 12:09:49 notice : Loaded module mariadbbackend: V2.0.0 from /usr/lib64/maxscale/libmariadbbackend.so 2018-02-21 12:09:49 notice : Loaded module MySQLBackendAuth: V1.0.0 from /usr/lib64/maxscale/libmysqlbackendauth.so 2018-02-21 12:09:49 notice : Loaded module maxscaled: V2.0.0 from /usr/lib64/maxscale/libmaxscaled.so 2018-02-21 12:09:49 notice : Loaded module MaxAdminAuth: V2.1.0 from /usr/lib64/maxscale/libmaxadminauth.so 2018-02-21 12:09:49 warning: Protocol module 'mysqlclient' has been deprecated, use 'mariadbclient' instead. 2018-02-21 12:09:49 notice : Loaded module mariadbclient: V1.1.0 from /usr/lib64/maxscale/libmariadbclient.so 2018-02-21 12:09:49 notice : Loaded module MySQLAuth: V1.1.0 from /usr/lib64/maxscale/libmysqlauth.so 2018-02-21 12:09:49 notice : Monitor 'MySQL-Monitor' is missing the 'journal_max_age' parameter, using default value of 28800 seconds. 2018-02-21 12:09:49 notice : Monitor 'MySQL-Monitor' is missing the 'script_timeout' parameter, using default value of 90 seconds. 2018-02-21 12:09:49 notice : No query classifier specified, using default 'qc_sqlite'. 2018-02-21 12:09:49 notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so 2018-02-21 12:09:49 warning: Removing stale journal file for monitor 'MySQL-Monitor'. 2018-02-21 12:09:49 notice : Encrypted password file /var/lib/maxscale/.secrets can't be accessed (No such file or directory). Password encryption is not used. 2018-02-21 12:09:49 warning: [readwritesplit] Router options for readwritesplit are deprecated. 2018-02-21 12:09:49 notice : [MySQLAuth] [RW-Split-Router] Loaded 8 MySQL users for listener RW-Split-Listener. 2018-02-21 12:09:49 notice : Listening for connections at [::]:4006 with protocol MySQL 2018-02-21 12:09:49 notice : [MySQLAuth] [Read-Connection-Router-Slave] Loaded 8 MySQL users for listener Read-Connection-Listener-Slave. 2018-02-21 12:09:49 notice : Listening for connections at [::]:4009 with protocol MySQL 2018-02-21 12:09:49 notice : [MySQLAuth] [Read-Connection-Router-Master] Loaded 8 MySQL users for listener Read-Connection-Listener-Master. 2018-02-21 12:09:49 notice : Listening for connections at [::]:4008 with protocol MySQL 2018-02-21 12:09:49 notice : Listening for connections at [/tmp/maxadmin.sock]:0 with protocol MaxScale Admin 2018-02-21 12:09:49 notice : Started MaxScale log flusher. 2018-02-21 12:09:49 notice : Started REST API on [127.0.0.1]:8989 2018-02-21 12:09:49 notice : MaxScale started with 4 worker threads, each with a stack size of 8388608 bytes. 2018-02-21 12:09:49 notice : Server changed state: server1[192.168.121.83:3306]: new_master. [Running] -> [Master, Running] 2018-02-21 12:09:49 notice : Server changed state: server2[192.168.121.30:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:09:49 notice : Server changed state: server3[192.168.121.166:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:09:49 notice : Server changed state: server4[192.168.121.246:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:09:49 notice : [mariadbmon] A Master Server is now available: 192.168.121.83:3306 2018-02-21 12:09:57 notice : Server changed state: server2[192.168.121.30:3306]: lost_slave. [Slave, Running] -> [Running] 2018-02-21 12:09:59 notice : Server changed state: server2[192.168.121.30:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:09:59 notice : Server changed state: server3[192.168.121.166:3306]: lost_slave. [Slave, Running] -> [Running] 2018-02-21 12:10:01 notice : Server changed state: server3[192.168.121.166:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:10:01 notice : Server changed state: server4[192.168.121.246:3306]: lost_slave. [Slave, Running] -> [Running] 2018-02-21 12:10:02 notice : Server changed state: server4[192.168.121.246:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:10:06 notice : Updated 'passive' from 'false' to 'true' 2018-02-21 12:10:52 error : Monitor was unable to connect to server [192.168.121.83]:3306 : "Can't connect to MySQL server on '192.168.121.83' (115)" 2018-02-21 12:10:52 notice : [mariadbmon] Server [192.168.121.83]:3306 lost the master status. 2018-02-21 12:10:52 notice : Server changed state: server1[192.168.121.83:3306]: master_down. [Master, Running] -> [Down] 2018-02-21 12:10:52 error : [mariadbmon] No Master can be determined. Last known was 192.168.121.83:3306 2018-02-21 12:10:57 notice : Server changed state: server2[192.168.121.30:3306]: new_master. [Slave, Running] -> [Master, Running] 2018-02-21 12:10:57 notice : Server changed state: server4[192.168.121.246:3306]: lost_slave. [Slave, Running] -> [Running] 2018-02-21 12:10:57 notice : [mariadbmon] A Master Server is now available: 192.168.121.30:3306 2018-02-21 12:10:58 notice : Server changed state: server4[192.168.121.246:3306]: new_slave. [Running] -> [Slave, Running] 2018-02-21 12:11:21 notice : Updated 'passive' from 'true' to 'false' 2018-02-21 12:17:38 error : Monitor was unable to connect to server [192.168.121.166]:3306 : "Can't connect to MySQL server on '192.168.121.166' (115)" 2018-02-21 12:17:38 notice : Server changed state: server3[192.168.121.166:3306]: slave_down. [Slave, Running] -> [Down] 2018-02-21 12:18:21 notice : Server changed state: server3[192.168.121.166:3306]: slave_up. [Down] -> [Slave, Running] 2018-02-21 12:18:44 error : Monitor was unable to connect to server [192.168.121.30]:3306 : "Can't connect to MySQL server on '192.168.121.30' (115)" 2018-02-21 12:18:44 notice : [mariadbmon] Server [192.168.121.30]:3306 lost the master status. 2018-02-21 12:18:44 notice : Server changed state: server2[192.168.121.30:3306]: master_down. [Master, Running] -> [Down] 2018-02-21 12:18:44 warning: [mariadbmon] Failover of server 'server1' did not take place within 90 seconds, failover needs to be re-triggered 2018-02-21 12:18:44 alert : [mariadbmon] Multiple failed master servers detected: 'server1' is the first master to fail but server 'server2' has also triggered a master_down event. 2018-02-21 12:18:44 error : [mariadbmon] Failed to perform failover, disabling automatic failover. To re-enable failover, manually set 'auto_failover' to 'true' for monitor 'MySQL-Monitor' via MaxAdmin or the REST API, or restart MaxScale. 2018-02-21 12:18:44 error : [mariadbmon] No Master can be determined. Last known was 192.168.121.30:3306