The Ultimate Guide to High Availability with MariaDB

Comments - MaxScale, "No Master can be determined"

5 years, 10 months ago Sam
Re: MaxScale, "No Master can be determined"
This comment has the status of 'removed' and can only be seen by you.

I reinstalled mariadb instances. Now with mariadb:10.3.

I created also following "users" and grants for those. Also IP address 127.17.0.1 was added:

create user 'maxscale'@'127.17.0.1' identified by 'admin';
create user 'maxscale'@'%' identified by 'admin';
grant all privileges on *.* to 'maxscale'@'127.17.0.1' with grant option;
grant all privileges on *.* to 'maxscale'@'%' with grant option;

It does not work yet, but something happens:

MaxScale> list servers
Servers.
-------------------+-----------------+-------+-------------+--------------------
Server             | Address         | Port  | Connections | Status
-------------------+-----------------+-------+-------------+--------------------
server1            | 172.17.0.2      |  3306 |           0 | Master, Running
server2            | 172.17.0.3      |  3306 |           0 | Auth Error, Down
server3            | 172.17.0.4      |  3306 |           0 | Auth Error, Down
-------------------+-----------------+-------+-------------+--------------------

MaxScale> list servers
root@mycomputer:~# maxadmin
MaxScale> list servers
Servers.
-------------------+-----------------+-------+-------------+--------------------
Server             | Address         | Port  | Connections | Status
-------------------+-----------------+-------+-------------+--------------------
server1            | 172.17.0.2      |  3306 |           0 | Master, Running
server2            | 172.17.0.3      |  3306 |           0 | Running
server3            | 172.17.0.4      |  3306 |           0 | Running
-------------------+-----------------+-------+-------------+--------------------

No slaves yet.

 
5 years, 10 months ago Sam
Re: MaxScale, "No Master can be determined"

There is following error mentioned in journalctl -xe:

Oct 19 15:59:40 mycomputer maxscale[31833]: MaxScale started with 2 worker threads, each with a stack size of 8388608 bytes.
Oct 19 15:59:40 mycomputer maxscale[31833]: [mariadbmon] Automatic rejoin was not attempted on server 'server2' even though it is a valid candidate. Will keep retrying with this message suppressed for all servers. Errors: 
                                             'server2' does not have a valid 'gtid_current_pos'.
 
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.