The transfer you requested has been deleted.
Where should I Upload it?
That's up to you.
It seems like you're not using the standard logging level, so there's too much noise and not possible to understand what's going on.
Unfortunately, nothing can be seen in the standard log level:
2023-07-24 14:19:42 INFO: [Tc19b355a] id: 868683026742696, time: 2023-07-24 14:19:40, lat: 52.49500, lon: 13.71043, speed: 5.5, course: 39.4
2023-07-24 14:19:42 INFO: [Tb64469f1: gps103 < 80.187.118.228] 696d65693a3836343839353033343734333036302c747261636b65722c3233303732343134313934352c2c462c3132313934352e30302c412c353233382e32373438332c4e2c30313334342e36313634342c452c332e3036332c3132352e34363b
2023-07-24 14:19:42 INFO: [Tb64469f1] id: 864895034743060, time: 2023-07-24 14:19:45, lat: 52.63791, lon: 13.74361, speed: 3.1, course: 125.5
2023-07-24 14:19:43 INFO: [T48da4012] disconnected
2023-07-24 14:19:43 INFO: [T06ae5de9] connected
2023-07-24 14:19:43 INFO: [T06ae5de9] id: ffffffff-c3e9-ca1c-ffff-ffff9f6971b4, time: 2023-07-24 14:19:26, lat: 52.77958, lon: 11.26575, course: 0.0, accuracy: 6.1
2023-07-24 14:19:44 INFO: [Tb3e34e0a: gps103 < 80.187.116.51] 696d65693a3836383638333032363531363338392c747261636b65722c3233303732343132313934372c2c462c3132313934322e3030302c412c353233362e343639362c4e2c30313333372e343831392c452c302e30302c303b
2023-07-24 14:19:44 INFO: [Tb3e34e0a] id: 868683026516389, time: 2023-07-24 14:19:42, lat: 52.60783, lon: 13.62470, course: 0.0
2023-07-24 14:19:44 INFO: [T57c7a3da: gps103 < 80.187.118.145] 696d65693a3836343839353033323535383630312c747261636b65722c3233303732343134313934372c2c462c3132313934372e30302c412c353233362e34383531362c4e2c30313333372e34393637332c452c2c3b
2023-07-24 14:19:44 INFO: [T57c7a3da] id: 864895032558601, time: 2023-07-24 14:19:47, lat: 52.60809, lon: 13.62495, course: 0.0
2023-07-24 14:19:45 INFO: [Td2e0555a: gps103 < 80.187.117.189] 696d65693a3836343839353033323835343836392c747261636b65722c3233303732343134313934372c2c462c3132313934372e30302c412c353232392e35393831332c4e2c30313334332e30393437392c452c302e3134312c303b
2023-07-24 14:19:45 INFO: [Td2e0555a] id: 864895032854869, time: 2023-07-24 14:19:47, lat: 52.49330, lon: 13.71825, speed: 0.1, course: 0.0
2023-07-24 14:19:45 INFO: [T8b9384a5: gt06 < 80.187.119.220] 78781f121707180c132fca05a4e69c01763e1833350e01060137200068ab005606470d0a
2023-07-24 14:26:37 INFO: user: 15, action: login, from: 80.187.84.181:3190
2023-07-24 14:26:51 INFO: user: 15, report: route, from: 2023-07-24 13:26, to: 2023-07-24 14:26, devices: [173], groups: []
2023-07-24 14:26:51 INFO: user: 15, report: events, from: 2023-07-24 13:26, to: 2023-07-24 14:26, devices: [173], groups: []
2023-07-24 14:32:09 INFO: user: 15, action: login, from: 80.187.119.175:16069
2023-07-24 14:39:33 INFO: Operating system name: Windows Server 2012 R2 version: 6.3 architecture: amd64
2023-07-24 14:39:33 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Eclipse Adoptium version: 17.0.6+10
2023-07-24 14:39:33 INFO: Memory limit heap: 1536mb non-heap: 0mb
2023-07-24 14:39:33 INFO: Character encoding: Cp1252 charset: windows-1252
at 14:19:45 was the last recording, then only logins are possible, but no more recording.
at 14:39:33 I restart the service
All the important stuff is logged with the standard logging level. Have you done the troubleshooting steps?
Ok in the standard logging level I only see that the last position was recorded at 14:19:45, after that only user logins are logged.
But unfortunately I don't see why Traccar no longer processes the incoming positions.
In the detailed log, you can see that many exceptions are thrown, unfortunately I can't explain what they mean.
Do you mean https://www.traccar.org/troubleshooting/ ? Yes, I've already looked at these.
If you've already done the troubleshooting, you should have a pretty good idea on where the problem is.
Hello,
our server has been running for over a year without any problems or dropouts. For about 2 weeks there has been a sudden failure of the recording. This means you can log in to the website and see all devices, but no new coordinates will be recorded.
It runs on a Windows Server 2012 R2 and with Maria DB 10.5.16. Here is the log file, from 00:37 the recording was stopped.
tracker-server.log
Where is the problem?
What else can I test/try?