Hello.
I've noticed that after adding couple more tracker devices to the database my logs doesnt's look nice, can you hint me out where the problem is? Server is running well, it is 4GB VPS and it's using only 500MB-1GB of ram right now. There is like 100 devices, but 20 are running at the same time. When I check position just before the connection reset by peer the deivce is on the map running well. These all are mostly xexun and gps103 protocols.
This is example log:
2015-08-09 18:18:54 DEBUG: [92D10093: 5002 <- 94.254.145.54] - HEX: 283032373034323533353136314252303031353038303941353134342e363933314e30313833352e33323639453030302e31313631383532302e3030303030303030303030304c303030303030303029
2015-08-09 18:18:54 INFO: device: 253, time: Sun Aug 09 18:18:52 CEST 2015, lat: 51.744885, lon: 18.588781666666666
2015-08-09 18:18:57 WARN: Connection reset by peer - java.io.IOException (FileDispatcherImpl.java:-2)
2015-08-09 18:18:57 INFO: Closing connection by exception
2015-08-09 18:18:57 INFO: Closing connection by disconnect
2015-08-09 18:18:58 WARN: Connection reset by peer - java.io.IOException (FileDispatcherImpl.java:-2)
2015-08-09 18:18:58 INFO: Closing connection by exception
2015-08-09 18:18:58 INFO: Closing connection by disconnect
2015-08-09 18:18:59 WARN: Connection reset by peer - java.io.IOException (FileDispatcherImpl.java:-2)
2015-08-09 18:18:59 INFO: Closing connection by exception
2015-08-09 18:18:59 INFO: Closing connection by disconnect
2015-08-09 18:19:00 WARN: Connection reset by peer - java.io.IOException (FileDispatcherImpl.java:-2)
2015-08-09 18:19:00 INFO: Closing connection by exception
2015-08-09 18:19:00 INFO: Closing connection by disconnect
2015-08-09 18:19:00 DEBUG: [9CE12590: 5001 <- 188.146.77.11] - HEX: 696d65693a3836363938393737313938333631322c747261636b65722c3135303831303030313134332c3530383930313737352c462c3136313134332e30302c412c343934372e31313034332c4e2c30313931322e30333335302c452c302e3032342c3b
2015-08-09 18:19:00 INFO: device: 195, time: Sun Aug 09 18:11:43 CEST 2015, lat: 49.78517383333333, lon: 19.200558333333333
2015-08-09 18:19:02 WARN: Connection reset by peer - java.io.IOException (FileDispatcherImpl.java:-2)
2015-08-09 18:19:02 INFO: Closing connection by exception
2015-08-09 18:19:02 INFO: Closing connection by disconnect
Those messages basically mean that connection has been closed from the device side. If you download new Traccar version (3.1), you can actually track which devices disconnected and see if there are any problem with any specific device.
OK thanks for your reply Anton. So it's most likely not a server problem but specific device, I shouldnt be worried much.
Hello.
I've noticed that after adding couple more tracker devices to the database my logs doesnt's look nice, can you hint me out where the problem is? Server is running well, it is 4GB VPS and it's using only 500MB-1GB of ram right now. There is like 100 devices, but 20 are running at the same time. When I check position just before the connection reset by peer the deivce is on the map running well. These all are mostly xexun and gps103 protocols.
This is example log: