Hi,
I've been using Traccar for many years and recently deployed another instance, this time using version 6.15.3 and a MySQL DB. I have some custom Python handling some non-supported trackers that means I send information to Traccar using OsmAnd. This has worked for many hundreds of devices until suddenly about an hour ago it stopped without any reason why.
Now when I send an OsmAnd request Traccar crashes, it happens after a single request. I've enabled finest logging and there is nothing to me that really suggests why but I don't know exactly what I am looking at. Here is the log, there is no error the log just finishes and the service has stopped running.
2026-10-31 20:48:56 DEBUG: HikariPool-1 - Pool stats (total=20/20, idle=20/20, active=0, waiting=0)
2026-10-31 20:48:56 DEBUG: HikariPool-1 - Fill pool skipped, pool has sufficient level or currently being filled.
2026-10-31 20:48:57 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@17e1f27f is alive
2026-10-31 20:49:00 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@38ad5dd9 is alive
2026-10-31 20:49:00 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@31b5e3ad is alive
2026-10-31 20:49:04 DEBUG: -Dio.netty.buffer.checkAccessible: true
2026-10-31 20:49:04 DEBUG: -Dio.netty.buffer.checkBounds: true
2026-10-31 20:49:04 DEBUG: Loaded default ResourceLeakDetector: io.netty.util.ResourceLeakDetector@6977fca3
2026-10-31 20:49:04 INFO: [T0c157c07] connected
2026-10-31 20:49:04 INFO: [T0c157c07: osmand < 0:0:0:0:0:0:0:1] GET /?deviceid=1000001&lat=xxxxxx&lon=-xxxxxx&time=2026-10-31T20:49:03 HTTP/1.1\r\nHost: xxxxxx:5055\r\nUser-Agent: python-requests/2.34.2\r\nAccept-Encoding: gzip, deflate, zstd\r\nAccept: */*\r\nConnection: keep-alive\r\n\r\n
2026-10-31 20:49:06 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@40a1e095 is alive
2026-10-31 20:49:10 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@c4e2e68 is alive
2026-10-31 20:49:11 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@5c78b615 is alive
2026-10-31 20:49:16 DEBUG: HikariPool-1 - keepalive: connection com.mysql.cj.jdbc.ConnectionImpl@5b0cdb9f is alive
Would anyone please have any ideas? Could there be something stuck in the database that is being unhandled?
I've tried a manual request with Postman and given a device a new device ID, it says it is registering the device ID and then crashes, I can open the DB in BeeKeeper studio so the DB appears to at least be openable.
Thanks
Where do you see the crash?
Sorry when I say crash, I mean the service just stops (as seen in windows event viewer saying Traccar has stopped suddenly) and the web page no longer responds. I connected up another generic Teltonika tracker and the behaviour continues so it appears it stops running on any external data being input - logging into the web page works OK.
I've moved it to another database and this appears to now work (although I've lost all my devices/users/groups etc) suggesting it was a problem in the DB somewhere.
Hi,
I've been using Traccar for many years and recently deployed another instance, this time using version 6.15.3 and a MySQL DB. I have some custom Python handling some non-supported trackers that means I send information to Traccar using OsmAnd. This has worked for many hundreds of devices until suddenly about an hour ago it stopped without any reason why.
Now when I send an OsmAnd request Traccar crashes, it happens after a single request. I've enabled finest logging and there is nothing to me that really suggests why but I don't know exactly what I am looking at. Here is the log, there is no error the log just finishes and the service has stopped running.
Would anyone please have any ideas? Could there be something stuck in the database that is being unhandled?
I've tried a manual request with Postman and given a device a new device ID, it says it is registering the device ID and then crashes, I can open the DB in BeeKeeper studio so the DB appears to at least be openable.
Thanks