Error in the log file when starting the server "Error fetching reserved words list"

Jon Williams4 hours ago

Hi,

I recently upgraded my traccar server from Raspbian bookworm to trixie and after the upgrade I'm getting the following error in the traccar log files when starting the server

2025-12-08 14:49:36  INFO: HikariPool-1 - Start completed.
2025-12-08 14:49:39  INFO: Error fetching reserved words list from JDBC driver - Unknown column 'RESERVED' in 'WHERE' - SQLSyntaxErrorException (... < DatabaseModule:91 < <gener:-1 < *:-1 < ... < MainModule:139 < <gener:-1 < ...)
2025-12-08 14:49:41  INFO: Successfully acquired change log lock
2025-12-08 14:49:41  INFO: Clearing database change log checksums for database mariadb
2025-12-08 14:49:41  INFO: Successfully released change log lock

Traccar seems to be working OK though. Should I be worried or can I safely ignore the error?

Supplementary information :-

I'm using a MySQL (MariaDB) database as the back end with the following in my config file

    <entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
    <entry key='database.url'>jdbc:mysql://localhost/traccar_db?zeroDateTimeBehavior=round&amp;serverTimezone=Europe/London&amp;allowPublicKeyRetrieval=true&amp;useSSL=false&amp;allowMultiQueries=true&amp;autoReconnect=true&amp;useUnicode=yes&amp;characterEncoding=UTF-8&amp;sessionVariables=sql_mode=''</entry>

DB migration method

I migrated the traccar database to the new server by dumping to flat file using mysqldump, and then importing that into the new database that I manually created on the new machine as follows

CREATE DATABASE traccar_db;
CREATE USER 'traccar'@'localhost' IDENTIFIED BY 'redacted';
GRANT ALL PRIVILEGES ON traccar_db.* TO 'traccar'@'localhost';
FLUSH PRIVILEGES;
QUIT

Thanks in advance for any advice

Jon.

Anton Tananaev3 hours ago

I think it should be fine, as long as everything else is working.

Jon Williams3 hours ago

Thank you Anton. Sudden errors always make me twitchy, but I will take your advice and ignore for the time being.

Anton Tananaev3 hours ago

It might cause problems on upgrading, so that's something to keep in mind.

Jon Williams3 hours ago

Looking at the logs - I transitioned to the new OS yesterday and started getting the error at that point. (but didn't notice it then - my bad)

This afternoon I upgraded traccar to 6.11.1 (from 6.10.0) and the upgrade seemed to work OK, with the database changes being applied with no other reported errors. I first noticed the error at this point.

If you want to know mariadb version numbers then I'm happy to supply.

Anton Tananaev2 hours ago

It sounds like it should be fine if database was updated.

Jon Williamsan hour ago

I have a fix. Change the jdbc connector to the mariadb connector (instead of the mysql connector) and the error goes away.

Instead of

    <entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
    <entry key='database.url'>jdbc:mysql://localhost/traccar_db?zeroDateTimeBehavior=round&amp;serverTimezone=Europe/London&amp;allowPublicKeyRetrieval=true&amp;useSSL=false&amp;allowMultiQueries=true&amp;autoReconnect=true&amp;useUnicode=yes&amp;characterEncoding=UTF-8&amp;sessionVariables=sql_mode=''</entry>

Use this

    <entry key='database.driver'>org.mariadb.jdbc.Driver</entry>
    <entry key='database.url'>jdbc:mariadb://localhost/traccar_db?zeroDateTimeBehavior=round&amp;serverTimezone=Europe/London&amp;allowPublicKeyRetrieval=true&amp;useSSL=false&amp;allowMultiQueries=true&amp;autoReconnect=true&amp;useUnicode=yes&amp;characterEncoding=UTF-8&amp;sessionVariables=sql_mode=''</entry>

I am pretty certain that Anton is correct and the error is is nothing to worry about, but the above fix seems to be a good workaround (for those that follow later.)