Suddenly no more positions, but tracker transmits

I have installed a new GPS tracker with Xexun2 protocol. This worked perfectly for several days. Since yesterday, however, no more positions have been displayed. However, the online status works.

In the log file you can see that the Traccar server is no longer responding to the transmitter.

Can anyone help me?

Last position on the Traccar server: 12.03.2025, 09:14:13

Log-File before and after last position:

2025-03-11 09:00:37  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:37, lat: 51.48331, lon: 11.97917, speed: 13.9, course: 161.4
2025-03-11 09:00:37  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363786395707041284300001fffe01faaf
2025-03-11 09:00:38  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363886395707041284300066e3440100636067c9c7dc1a0064828000254700224092e15273d5bab240b3fbbf029c62a1b60116290271003142f9999a0000092b2a2a284000000a000000007d00000409020a0100204d4f56455f4954562030303a30353a343720706f7765723a3431353535312040faaf
2025-03-11 09:00:56  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363986395707041284300066e6bc0100639467cfedab1a00518280002547002240921b18e219652c40b408f71a9fbe77010d2000f3066c43c5333301001127201e1c4000000a000000028100000409020a0100204d4f56455f4954562031363a30303a343120706f7765723a3339343938342040faaf
2025-03-11 09:00:57  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:43, lat: 51.48275, lon: 11.97957, speed: 13.1, course: 164.4
2025-03-11 09:00:57  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363986395707041284300001fffe01faaf
2025-03-11 09:00:59  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363a86395707041284300066e6d50100639567cfedaf1a00518280002547002240921b32f449129940b408ee9c23b795010d200119064d43bf199a0000152221201f4000000a000000028100000409020a0100204d4f56455f4954562031363a30303a343620706f7765723a3339343938342040faaf
2025-03-11 09:00:59  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:47, lat: 51.48220, lon: 11.98000, speed: 15.2, course: 161.3
2025-03-11 09:00:59  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363a86395707041284300001fffe01faaf
2025-03-11 09:00:59  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363b86395707041284300066e7520100639667cfedb41a00518280002547002240921b5463497b7440b408e8b827fa1a010d210000066343ad26660100152524201e4000000a000000028100000409020a0100204d4f56455f4954562031363a30303a353120706f7765723a3339343938342040faaf
2025-03-11 09:00:59  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:52, lat: 51.48182, lon: 11.98054, course: 163.5
2025-03-11 09:00:59  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363b86395707041284300001fffe01faaf
2025-03-11 09:01:00  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363c86395707041284300066e5760100639767cfedbb1a00518280002547002240921b70f7b9e06140b408e710cb295f010f21000006634394cccd01001025241e1d4000000a000000028100000409020a0100204d4f56455f4954562031363a30303a353620706f7765723a3339343938342040faaf
2025-03-11 09:01:00  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:59, lat: 51.48171, lon: 11.98101, course: 163.5
2025-03-11 09:01:00  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363c86395707041284300001fffe01faaf
2025-03-11 09:01:00  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363d86395707041284300066e3440100636067c9c7dc1a0064828000254700224092e15273d5bab240b3fbbf029c62a1b60116290271003142f9999a0000092b2a2a284000000a000000007d00000409020a0100204d4f56455f4954562030303a30353a343720706f7765723a3431353535312040faaf
2025-03-11 09:01:31  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363e86395707041284300070eee001006d9867cfedda1a0051828401010600020000a9ba0078d315230025470022000000000000000000000000000000000000000000000000000000040000000000004000000a000000028100000409020a01001c4d4f56452031363a30313a323520706f7765723a3339343938342040faaf
2025-03-11 09:01:31  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:59, lat: 51.48171, lon: 11.98101, course: 163.5
2025-03-11 09:01:31  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363e86395707041284300001fffe01faaf
2025-03-11 09:01:36  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014363f86395707041284300074ec040100719967cfeddf1a0051828401010600020000a9ba0078d3142300254700220000000000000000000000000000000000061800000000000000000500ff1e1a17144000000a000000028100000409020a0100204d4f56455f4954562031363a30313a333020706f7765723a3339343938342040faaf
2025-03-11 09:01:36  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:59, lat: 51.48171, lon: 11.98101, course: 163.5
2025-03-11 09:01:36  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014363f86395707041284300001fffe01faaf
2025-03-11 09:01:39  INFO: Event id: 9180017166, time: 2025-03-11 09:01:39, type: deviceUnknown, notifications: 0
2025-03-11 09:01:41  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364086395707041284300074ec050100719a67cfede41f0051828401010600020000a9ba0078d3142300254700220000000000000000000000000000000000071500000000000000000400ff181813124000000a000000028100000409020a0100204d4f56455f4954562031363a30313a333520706f7765723a3339343938342040faaf
2025-03-11 09:01:41  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:00:59, lat: 51.48171, lon: 11.98101, course: 163.5
2025-03-11 09:01:41  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014364086395707041284300001fffe01faaf
2025-03-11 09:01:43  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364186395707041284300066e5f50100639b67cfede61f00518280002547002240921bef1fddebd940b408c04d551d69060717010e06a54323999a0100301d1815144000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343020706f7765723a3339343938342040faaf
2025-03-11 09:01:43  INFO: [Tda6c4ac6] id: 863957070412843, time: 2025-03-11 09:01:42, lat: 51.47919, lon: 11.98306, speed: 14.6, course: 170.1
2025-03-11 09:01:43  INFO: [Tda6c4ac6: xexun2 > 109.42.49.214] faaf0014364186395707041284300001fffe01faaf
2025-03-11 09:01:43  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364286395707041284300066e33f0100636067c9c7dc1f0064828000254700224092e15273d5bab240b3fbbf029c62a1b60116290271003142f9999a0000092b2a2a284000000a000000007d00000409020a0100204d4f56455f4954562030303a30353a343720706f7765723a3431353535312040faaf
2025-03-11 09:02:02  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364386395707041284300066e4f40100639c67cfedea1f00518280002547002240921bfbbf0278feef40b408b9de69ad43060819012b079d4325199a01001d1e1b18164000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343420706f7765723a3339343938342040faaf
2025-03-11 09:02:22  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364486395707041284300066e4f40100639c67cfedea1f00518280002547002240921bfbbf0278feef40b408b9de69ad43060819012b079d4325199a01001d1e1b18164000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343420706f7765723a3339343938342040faaf
2025-03-11 09:02:37  INFO: [T7b3b9617: watch < 80.187.68.208] [SG*9180017166*0009*LK,0,40]
2025-03-11 09:02:37  INFO: Event id: 9180017166, time: 2025-03-11 09:02:37, type: deviceOnline, notifications: 0
2025-03-11 09:02:37  INFO: [T7b3b9617: watch > 80.187.68.208] [SG*9180017166*0002*LK]
2025-03-11 09:02:42  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364586395707041284300066e4f40100639c67cfedea1f00518280002547002240921bfbbf0278feef40b408b9de69ad43060819012b079d4325199a01001d1e1b18164000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343420706f7765723a3339343938342040faaf
2025-03-11 09:03:35  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364686395707041284300066e4fe0100639c67cfedea1500518280002547002240921bfbbf0278feef40b408b9de69ad43060819012b079d4325199a01001d1e1b18164000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343420706f7765723a3339343938342040faaf
2025-03-11 09:03:52  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364786395707041284300066e4fe0100639c67cfedea1500518280002547002240921bfbbf0278feef40b408b9de69ad43060819012b079d4325199a01001d1e1b18164000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343420706f7765723a3339343938342040faaf
2025-03-11 09:04:09  INFO: [Tda6c4ac6: xexun2 < 109.42.49.214] faaf0014364886395707041284300066e5010100639c67cfedea1200518280002547002240921bfbbf0278feef40b408b9de69ad43060819012b079d4325199a01001d1e1b18164000000a000000028100000409020a0100204d4f56455f4954562031363a30313a343420706f7765723a3339343938342040faaf

Thank You
Michael

Does restart help?

Yes. It did.

I'm afraid the problem is probably only a temporary fix. The technician from the tracker company was unable to detect any irregularities in the tracker.

If it appears again, I will post the log again.