Comments - MaxScale, "No Master can be determined"

5 years, 7 months ago Sam

In logs, maxscale otherwise starts up:

2018-10-18 07:59:45   info   : [MySQLAuth] Added user: INSERT OR REPLACE INTO mysqlauth_users VALUES ('maxscale', '127.0.0.1', 'mysql', 1, '4ACFE3202A5FF5CF467898FC58AAB1D615029441')
2018-10-18 07:59:45   info   : [MySQLAuth] Added user: INSERT OR REPLACE INTO mysqlauth_users VALUES ('maxscale', '10.144.114.162', 'mysql', 1, '4ACFE3202A5FF5CF467898FC58AAB1D615029441')
2018-10-18 07:59:45   notice : [MySQLAuth] [ReadService] Loaded 15 MySQL users for listener ReadListener.
2018-10-18 07:59:45   notice : Listening for connections at [::]:4307 with protocol MySQL
2018-10-18 07:59:45   info   : Started session [2] for ReadService service 
2018-10-18 07:59:45   notice : Service 'ReadService' started (2/3)
2018-10-18 07:59:45   notice : Listening for connections at [/tmp/maxadmin.sock]:0 with protocol MaxScale Admin
2018-10-18 07:59:45   info   : Started session [3] for CLI service 
2018-10-18 07:59:45   notice : Service 'CLI' started (3/3)
2018-10-18 07:59:45   notice : Started MaxScale log flusher.
2018-10-18 07:59:45   info   : [qc_sqlite] In-memory sqlite database successfully opened for thread 140506755454720.
2018-10-18 07:59:45   info   : [qc_sqlite] In-memory sqlite database successfully opened for thread 140506747062016.
2018-10-18 07:59:45   notice : Started REST API on [127.0.0.1]:8989
2018-10-18 07:59:45   info   : [qc_sqlite] In-memory sqlite database successfully opened for thread 140506730276608.
2018-10-18 07:59:45   info   : [qc_sqlite] In-memory sqlite database successfully opened for thread 140506738669312.
2018-10-18 07:59:45   notice : MaxScale started with 4 worker threads, each with a stack size of 8388608 bytes.

In other window: No Master can be determined

Tried to set as master, but it did not help.

MaxScale> set server server1 master

in logs:

2018-10-18 08:09:36   info   : (4) [cli] MaxAdmin: set server server1 master
2018-10-18 08:09:36   notice : Server changed state: server1[172.17.0.3:3306]: lost_master. [Master, Running] -> [Running]

All servers are in Running state (not as master / slave states):

MaxScale> list servers
Servers.
-------------------+-----------------+-------+-------------+--------------------
Server             | Address         | Port  | Connections | Status              
-------------------+-----------------+-------+-------------+--------------------
server1            | 172.17.0.3      |  3306 |           0 | Running
server2            | 172.17.0.4      |  3306 |           0 | Running
server3            | 172.17.0.5      |  3306 |           0 | Running
-------------------+-----------------+-------+-------------+--------------------


 
5 years, 7 months ago Sam

Same happens also with readwritesplit.

 
5 years, 7 months ago Markus Mäkelä

Is it a Galera cluster or a cluster with master-slave replication?

 
5 years, 7 months ago Sam

Hi! It is not galera cluster. It is MaxScale with Master Slave Slave (M-S-S) configuration. (M-S would be enough too.) I have tried with readwritesplit and readconnroute. There may be something basic missing. Grants given incorrectly? Something else missing / not executed?

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.