Why a device position hangs on the map forever?

Mauro Socci6 years ago

Sometimes the position of a device hangs on the map suddenly and randomly. From that moment its marker continues to turn green in motion, yellow when parked, etc. but remains fixed on the map forever (always in that geographical position). Do not move anymore. Restarting the server or waiting for automatic position deletion (10 days) do not solve the problem. The only way is to delete the device and reinsert a new one with same name & device ID. But the history is lost.
Release: 3.16 on Windows server 2012.
Protocols: 5 Osmand, 6 TK103, 2 Teltonika, 1 GT06 (all affected by this problem, but Osmand more frequently).
Database: H2 database, 14 devices active, automatic cancellation ( <entry key='database.positionsHistoryDays'>10</entry> ) So always a light database. I shut down and restart the server weekly.
How can I fix this annoying problem? Or just recover the device when it happens?
Thanks, Mauro.

Anton Tananaev6 years ago

Check position time.

Mauro Socci6 years ago

Thanks for the answer Anton. So for some reason sometimes the devices send a position with wrong time? It happens on all protocols and also on three Traccar Clients 5.10 Osmand (on Android 4.4 and 7.1 polling 10-15 secs, four times in three months). Is there something to do to prevent it? Or a way to fix it when happens?

Mauro Socci6 years ago

Another question if possible: the web GUI (website) sometimes do not update positions, status, warnings, etc. It happens if the webpage is leaved open for more than one hour about (both in full-screen or in background). The Internet connection is stable. Reloading the webpage, the positions/status becomes updated immediately. It happens with Chrome and Firefox in Windows 7/8 and also in Chrome Android. Increasing 'web.timeout' milliseconds could help for this? Or it's better to search for a solution to automatically reload the webpage every X minutes?

Anton Tananaev6 years ago

Wrong time with Traccar Client can only happen if time on your phone is incorrect.

Web app is not really designed to be open for very long periods of time. It's very hard to test what happens. Possibly some timeouts in browser.