Attemting to connect to file socket instead of tcp causes issues

[noenik]

I recently updated container image versions for both Portabase and the agent. I initially pulled with the latest tag for testing and now wanted to pin the version. However, backup of my MySQL databases stopped working after this. The reason is that the agent tries to connect to the socket when the database is not actually on the same host. Instead, the database is reached over tcp by using ssh tunneling. Thus the backups fail with the following error:

-- Connecting to localhost...
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect

I looked at the documentation for MySQL database but I could not see any new configuration indicating a way for me to specify the method by which the agent should connect to the database.

I'm not exactly sure when this happened, I stepped down version by version until 1.12 and it was still not working. I then selected 1.8 since that was released around the time I initially pulled the image and that worked. So it was somewhere between 1.8 and 1.12.

Is there a setting we can use to specify using tcp and not the socket?

[RambokDev]

Hi,

Could you share your sanitized agent Docker Compose configuration?

Is the database you’re trying to back up MariaDB or MySQL? Historically, we were using MySQL for both, but these are now separated.

Do you have any relevant context logs you could share?

Regards

[RambokDev]

For your network configuration do you share host localhost with the agent one ? Using network mode or the extra host ?

[noenik]

@RambokDev Thank you for looking into this.

It is a MySQL database.

The service in compose looks like this

  portabase_agent:
    container_name: portabase_agent
    image: portabase/agent:1.8
    restart: always
    volumes:
        - ./databases.json:/data/config.json
    network_mode: host
    environment:
        POLLING: 3600
        APP_ENV: production
        DATA_PATH: "/data"
        LOG: info
        EDGE_KEY: "${EDGE_KEY}"

and the databases.json file:

{
  "databases": [
    {
      "name": "my-db",
      "database": "my-db",
      "type": "mysql",
      "host": "localhost",
      "port": 3306,
      "username": "my-db-user",
      "password": "my-db-password",
      "generated_id": "random-uuid"
    }
  ]
}

I have a systemd service making sure the port to the database server is always forwarded over SSH. This has been working just fine.

I stepped up version by version now to see which one broke, and it works up until agent v1.11, when I try it with v1.12 and onward it gives me the same error. It seems to be trying to connect to the database over its file socket /var/lib/mysql/mysql.sock, however, that obviously does not exist in my setup.

If there is anything else I can check, or if there is something you'd like me to test just let me know.

[RambokDev]

Hi @noenik,

Thanks for all the details. I’ve identified the issue, and we’ll fix it.

In the short term, could you replace localhost with 127.0.0.1 in your databases.json file?

Regards,

[noenik]

Hi @noenik,

Thanks for all the details. I’ve identified the issue, and we’ll fix it.

In the short term, could you replace localhost with 127.0.0.1 in your databases.json file?

Regards,

Thank you, changing the host to 127.0.0.1 fixed the issue.