Device position not updating on map and More Details but ok in Reports and Replay

Norm3 years ago

Victor, did you figure this out?

I am having the same issue. Device is stuck in same position on map for 3 days. But a report shows correct locations. No errors anyplace I can find.

Maurice Oduor3 years ago

I am facing a similar problem where the device is showing online but position on map is frozen in one place despite the device moving, but doesn't update the position on map.

The same device when configured to report to the manufacturer's server it works fine, it's online and update positions in realtime as it moves.

Anyone with a solution.

Victor Butler3 years ago

I think the issue might have been indeed related to the new config setup required for the firebase push notifications. I haven't seen any more positions "freeze" after I entered the new firebase config. However, I still cannot explain the random position update on the map if we assume the firebase config was to blame for.
Try updating the config and then monitor the server. Note, that after you do the update, the device has to report at least one new position to get it reflected on the map. If the device is offline, the position will not be automatically updated to the last one (from the database).

Tracker2 years ago

Hi Victor, I am having the same problem, I handle close to 1000 devices and for a number of them I am having the problem that you mention, in some cases the devices show an erroneous location and date of days or even months before, despite the fact that in route reports everything seems normal and with current and real positions. I wanted to ask you how you solved this inconvenience and if you can guide me on this please, I would be very grateful.

Victor Butler8 months ago

Hello,

No the issue is still not resolved, I just experienced the same problem once again. Searching on the forum I saw this old post and remembered I had the problem before.
We thought it might be the firebase config back then but now with server version 6.1. the issue still persists.

Urdanegui Castillo 8 months ago

The problem is still in force until now, it has not been solved the devices freeze randomly. Completely ruled out device problem as testing in DEMO if they work.

Victor Butler8 months ago

Urdanegui Castillo, are you using TCP or UDP protocol for the devices that are freezing?

BITPC2 months ago

Hello,

I'm new to traccar, only using it for a month but I like it because we can really tightly integrated it in a custom software project where we need tracking information.

I just had the same issue with one of 16 devices connected. on the map there was always the same old location showing from 2 days ago, but in event an trips etc all was right.

I figured something may be wrong with that specific log, so i went to the mysql database, and searched for the mentioned id you can see in details when you click the device on the map in the table tc_positions:

I found the record and i then did an update query to invalidate this record for this device: update traccar.tc_positions set deviceid=2000 where id=53558;
so in fact i changed the deviceid from the log entry in tc_postions table from the real value 2 to a non existing deviceid, and voila, solved: the stuck device then immediately updated on the map to the current correct location.

So something must be wrong with this single data record that the traccar server is keeping this as the "current" record for the map.

to confirm this then i reverted my change: update traccar.tc_positions set deviceid=2 where id=53558; and yes: again the device went back to the same stuck old position.

then I export both the "stuck" record and the last one for that device to compare the data:

INSERT INTO `` (`id`,`protocol`,`deviceid`,`servertime`,`devicetime`,`fixtime`,`valid`,`latitude`,`longitude`,`altitude`,`speed`,`course`,`address`,`attributes`,`accuracy`,`network`,`geofenceids`) 

BAD: VALUES (53558,'teltonika',2,'2025-03-03 17:54:46','2025-03-03 17:54:43','2025-03-03 17:54:43','0', 51.09797  ,3.546095 ,0,0,0  ,NULL,'{\"priority\":0,\"sat\":0,\"event\":303,\"ignition\":false,\"motion\":true,\"rssi\":2,\"io200\":0,\"io69\":2 ,\"io113\":100,\"io303\":0,\"pdop\":0.0,\"hdop\":0.0,\"power\":11.805,\"io24\":0,\"battery\":4.0280000000000005,\"io68\":0,\"operator\":20620,\"tripOdometer\":0,\"odometer\":929399,\"io449\":0,\"distance\":0.0,\"totalDistance\":904637.286416208}', 0,'null','[10]');

GOOD:VALUES (56962,'teltonika',2,'2025-03-05 08:33:09','2025-03-05 08:32:26','2025-03-05 08:32:26','1', 50.9736316,3.5168683,8,0,129,NULL,'{\"priority\":0,\"sat\":22,\"event\":0, \"ignition\":false,\"motion\":false,\"rssi\":5,\"io200\":0,\"io69\":1,\"io113\":100,\"io303\":0,\"pdop\":0.8,\"hdop\":0.5,\"power\":11.75 ,\"io24\":0,\"battery\":4.107             ,\"io68\":0,\"operator\":20620,\"tripOdometer\":0,\"odometer\":994434,\"io449\":0,\"distance\":0.0,\"totalDistance\":969860.2666361935}',0,'null','null');

I personally do not see any remarkable things about the data in the "BAD" record, except the battery voltage has a lot more digits, and there sat=0, but I dont see how that would cause such issue.

to further test i went ahead and changed the attributes of the 'BAD' record tot the attributes of the last record, no change.
i also tested changing the geofenceID to null and toggling valid from 0 to 1, changing to the battery voltage to less digits, setting sattelites to 22, bu tall brought no change.

so i have no clue what is bad about the 'BAD' record that makes this one stuck on the map.

the only thing that helps is removing/updating the offending record so it is not there anymore for the device

maybe anyone with deeper knowledge of how the actual position record is selected by the backend server to show on the map could shed a light on this?

Anton Tananaev2 months ago

I don't see any issue with that records. Were there any errors or warnings in the log?

BITPC2 months ago

Hello, you mean the Log section at settings => logs? that is completely empty.

Anton Tananaev2 months ago

No, I mean actual server logs.

BITPC2 months ago

ok, i found the logs: around the time of the position log that is stuck on the screen i see we got a 7 position updates at once for this device that got stuck (identifier 867747074598598) , probably because of bad mobile connection, but I don't know if this can be a cause of this issue:

2025-03-03 18:53:57  INFO: user: 1, action: login, from: 192.168.11.251
2025-03-03 18:54:23  INFO: [T4ae9df14] connected
2025-03-03 18:54:24  INFO: [T4ae9df14: teltonika < 194.88.242.123] 000f383637373437303734353938353938
2025-03-03 18:54:24  INFO: Event id: 867747074598598, time: 2025-03-03 18:54:24, type: deviceOnline, notifications: 0
2025-03-03 18:54:24  INFO: [T4ae9df14: teltonika > 194.88.242.123] 01
2025-03-03 18:54:25  INFO: [T4ae9df14: teltonika < 194.88.242.123] 00000000000002f08e07000001955d1d6f4800021d17561e753c9400000000000000012f0011000700ef0000f00000150200c800004502007164012f01000600b5000000b6000000422e350018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d1d733000021d17561e753c940000000000000000f00011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e2e0018000000430fb900440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d1d86b800021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e2c0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d1e6d3000021d17561e753c940000000000000000f00011000700ef0000f00000150200c800004502007164012f00000600b5000000b6000000422e300018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d24687000021d17561e753c9400000000000000012f0011000700ef0000f00000150200c800004502007164012f01000600b5000000b6000000422e390018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d246c5800021d17561e753c940000000000000000f00011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e350018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d247fe000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e2a0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c100000000000000000700003041
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:46:05, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:46:06, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:46:11, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:47:10, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:53:42, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:53:43, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:53:48, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:25  INFO: [T4ae9df14: teltonika > 194.88.242.123] 00000007
2025-03-03 18:54:39  INFO: [T4ae9df14: teltonika < 194.88.242.123] 000000000000006e8e01000001955d253f4800021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e320018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c1000000000000000001000086e2
2025-03-03 18:54:39  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:54:37, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:39  INFO: [T4ae9df14: teltonika > 194.88.242.123] 00000001
2025-03-03 18:54:46  INFO: [T4ae9df14: teltonika < 194.88.242.123] 000000000000006e8e01000001955d2556b800021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e1d0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c100000000000000000100001bb3
2025-03-03 18:54:46  INFO: [T4ae9df14] id: 867747074598598, time: 2025-03-03 18:54:43, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:54:46  INFO: [T4ae9df14: teltonika > 194.88.242.123] 00000001
2025-03-03 18:55:48  INFO: user: 1, action: login, from: 192.168.11.251
2025-03-03 18:56:20  INFO: [Td1d94906] connected
2025-03-03 18:56:20  INFO: [Td1d94906: teltonika < 194.88.243.112] 000f383634323735303733363536333139
2025-03-03 18:56:20  WARN: Unknown device - 864275073656319 (194.88.243.112)
2025-03-03 18:56:20  INFO: [Td1d94906: teltonika > 194.88.243.112] 00
2025-03-03 18:56:20  INFO: [Td1d94906] disconnected

I'm a bit confused with the timestamps: in the database the 'bad' stuck record has servertime timestamp 2025-03-03 17:54:46, on the gui it has this timestamp + 1h, according to timezone probably), but now i'm confused for what time exactly i need to check in the server log file.

there are no entries for log timestamp 2025-03-03 17:54 , and the logs with 2025-03-03 17:54: in the data from the device i see at log date time 18:20

2025-03-03 18:20:04  INFO: [T8b01aff7] connected
2025-03-03 18:20:04  INFO: [T8b01aff7: teltonika < 194.88.242.123] 000f383637373437303734353938353938
2025-03-03 18:20:04  INFO: Event id: 867747074598598, time: 2025-03-03 18:20:04, type: deviceOnline, notifications: 0
2025-03-03 18:20:04  INFO: [T8b01aff7: teltonika > 194.88.242.123] 01
2025-03-03 18:20:05  INFO: [T8b01aff7: teltonika < 194.88.242.123] 000000000000014d8e03000001955cef086001021d17561e753c940000000000000000f60012000800ef0000f00100150200c800004502007164012f0000f600000600b5000000b6000000422e2c0018000000430fba00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf7556001021d17561e753c940000000000000000f60012000800ef0000f00100150200c800004502007164012f0100f601000600b5000000b6000000422e2c0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf83fc001021d17561e753c940000000000000000f60012000800ef0000f00000150200c800004502007164012f0000f600000600b5000000b6000000422e2c0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c100000000000000000300004f54
2025-03-03 18:20:05  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 17:55:24, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:05  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:04:28, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:05  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:05:28, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:05  INFO: [T8b01aff7: teltonika > 194.88.242.123] 00000003
2025-03-03 18:20:08  INFO: [T8b01aff7: teltonika < 194.88.242.123] 000000000000049c8e0b000001955cede36800021d17561e753c940001008305000600000011000700ef0000f00100150200c800004501007164012f01000600b5001600b6001400422e2a0018000600430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cee0a7800021d17561e753c9400000000000000012f0011000700ef0000f00100150100c800004502007164012f00000600b5000000b6000000422e2b0018000000430fba00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cee163000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e000018000000430fb900440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cee25d000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e050018000000430fba00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cef0c4800021d17561e753c940000000000000000f00011000700ef0000f00000150200c800004502007164012f00000600b5000000b6000000422e280018000000430fb900440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf6c4d800021d17561e753c9400000000000000012f0011000700ef0000f00000150200c800004502007164012f01000600b5000000b6000000422e2c0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf6c8c000021d17561e753c940000000000000000f00011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e2c0018000000430fb800440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf6e03000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e2c0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf72e5000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e2c0018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf7594800021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00
2025-03-03 18:20:08  INFO: [T8b01aff7: teltonika < 194.88.242.123] 000600b5000000b6000000422e2b0018000000430fba00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cf83fca00021d17561e753c940000000000000000f00011000700ef0000f00000150200c800004502007164012f00000600b5000000b6000000422e2d0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c100000000000000000b00002844
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 17:54:09, lat: 51.09997, lon: 3.54610, speed: 3.2, course: 131.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 17:54:19, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 17:54:22, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 17:54:26, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 17:55:25, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:03:51, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:03:52, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:03:58, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:04:18, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:04:29, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:05:28, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:08  INFO: [T8b01aff7: teltonika > 194.88.242.123] 0000000b
2025-03-03 18:20:10  INFO: [T8b01aff7: teltonika < 194.88.242.123] 000000000000049c8e0b000001955cfab89000021d17561e753c9400000000000000012f0011000700ef0000f00000150200c800004502007164012f01000600b5000000b6000000422e2c0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cfabc7800021d17561e753c940000000000000000f00011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422dfb0018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cfb0e8000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e000018000000430fb700440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cfbf4f800021d17561e753c940000000000000000f00011000700ef0000f00000150200c800004502007164012f00000600b5000000b6000000422e060018000000430fba00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cff505800021d17561e753c9400000000000000012f0011000700ef0000f00000150200c800004502007164012f01000600b5000000b6000000422de80018000000430fbc00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cff544000021d17561e753c940000000000000000f00011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422dd90018000000430fb800440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955cff63e000021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422dfe0018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d004a5800021d17561e753c940000000000000000f00011000700ef0000f00000150100c800004502007164012f00000600b5000000b6000000422e000018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d05110000021d17561e753c9400000000000000012f0011000700ef0000f00000150200c800004502007164012f01000600b5000000b6000000422e2c0018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d0514e800021d17561e753c940000000000000000f00011000700ef0000f00100150200c800004502007164012f01000600b5000000b6000000422e2b0018000000430fb800440000000400f10000508c00c7000000000010000e2e7701c10000000000000000000001955d05248800021d17561e753c9400000000000000012f0011000700ef0000f00100150200c800004502007164012f00000600b5000000b6000000422e2c0018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c100000000000000000b000014b7
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:08:10, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:08:11, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:08:32, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:09:31, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:13:11, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:13:12, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:13:16, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:14:15, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:19:28, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:19:29, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:19:33, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:10  INFO: [T8b01aff7: teltonika > 194.88.242.123] 0000000b
2025-03-03 18:20:21  INFO: [T6daec0ef: teltonika < 37.185.130.15] 000000000000009e8e01000001955d05d06800021d16c01e753bdc000000000000000000001a000d00ef0100f00100500100150200c80000450200010000b30000020000030000b401007157010701000400b6000000422f9800430f8f000900d8000700f10000507900c7000000000010001cd72e004800000000004900000000004a00000000004b000000000002000b0000000214638934000e0000000015f226db000001000019fa
2025-03-03 18:20:21  INFO: [T6daec0ef] id: 357544370085967, time: 2025-03-03 18:20:17, lat: 51.09995, lon: 3.54608, course: 0.0
2025-03-03 18:20:21  INFO: [T6daec0ef: teltonika > 37.185.130.15] 00000001
2025-03-03 18:20:35  INFO: [T8b01aff7: teltonika < 194.88.242.123] 000000000000006e8e01000001955d060b0000021d17561e753c940000000000000000f00011000700ef0000f00000150200c800004502007164012f00000600b5000000b6000000422e2c0018000000430fbb00440000000400f10000508c00c7000000000010000e2e7701c10000000000000000010000f0d4
2025-03-03 18:20:35  INFO: [T8b01aff7] id: 867747074598598, time: 2025-03-03 18:20:32, lat: 51.09997, lon: 3.54610, course: 0.0
2025-03-03 18:20:35  INFO: [T8b01aff7: teltonika > 194.88.242.123] 00000001

the only warn and error events in the whole log file from that day are less than 5 2025-03-03 18:31:50 WARN: [T7b6063b2] error - Connection reset - SocketException (...) messages. nothging else

also no other errors in the log file from today apart from connection resets
if it helps i could mail the log files?
regards

Anton Tananaev2 months ago

Everything looks normal in the logs. Are you using the latest official release without any code modifications?

BITPC2 months ago

yes, we are using version 6.6 with no code modifications on a dedicated windows VM, linked to a local dedicated mysql database on the VM itself .

Where in code could we find the query which tc_position record is selected for each device on the actual status map? to me it looks like for some reason the wrong record (not the latest) is selected from the database for the status map.

Anton Tananaev2 months ago

Position id is linked from the devices table.