Traccar Server Throttling Issue with OSMAND Protocol

adriantonaa year ago

Hello fellow forum members,

I hope you’re all having a great day! I’m reaching out because I’ve encountered an interesting challenge with my Traccar server, and I’m hoping someone here might have some insights.

Background:

I’m running a server called HMDM, which is specifically designed for managing mobile devices (in this case, Android devices).
The server collects device location data approximately every 10 seconds.

Integration with Traccar:
Recently, I’ve successfully set up communication between my HMDM server and my Traccar server using the OSMAND protocol.
Everything seemed to be working smoothly—until I noticed a peculiar behavior.

The Issue:
After processing several location updates in quick succession, it appears that the Traccar server’s response time slows down significantly for requests coming from my HMDM server.
Specifically, it seems to throttle the processing speed to around two requests every 5 seconds for this specific IP address.

Troubleshooting So Far:
I’ve diligently checked the Traccar logs, but there’s no indication of throttling or any related messages.

My Questions:
Does Traccar indeed have any built-in throttling mechanisms for the OSMAND protocol?
If it does, how can I adjust or increase this limit?
Alternatively, is there a way to whitelist the IP address of my HMDM server to bypass any potential throttling?
I greatly appreciate any insights or suggestions you might have. Let’s unravel this mystery together!

Thank you in advance, and happy tracking!

Best regards,

Anton Tananaeva year ago

Do you have logs?

adriantonaa year ago

Sorry there is it:

Traccar log acepting various positions por second:

[object Object]

Same log but only two positions per every five seconds:

[object Object]
Anton Tananaeva year ago

I see that Traccar response is instant, which already contradicts what you said earlier about delayed responses.

adriantonaa year ago

Thank you very much for your prompt reply,

I apologize—it was my mistake. As I’m still learning, I should have recognized that the ‘osmand >’ string in the log was indeed the answer.

I’ll investigate further on my server’s side.

Once again, thank you for taking the time to review my post, and congratulations on such a wonderful project!"

JCardus10 months ago

I'm also having an issue with osmand on the latest master.

I'm timing out at 5 seconds on the client side, but I don't see any response on the server log. I have geocoding disabled.

here's my log:

[object Object]
Anton Tananaev10 months ago

Are you sure you don't have any external services that could cause delays, like reverse geocoding?

JCardus10 months ago
Anton Tananaev10 months ago

And you're sure you provided the complete log without filtering anything?

JCardus10 months ago

Yes I'm sure, I didn't filter anything.

Anton Tananaev10 months ago

You can try server.instantAcknowledgement and see if it helps.

JCardus10 months ago

WIth that I get the response, but the device doesn't update.

Anton Tananaev10 months ago

And you're using the latest official release without any code modifications?

JCardus10 months ago

Yes, 6.3.

Anton Tananaev10 months ago

Don't have any other ideas. You would have to debug it.