Comments - MaxScale Read/Write Splitting with Galera Cluster

8 years ago Yu Denis

Having socket info should not be a problem.If specified,i got:

---------------------+--------------------+-----------------+-------+--------
Service Name         | Protocol Module    | Address         | Port  | State
---------------------+--------------------+-----------------+-------+--------
Splitter Service     | MySQLClient        | *               |  3308 | Running
Splitter Service     | MySQLClient        | /tmp/ClusterMaster |     0 | Running
CLI                  | maxscaled          | localhost       |  6603 | Running
---------------------+--------------------+-----------------+-------+--------

Make sure the user starting the maxscale is the same user owns /tmp/ClusterMaster. Initially i had root own everything, then later i started the maxscale with "mysql" user, but /tmp/ClusterMaster was sill owned by root, that caused problem in my case:


2016-04-12 13:37:14   error  : Failed to unlink Unix Socket /tmp/ClusterMaster: 1 Operation not permitted
2016-04-12 13:37:14   error  : Failed to bind to UNIX Domain socket '/tmp/ClusterMaster': 98, Address already in use
2016-04-12 13:37:14   error  : Unable to start to listen port 0 for MySQLClient Splitter Service.

After deleting the file owned by root, everything is fine.

- Denis

- Denis

 
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.