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.
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.
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.
That's not where the Docker version is defined.
Juliet, are you using a Docker image?
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?
Hi Michael,
Check the entrypoint path
entrypoint: ["/opt/traccar/jre/bin/java"]
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.
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..
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.
Perfect! I'm glad you fixed it. The error was because, starting with version 6.8, the path to the Java executable changed.
Только эти параметры не изменить в Synology. По факту придётся скачивать новый образ и с него выполнить новую установку, с новыми параметрами по умолчанию.
Спасёт только то, если база данных отдельная.
Только об этом ни кто в итоге не сказал, пришлось страдать и догадываться самому.
I am updating to say that in release 6.9, in my case, it is working again.
Thank you.