Little Issue with Bursty Real-Time Location Updates
Have you checked logs?
Yes, I've checked the logs, and I’ve noticed that the updates come in bursts. Below are some relevant log entries that show the timestamps and positions being received in bursts.
Here’s a snippet of the logs for reference:
2025-12-31 00:00:15 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-30 23:58:53, course: 140.0
2025-12-31 00:00:15 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-30 23:59:03, course: 140.0
2025-12-31 00:00:15 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-30 23:59:13, course: 140.0
2025-12-31 00:00:15 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-30 23:59:23, course: 140.0
2025-12-31 00:00:15 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-30 23:59:33, course: 140.0
2025-12-31 00:00:16 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-31 00:00:13, course: 140.0
2025-12-31 00:00:22 INFO: [T58497f17] id: 862997066413117, time: 2025-12-31 00:00:20, course: 188.0
2025-12-31 00:00:25 INFO: [Tb3e96f31] id: 863553060348509, time: 2025-12-31 00:00:23, course: 140.0
2025-12-31 00:00:29 INFO: [Tf28ab944] id: 862997066410055, time: 2025-12-31 00:00:27, course: 122.0
2025-12-31 00:00:32 INFO: [T33783f3c] id: 862997066412085, time: 2025-12-31 00:00:30, course: 358.0
The logs show multiple devices, such as 863553060348509 and 862997066413117, sending position updates in bursts. This is causing the inconsistency I’m experiencing. When I check the database later, the positions are correctly stored, but the real-time updates are not being evenly distributed as expected.
Could this be an issue with the server's processing of incoming data or a configuration issue on my end?
Unfortunately that's not all the log data that would be needed to answer your questions.
Thanks for your reply.
If there’s any specific information you need that’s not included in the above logs, please let me know, and I’ll be happy to provide it.
Additionally, I’ve noticed the following warnings in the logs, which may be related to network issues:
2025-11-30 04:45:23 WARN: [T84a22e4f] error - Connection reset - SocketException (...)
2025-11-30 04:46:27 WARN: [T5ab5004b] error - Connection reset - SocketException (...)
2025-11-30 04:46:58 WARN: Geocoder network error - HTTP 429 Too Many Requests - ClientErrorException (... < JsonGeocoder:126 < ReportUtils:190 < *:267 < *:342 < *:295 < TripsReportProvider:65 < ReportResource:258 < ...)
I’d also like to mention that there are no other errors or warnings in the logs, aside from the ones shared above. Since the log files are quite large, it’s difficult to share everything, but these are the relevant entries I’ve come across.
Additionally, I do not require the geocoder since I handle the geolocation manually.
Thanks again for your help, and let me know if you need anything else from my side.
Ideally you provide full connection session, including raw data and any other logs in between.
Thanks for your suggestions. I've now downloaded the full log for the day (2025-12-30). The file is around
18MB in size, which makes it too large and lengthy to paste directly here.
To share this log data conveniently, could please suggest the best method for sharing?
Please let me know how you'd like to proceed!
There's no need to go from one extreme to another. You have to extract the relevant time frame, not the whole day.
Thanks for your suggestions. I have gone through the entire log for the day and couldn't identify anything
amiss. However, I've extracted one of the trips that had bursts in the front end, which might be relevant to
the issue.
2025-12-30 09:40:54 INFO: Event id: 863553060348509, time: 2025-12-30 09:40:54,type: deviceMoving, notifications: 0
2025-12-30 09:40:54 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:40:54, lat: x.16688, lon: xx.449657, speed: 32.9, course: 265.0
2025-12-30 09:41:04 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:41:04, lat: x.16686, lon: xx.449507, speed: 33.5, course: 274.0
2025-12-30 09:41:14 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:41:14, lat: x.16689, lon: xx.449355, speed: 32.9, course: 272.0
2025-12-30 09:41:24 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:41:24, lat: x.16699, lon: xx.449200, speed: 32.9, course: 2xx.40
2025-12-30 09:41:34 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:41:33, lat: x.16717, lon: xx.449051, speed: 32.4, course: 276.0
2025-12-30 09:41:44 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:41:43, lat: x.16730, lon: xx.448900, speed: 32.9, course: 276.0
2025-12-30 09:41:54 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:41:53, lat: x.16757, lon: xx.448748, speed: 32.9, course: 282.0
2025-12-30 09:42:04 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:42:03, lat: x.16786, lon: xx.448596, speed: 33.5, course: 281.0
2025-12-30 09:42:15 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:42:13, lat: x.16813, lon: xx.448443, speed: 34.0, course: 278.0
2025-12-30 09:42:24 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:42:23, lat: x.16841, lon: xx.448289, speed: 34.6, course: 281.0
2025-12-30 09:42:36 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:42:33, lat: x.16874, lon: xx.448139, speed: 32.9, course: 282.0
2025-12-30 09:42:44 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:42:43, lat: x.16907, lon: xx.447989, speed: 33.5, course: 282.0
2025-12-30 09:42:54 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:42:53, lat: x.16940, lon: xx.447841, speed: 31.9, course: 283.0
2025-12-30 09:43:04 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:43:03, lat: x.16978, lon: xx.447692, speed: 34.0, course: 284.0
2025-12-30 09:43:14 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:43:13, lat: x.17016, lon: xx.447543, speed: 32.9, course: 285.0
2025-12-30 09:43:24 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:43:23, lat: x.17057, lon: xx.447392, speed: 32.9, course: 286.0
2025-12-30 09:43:34 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:43:33, lat: x.17096, lon: xx.447241, speed: 33.5, course: 281.0
2025-12-30 09:43:44 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:43:43, lat: x.17129, lon: xx.447092, speed: 32.4, course: 281.0
2025-12-30 09:43:55 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:43:53, lat: x.17161, lon: xx.446940, speed: 33.5, course: 282.0
2025-12-30 09:44:04 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:44:03, lat: x.17192, lon: xx.446788, speed: 33.5, course: 280.0
2025-12-30 09:44:14 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:44:13, lat: x.17225, lon: xx.446638, speed: 32.4, course: 284.0
2025-12-30 09:44:24 INFO: [Td2c7e84e] id: 863553060348509, time: 2025-12-30 09:44:23, lat: x.17263, lon: xx.446504, speed: 32.4, course: 284.0
2025-12-30 09:51:19 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:44:33, lat: x.17302, lon: xx.446355, speed: 32.9, course: 283.0
2025-12-30 09:51:20 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:44:43, lat: x.17340, lon: xx.446207, speed: 32.9, course: 281.0
2025-12-30 09:51:20 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:44:53, lat: x.17375, lon: xx.446057, speed: 32.4, course: 283.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:45:03, lat: x.17412, lon: xx.445907, speed: 33.5, course: 285.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:45:13, lat: x.17455, lon: xx.445764, speed: 32.4, course: 279.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:45:23, lat: x.17480, lon: xx.445618, speed: 31.3, course: 281.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:45:33, lat: x.17520, lon: xx.445477, speed: 30.2, course: 292.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:45:43, lat: x.17606, lon: xx.445363, speed: 29.7, course: 331.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:45:53, lat: x.17744, lon: xx.445340, speed: 30.2, course: 354.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:46:03, lat: x.17888, lon: xx.445321, speed: 31.3, course: 351.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:46:13, lat: x.18030, lon: xx.445300, speed: 31.3, course: 346.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:46:23, lat: x.18170, lon: xx.445264, speed: 30.2, course: 344.0
2025-12-30 09:51:21 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:46:33, lat: x.18295, lon: xx.445206, speed: 27.0, course: 323.0
2025-12-30 09:51:22 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:46:43, lat: x.18335, lon: xx.445126, speed: 14.0, course: 262.0
2025-12-30 09:51:22 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:46:53, lat: x.18323, lon: xx.445087, speed: 6.5, course: 254.0
2025-12-30 09:51:22 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:47:03, lat: x.18319, lon: xx.445063, speed: 3.8, course: 271.0
2025-12-30 09:51:22 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:47:13, lat: x.18318, lon: xx.445047, speed: 2.7, course: 255.0
2025-12-30 09:51:22 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:47:23, lat: x.18313, lon: xx.445034, speed: 2.2, course: 258.0
2025-12-30 09:51:22 INFO: [T85b195f1] id: 863553060348509, time: 2025-12-30 09:47:33, lat: x.18311, lon: xx.445032, course: 258.0
2025-12-30 09:51:22 INFO: Event id: 863553060348509, time: 2025-12-30 09:47:43,type: deviceStopped, notifications: 0
Here is some raw data as you mentioned:
242459313038322c3836333535333036303334383530392c4343452c130000000a0067001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011aa40540230041000006025f9d3f00032eb3610404d459e6300c2f2b2a060d738f97031c01000000020e0cd80101006e00052f0300baff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a880540230041000006025f9d3f00032eb3610404de59e6300c2f2b2a060d7d8f97031c01000000020e0cd80101006e00052f0300baff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a9b0540230041000006025f9d3f00032eb3610404e859e6300c2f2b2a060d878f97031c01000000020e0cd80101006e00052f0300b2ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a830540230041000006025f9d3f00032eb3610404f259e6300c2f2b2a060d918f97031c01000000020e0cd80101006e00052f0300b2ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a710540230041000006025f9d3f00032eb3610404fc59e6300c2f2b2a060d9b8f97031c01000000020e0cd80101006e00052f0300b2ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a7a0540230041000006025f9d3f00032eb3610404065ae6300c2f2b2a060da58f97031c01000000020e0cd80101006e0005260300b0ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a780540230041000006025f9d3f00032eb3610404105ae6300c2f2b2a060daf8f97031c01000000020e0cd80101006e0005260300b0ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a9f0540230041000006025f9d3f00032eb36104041a5ae6300c2f2b2a060db98f97031c01000000020e0cd80101006e0005260300b0ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a9b0540230041000006025f9d3f00032eb3610404245ae6300c2f2b2a060dc38f97031c01000000020e0cd80101006e0005260300b0ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a270540230041000006025f9d3f00032eb36104042e5ae6300c2f2b2a060dcd8f97031c01000000020e0cd80101006e0003290300b9ff4b060101034c54452a43330d0a
2424553234322c3836333535333036303334383530392c4343452c27000000020067001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a090540230041000006025f9d3f00032eb3610404f958e6300c2f2b2a060d988e97031c01000000020e0cd80101006e0005290300b6ff4b060101034c544567001900060501060b071f140015001b000b0800000968000a07000b0300160000170000180000199d011a060540230041000006025f9d3f00032eb36104040359e6300c2f2b2a060da28e97031c01000000020e0cd80101006e0005290300baff4b060101034c54452a44410d0a
2424583133372c3836333535333036303334383530392c4343452c13000000010067001900060501060e071f140015001b000b083c00090c010a06000b0000160000170000180000199e011a91054023004100000602d1953f0003af89610404885ae6300c342d2a060d279097031c01000000020e0cd80101006e0009260300adff4b060101034c54452a39320d0a
Using Meitrack protocol we can decode this.
Sorry that's not something I can work with. I asked for proper logs and you give me filtered logs again and some raw data ripped out of context. I won't be able to help here.
No worries. I’ve reviewed the full logs and didn’t find any issues there. It appears to be something on my end — most likely related to my server’s network or RAM.
Thanks to the Traccar team for the great product. Wishing you all a happy New Year.
Hi Traccar Team,
I'm experiencing a little issue with real-time location updates. My devices are set to send updates every 30 seconds, but sometimes there’s a delay of up to a minute, and then updates appear in bursts instead of being spaced evenly.
When I check the database for all positions, it is correctly stored.
Setup:
Looking for:
Thanks for your help!