[MXS-1408] maxadmin not working in latest version Created: 2017-09-12  Updated: 2017-11-20  Resolved: 2017-11-20

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 2.2.0
Fix Version/s: 2.2.1

Type: Bug Priority: Major
Reporter: bart vrancken Assignee: Johan Wikman
Resolution: Not a Bug Votes: 0
Labels: None

Sprint: 2017-45

 Description   

using the socket does work, but with TCP not working.

TCPDUMP shows traffic, telnet works:

root@pxc1:~/MaxScale/_build# telnet localhost 6603
Trying ::1...
Connected to localhost.
Escape character is '^]'.
USER

root@pxc1:~/MaxScale/_build# maxadmin -h 172.16.0.111 -pmariadb list servers
Unable to connect to MaxScale at 172.16.0.111, 6603: Connection refused
Found default MaxAdmin socket in: /tmp/maxadmin.sock
Try connecting with:

maxadmin -S /tmp/maxadmin.sock

root@pxc1:~/MaxScale/_build# maxadmin -h 127.0.0.1 -pmariadb list servers
Unable to connect to MaxScale at 127.0.0.1, 6603: Connection refused
Found default MaxAdmin socket in: /tmp/maxadmin.sock
Try connecting with:

maxadmin -S /tmp/maxadmin.sock

root@pxc1:~/MaxScale/_build# maxadmin -h ::1 -pmariadb list servers
Unable to connect to MaxScale at ::1, 6603: Connection refused
Found default MaxAdmin socket in: /tmp/maxadmin.sock
Try connecting with:

maxadmin -S /tmp/maxadmin.sock

using older maxadmin (2.0.1)

root@pxc2:~# maxadmin -h 172.16.0.111 -pmariadb list servers
Unable to connect to MaxScale at 172.16.0.111, 6603: Connection refused
root@pxc2:~# maxadmin -h 172.16.0.111 -uroot -pmariadb list servers
Unable to connect to MaxScale at 172.16.0.111, 6603: Connection refused
root@pxc2:~# maxadmin -h 172.16.0.111 -umaxadmin -pmariadb list servers
Unable to connect to MaxScale at 172.16.0.111, 6603: Connection refused
root@pxc2:~# maxadmin -h 172.16.0.111 -umariadb -pmariadb list servers
Unable to connect to MaxScale at 172.16.0.111, 6603: Connection refused
root@pxc2:~# maxadmin -h 172.16.0.111 -P 6603 -umariadb -pmariadb list servers
Unable to connect to MaxScale at 172.16.0.111, 6603: Connection refused



 Comments   
Comment by Johan Wikman [ 2017-09-21 ]

bartvrancken I am sorry, but I don't quite understand the problem. Could you please copy your config file here (with any sensitive data removed).

Comment by Johan Wikman [ 2017-10-04 ]

Closing as incomplete as without more information it is not possible to investigate.

Please create a new one if needed.

Comment by bart vrancken [ 2017-10-04 ]

@johan wikman

sorry , i missed a few notifications. these items i discussed on IRC and one of the devs understood it and asked to log it here too.

There are multiple problems:

1. The socket works, but not using the port method. Its the client that is broken, as a telnet to the port works fine. TCPdump shows the maxadmin is trying to connect, but seems to fail?

2. Connecting to the port method will still report errors that the socket is not available, which is not an 'issue to report' as i am not using the socket at that port.

Comment by Johan Wikman [ 2017-10-05 ]

Thanks, I will take a look at it.

Comment by Johan Wikman [ 2017-10-05 ]

bartvrancken Could you provide the maxadmin related parts of your config file?

Comment by Johan Wikman [ 2017-10-05 ]

bartvrancken
With telnet you try to localhost, but with maxadmin to specific address:

root@pxc1:~/MaxScale/_build# telnet localhost 6603
root@pxc1:~/MaxScale/_build# maxadmin -h 172.16.0.111 -pmariadb list servers

Please try telneting to 172.16.0.111 or using 127.0.0.1 with maxadmin. What is the result?

Comment by Johan Wikman [ 2017-10-05 ]

In the listener setup for the maxadmin service, what do you have as value for address ?

I get exactly the behaviour you experience with

address=localhost

With

address=0.0.0.0

connecting with maxadmin, using an address other than localhost, works fine.

Comment by bart vrancken [ 2017-10-06 ]

In the config i tried:

127.0.0.1
::1
172.16.0.111

All cases telnet works, but maxadmin did not.

@"connecting with maxadmin, using an address other than localhost, works fine."

Which is a problem no? If there is a TCP socket it should work to localhost too (or specific IP to listen on)

@"Please try telneting to 172.16.0.111 or using 127.0.0.1 with maxadmin. What is the result?"

With 0.0.0.0 it does work

@ Config:

[CLI_Listener]
type=listener
service=CLI
protocol=maxscaled
#address=localhost
#port=6603
socket=default

I commented them as combining them does not work, while it does with listener/splitter and other items.

Comment by Johan Wikman [ 2017-10-06 ]

With "connecting with maxadmin, using an address other than localhost, works fine." I meant it works also with an address other than localhost.

If you want to be able to use maxscale over a Unix domain socket and a TCP socket/port, you can always have two listeners:

[MaxAdmin Unix Listener]
type=listener
service=MaxAdmin Service
protocol=maxscaled
socket=default
 
[MaxAdmin Inet Listener]
type=listener
service=MaxAdmin Service
protocol=maxscaled
address=0.0.0.0
port=6603

Comment by Johan Wikman [ 2017-11-09 ]

bartvrancken Is there something unclear still with this one? Otherwise I will close it.

Thanks, Johan

Comment by Johan Wikman [ 2017-11-20 ]

Without new information that would suggest otherwise, I'll close this as a non-bug.

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