CentOS 6.5(Final)

If you are using MySQL 5.1 servers, you need to set "mysql51_replication=true" in your mysqlmon section. See here https://github.com/mariadb-corporation/MaxScale/blob/master/Documentation/Monitors/MySQL-Monitor.md#mysql51_replication

thanks but that helped only with error "MySQL version is lower than 5.5"

Rest two issues remained
Error: Failed to set socket options. Error 95: Operation not supported
Error : Unable to start to listen port 0 for MySQLClient Read Connection Router.

actually only one error remained
Error: Failed to set socket options. Error 95: Operation not supported

szemlyanoy Which error has remained ?

This one - "Error: Failed to set socket options. Error 95: Operation not supported"

szemlyanoy What OS you are running on ? Is MaxScale service able to come up now ?

Please attach your entire config file.

Thanks,
Dipti

it's CentOS release 6.5 (Final)

Config below:

[maxscale]
threads=4
enable_root_user=1

[MySQL Monitor]
type=monitor
module=mysqlmon
servers=ib1
user=maxscale
passwd=***
monitor_interval=10000
mysql51_replication=true

[qla]
type=filter
module=qlafilter
options=/tmp/QueryLog

[fetch]
type=filter
module=regexfilter
match=fetch
replace=select

[hint]
type=filter
module=hintfilter

[Read Connection Router]
type=service
router=readconnroute
servers=ib1
user=maxscale
passwd=***
router_options=slave

[Debug Interface]
type=service
router=debugcli

[Debug Listener]
type=listener
service=Debug Interface
protocol=telnetd
port=4442

[CLI]
type=service
router=cli

[CLI Listener]
type=listener
service=CLI
protocol=maxscaled
port=6603

[Read Connection Listener]
type=listener
service=Read Connection Router
protocol=MySQLClient
port=3306
socket=/var/lib/maxscale/readconn.sock

[ib1]
type=server
address=***
port=3306
protocol=MySQLBackend

szemlyanoy What OS you are running on ?

Dipti,
I mentioned it above - "it's CentOS release 6.5 (Final)"

The "Error: Failed to set socket options. Error 95: Operation not supported" message is due to the socket. It is not a real error as it is due to TCP_NODELAY option being applied to a Unix domain socket. This is a know bug and is fixed in the develop branch.

Got the same "Error 95: Operation not supported" with 1.2.0 on Ubuntu 14.04, installed from the DEB, being in use as a rwsplitter. MaxScale starts the process, I can even use maxadmin to see that MaxScale is perfectly able to monitor and handle the Galera Cluster behind it but both service maxscale start and service maxscale stop result in failure.

Is there any workaround for this?

My problem is that, although MaxScale is running and working properly, the exit codes from this issue make it LSB-incompatible which makes it practically impossible to use MaxScale as a managed resource in Pacemaker.

Do you maybe happen to have any ideas regarding whether there is another way to make MaxScale itself high-available?