Are you sure all those messages are valid? Especially check the length field.
Hi Anton,
so we debugged the logs and found out device position data is getting marked as outdated in cache and after that it is not processing any ping which is coming. After we restart traccar services it starts getting processed.
Any input on this situation?
Thanks
I already gave you a suggestion on what to check.
Try activating the invalid position filter!
that is already applied.
@Anton,
this packets seems to be valid.
7878231217041a0e2c04c002deef7808cfa11500140001951c0fb3003623003d849b177bce630d0a
It is also not getting processed.
You have to check all of them from the start of the connection, not just this one.
so if any one of them is not valid then it will not process any further valid packets also?
sorry I am asking too many questions but I want to be clear about how it works.
Yes, if the length is incorrect, there's no way for server to properly separate messages in the stream.
Hi Anton,
We have checked logs and found out that our devices which are creating issues they have started second channel while the first channel is still activate.because of that device is not updating positions after that.
Is it device fault or some configuration at our server side?
Thanks
Why do you think it's an issue? It won't cause any problems.
Hi,
We have few devices working on GT06 protocol.these devices are sending in between few strings which are not starting by 7878 or 7979. After that server has stopped responding to the genuine pings also because of that devices are going inactive.Please find the logs snapshot for the same.
How can we solve this issue?
https://drive.google.com/file/d/1gEZUw8YUdb0pSa6DjoHum57fo75BP8FX/view?usp=sharing