Traccar server 6.8.0 service failed to start

Rene 4 months ago

I am updating to say that in release 6.9, in my case, it is working again.

pi@raspberrypi:~ $ docker run --rm -it --entrypoint sh traccar/traccar:6.9-alpine
/opt/traccar # /opt/traccar/jre/bin/java -version
openjdk version "21.0.8" 2025-07-15 LTS
OpenJDK Runtime Environment Temurin-21.0.8+9 (build 21.0.8+9-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.8+9 (build 21.0.8+9-LTS, mixed mode)
/opt/traccar # /opt/traccar/jre/bin/java -Xms256m -Xmx256m -Djava.net.preferIPv4Stack=true -jar tracker-server.jar conf/traccar.xml
Running Changeset: changelog-4.0-clean::changelog-4.0-clean::author
Running Changeset: changelog-4.0-clean::changelog-4.0-clean-common::author
Running Changeset: changelog-4.1::changelog-4.1-mssql::author
Running Changeset: changelog-4.7::changelog-4.7::author
Running Changeset: changelog-4.9::changelog-4.9::author
Running Changeset: changelog-4.10::changelog-4.10::author
Running Changeset: changelog-4.11::changelog-4.11::author
Running Changeset: changelog-4.13::changelog-4.13::author
Running Changeset: changelog-4.15::changelog-4.15::author
Running Changeset: changelog-5.0::changelog-5.0::author
Running Changeset: changelog-5.1::changelog-5.1::author
Running Changeset: changelog-5.2::changelog-5.2::author
Running Changeset: changelog-5.3::changelog-5.3::author
Running Changeset: changelog-5.4::changelog-5.4::author
Running Changeset: changelog-5.5::changelog-5.5::author
Running Changeset: changelog-5.6::changelog-5.6::author
Running Changeset: changelog-5.7::changelog-5.7::author
Running Changeset: changelog-5.8::changelog-5.8::author
Running Changeset: changelog-5.9::changelog-5.9::author
Running Changeset: changelog-5.10::changelog-5.10::author
Running Changeset: changelog-5.11::changelog-5.11::author
Running Changeset: changelog-6.2::changelog-6.2::author
Running Changeset: changelog-6.3::changelog-6.3-old::author
Running Changeset: changelog-6.3::changelog-6.3-new::author
Running Changeset: changelog-6.6::changelog-6.6::author
Running Changeset: changelog-6.7.0::changelog-6.7.0::author
Running Changeset: changelog-6.8.0::changelog-6.8.0-timescale::author
Running Changeset: changelog-6.9.0::changelog-6.9.0::author

UPDATE SUMMARY
Run:                         28
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:           28

Liquibase: Update has been successful. Rows affected: 1

Thank you.

Juliet Tee 4 months ago

Just to highlight that latest Traccar Server 6.9.0 still inherit the same problem with bindled Java version 21.0.7 with Traccar Server setup files.

Juliet Tee 4 months ago

Latest Traccar Server 6.9.0 still inherit the same problem with service unable to start with bundled Java version 21.0.7 which comes with Traccar Server setup files. I have to upgrade to Java version 21.0.8 for Traccar Server service to run properly for the moment until bugs fixes.

Rene 4 months ago

Hi Juliet,

I think the problem may be the version defined here: https://github.com/traccar/traccar/blob/master/.github/workflows/release.yml#L41
JDK_VERSION="21.0.7+6"

Let's see if Anton can confirm this.

Anton Tananaev 4 months ago

That's not where the Docker version is defined.

Rene 4 months ago

Juliet, are you using a Docker image?

Michael 3 months ago

Hi,

I am having the same problem updating from 6.7.3 to 6.9.1 with docker.
Error message: Failed starting container: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "java": executable file not found in $PATH: unknown

Any idea?

Rene 3 months ago

Hi Michael,

Check the entrypoint path

entrypoint: ["/opt/traccar/jre/bin/java"]

Michael 3 months ago

Hi Rene,

What to check exactly?
Was there a change from the docker image 6.7.3 to 6.9.1 as up to 6.7.3 every docker instance is running fine.
The only thing I do is a "recreate container" with the latest docker image (6.9.1) and the start of the container fails.

Michael 3 months ago

oh wait, I have old ENV variables set:

JAVA_ALPINE_VERSION 	8.212.04-r0
JAVA_HOME 	/usr/lib/jvm/java-1.8-openjdk/jre
JAVA_VERSION 	8u212
LANG 	C.UTF-8
PATH 	/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/java-1.8-openjdk/jre/bin:/usr/lib/jvm/java-1.8-openjdk/bin
TRACCAR_VERSION 	4.12

Can these be deleted? I set them long ago and it is working up to version 6.7.3..

Michael 3 months ago

OK. I think it is fixed. I had to delete all these ENV and ENTRYPOINT values in Portainer as it would override the new defaults.

Rene 3 months ago

Perfect! I'm glad you fixed it. The error was because, starting with version 6.8, the path to the Java executable changed.

kaket07 3 months ago

Только эти параметры не изменить в Synology. По факту придётся скачивать новый образ и с него выполнить новую установку, с новыми параметрами по умолчанию.
Спасёт только то, если база данных отдельная.

kaket07 3 months ago

Только об этом ни кто в итоге не сказал, пришлось страдать и догадываться самому.

dlc_1235321 3 months ago

Just to add an information. I am using the helm chart. And I was only able to resolve this changing the java command inside the values.yaml.

This is the original:
command: ["java", "-Xms512m", "-Xmx512m", "-Djava.net.preferIPv4Stack=true"]

And after modifying:
command: ["jre/bin/java", "-Xms512m", "-Xmx512m", "-Djava.net.preferIPv4Stack=true"]

Using the tag 6.10.0