Problem receiving events in real time

Charlie Michael3 years ago

Hi.

For the last three days we have been experiencing problems receiving the events from the vehicles in real time. We are receiving them with a considerable delay and they always arrive in large quantities (more than ten records, in which the server time is the same, varying the devicetime and fixtime). Can you help us identify what might be causing this problem?

Thanks

Anton Tananaev3 years ago

Have you checked logs?

Charlie Michael3 years ago

Yes, that was the first thing we did.

Here's an example of what appears in the logs:

2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:49:45, lat: -25.81965, lon: 32.57863, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:50:00, lat: -25.81965, lon: 32.57863, course: 0.0
...
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:53:02, lat: -25.81965, lon: 32.57863, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:53:17, lat: -25.81965, lon: 32.57863, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:53:32, lat: -25.81965, lon: 32.57863, course: 0.0
Anton Tananaev3 years ago

OK, but I don't see the most important part in your log - the raw data.

Charlie Michael3 years ago

Sorry, here's the full record:

2022-05-21 12:22:20  INFO: Response: true
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:49:45, lat: -25.81965, lon: 32.57863, course: 0.0
...
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:53:17, lat: -25.81965, lon: 32.57863, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:53:32, lat: -25.81965, lon: 32.57863, course: 0.0
2022-05-21 12:22:20  INFO: Response: 
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021281437, time: 2022-05-20 18:53:47, lat: -25.81965, lon: 32.57863, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58: teltonika < 197.235.69.244] HEX: 03e1cafe017e000f333532383438303231343133343336081100000180e23181a200184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e231bcbd00184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e231f7d600184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e23232f000184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e2326e0a00184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e232a92400184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e232e43e00184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e2331f5800184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a118000001c7000000000000000180e2335a7200184105e0f75226e000000000000000000a05010002004501f000150004b5001eb6001c4601a118000001c7000000000000000180e233958c00184105e0f75226e000000000000000000a05010002004501f000150004b5001eb6001c4601a318000001c7000000000000000180e233d0a600184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a518000001c7000000000000000180e2340bc000184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a618000001c7000000000000000180e23446bc00184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a718000001c7000000000000000180e23481d600184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a718000001c7000000000000000180e234bcf000184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a818000001c7000000000000000180e234f80a00184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a718000001c7000000000000000180e235332400184105e0f75226e000000000000000000a05010002004501f000150504b5001eb6001c4601a718000001c7000000000011
2022-05-21 12:22:20  INFO: [b9808e58: teltonika > 197.235.69.244] HEX: 00050000017e11
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 15:58:56, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: Response: 
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 15:59:12, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 15:59:27, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: Response: 
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 15:59:42, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: Response: 
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 15:59:57, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 16:00:12, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 16:00:27, lat: -14.56110, lon: 40.69145, course: 0.0
2022-05-21 12:22:20  INFO: Response: 
2022-05-21 12:22:20  INFO: [b9808e58] id: 352848021413436, time: 2022-05-20 16:00:42, lat: -14.56110, lon: 40.69145, course: 0.0
Anton Tananaev3 years ago

Seems like device is just sending data in a batch. Why do you think there's some server issue?

Charlie Michael3 years ago

Because if we go see the location of the vehicle in Traccar, it shows data for previous hours, and never in real time.

In some vehicles there is a difference of more than 12 hours, so in Traccar we don't see them in real time.

Is there any way to avoid them being sent in batches?

Anton Tananaev3 years ago

If it's a device problem, there's obviously nothing you can do on the server side to solve it. You need to make sure your device is reporting the data in real time to get it in real time.

Charlie Michael3 years ago

I understand Anton, but the problem is that there are more than 50 devices and all of them, from two days ago, are reporting the same way.
These are devices that have been reporting for a few years and we have never had this problem.
That's why we find it strange that all of a sudden this situation is happening to all devices.
If it was one or two, we would understand, but it is happening to all devices.

Do you have any suggestion to solve this problem?

Thanks

Anton Tananaev3 years ago

All Teltonika? Have you talked to their support?

Charlie Michael3 years ago

Not yet