traccar / traccar-docker Goto Github PK

Traccar Docker

traccar-docker's Introduction

Traccar

Overview

Traccar is an open source GPS tracking system. This repository contains Java-based back-end service. It supports more than 200 GPS protocols and more than 2000 models of GPS tracking devices. Traccar can be used with any major SQL database system. It also provides easy to use REST API.

Other parts of Traccar solution include:

There is also a set of mobile apps that you can use for tracking mobile devices:

Features

Some of the available features include:

Real-time GPS tracking
Driver behaviour monitoring
Detailed and summary reports
Geofencing functionality
Alarms and notifications
Account and device management
Email and SMS support

Build

Please read build from source documentation on the official website.

Team

Anton Tananaev ([email protected])
Andrey Kunitsyn ([email protected])

License

Apache License, Version 2.0

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

traccar-docker's People

Contributors

Stargazers

Watchers

Forkers

chesty franky1 souhaiebtar mapoloco tijnhendrikson magna-z oliv3 ardasysmic leemit meliani usbpendrive bischi1220 narmidm evrimulgen thebrain8791 r3vol-sarl codericbrainstorm zeppelinen jtonline99 lanxianhui aymanelarian ass-a2s zippynetworks dragonxu geanttechnology manniru edwincrug yashodhank sevencode renatofilipov mykoan crypt0ginge trackcar vineet019 zarumaru shahzaibb kondorsoft itsmbabel eddyslade vic20191109 krasi-georgiev fariias gajjucoderboi stskrp wvides emone dough29 chandusekhar arribada jotelha saitowers kotenev rakishmu skinsch jheduart daniel-labs marceluphd wkhaksar csinisa astraube davehlong andretimua cloudforks thegumza mrabbah gudangfilmgue balaur deskti 99minutos enoxos karadonga shygnome mm86133 maksim-se bar-software imageone10 salamatracker raceland-automacao-lda wexa adwisatya sean97140 gps-watch ferdinakusumah moosa-nasir aymenouledsahel rogernavarro myousefi62 tracall anirudh-ramesh sathasivamr inginjadipro shabakconsultantsinc gibby nimarosa d3ibys hoadnguyen socramjunio2 bhargavweb j2vdeveloper brownjv

traccar-docker's Issues

Traccar auto-starts after reboot

While this doesn't sound as a bug when first reading the subject, let me elaborate.

I use this container within an unRAID installation.
unRAID has the option to set which containers to auto-start and which to NOT auto-start.
For some reason, this container ignores the setting and auto-starts anyway.

Update repo location

I see that we are still using old https://github.com/tananaev/traccar/ location here. It should be updated to https://github.com/traccar/traccar/.

Document logger.console configuration option

Setting logger.console to true in traccar.xml file allow to configure the logging system to write on the standard output of the process. This is useful in containerised deployments. I had to crawl in the source code to discover this possibility. Any chance to see this documented in the traccar documentation or in docker hub documentation page ?

Update to 4.12

Hi @magna-z, could you update the image to the recently released version 4.12? Thanks! 🙂

Unable to load library 'systemd'

Hi, i've just discovered Traccar and love it!
I'm running the Docker image and everythings looks like it's working fine, but i get this error in the log:

WARN: No systemd support - Unable to load library 'systemd':
Error loading shared library libsystemd.so: No such file or directory
Error loading shared library libsystemd.so: No such file or directory
Native library (linux-x86-64/libsystemd.so) not found in resource path ([file:/opt/traccar/tracker-server.jar]) - UnsatisfiedLinkError (... < HealthCheckService:39 < Main:115 < *:148 < *:110)

I guess this is related to the Docker image (4.10-alpine) and also the server code, but i thought it's more appropriate here.

Docker compose file

Hi! I'm trying to use this with docker compose. Do you have any sample to start out? I want to use your Traccar container with HTTPS in my own Ubuntu server with ISPConfig/Let'sEncrypt.

Thanks!

How to mount the DB to an external folder?

I found these apparently old instructions: https://www.traccar.org/docker/ and tried adding
-v /my-database-folder:/opt/traccar/data/database to your instructions but no entry appears inside /my-database-folder

Please give me a hint how to make my DB survive inside a folder of my choice.

Update to 5.0

Just another ping to kindly ask to update the latest version, which was released recently. 😃

Create image for 4.10 version

MySQL Connection does not work

Hello,

many thanks for your work regarding this docker setup! I am able to use traccar with all of my gps devices, thats fine. But I am still using the H2 database and I want to switch to MySQL.

I want to use the MySQL on the Host Machine, which is running Ubuntu 16.04 and MySQL at version 5.7.33-0ubuntu0.16.04.1. I already created a database for traccar and also an user as well as a password for it. I double checked all of it. The user has access to the database. I tried to change the traccar.xml as mentioned in your instructions. I deleted the 4 rows regarding the H2 database and addes the following rows instead:

<entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
<entry key='database.url'>jdbc:mysql://localhost:3306/db_traccar?serverTimezone=UTC&useSSL=false&allowMultiQueries=true&autoReconnect=true&useUnicode=yes&characterEncoding=UTF-8&sessionVariables=sql_mode=''</entry>
<entry key='database.user'>traccar</entry>
<entry key='database.password'>myPassword</entry>

But after running the docker I cannot connect to the web UI anymore. Looking into the logs revealed:

2021-02-05 14:39:37 INFO: HikariPool-1 - Starting...
2021-02-05 14:41:12 ERROR: HikariPool-1 - Exception during pool initialization. - connect timed out - SocketTimeoutException (... < DataManager:126 < *:85 < Context:289 < Main:120 < ...)
2021-02-05 14:41:12 ERROR: Main method error - connect timed out - SocketTimeoutException (... < DataManager:126 < *:85 < Context:289 < Main:120 < ...)

over and over without end. I also changed the "localhost" in the url to the ip address of the host. But it had no effect. I also changed the "bind-address" parameter to 0.0.0.0 in the mysql config file (and restarted mysql).

But it is still the same. It does not work with MySQL database on the host.

What can I do else?

Update to 4.13

Hi @magna-z, could you publish a new image with 4.13? Thanks! :-)

update to 3.7

Hi would it be possible to get this docker updated on hub to version 3.7 of the traccar ?

Traccra needs Java 11 but Docker is based on Java 8

Since today update, I'm trying to launch traccar on docker but I'm getting the following error:

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/traccar/Main has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:495)

Traccar 4.13 doesn't support docker containers on Raspberry Pi, broken libseccomp2

$ docker run --platform linux/arm/v7 --restart always --name traccar --hostname traccar -p 80:8082 -p 5000-5150:5000-5150 -p 5000-5150:5000-5150/udp -v /var/docker/traccar/logs:/opt/traccar/logs:rw -v /var/docker/traccar/traccar.xml:/opt/traccar/conf/traccar.xml:ro traccar/traccar:4.13
is refused with "docker: Error response from daemon: image with reference traccar/traccar:4.13 was found but does not match the specified platform: wanted linux/arm/v7, actual: linux/amd64"

But works for
$ docker run --platform linux/arm/v7 --restart always --name traccar --hostname traccar -p 80:8082 -p 5000-5150:5000-5150 -p 5000-5150:5000-5150/udp -v /var/docker/traccar/logs:/opt/traccar/logs:rw -v /var/docker/traccar/traccar.xml:/opt/traccar/conf/traccar.xml:ro traccar/traccar:4.12

change Java heap size

Hi,

Could you inform me how to increase java heap size when we are using docker ?
I refer to this documentation https://www.traccar.org/optimization/,

Please Advice

Thanks in advance

Publish container for Traccar 4.2

Traccar 4.2 has been released 7 days ago, please release a container image with that version.

MySQL DB is locked

I have my Traccar DB into MariaDB. Whenever the host is restarted, I cannot get Traccar to boot up, it is something related to the DB being locked by an old session.

Below is my log for Traccar

Caused by: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by 7249574b5437 (172.18.0.8) since 2/21/23, 7:19 PM
	at liquibase.lockservice.StandardLockService.waitForLock(StandardLockService.java:275)
	at liquibase.Liquibase$18.run(Liquibase.java:2187)
	at liquibase.Scope.lambda$child$0(Scope.java:180)
	at liquibase.Scope.child(Scope.java:189)
	at liquibase.Scope.child(Scope.java:179)
	at liquibase.Scope.child(Scope.java:158)
	at liquibase.Liquibase.runInScope(Liquibase.java:2431)
	at liquibase.Liquibase.clearCheckSums(Liquibase.java:2182)
	at org.traccar.storage.DatabaseModule.provideDataSource(DatabaseModule.java:95)
	at org.traccar.storage.DatabaseModule$$FastClassByGuice$$1804533.GUICE$TRAMPOLINE(<generated>)
	at org.traccar.storage.DatabaseModule$$FastClassByGuice$$1804533.apply(<generated>)
	at com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:260)
	at com.google.inject.internal.ProviderMethod.doProvision(ProviderMethod.java:171)
	at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.provision(InternalProviderInstanceBindingImpl.java:185)
	at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.get(InternalProviderInstanceBindingImpl.java:162)
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
	at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:169)
	at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:45)
	at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:40)
	at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:60)
	at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
	at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91)
	at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:300)
	at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:60)
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
	at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:169)
	at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:45)
	at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1101)`

And this is my compose for both Traccar anr MariaDB

  traccar:
    container_name: traccar
    restart: always
    volumes:
      - $LOCAL_TIME:/etc/localtime:ro
      - $PERSIST/traccar/logs:/opt/traccar/logs:rw
      - $PERSIST/traccar/traccar.xml:/opt/traccar/conf/traccar.xml:ro
    ports:
      - 8082:8082
    depends_on: #https://www.traccar.org/mysql/
      - mariadb
    image: 'traccar/traccar:alpine'`

  mariadb:
    container_name: mariadb
    restart: $RESTART_POLICY
    environment:
       - MARIADB_ROOT_PASSWORD=$DB_PASSWORD
       - MARIADB_USER=traccar
       - MARIADB_PASSWORD=$DB_PASSWORD
       - MARIADB_DATABASE=traccar
       - MARIADB_ROOT_HOST=192.168.1.10
       - MYSQL_ROOT_PASSWORD=$DB_PASSWORD
       - PGID=$PGID
       - PUID=$PUID
       - TZ=$TZ
    volumes:
       - $PERSIST/mariadb:/config
       - $LOCAL_TIME:/etc/localtime:ro
mysql --user=[User] --password=[Password] -h[Host] [db_name]<[mysql_file]
    healthcheck:
      test: ["CMD", "mysqladmin", "ping", "--silent"]
    ports:
      - 3306:3306
    tty: true
    image: 'lscr.io/linuxserver/mariadb:latest'

This is my traccar.xml file

<properties>
<entry key="config.default">./conf/default.xml</entry>
<!-- 

    This is the main configuration file. All your configuration parameters should be placed in this file.

    Default configuration parameters are located in the "default.xml" file. You should not modify it to avoid issues
    with upgrading to a new version. Parameters in the main config file override values in the default file. Do not
    remove "config.default" parameter from this file unless you know what you are doing.

    For list of available parameters see following page: https://www.traccar.org/configuration-file/

<!--  MariaDB-MySQL  -->
<!--  <entry key='database.driver'>com.mysql.jdbc.Driver</entry>  -->
<entry key="database.driver">com.mysql.cj.jdbc.Driver</entry>
<entry key="database.url">jdbc:mysql://mariadb:3306/traccar?serverTimezone=Australia/Melbourne&allowPublicKeyRetrieval=true&useSSL=false&allowMultiQueries=true&autoReconnect=true&useUnicode=yes&characterEncoding=UTF-8&sessionVariables=sql_mode=''</entry>
<entry key="database.user">traccar</entry>
<entry key="database.password">1234ABCD</entry>
<!--  GeoCoder  -->
<entry key="geocoder.enable">true</entry>
<entry key="geocoder.type">nominatim</entry>
<entry key="geocoder.url">http://188.40.20.228/nominatim/reverse.php</entry>
<entry key="geocoder.format">%r, %h, %u, %t - %s</entry>
</properties>

Update to 4.14

To keep the tradition alive, here's a a friendly ping for @magna-z to please update to 4.14 ;-)

Add a flag to force unlocking the database tables at startup

We are running traccar on a Rpi which runs on battery and quite often it doesn't get shutdown gracefully which leaves the db tables lockes.
Would you accept a PR that adds a flag at startup that forces db unlocking?

something like

java -cp lib/h2*.jar org.h2.tools.Shell -url "jdbc:h2:/opt/traccar/data/database" -driver org.h2.Driver -user sa
SELECT * FROM PUBLIC.DATABASECHANGELOGLOCK;
update PUBLIC.DATABASECHANGELOGLOCK set locked=0 WHERE ID=1;

Memory slowly being eaten by java

Very happy with your traccar build, but I've noticed that over a certain amount of time, the java process just keeps eating more and more ram (typical of java...) and when running on low-RAM Amazon EC2, it can cause a OOM and crash the entire EC2.

Is there any chance you could cap ram usage with "-Xmx XXX" or maybe we can pass a variable in the docker run command?

Cheers!

Docker hub automated builds

Do we need to do anything about this?

https://success.docker.com/article/github-services-to-webhooks-migration

Abnormal RAM usage

As referenced on the forums in this post I have an issue with a docker-compose deployment.

RAM usage shoots up to 6GB with no load right away, spawning a huge number of java processes as you can see here: https://imgur.com/a/v4PZNrE

I did try using the docker run command on the project homepage, and still have a huge ram usage, and lots of java processes.

What could be going wrong? I did try both using the traccar/traccar-docker image and building from Dockerfile, to no change.

deploy trracr on pine64 running armbian buster

hi, I tried to deploy traccar/traccar:latest and also traccar/traccar:4.10-alpine to my pine64 running armbian buster.
But badly both versions wasn't running and the log shows this error:

standard_init_linux.go:211: exec user process caused "exec format error"

Can anyone help me to get it working? I think it also caused of arm compatibility? Is there anything to do to get your multiarch version running?

Thanks so much!
Tobi

Originally posted by @toblie in #53 (comment)

Docker-compose support

Hi,

It is possible to provide an official docker-compose file to run this docker?

Regards

upgrade to 3.8 :)

Hey sorry to bother you again but he just relased version 3.8, you mind updating your image for that?

https://www.traccar.org/blog/traccar-3-8/

Raspberry Pi 4 8GB modified Dockerfile

Current dockerfile did for some reason not work on my Pi 4 so modified it a bit.

FROM debian:latest

ENV TRACCAR_VERSION 4.10

WORKDIR /opt/traccar

RUN set -ex && \
    apt-get update &&\
    TERM=xterm DEBIAN_FRONTEND=noninteractive apt-get install --yes --no-install-recommends unzip wget default-jre && \
    wget -qO /tmp/traccar.zip https://github.com/traccar/traccar/releases/download/v$TRACCAR_VERSION/traccar-other-$TRACCAR_VERSION.zip && \
    unzip -qo /tmp/traccar.zip -d /opt/traccar && \
    apt-get autoremove --yes unzip wget && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/* /tmp/*

ENTRYPOINT ["java", "-Xms512m", "-Xmx512m", "-Djava.net.preferIPv4Stack=true"]

CMD ["-jar", "tracker-server.jar", "conf/traccar.xml"]

To create the Docker:

sudo nano Dockerfile (insert text above)
docker build -t debian-traccar-nginx .

After creating a volume traccar_raspberry under docker volumes

docker run -d \
  --name Traccar \
  -p 5002:5002/tcp \
  -p 5002:5002/udp \
  -p 5055:5055/tcp \
  -p 5093:5093/tcp \
  -p 5093:5093/udp \
  -p 82:8082 \
  --mount source=traccar_raspberry,target=/opt/traccar \
  --restart=unless-stopped \
  debian-traccar-nginx:latest

I am now a happy man!

Deploy using docker compose throw error='Out of memory'

I try to deploy using docker compose file for traccar in a 1gb DO droplet, but its throwing following error

traccar-gps    | OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000eaaa0000, 357957632, 0) failed; error='Out of memory' (errno=12)
traccar-gps    | #
traccar-gps    | # There is insufficient memory for the Java Runtime Environment to continue.
traccar-gps    | # Native memory allocation (mmap) failed to map 357957632 bytes for committing reserved memory.

Docker Hub alternative

@magna-z, looks like Docker is removing a free team option for Docker Hub. Is there a way to migrate to a non-team free account? I can probably create a repo as a personal account, right? What are the implications?

Increasing JVM memory size and other optimizations

As I look at some of the optimizations mentioned here, I see a number of ways to help incorporate them into Docker.

Is there way to make some of these optimizations through the Dockerfile? (e.g. turning the JVM size into an environment variable, etc.)

Using Docker as default deployment option

I have created a thread here to discuss it:

traccar/traccar#4048

Basically it's becoming harder to maintain old legacy installers and services, so I'm thinking of making Docker main deployment option.

The requirement would be the ease of installation and availability on all platforms (Linux, Mac and Windows).

@magna-z, what do you think about the idea? I see that your instructions are mostly focused on Linux deployment. What do we need to do to make it easily deployable on Windows and Mac?

Support for environment variables and files

I'm not sure if this is correct repo, but it is more related to docker.

It would be good to add support server configuration via environment variables, especially database config.
Editing config file is not that usual flow used by docker.

Also it would be good to support file variables for secrets https://docs.docker.com/engine/swarm/secrets/

How to find my log file (tracker-server.log) on synology installation

Hello,
I installed traccar on my synology nas through docker (https://hub.docker.com/r/magnaz/traccar/)
The service is online and I find the server at the internal IP: http://192.168.1.103:55000/

But: How to find my device in log file (tracker-server.log)?
I'm not a great expert ... sorry !!

With v5.0: java.util.zip.ZipException: invalid entry CRC

Thanks for the awesome project!

When I try to start v5.0 I get the following error:

[+] Running 4/4
 ⠿ traccar Pulled                                                                                                                                                                                              8.9s
   ⠿ df9b9388f04a Already exists                                                                                                                                                                               0.0s
   ⠿ 439c5aa8b3c7 Pull complete                                                                                                                                                                                0.6s
   ⠿ cacfe428443a Pull complete                                                                                                                                                                                7.0s
[+] Running 2/2
 ⠿ Network traccar_default      Created                                                                                                                                                                        0.1s
 ⠿ Container traccar-traccar-1  Created                                                                                                                                                                        0.3s
Attaching to traccar-traccar-1
traccar-traccar-1  | java.util.zip.ZipException: invalid entry CRC (expected 0xa1999cf7 but got 0x5532a62e)
traccar-traccar-1  |    at java.base/java.util.zip.ZipInputStream.read(ZipInputStream.java:224)
traccar-traccar-1  |    at java.base/java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:143)
traccar-traccar-1  |    at org.h2.util.Utils.loadResource(Utils.java:420)
traccar-traccar-1  |    at org.h2.util.Utils.getResource(Utils.java:386)
traccar-traccar-1  |    at org.h2.message.DbException.<clinit>(DbException.java:74)
traccar-traccar-1  |    at org.h2.message.TraceObject.<clinit>(TraceObject.java:108)
traccar-traccar-1  |    at org.h2.Driver.connect(Driver.java:59)
traccar-traccar-1  |    at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
traccar-traccar-1  |    at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:359)
traccar-traccar-1  |    at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
traccar-traccar-1  |    at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:470)
traccar-traccar-1  |    at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
traccar-traccar-1  |    at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:100)
traccar-traccar-1  |    at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
traccar-traccar-1  |    at org.traccar.database.DataManager.initDatabase(DataManager.java:120)
traccar-traccar-1  |    at org.traccar.database.DataManager.<init>(DataManager.java:79)
traccar-traccar-1  |    at org.traccar.Context.init(Context.java:307)
traccar-traccar-1  |    at org.traccar.Main.run(Main.java:113)
traccar-traccar-1  |    at org.traccar.Main.main(Main.java:107)

My docker-compose.yml:

services:
  traccar:
    image: traccar/traccar:latest
    ports:
      - 172.17.0.1:8082:8082
    volumes:
      - ./logs:/opt/traccar/logs
      - ./traccar.xml:/opt/traccar/conf/traccar.xml
      - ./data:/opt/traccar/data
    restart: always

When I change to image: traccar/traccar:4.15 everything works well.

Any ideas?

Thanks

WebUI shows 404 - Not found

Hi Team

Trying to update to the latest docker container "traccar/traccar", Traccar stopped worked entirely. (5.4)

In the Web UI I get the plain message: "404 - Not Found".
The log entry is down below.

Looks like it fails on systemd not found, but I have no idea what is causing this. Google and forums are of no help.

I already set this entry and it doesn't work: <entry key='web.healthCheck'>false</entry>
I am using a MySQL database driver, MariaDB 10.6.

Any help or hints towards the right direction are very much appreciated, thank you

2022-10-24 21:41:09  WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2022-10-24 21:41:10  INFO: Started o.e.j.s.ServletContextHandler@620572db{/,null,AVAILABLE}
2022-10-24 21:41:10  INFO: Started ServerConnector@7dbae40{HTTP/1.1, (http/1.1)}{0.0.0.0:8082}
2022-10-24 21:41:10  INFO: Started Server@638afcaa{STARTING}[10.0.12,sto=0] @9354ms
2022-10-24 21:41:10  WARN: No systemd support - Unable to load library 'systemd':
Error loading shared library libsystemd.so: No such file or directory
Error loading shared library libsystemd.so: No such file or directory
Native library (linux-x86-64/libsystemd.so) not found in resource path (tracker-server.jar) - UnsatisfiedLinkError (... < TaskHealthCheck:49 < <gener:-1 < *:-1 < ... < ScheduleManager:42 < ...)

Install information

2022-10-24 21:41:02  INFO: Operating system name: Linux version: 5.19.14-Unraid architecture: amd64
2022-10-24 21:41:02  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Alpine version: 11.0.17+8-alpine-r0

I also have this thread on the Traccar forum

Raspberry pi ARM support

Not sure if i'm missing something obvious or this image doesn't support the pi? some pointers as to how to get it going would very much appreciated. Thanks

SMS notifications

Dear,

Is it possible that the sms notifications don't work in docker? I get this error :

 WARN: SMS send failed - HTTP 500 Server Error - InternalServerErrorException (...)

my xml file:

<?xml version='1.0' encoding='UTF-8'?>

<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>

<properties>

   <entry key='config.default'>./conf/default.xml</entry>

    <!--

   This is the main configuration file. All your configuration parameters should be placed in this file.

    Default configuration parameters are located in the "default.xml" file. You should not modify it to avoid issues
    with upgrading to a new version. Parameters in the main config file override values in the default file. Do not
    remove "config.default" parameter from this file unless you know what you are doing.

    For list of available parameters see following page: https://www.traccar.org/configuration-file/

    -->

   <entry key='database.driver'>org.h2.Driver</entry>
   <entry key='database.url'>jdbc:h2:./data/database</entry>
   <entry key='database.user'>sa</entry>
   <entry key='database.password'></entry>

    <!-- position forwarding to mqtt -->
   <entry  key='forward.enable'>true</entry>
   <entry  key='forward.json'>true</entry>
   <entry  key='forward.url'>http://192.168.xxx.xxx:xxx/</entry>

   <!-- SMS Gateway -->
   <entry key='notificator.types'>sms</entry>
   <entry key='notificator.sms.manager.class'>org.traccar.sms.HttpSmsClient</entry>
   <entry key='sms.http.url'>http://192.168.xxx.xxx:xxxx/</entry>
   <entry key='sms.http.authorization'>xxxxxxxx</entry>
   <entry key='sms.http.template'>{"To": "{phone}","Msg": "{message}"}</entry>
</properties>

kind regards

error - Connection reset by peer - IOException (...)

I use Unraid and I am running Traccar Docker Version 4.11 and I am using MariaDB Version 10.4.16 in another docker for the database.

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is #####
Server version: 10.4.16-MariaDB-1:10.4.16+maria~bionic-log mariadb.org binary distribution

At this point, I only have two iPhones connected to the server via the Traccar Client app for testing purposes. I just connected the second client today and I am now receiving error - Connection reset by peer - IOException (...) in the logs every time my device connects. Yesterday, when only my client was connected, I did not have this problem. Also, the server has not been up for very long. I connected my first client about a week ago and I just created the database 2 days ago.

Actually, as I type this, I received a new error in the logs that I have not seen before. WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@26b1c55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value. The full logs are at the end of this post.

Here are the log files from the server:

2020-11-12 09:02:43  INFO: [46904558] connected
2020-11-12 09:02:43  INFO: [46904558: osmand < 198.233.237.1] HEX: 504f5354202f3f69643d363830353735352674696d657374616d703d31363035323030353632266c61743d34372e363130323532266c6f6e3d2d3132322e3332393534322673706565643d302662656172696e673d3026616c7469747564653d39312e35393539323731353230353534382661636375726163793d32392e333436343130353338383131333426626174743d383020485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:02:43  INFO: [46904558: osmand > 198.233.237.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:02:43  INFO: [46904558] id: 6805755, time: 2020-11-12 09:02:42, lat: 47.61025, lon: -122.32954, course: 0.0, accuracy: 29.3
2020-11-12 09:02:43  WARN: [46904558] error - Connection reset by peer - IOException (...)
2020-11-12 09:02:43  INFO: [46904558] disconnected
2020-11-12 09:06:59  INFO: [0877220a] connected
2020-11-12 09:06:59  INFO: [0877220a: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323030383139266c61743d34372e353430373737266c6f6e3d2d3132322e3237313033392673706565643d302662656172696e673d3026616c7469747564653d33352e37383336353730373339373436312661636375726163793d313026626174743d383320485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:06:59  INFO: [0877220a: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:06:59  INFO: [0877220a] id: 277587, time: 2020-11-12 09:06:59, lat: 47.54078, lon: -122.27104, course: 0.0, accuracy: 10.0
2020-11-12 09:07:29  INFO: [0877220a] disconnected
2020-11-12 09:07:43  INFO: [5c28e276] connected
2020-11-12 09:07:43  WARN: [5c28e276] error - Connection reset by peer - IOException (...)
2020-11-12 09:07:43  INFO: [5c28e276] disconnected
2020-11-12 09:11:59  INFO: [8d553a07] connected
2020-11-12 09:11:59  INFO: [8d553a07: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031313139266c61743d34372e353430373737266c6f6e3d2d3132322e3237313033392673706565643d302662656172696e673d3026616c7469747564653d33362e35383232343130353833343936312661636375726163793d313026626174743d383320485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:11:59  INFO: [8d553a07: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:11:59  INFO: [8d553a07] id: 277587, time: 2020-11-12 09:11:59, lat: 47.54078, lon: -122.27104, course: 0.0, accuracy: 10.0
2020-11-12 09:12:29  INFO: [8d553a07] disconnected
2020-11-12 09:12:44  INFO: [ba5083df] connected
2020-11-12 09:12:44  WARN: [ba5083df] error - Connection reset by peer - IOException (...)
2020-11-12 09:12:44  INFO: [ba5083df] disconnected
2020-11-12 09:17:00  INFO: [bb2ec03b] connected
2020-11-12 09:17:00  INFO: [bb2ec03b: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031343230266c61743d34372e353430373932266c6f6e3d2d3132322e3237313039332673706565643d302662656172696e673d3026616c7469747564653d34312e34353432353033333536393333362661636375726163793d313026626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:17:00  INFO: [bb2ec03b: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:17:00  INFO: [bb2ec03b] id: 277587, time: 2020-11-12 09:17:00, lat: 47.54079, lon: -122.27109, course: 0.0, accuracy: 10.0
2020-11-12 09:17:30  INFO: [bb2ec03b] disconnected
2020-11-12 09:17:45  INFO: [579705fe] connected
2020-11-12 09:17:45  WARN: [579705fe] error - Connection reset by peer - IOException (...)
2020-11-12 09:17:45  INFO: [579705fe] disconnected
2020-11-12 09:22:00  INFO: [fb6fa746] connected
2020-11-12 09:22:00  INFO: [fb6fa746: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031373230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e33363935303237323333343438332661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:22:00  INFO: [fb6fa746: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:22:00  INFO: [fb6fa746] id: 277587, time: 2020-11-12 09:22:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:22:30  INFO: [fb6fa746] disconnected
2020-11-12 09:22:46  INFO: [2a96a2d7] connected
2020-11-12 09:22:46  WARN: [2a96a2d7] error - Connection reset by peer - IOException (...)
2020-11-12 09:22:46  INFO: [2a96a2d7] disconnected
2020-11-12 09:27:00  INFO: [252cc16d] connected
2020-11-12 09:27:00  INFO: [252cc16d: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032303230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e343134323833383635323936342661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:27:00  INFO: [252cc16d: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:27:00  INFO: [252cc16d] id: 277587, time: 2020-11-12 09:27:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:27:31  INFO: [252cc16d] disconnected
2020-11-12 09:27:47  INFO: [77616c94] connected
2020-11-12 09:27:47  WARN: [77616c94] error - Connection reset by peer - IOException (...)
2020-11-12 09:27:47  INFO: [77616c94] disconnected
2020-11-12 09:32:00  INFO: [349203be] connected
2020-11-12 09:32:00  INFO: [349203be: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032333230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e34383838353036313639393534342661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:32:00  INFO: [349203be: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:32:00  INFO: [349203be] id: 277587, time: 2020-11-12 09:32:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:32:30  INFO: [349203be] disconnected
2020-11-12 09:32:48  INFO: [945b7bcb] connected
2020-11-12 09:32:48  WARN: [945b7bcb] error - Connection reset by peer - IOException (...)
2020-11-12 09:32:48  INFO: [945b7bcb] disconnected
2020-11-12 09:37:00  INFO: [0f6d0076] connected
2020-11-12 09:37:00  INFO: [0f6d0076: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032363230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e35303135313436323539343333372661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:37:00  INFO: [0f6d0076: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:37:00  INFO: [0f6d0076] id: 277587, time: 2020-11-12 09:37:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:37:30  INFO: [0f6d0076] disconnected
2020-11-12 09:37:48  INFO: [03ae082d] connected
2020-11-12 09:37:48  WARN: [03ae082d] error - Connection reset by peer - IOException (...)
2020-11-12 09:37:48  INFO: [03ae082d] disconnected
2020-11-12 09:42:01  INFO: [f07c47e1] connected
2020-11-12 09:42:01  INFO: [f07c47e1: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032393231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e32333831313839343738373030312661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:42:01  INFO: [f07c47e1: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:42:01  INFO: [f07c47e1] id: 277587, time: 2020-11-12 09:42:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:42:31  INFO: [f07c47e1] disconnected
2020-11-12 09:42:49  INFO: [a9261418] connected
2020-11-12 09:42:49  WARN: [a9261418] error - Connection reset by peer - IOException (...)
2020-11-12 09:42:49  INFO: [a9261418] disconnected
2020-11-12 09:47:01  INFO: [a48df3f3] connected
2020-11-12 09:47:01  INFO: [a48df3f3: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033323231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e37303239303231363130393731332661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:47:01  INFO: [a48df3f3: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:47:01  INFO: [a48df3f3] id: 277587, time: 2020-11-12 09:47:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:47:31  INFO: [a48df3f3] disconnected
2020-11-12 09:47:49  INFO: [a8b59851] connected
2020-11-12 09:47:49  WARN: [a8b59851] error - Connection reset by peer - IOException (...)
2020-11-12 09:47:49  INFO: [a8b59851] disconnected
2020-11-12 09:52:01  INFO: [fd5b3f97] connected
2020-11-12 09:52:01  INFO: [fd5b3f97: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033353231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e35373134343230353839373635342661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:52:01  INFO: [fd5b3f97: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:52:01  INFO: [fd5b3f97] id: 277587, time: 2020-11-12 09:52:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:52:31  INFO: [fd5b3f97] disconnected
2020-11-12 09:52:50  INFO: [9d03f21d] connected
2020-11-12 09:52:50  WARN: [9d03f21d] error - Connection reset by peer - IOException (...)
2020-11-12 09:52:50  INFO: [9d03f21d] disconnected
2020-11-12 09:57:02  INFO: [bd5ad5de] connected
2020-11-12 09:57:02  INFO: [bd5ad5de: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033383232266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e34343634343337353736363730332661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:57:02  INFO: [bd5ad5de: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:57:02  INFO: [bd5ad5de] id: 277587, time: 2020-11-12 09:57:02, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:57:32  INFO: [bd5ad5de] disconnected
2020-11-12 09:57:50  INFO: [c5241048] connected
2020-11-12 09:57:50  WARN: [c5241048] error - Connection reset by peer - IOException (...)
2020-11-12 09:57:50  INFO: [c5241048] disconnected
2020-11-12 10:02:02  INFO: [8b9ba6db] connected
2020-11-12 10:02:02  INFO: [8b9ba6db: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034313232266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d33382e39373638393431303739313930322661636375726163793d313026626174743d383020485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:02:02  INFO: [8b9ba6db: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:02:02  INFO: [8b9ba6db] id: 277587, time: 2020-11-12 10:02:02, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:02:32  INFO: [8b9ba6db] disconnected
2020-11-12 10:02:51  INFO: [de2c431a] connected
2020-11-12 10:02:51  WARN: [de2c431a] error - Connection reset by peer - IOException (...)
2020-11-12 10:02:51  INFO: [de2c431a] disconnected
2020-11-12 10:07:03  INFO: [5d57336d] connected
2020-11-12 10:07:03  INFO: [5d57336d: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034343233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d33392e37343235363531353731323337342661636375726163793d313026626174743d373920485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:07:03  INFO: [5d57336d: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:07:03  INFO: [5d57336d] id: 277587, time: 2020-11-12 10:07:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:07:33  INFO: [5d57336d] disconnected
2020-11-12 10:07:52  INFO: [006d6435] connected
2020-11-12 10:07:52  WARN: [006d6435] error - Connection reset by peer - IOException (...)
2020-11-12 10:07:52  INFO: [006d6435] disconnected
2020-11-12 10:12:03  INFO: [1ff03709] connected
2020-11-12 10:12:03  INFO: [1ff03709: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034373233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e32323130393634353438313832322661636375726163793d313026626174743d373720485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:12:03  INFO: [1ff03709: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:12:03  INFO: [1ff03709] id: 277587, time: 2020-11-12 10:12:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:12:33  INFO: [1ff03709] disconnected
2020-11-12 10:12:52  INFO: [d52b1288] connected
2020-11-12 10:12:52  WARN: [d52b1288] error - Connection reset by peer - IOException (...)
2020-11-12 10:12:52  INFO: [d52b1288] disconnected
2020-11-12 10:17:03  INFO: [c270a8d9] connected
2020-11-12 10:17:03  INFO: [c270a8d9: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035303233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e36313334343631393034343338322661636375726163793d313026626174743d373620485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9] id: 277587, time: 2020-11-12 10:17:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:17:33  INFO: [c270a8d9] disconnected
2020-11-12 10:17:52  INFO: [9bd54c2e] connected
2020-11-12 10:17:52  WARN: [9bd54c2e] error - Connection reset by peer - IOException (...)
2020-11-12 10:17:52  INFO: [9bd54c2e] disconnected

And the second error:

2020-11-12 10:22:04  INFO: [9587f2b7] connected
2020-11-12 10:22:04  INFO: [9587f2b7: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035333234266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e393439333732333535393932322661636375726163793d313026626174743d373520485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@26b1c55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@1a05e3fd (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b8f1c9f (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@174cfe55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@4d1fd15d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@78b0c908 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b285965 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  INFO: [9587f2b7: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:22:04  INFO: [9587f2b7] id: 277587, time: 2020-11-12 10:22:04, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:22:34  INFO: [9587f2b7] disconnected

Any help with this is much appreciated. I am in the process of building a Raspberry Pi Client for Traccar, but I need these errors resolved before I can move forward.

Thank you!

error - Connection reset by peer

I use Unraid and I am running Traccar Docker Version 4.11 and I am using MariaDB Version 10.4.16 in another docker for the database.

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is #####
Server version: 10.4.16-MariaDB-1:10.4.16+maria~bionic-log mariadb.org binary distribution

Here are the log files from the server:

2020-11-12 09:02:43  INFO: [46904558] connected
2020-11-12 09:02:43  INFO: [46904558: osmand < 198.233.237.1] HEX: 504f5354202f3f69643d363830353735352674696d657374616d703d31363035323030353632266c61743d34372e363130323532266c6f6e3d2d3132322e3332393534322673706565643d302662656172696e673d3026616c7469747564653d39312e35393539323731353230353534382661636375726163793d32392e333436343130353338383131333426626174743d383020485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:02:43  INFO: [46904558: osmand > 198.233.237.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:02:43  INFO: [46904558] id: 6805755, time: 2020-11-12 09:02:42, lat: 47.61025, lon: -122.32954, course: 0.0, accuracy: 29.3
2020-11-12 09:02:43  WARN: [46904558] error - Connection reset by peer - IOException (...)
2020-11-12 09:02:43  INFO: [46904558] disconnected
2020-11-12 09:06:59  INFO: [0877220a] connected
2020-11-12 09:06:59  INFO: [0877220a: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323030383139266c61743d34372e353430373737266c6f6e3d2d3132322e3237313033392673706565643d302662656172696e673d3026616c7469747564653d33352e37383336353730373339373436312661636375726163793d313026626174743d383320485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:06:59  INFO: [0877220a: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:06:59  INFO: [0877220a] id: 277587, time: 2020-11-12 09:06:59, lat: 47.54078, lon: -122.27104, course: 0.0, accuracy: 10.0
2020-11-12 09:07:29  INFO: [0877220a] disconnected
2020-11-12 09:07:43  INFO: [5c28e276] connected
2020-11-12 09:07:43  WARN: [5c28e276] error - Connection reset by peer - IOException (...)
2020-11-12 09:07:43  INFO: [5c28e276] disconnected
2020-11-12 09:11:59  INFO: [8d553a07] connected
2020-11-12 09:11:59  INFO: [8d553a07: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031313139266c61743d34372e353430373737266c6f6e3d2d3132322e3237313033392673706565643d302662656172696e673d3026616c7469747564653d33362e35383232343130353833343936312661636375726163793d313026626174743d383320485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:11:59  INFO: [8d553a07: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:11:59  INFO: [8d553a07] id: 277587, time: 2020-11-12 09:11:59, lat: 47.54078, lon: -122.27104, course: 0.0, accuracy: 10.0
2020-11-12 09:12:29  INFO: [8d553a07] disconnected
2020-11-12 09:12:44  INFO: [ba5083df] connected
2020-11-12 09:12:44  WARN: [ba5083df] error - Connection reset by peer - IOException (...)
2020-11-12 09:12:44  INFO: [ba5083df] disconnected
2020-11-12 09:17:00  INFO: [bb2ec03b] connected
2020-11-12 09:17:00  INFO: [bb2ec03b: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031343230266c61743d34372e353430373932266c6f6e3d2d3132322e3237313039332673706565643d302662656172696e673d3026616c7469747564653d34312e34353432353033333536393333362661636375726163793d313026626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:17:00  INFO: [bb2ec03b: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:17:00  INFO: [bb2ec03b] id: 277587, time: 2020-11-12 09:17:00, lat: 47.54079, lon: -122.27109, course: 0.0, accuracy: 10.0
2020-11-12 09:17:30  INFO: [bb2ec03b] disconnected
2020-11-12 09:17:45  INFO: [579705fe] connected
2020-11-12 09:17:45  WARN: [579705fe] error - Connection reset by peer - IOException (...)
2020-11-12 09:17:45  INFO: [579705fe] disconnected
2020-11-12 09:22:00  INFO: [fb6fa746] connected
2020-11-12 09:22:00  INFO: [fb6fa746: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031373230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e33363935303237323333343438332661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:22:00  INFO: [fb6fa746: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:22:00  INFO: [fb6fa746] id: 277587, time: 2020-11-12 09:22:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:22:30  INFO: [fb6fa746] disconnected
2020-11-12 09:22:46  INFO: [2a96a2d7] connected
2020-11-12 09:22:46  WARN: [2a96a2d7] error - Connection reset by peer - IOException (...)
2020-11-12 09:22:46  INFO: [2a96a2d7] disconnected
2020-11-12 09:27:00  INFO: [252cc16d] connected
2020-11-12 09:27:00  INFO: [252cc16d: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032303230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e343134323833383635323936342661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:27:00  INFO: [252cc16d: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:27:00  INFO: [252cc16d] id: 277587, time: 2020-11-12 09:27:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:27:31  INFO: [252cc16d] disconnected
2020-11-12 09:27:47  INFO: [77616c94] connected
2020-11-12 09:27:47  WARN: [77616c94] error - Connection reset by peer - IOException (...)
2020-11-12 09:27:47  INFO: [77616c94] disconnected
2020-11-12 09:32:00  INFO: [349203be] connected
2020-11-12 09:32:00  INFO: [349203be: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032333230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e34383838353036313639393534342661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:32:00  INFO: [349203be: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:32:00  INFO: [349203be] id: 277587, time: 2020-11-12 09:32:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:32:30  INFO: [349203be] disconnected
2020-11-12 09:32:48  INFO: [945b7bcb] connected
2020-11-12 09:32:48  WARN: [945b7bcb] error - Connection reset by peer - IOException (...)
2020-11-12 09:32:48  INFO: [945b7bcb] disconnected
2020-11-12 09:37:00  INFO: [0f6d0076] connected
2020-11-12 09:37:00  INFO: [0f6d0076: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032363230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e35303135313436323539343333372661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:37:00  INFO: [0f6d0076: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:37:00  INFO: [0f6d0076] id: 277587, time: 2020-11-12 09:37:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:37:30  INFO: [0f6d0076] disconnected
2020-11-12 09:37:48  INFO: [03ae082d] connected
2020-11-12 09:37:48  WARN: [03ae082d] error - Connection reset by peer - IOException (...)
2020-11-12 09:37:48  INFO: [03ae082d] disconnected
2020-11-12 09:42:01  INFO: [f07c47e1] connected
2020-11-12 09:42:01  INFO: [f07c47e1: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032393231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e32333831313839343738373030312661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:42:01  INFO: [f07c47e1: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:42:01  INFO: [f07c47e1] id: 277587, time: 2020-11-12 09:42:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:42:31  INFO: [f07c47e1] disconnected
2020-11-12 09:42:49  INFO: [a9261418] connected
2020-11-12 09:42:49  WARN: [a9261418] error - Connection reset by peer - IOException (...)
2020-11-12 09:42:49  INFO: [a9261418] disconnected
2020-11-12 09:47:01  INFO: [a48df3f3] connected
2020-11-12 09:47:01  INFO: [a48df3f3: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033323231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e37303239303231363130393731332661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:47:01  INFO: [a48df3f3: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:47:01  INFO: [a48df3f3] id: 277587, time: 2020-11-12 09:47:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:47:31  INFO: [a48df3f3] disconnected
2020-11-12 09:47:49  INFO: [a8b59851] connected
2020-11-12 09:47:49  WARN: [a8b59851] error - Connection reset by peer - IOException (...)
2020-11-12 09:47:49  INFO: [a8b59851] disconnected
2020-11-12 09:52:01  INFO: [fd5b3f97] connected
2020-11-12 09:52:01  INFO: [fd5b3f97: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033353231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e35373134343230353839373635342661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:52:01  INFO: [fd5b3f97: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:52:01  INFO: [fd5b3f97] id: 277587, time: 2020-11-12 09:52:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:52:31  INFO: [fd5b3f97] disconnected
2020-11-12 09:52:50  INFO: [9d03f21d] connected
2020-11-12 09:52:50  WARN: [9d03f21d] error - Connection reset by peer - IOException (...)
2020-11-12 09:52:50  INFO: [9d03f21d] disconnected
2020-11-12 09:57:02  INFO: [bd5ad5de] connected
2020-11-12 09:57:02  INFO: [bd5ad5de: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033383232266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e34343634343337353736363730332661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:57:02  INFO: [bd5ad5de: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:57:02  INFO: [bd5ad5de] id: 277587, time: 2020-11-12 09:57:02, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:57:32  INFO: [bd5ad5de] disconnected
2020-11-12 09:57:50  INFO: [c5241048] connected
2020-11-12 09:57:50  WARN: [c5241048] error - Connection reset by peer - IOException (...)
2020-11-12 09:57:50  INFO: [c5241048] disconnected
2020-11-12 10:02:02  INFO: [8b9ba6db] connected
2020-11-12 10:02:02  INFO: [8b9ba6db: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034313232266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d33382e39373638393431303739313930322661636375726163793d313026626174743d383020485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:02:02  INFO: [8b9ba6db: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:02:02  INFO: [8b9ba6db] id: 277587, time: 2020-11-12 10:02:02, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:02:32  INFO: [8b9ba6db] disconnected
2020-11-12 10:02:51  INFO: [de2c431a] connected
2020-11-12 10:02:51  WARN: [de2c431a] error - Connection reset by peer - IOException (...)
2020-11-12 10:02:51  INFO: [de2c431a] disconnected
2020-11-12 10:07:03  INFO: [5d57336d] connected
2020-11-12 10:07:03  INFO: [5d57336d: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034343233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d33392e37343235363531353731323337342661636375726163793d313026626174743d373920485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:07:03  INFO: [5d57336d: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:07:03  INFO: [5d57336d] id: 277587, time: 2020-11-12 10:07:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:07:33  INFO: [5d57336d] disconnected
2020-11-12 10:07:52  INFO: [006d6435] connected
2020-11-12 10:07:52  WARN: [006d6435] error - Connection reset by peer - IOException (...)
2020-11-12 10:07:52  INFO: [006d6435] disconnected
2020-11-12 10:12:03  INFO: [1ff03709] connected
2020-11-12 10:12:03  INFO: [1ff03709: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034373233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e32323130393634353438313832322661636375726163793d313026626174743d373720485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:12:03  INFO: [1ff03709: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:12:03  INFO: [1ff03709] id: 277587, time: 2020-11-12 10:12:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:12:33  INFO: [1ff03709] disconnected
2020-11-12 10:12:52  INFO: [d52b1288] connected
2020-11-12 10:12:52  WARN: [d52b1288] error - Connection reset by peer - IOException (...)
2020-11-12 10:12:52  INFO: [d52b1288] disconnected
2020-11-12 10:17:03  INFO: [c270a8d9] connected
2020-11-12 10:17:03  INFO: [c270a8d9: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035303233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e36313334343631393034343338322661636375726163793d313026626174743d373620485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9] id: 277587, time: 2020-11-12 10:17:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:17:33  INFO: [c270a8d9] disconnected
2020-11-12 10:17:52  INFO: [9bd54c2e] connected
2020-11-12 10:17:52  WARN: [9bd54c2e] error - Connection reset by peer - IOException (...)
2020-11-12 10:17:52  INFO: [9bd54c2e] disconnected

And the second error:

2020-11-12 10:22:04  INFO: [9587f2b7] connected
2020-11-12 10:22:04  INFO: [9587f2b7: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035333234266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e393439333732333535393932322661636375726163793d313026626174743d373520485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@26b1c55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@1a05e3fd (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b8f1c9f (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@174cfe55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@4d1fd15d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@78b0c908 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b285965 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  INFO: [9587f2b7: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:22:04  INFO: [9587f2b7] id: 277587, time: 2020-11-12 10:22:04, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:22:34  INFO: [9587f2b7] disconnected

Any help with this is much appreciated. I am in the process of building a Raspberry Pi Client for Traccar, but I need these errors resolved before I can move forward.

Thank you!

Reconnect DockerHub with GitHub

Hello @tananaev!
Please, reconnect "traccar" organization on DockerHub with GitHub for restore autobuilds after data breach on hub.docker.com.

ipv6 not support

docker traccar can't use ipv6

arquivo tracker-server

Docker-compose path/fiile problem. "Are you trying to mount a directory onto a file?"

Im using Docker-compose to run Traccar and I am having difficulty getting this to work. I want to map the traccar.xml file and not he folder but when I add path to the compose file I get an error that its a directory.

compose file:

version: '3.8'
services:
 traccar:
   container_name: traccar
   hostname: traccar
   image: traccar/traccar:latest
   depends_on: ["db"]
   environment:
      MYSQL_HOST: db
      MYSQL_ROOT_PASSWORD: traccar
      MYSQL_DATABASE: traccar
      MYSQL_USER: traccar
      MYSQL_PASSWORD: traccar
   restart: unless-stopped
   ports:
     - '8082:8082/tcp'
     - '5013:5013/tcp'
     - '5013:5013/udp'
     - '5015:5015/tcp'
     - '5015:5015/udp'
     - '5093:5093/tcp'
     - '5093:5093/udp'
   volumes:
     - ./logs:/opt/traccar/logs:rw
     - ./conf/traccar.xml:/opt/traccar/conf/traccar.xml:ro


 db:
   image: mysql:8.0.20
   container_name: traccar-mysql
   volumes:
     - ./mysql/data:/var/lib/mysql
   restart: always
   cap_add:
     - SYS_NICE
   environment:
     MYSQL_ROOT_PASSWORD: traccar
     MYSQL_DATABASE: traccar
     MYSQL_USER: traccar
     MYSQL_PASSWORD: traccar

I get the following error.

ERROR: for traccar Cannot start service traccar: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/collision/docker/traccar/conf/traccar.xml" to rootfs at "/opt/traccar/conf/traccar.xml": mount /home/collision/docker/traccar/conf/traccar.xml:/opt/traccar/conf/traccar.xml (via /proc/self/fd/6), flags: 0x5001: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Upgrade

Hello, I have installed traccar magnaz 3.14 and all is ok, but I want to upgrade it to 3.15 but I don know how to conserve my files: car, distances, etc.

Can you explain how to do it in docker for synology please?

Thank you very much.

Include MQTT

Hi, i'm wondering if you can include this MQTT project natively into your docker image?

https://github.com/ivanfmartinez/ivanfm-traccar-mqtt

It would be very, very nice! :)

Regards

Docker compose - not working - keeps restarting container.

After running my docker compose, the container keeps restarting. Here is my docker-compose file.
Am i doing something incorrect. Please advice.

version: '3'
services:
  traccar:
    image: "traccar/traccar:latest"
    restart: always
    entrypoint:
      - java
      - -Xms2g
      - -Xmx2g
      - -Djava.net.preferIPv4Stack=true    
    ports:
      - "5000-5150:5000-5150"
      - "5000-5150:5000-5150/udp"
      - "8082:8082"
    volumes:
      - "/data/traccar/logs:/opt/traccar/logs:rw"
      - "/data/traccar/data:/opt/traccar/data:rw"
      - "/root/traccar/traccar.xml:/opt/traccar/conf/traccar.xml:ro"
      - "/etc/localtime:/etc/localtime:ro"
      - "/etc/timezone:/etc/timezone:ro"
    ulimits:
      nproc: 65535
      nofile:
        soft: 50000
        hard: 50000

How to increase java RAM limit in existing Traccar docker container

I can see this command in the Portainer interface:
java -Xms512m -Xmx512m -Djava.net.preferIPv4Stack=true -jar tracker-server.jar conf/traccar.xml

My question is how to increase the 512m command to 1Gig for example?

Thanks.

Database backup

Every time I stop and rm my traccar docker, the database always resets, Is there a way how I prevent this?

can't connect to mysql/postgres

i use traccar client on android and running the server on a raspberrypi400

long story short : i used docker-compose and had my embedded H2 database volume maped on a host dir. db got corrupted so i tried to switch to porttgres or mysql with no luck

my dockerr-compose.yml

version: '2.4'

services:
  mariadb:
    container_name: mariadb-traccar
    hostname: mariadb
    restart: unless-stopped
    image: yobasystems/alpine-mariadb
    command: --default-authentication-plugin=mysql_native_password
    volumes:
      - /run/media/ippo/TOSHIBA/traccar/db:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: pass
    ports:
      - 3306:3306
    healthcheck:
      test:  mysqladmin ping -h 127.0.0.1 -u user --password=pass
      interval: 60s
      timeout: 5s
      retries: 5
      start_period: 30s
    networks:
     - net
    
  traccar:
     image: myimage
     container_name: traccar
     hostname: xxx.xxx.xxx.duckdns.org
     restart: unless-stopped
     ports:
     - 5055:5055/tcp
     - 82:8082
     environment:
      MYSQL_DATABASE: db
      MYSQL_USER: user
      MYSQL_PASSWORD: pass
    
     volumes:
      - /run/media/ippo/TOSHIBA/traccar/conf/traccar.xml:/opt/traccar/conf/traccar.xml
      - /run/media/ippo/TOSHIBA/traccar/logs:/opt/traccar/logs:rw
      - /run/media/ippo/TOSHIBA/traccar/data:/opt/traccar/web:rw
     depends_on:
       - mariadb
     networks:
     - net
  
networks:
  net:
    driver: bridge
    enable_ipv6: false
    ipam:
      config:
        - subnet: 192.168.1.24/32

my traccar.xml

<?xml version='1.0' encoding='UTF-8'?>

<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>

<properties>

    <entry key='config.default'>./conf/default.xml</entry>

    <!--

    This is the main configuration file. All your configuration parameters should be placed in this file.

    Default configuration parameters are located in the "default.xml" file. You should not modify it to avoid issues
    with upgrading to a new version. Parameters in the main config file override values in the default file. Do not
    remove "config.default" parameter from this file unless you know what you are doing.

    For list of available parameters see following page: https://www.traccar.org/configuration-file/

    -->

    <entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
    <entry key='database.url'>jdbc:mysql:/mariadb:3306/traccar?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'>user</entry>
    <entry key='database.password'>pass</entry>

</properties>

docker-compose up throws error

Exception in thread "main" java.lang.RuntimeException: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Could not create connection to database server. Attempted reconnect 3 times. Giving up.

i tried my host ip "192.168.1.24" instead of hostname of my mysql service in this case "mariadb" in the docker-compose.yml

also localhost does not work

i tried to follow this
https://www.traccar.org/forums/topic/traccar-is-not-connecting-to-mysql-in-docker-compose-setup/

also tried commenting "skip networking" with docker exec -it mariadb-traccar nano /etc/my.cnf.d/mariadb-server.cnf

according to this

https://www.traccar.org/forums/topic/traccar-accessing-remote-database/#post-54192

all without luck

what would be a proper mysqlurl for a mariadb container and whatt would be the propper enviromental variables for docker-compose to spin up traccar?

Execution error Bad parameter in docker on Unraid

i have
Execution error
Bad parameter
using docker in Unraid copied tracar.xml and changed to MySQL.
any help ?

Creating a development docker & docker-compose

Hi @magna-z,
You can see myself and @tananaev discussion over here: traccar/traccar#4010

Would love to get your thoughts.