Device Connect / Disconnect frequently

Salman Saeed2 years ago

Dears

I am using alematics device and teltonika to test our server but it is Showing Online/Offline frequently.

For alematics, I could see the location and data but I checked the logs and found that soon device sent the data, server closes the connecting.

For Teltonika, I was trying to simulate it using tcp sender with persistant TCP, I can send IMEI and recieve ack, but after that server disconnect the connection., please see the logs below and sugggest where I am wrong or how I can resolve it.

2022-05-25 10:17:56  INFO: [T11e6d3e7: alematics < 172.20.30.8] faf8006b0003163065173adc
2022-05-25 10:17:56  INFO: [T11e6d3e7: alematics > 172.20.30.8] faf8006b0003163065173adc
2022-05-25 10:17:58  INFO: [T11e6d3e7: alematics < 172.20.30.8] 24542c322c3132342c3836383832323034303339343436302c32303232303532353130313735382c32303232303532353130313735382c32342e3736393538312c34362e3638383939312c34372c3234322c3635392c302e372c31302c312c302c302e3030302c31332e3533362c31303038372c300d0a
2022-05-25 10:17:58  INFO: [T11e6d3e7] id: 868822040394460, time: 2022-05-25 10:17:58, lat: 24.76958, lon: 46.68899, speed: 25.4, course: 242.0
2022-05-25 10:18:01  INFO: [T11e6d3e7] disconnected
2022-05-25 10:18:14  INFO: [T33622c31] connected
2022-05-25 10:18:15  INFO: [T33622c31: alematics < 172.20.30.8] faf8006c0003163065173adc
2022-05-25 10:18:15  INFO: [T33622c31: alematics > 172.20.30.8] faf8006c0003163065173adc
2022-05-25 10:18:18  INFO: [T33622c31] disconnected
2022-05-25 10:18:34  INFO: [T2005936e] connected
2022-05-25 10:18:35  INFO: [T2005936e: alematics < 172.20.30.8] faf8006d0003163065173adc
2022-05-25 10:18:35  INFO: [T2005936e: alematics > 172.20.30.8] faf8006d0003163065173adc
2022-05-25 10:18:38  INFO: [T2005936e] disconnected
2022-05-25 10:20:41  INFO: [T34eaa518] connected
2022-05-25 10:20:41  INFO: [T34eaa518: teltonika < 172.20.30.8] 000f333536333037303432343431303133
2022-05-25 10:20:41  INFO: [T34eaa518: teltonika > 172.20.30.8] 01
2022-05-25 10:20:41  INFO: [T34eaa518] disconnected
2022-05-25 10:20:50  INFO: [T4cacfda9] connected
2022-05-25 10:20:50  INFO: [T4cacfda9: teltonika < 172.20.30.8] 000f333536333037303432343431303133
2022-05-25 10:20:50  INFO: [T4cacfda9: teltonika > 172.20.30.8] 01
2022-05-25 10:20:50  INFO: [T4cacfda9] disconnected
2022-05-25 10:20:54  INFO: [Tc7febb9e] connected
2022-05-25 10:20:54  INFO: [Tc7febb9e: teltonika < 172.20.30.8] 000f333536333037303432343431303133
2022-05-25 10:20:54  INFO: [Tc7febb9e: teltonika > 172.20.30.8] 01
2022-05-25 10:20:54  INFO: [Tc7febb9e] disconnected
2022-05-25 10:20:56  INFO: [T99228ab8] connected
2022-05-25 10:20:56  INFO: [T99228ab8: teltonika < 172.20.30.8] 000f333536333037303432343431303133
2022-05-25 10:20:56  INFO: [T99228ab8: teltonika > 172.20.30.8] 01
2022-05-25 10:20:56  INFO: [T99228ab8] disconnected
2022-05-25 10:21:00  INFO: [T55d10af1] connected
2022-05-25 10:21:00  INFO: [T55d10af1: teltonika < 172.20.30.8] 000f333536333037303432343431303133
2022-05-25 10:21:00  INFO: [T55d10af1: teltonika > 172.20.30.8] 01
2022-05-25 10:21:03  INFO: [T55d10af1] disconnected
Anton Tananaev2 years ago

Seems like your device doesn't like the response from the server.

Salman Saeed2 years ago

Since device is not expecting mangoes instead of Ack :-0 from the server so I believe server is trying to send proper response but for some reason its not delivered(We double checked from the device, no ack received).

Would you please guide me based on your experience how I can troubleshoot further, there is nothing inside traccar log.

BTW our team is also Troubleshooting so if I found something, will get back.

Anton Tananaev2 years ago

As you can see from the log, the ack is sent. If it's not received at all, then you probably have some network issue. Maybe some SIM card problem.

Salman Saeed2 years ago

Dear Anton
Good day!

Thanks for the feedback, yes you are correct that server was trying to send ACK but its getting failed. I've found that the server was configured with Domain using reverse proxy (I am not sure about its configuration as it was done by IT) which was causing this issue, asked IT team to rectify this issue and then it got resolved.