Traccar server 6.8.0 service failed to start
I have reverted back to older working version of Traccar 6.7.3 server which is good and operational!
root@traccar:/opt/traccar# systemctl status traccar
● traccar.service - traccar
Loaded: loaded (/etc/systemd/system/traccar.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-07-08 12:45:13 +08; 42s ago
Main PID: 8369 (java)
Tasks: 44 (limit: 760)
CPU: 1min 35.161s
CGroup: /system.slice/traccar.service
└─8369 /opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml
Jul 08 12:45:13 traccar systemd[1]: Started traccar.service - traccar.
Jul 08 12:45:44 traccar traccar[8369]: Database is up to date, no changesets to execute
Jul 08 12:45:44 traccar traccar[8369]: UPDATE SUMMARY
Jul 08 12:45:44 traccar traccar[8369]: Run: 0
Jul 08 12:45:44 traccar traccar[8369]: Previously run: 51
Jul 08 12:45:44 traccar traccar[8369]: Filtered out: 0
Jul 08 12:45:44 traccar traccar[8369]: -------------------------------
Jul 08 12:45:44 traccar traccar[8369]: Total change sets: 51
root@traccar:/opt/traccar#
Your lib folder clearly shows that you have not made a clean installation.
Starting install from scratch again after deleted /opt/traccar folder...
login as: root
root@192.168.88.250's password:
Linux traccar 6.12.35-v8+ #1891 SMP PREEMPT Mon Jun 30 15:33:03 BST 2025 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have no mail.
Last login: Tue Jul 8 13:03:22 2025 from 192.168.88.21
root@traccar:~# cd /opt/traccar
root@traccar:/opt/traccar# ls -l
total 637500
drwxr-xr-x 2 root root 4096 Jul 8 12:58 conf
root@traccar:/opt/traccar#
Just to be sure I did a clean installation on an aarch64 Linux:
wget https://github.com/traccar/traccar/releases/download/v6.8.1/traccar-linux-arm-6.8.1.zip
unzip traccar-linux-arm-6.8.1.zip
./traccar.run
service traccar start
Everything worked perfectly. No issues.
Either you're doing something wrong or there's something wrong with your host OS.
Okay. I rebooted the server and query if the traccar service is dead and old setup totally removed ... still getting same error after a new installed!
root@traccar:/opt/traccar# uname -a
Linux traccar 6.12.35-v8+ #1891 SMP PREEMPT Mon Jun 30 15:33:03 BST 2025 aarch64 GNU/Linux
root@traccar:/opt/traccar# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@traccar:/opt/traccar#
root@traccar:/opt/traccar# systemctl status traccar
○ traccar.service - traccar
Loaded: loaded (/etc/systemd/system/traccar.service; enabled; preset: enabled)
Active: inactive (dead) (Result: exit-code) since Tue 2025-07-08 13:16:16 +08; 4min 29s ago
Duration: 7ms
Process: 1585 ExecStart=/opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml (code=exited, status=203/EXEC)
Main PID: 1585 (code=exited, status=203/EXEC)
CPU: 4ms
Jul 08 13:16:16 traccar systemd[1]: Stopped traccar.service - traccar.
No idea. Send SSH details if you want me to take a look.
Ok. Great. Info sent via support email. Thanks alot. Anton.
I removed my existing cloned server database and traccar folder and reboot to begin fresh install with similar error too ... on a fresh copy of latest server version 6.8.1 failed to start.
I had some more issues with TimescaleDB, and disabled the TimescaleDB check for now to further investigate what went wrong.
It migrated and chunked all the Data, and afterwards Traccar could receive new data, but didnt show up in the interface. Its as if no data was ever being received.
It needed to drop the primary keys on tc_positions and tc_events, then add a new primary key with deviceid, id and fixtime on tc_positions.
But I'm not sure yet, if this is because the db has had 3 migrations behind it. The primary key name wasn't what Liquibase expected, so I had to manually rename it.
My current changeset is this here, but it still doesnt work correctly.
<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd"
logicalFilePath="changelog-6.8.0">
<changeSet author="author" id="changelog-6.8.0-timescale" runInTransaction="false">
<preConditions onFail="MARK_RAN">
<dbms type="postgresql"/>
<sqlCheck expectedResult="1">
SELECT COUNT(*) FROM pg_available_extensions WHERE name = 'timescaledb';
</sqlCheck>
</preConditions>
<sql splitStatements="true" endDelimiter=";">
CREATE EXTENSION IF NOT EXISTS timescaledb;
ALTER TABLE tc_positions DROP CONSTRAINT IF EXISTS tc_positions_pkey;
ALTER TABLE tc_events DROP CONSTRAINT IF EXISTS tc_events_pkey;
DROP INDEX IF EXISTS position_deviceid_fixtime;
DROP INDEX IF EXISTS event_deviceid_servertime;
ALTER TABLE tc_positions ADD PRIMARY KEY (id, deviceid, fixtime);
ALTER TABLE tc_events ADD PRIMARY KEY (id, deviceid, eventtime);
SELECT create_hypertable(
'tc_positions',
'fixtime',
partitioning_column => 'deviceid',
number_partitions => 8,
migrate_data => TRUE,
if_not_exists => TRUE
);
SELECT create_hypertable(
'tc_events',
'eventtime',
partitioning_column => 'deviceid',
number_partitions => 8,
migrate_data => TRUE,
if_not_exists => TRUE
);
CREATE INDEX IF NOT EXISTS tc_positions_id_idx ON tc_positions(id);
CREATE INDEX IF NOT EXISTS tc_events_id_idx ON tc_events(id);
CREATE INDEX IF NOT EXISTS position_deviceid_fixtime ON tc_positions(deviceid, fixtime);
CREATE INDEX IF NOT EXISTS event_deviceid_servertime ON tc_events(deviceid, eventtime);
</sql>
</changeSet>
</databaseChangeLog>
Juliet Tee, I checked the server and indeed there's something wrong. But I noticed that it's extremely slow and the amount of available RAM is really low. Not sure if it's related, but the server is almost unusable. Have you tried adding more resources?
Kalabint what was the primary key? btw it probably make sense to move this to a separate topic because the two issues are completely unrelated.
Ok. Anton. I am using Raspberry Pi 3B+ with 8 units of tracker device only.
I have to redo from scratch brand new OS to prove the error is not related to my existing setup or new setup. I guess newbies will face similar problem too with brand new setup with this new version 6.8.1.
I have formatted clean image of Raspberry Pi OS and just did the brand new installation of Traccar Server 6.8.1 with similar errors like previously.
I seriously feel there is a bug in your setup image 6.8.0 onwards and nothing wrong with my old image or existing brand new Raspberri Pi OS image.
Thanks anyway for your troubleshooting errort.
I think you should look into the root cause of the errors related to ... "slf4j" as we all suspected earlier. No errors to version 5.7.3 and previous upgrades is fine.
root@traccar:/opt/traccar# systemctl status traccar
× traccar.service - traccar
Loaded: loaded (/etc/systemd/system/traccar.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2025-07-10 15:02:33 +08; 1s ago
Duration: 689ms
Process: 2810 ExecStart=/opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml (code=exited, status=1/FAILURE)
Main PID: 2810 (code=exited, status=1/FAILURE)
CPU: 1.799s
Jul 10 15:02:33 traccar traccar[2810]: at org.traccar.Main.<clinit>(Main.java:42)
Jul 10 15:02:33 traccar traccar[2810]: Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
Jul 10 15:02:33 traccar traccar[2810]: at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
Jul 10 15:02:33 traccar traccar[2810]: at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
Jul 10 15:02:33 traccar traccar[2810]: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
Jul 10 15:02:33 traccar traccar[2810]: ... 1 more
Jul 10 15:02:33 traccar systemd[1]: traccar.service: Main process exited, code=exited, status=1/FAILURE
Jul 10 15:02:33 traccar systemd[1]: traccar.service: Failed with result 'exit-code'.
Jul 10 15:02:33 traccar systemd[1]: Stopped traccar.service - traccar.
Jul 10 15:02:33 traccar systemd[1]: traccar.service: Consumed 1.799s CPU time.
root@traccar:/opt/traccar#
Here is a source of the error ...
Derived from this error origin ...
What do you think?
You are the only person with this problem so far. We have something like 10 server on the new version and there are probably many other people using it without any issues. I still suspect it's something with your specific setup. If you don't believe me, try to set up a VM on some hosting. For example AWS or Oracle give free VMs you can test on.
Could there error means anything at version 6.8.1 ?