[MXS-1696] local_address does not work when threads > 1 Created: 2018-03-02  Updated: 2020-08-25  Resolved: 2018-03-20

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

Type: Bug Priority: Major
Reporter: Chris Calender (Inactive) Assignee: Johan Wikman
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

The newer variable, local_address, does not get set when threads > 1.

With the following configuration:

[maxscale]
 
threads=1
 
local_address=192.168.1.183
 
log_info=1

Then in the maxscale.log, I see an entry like:

2018-03-02 13:43:05   info  : Bound connecting socket to "192.168.1.183".

When I increase threads to be > 1:

threads=2
 
local_address=192.168.1.183
 
log_info=1

Then there is no such message in the log.

And it is more than not being logged, it is not set at all, afaict, because we see errors like this (it is using the wrong IP address, and not the one specified by "local_address"):

[Warning] Access denied for user 'maxscale1'@'192.168.1.184' (using password: YES)



 Comments   
Comment by Johan Wikman [ 2018-03-03 ]

I just tested locally and irrespective of the value of threads, I get that Bound connecting socket message when connecting with a client. I reviewed the code and there does not appear to be anything that would explain different behavior depending on the value of threads. With local_address having been defined and info level messages enabled then, when connecting with a client, there should be one of the following messages:

  • info : Bound connecting socket to...
  • error: Could not bind connecting socket to local address "...", connecting to server using default local address: "..."
  • error: Could not get address information for local address "...", connecting to server using default local address: "..."
Comment by Chris Calender (Inactive) [ 2018-03-04 ]

Both myself and the other tester are both using Ubuntu. Not sure if that makes a difference.

Comment by Johan Wikman [ 2018-03-05 ]

Should not make a difference and I am also using Ubuntu.

Comment by Johan Wikman [ 2018-03-20 ]

The actual problem is described in MXS-1714.

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