[MXS-1069] Unable to find server Created: 2016-12-30  Updated: 2017-01-02  Resolved: 2017-01-02

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation
Affects Version/s: 2.0.3
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Juan Valentín-Pastrana Assignee: markus makela
Resolution: Not a Bug Votes: 0
Labels: tests
Environment:

Testing maxscale on Ubuntu 64, MariaDB 10.1.20



 Description   

Cluster server names are maria1, maria2 & maria3. Cluster is replication. I can access them from maxscale host using:
$ mysql -h maria1 -u max -p

When starting maxscale I get:
$ sudo systemctl start maxscale
...
unable to find server 'maria1' that is configured in the monitor 'Galera Monitor'.
...
unable to find server 'maria3' that is configured as part of service 'Galera Service'.

That for all three servers.

My maxscale.cnf contains:
...
[Galera Service]
type=service
router=readconnroute
router_options=synced
servers=maria1,maria2,maria3
user=max
passwd=FB5D3518F83EC3EE40F800EFCD7F72B0
...
[server2]
type=server
address=192.168.1.122
port=3306
protocol=MySQLBackend

And names are accessible via /etc/hosts. Please help, I can't go any further with maxscale.



 Comments   
Comment by Juan Valentín-Pastrana [ 2017-01-01 ]

First node must be started issuing

  1. galera_new_cluster
Comment by markus makela [ 2017-01-02 ]

The names listed in the servers parameter need to be the server section names defined in maxscale.cnf. In your configuration file, the server at 192.168.1.122:3306 would be named server2:

[server2]
type=server
address=192.168.1.122
port=3306
protocol=MySQLBackend

You would configure the service to use this server by adding it to the servers parameter:

Galera Service]
type=service
router=readconnroute
router_options=synced
servers=server2

You need to add server definitions for all of the servers that you are going to use. You can use the host names from /etc/hosts as values for the address parameter.

Here's a tutorial on how to set up MaxScale that could be useful.

Generated at Thu Feb 08 04:04:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.