Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3331

Could not bind connecting socket to local address

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.5
    • Fix Version/s: 2.5.16
    • Component/s: Core
    • Labels:
      None
    • Environment:
      docker container - buster, mariadb backends 10.3.25
    • Sprint:
      MXS-SPRINT-139

      Description

      Hello,

      We tried to setup maxscale 2.5.5 on production after successfully setuped and working maxscale in LAB env. Test env is same as production env.

      We had N maxscales sitting on some servers and HA was fullfilled by keepalived.
      When traffic was delegated to keepalived VIP -> maxscale, this was appearing in LOG

      keepalived's vip : 192.168.205.254
      maxscale's ip : 192.168.205.10

      LOG :

      2020-12-09 04:55:20   error  : (3331) (server01) Could not bind connecting socket to local address "192.168.205.10", connecting to server using default local address: Address already in use
      2020-12-09 04:55:20   error  : (3331) (server02) Could not bind connecting socket to local address "192.168.205.10", connecting to server using default local address: Address already in use
      2020-12-09 04:55:21   error  : (3332) (server03) Could not bind connecting socket to local address "192.168.205.10", connecting t ........
      ............
      ............
      ............
      ............
      ............
      

      Config :

      [maxscale]
      local_address = 192.168.205.10
      threads = 5
      skip_permission_checks = true
      query_retries = 5
      admin_secure_gui = false
      auth_connect_timeout = 10s
      auth_read_timeout = 3s
      auth_write_timeout = 6s
      max_auth_errors_until_block = 0
      admin_host = 192.168.205.10
      admin_port = 8990
       
       
      [server01]
      type = server
      address = 192.168.205.10
      port = 3306
      protocol = MariaDBBackend
       
      [server02]
      type = server
      address = 192.168.205.11
      port = 3306
      protocol = MariaDBBackend
       
      [server03]
      type = server
      address = 192.168.205.21
      port = 3306
      protocol = MariaDBBackend
       
      [server04]
      type = server
      address = 192.168.205.20
      port = 3306
      protocol = MariaDBBackend
       
       
      [default-monitor]
      type = monitor
      module = galeramon
      servers = server01,server02
      user = root
      password = OMMITED
      monitor_interval = 2000ms
       
      [shardA-monitor]
      type = monitor
      module = galeramon
      servers = server03,server04
      user = root
      password = OMMITED
      monitor_interval = 2000ms
       
       
      [default-loadbalancer]
      type = service
      router = readconnroute
      servers = server01,server02
      router_options = master
      user = root
      password = OMMITED
      enable_root_user = 1
      connection_keepalive = 60s
       
      [shardA-loadbalancer]
      type = service
      router = readconnroute
      servers = server03,server04
      router_options = master
      user = root
      password = OMMITED
      enable_root_user = 1
      connection_keepalive = 60s
       
      [ShardRouter]
      type = service
      router = schemarouter
      targets = default-loadbalancer,shardA-loadbalancer
      user = root
      password = OMMITED
      enable_root_user = 1
      auth_all_servers = 1
       
       
      [ShardListener]
      type = listener
      service = ShardRouter
      protocol = MariaDBClient
      address = 192.168.205.254
      port = 3306
       
      [default-unix-listener]
      type = listener
      service = default-loadbalancer
      protocol = MariaDBClient
      socket = /var/lib/kolla/maxscale/default.sock
       
      [shardA-unix-listener]
      type = listener
      service = shardA-loadbalancer
      protocol = MariaDBClient
      socket = /var/lib/kolla/maxscale/shardA.sock
      
      

      • Backends are always in pair of 2 (galera cluster)
      • On one cluster are SOME databases and on second OTHER databases
      • Users are everywhere without grants + with grants where DB is

      Is this normal ?
      Could be a bug ?

      Regards,
      Michal Arbet

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            Arbet Michal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.