After updating MariaDB appears to have issues

[vankyvo]

After updating to the latest version, I noticed that my log shows the following line;

2025-05-26 17:51:12 ERROR: Main method error - Read timed out - SocketTimeoutException (... < DatabaseModule:90 < <gener:-1 < *:-1 < ... < MainModule:141 < <gener:-1 < ...)

[tananaev]

1. Which specific version?
2. What database driver are you using?
3. Please enable full stack traces and probably new log entry with it enabled.

[vankyvo]

Dear,

2025-05-26 18:16:08  INFO: Operating system name: Linux version: 4.4.302+ architecture: amd64
2025-05-26 18:16:08  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Alpine version: 17.0.15+6-alpine-r0
2025-05-26 18:16:08  INFO: Memory limit heap: 1024mb non-heap: 0mb
2025-05-26 18:16:08  INFO: Character encoding: UTF-8
2025-05-26 18:16:08  INFO: Version: 6.7.0
2025-05-26 18:16:08  INFO: Starting server...
2025-05-26 18:16:08  INFO: HikariPool-1 - Starting...
2025-05-26 18:16:37 ERROR: Main method error - unexpected end of stream, read 0 bytes from 4 (socket was closed by server) - EOFException (... < DatabaseModule:80 < <gener:-1 < *:-1 < ... < MainModule:141 < <gener:-1 < ...)

This is a clean startup,
Below is the MariaDB setup;

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>
<properties>

    <entry key='database.driver'>org.mariadb.jdbc.Driver</entry>
    <entry key='database.url'>jdbc:mariadb://192.168.178.5:32771/traccar_database?zeroDateTimeBehavior=round&amp;serverTimezone=UTC&amp;allowPublicKeyRetrieval=true&amp;useSSL=false&amp;allowMultiQueries=true&amp;autoReconnect=true&amp;useUnicode=yes&amp;characterEncoding=UTF-8&amp;sessionVariables=sql_mode=''</entry>
    <entry key='database.user'>Trac</entry>
    <entry key='database.password'>Car</entry>

</properties>

How would I go about and enable full traces?

[tananaev]

logger.fullStackTraces configuration option. But it seems like some database connection issue unrelated to Traccar itself.

[vankyvo]

that would be quite odd because it works perfectly fine for home-assistant with the same mariadb container,

Clients can log into the db fine...

[tananaev]

Maybe some compatibility issue with the new driver?

[vankyvo]

that could be, it stopped working after the most recent update

MariaDB and Traccar are both running on the latest versions,

Would you be able to try to replicate the problem on your end?

[tananaev]

We don't use MariaDB on our servers, but MySQL works just fine.

[vankyvo]

after playing around a lot of hours on this matter I think I might have figured out what is happening,

I deleted all documents, both on the MariaDB container and on the Traccar container,

When trying to connect the Traccar container with MariaDB from the first startup, when there are no files created in Traccar,
it does not connect with the DB,

When first allowing traccar to fully run under the default H2 config, after registering.
THEN you change the config file to the MySQL (as noted on the website here)
Then mariadb functions as expected.

I however am very curious if this connection will break after a new update from either Traccar or MariaDB.

[tananaev]

Seems to me like some container issues.

[alrassia]

I am facing the same issues with the database. I saw the same errors. At first it was consist on the errors as above in the traccar logs, then I downgraded to 6.7.0 and the issues resolved itself. I updated the docker image to 6.7.1 again and it also started working. However I do see the following errors in the mariadb logs after traccar starting, but after that the db connection seems to operate normally:

The mariadb logs show:

2025-06-01 20:13:55 24 [Warning] Aborted connection 24 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 28 [Warning] Aborted connection 28 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 19 [Warning] Aborted connection 19 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 25 [Warning] Aborted connection 25 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 18 [Warning] Aborted connection 18 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 27 [Warning] Aborted connection 27 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 22 [Warning] Aborted connection 22 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 26 [Warning] Aborted connection 26 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 20 [Warning] Aborted connection 20 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:13:55 21 [Warning] Aborted connection 21 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 38 [Warning] Aborted connection 38 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 37 [Warning] Aborted connection 37 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 31 [Warning] Aborted connection 31 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 33 [Warning] Aborted connection 33 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 29 [Warning] Aborted connection 29 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 39 [Warning] Aborted connection 39 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 30 [Warning] Aborted connection 30 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 35 [Warning] Aborted connection 35 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 32 [Warning] Aborted connection 32 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)
2025-06-01 20:21:08 36 [Warning] Aborted connection 36 to db: 'traccar' user: 'traccar' host: '172.17.0.1' (Got an error reading communication packets)

The errors show up 10x per startup of traccar, which could correspond to the threadpool of 10 traccar maintains.

I am using the debian images

Database driver is mariadb-java-client-3.5.3 in my case