Comments - MySQL Cluster setup and MaxScale configuration
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.
Pls help me for the error "Unable to connect to MaxScale at /tmp/maxadmin.sock"
<<code>>
]# ./maxscale -c ../ Info : MaxScale will be run in the terminal process. Configuration file : /etc/maxscale.cnf Log directory : /var/log/maxscale Data directory : /var/lib/maxscale Module directory : /usr/lib64/maxscale Service cache : /var/cache/maxscale2017-02-07 14:45:21 notice : MariaDB MaxScale 2.0.4 started 2017-02-07 14:45:21 notice : MaxScale is running in process 3351 2017-02-07 14:45:21 notice : Configuration file: /etc/maxscale.cnf 2017-02-07 14:45:21 notice : Log directory: /var/log/maxscale 2017-02-07 14:45:21 notice : Data directory: /var/lib/maxscale 2017-02-07 14:45:21 notice : Module directory: /usr/lib64/maxscale 2017-02-07 14:45:21 notice : Service cache: /var/cache/maxscale 2017-02-07 14:45:21 notice : Initialise readconnroute router module V1.1.0. 2017-02-07 14:45:21 notice : Loaded module readconnroute: V1.1.0 from /usr/lib64/maxscale/libreadconnroute.so 2017-02-07 14:45:21 notice : Initialise the MySQL Cluster Monitor module V2.1.0. 2017-02-07 14:45:21 notice : Loaded module ndbclustermon: V2.1.0 from /usr/lib64/maxscale/libndbclustermon.so 2017-02-07 14:45:21 notice : No query classifier specified, using default 'qc_sqlite'. 2017-02-07 14:45:21 notice : Loaded module qc_sqlite: V1.0.0 from /usr/lib64/maxscale/libqc_sqlite.so 2017-02-07 14:45:21 notice : Configuration was successfully verified.
MaxScale 2.0 introduced UNIX domain sockets for MaxAdmin as the default method of connecting. Instead of using
port=6603
you can usesocket=default
to configure the cli service to create a socket instead of a network port. For more details, refer to the MaxAdmin documentation.You can use the network interface by defining at least one network option for maxadmin:
maxadmin -P 6603 -p
This is my maxscale config:
But it is still error:
Check the error logs for any errors that could explain why the socket file was not created. If a simple restart of MaxScale doesn't fix it, I'd recommend filing a bug at jira.mariadb.org.
Thanks, I added this bug at: https://jira.mariadb.org/browse/MXS-1131