Online is switching to Offline very fast after update from ver 3.9 to 3.17

Sandu Ciprian Doca6 years ago

Hi. After I updated Traccar server from 3.9 to 3.17 version all the devices are kept online only for a couple of seconds.
All my devices are Teltonika and set to send every 4 minutes, 24/7, so I need to now exactly when is something wrong with one of the devices.
I searched all the forum, tried to timeout setting but no effect.

When I was using older versions of Traccar Server the devices went offline many minutes after the last position was received.

Anton Tananaev6 years ago

Have you checked logs?

Sandu Ciprian Doca6 years ago

here is a sample of my logs 

2018-06-30 19:17:26 DEBUG: [AFC87251: 5027 > 109.166.131.117] HEX: 00000001
2018-06-30 19:17:26  INFO: [AFC87251] id: 356307049204646, time: 2018-06-30 19:15:02, lat: 45.44313, lon: 28.01124, course: 0.0
2018-06-30 19:17:29  INFO: [B5D9EE7C] disconnected
2018-06-30 19:17:38  INFO: [B8796530] connected
2018-06-30 19:17:40 DEBUG: [B8796530: 5027 < 109.166.130.75] HEX: 000f333532303933303834313031363537
2018-06-30 19:17:40 DEBUG: [B8796530: 5027 > 109.166.130.75] HEX: 01
2018-06-30 19:17:42 DEBUG: [B8796530: 5027 < 109.166.130.75] HEX: 000000000000002f0801000001645179a138001112ab041a5175d80003010611000000050115050442339118000043101d44000000000100000e42
2018-06-30 19:17:42 DEBUG: [B8796530: 5027 > 109.166.130.75] HEX: 00000001
2018-06-30 19:17:42  INFO: [B8796530] id: 352093084101657, time: 2018-06-30 19:14:43, lat: 44.15462, lon: 28.64361, course: 262.0
2018-06-30 19:17:49  INFO: [05779A00] disconnected
2018-06-30 19:18:15 DEBUG: [8A0AB84A: 5027 < 109.166.134.162] HEX: 000000000000002f080100000164517cd1a0001112d8c81a4c4bb5001200b31200000005011505044233881800004310204400000000010000b5e3
2018-06-30 19:18:15 DEBUG: [8A0AB84A: 5027 > 109.166.134.162] HEX: 00000001
2018-06-30 19:18:15  INFO: [8A0AB84A] id: 352093083764091, time: 2018-06-30 19:18:12, lat: 44.12077, lon: 28.64478, course: 179.0
2018-06-30 19:18:26  INFO: [44855FDB] connected
2018-06-30 19:18:29 DEBUG: [44855FDB: 5027 < 109.166.137.218] HEX: 000f333536333037303438383338313534
2018-06-30 19:18:29 DEBUG: [44855FDB: 5027 > 109.166.137.218] HEX: 01
2018-06-30 19:18:31 DEBUG: [44855FDB: 5027 < 109.166.137.218] HEX: 0000000000000021080100000164517c0270001112d5cb1a4c3a58000200001000000000000000000100009e16
2018-06-30 19:18:31 DEBUG: [44855FDB: 5027 > 109.166.137.218] HEX: 00000001
2018-06-30 19:18:31  INFO: [44855FDB] id: 356307048838154, time: 2018-06-30 19:17:18, lat: 44.12033, lon: 28.64471, course: 0.0
2018-06-30 19:18:32  INFO: [87BFEC71] connected
2018-06-30 19:18:32  INFO: [AFC87251] disconnected
2018-06-30 19:18:33 DEBUG: [87BFEC71: 5027 < 109.166.132.185] HEX: 000f333532303933303834343939303639
2018-06-30 19:18:33 DEBUG: [87BFEC71: 5027 > 109.166.132.185] HEX: 01
2018-06-30 19:18:35 DEBUG: [87BFEC71: 5027 < 109.166.132.185] HEX: 000000000000002f080100000164517c2d90001112a7e41a517abafffd011711000000050115050442333d180000430fac4400000000010000195f
2018-06-30 19:18:35 DEBUG: [87BFEC71: 5027 > 109.166.132.185] HEX: 00000001
2018-06-30 19:18:35  INFO: [87BFEC71] id: 352093084499069, time: 2018-06-30 19:17:30, lat: 44.15475, lon: 28.64353, course: 279.0
2018-06-30 19:18:45 DEBUG: [B8796530: 5027 < 109.166.130.75] HEX: 000000000000002f080100000164517d4ab8001112ab041a5175d80003010612000000050115050442337e18000043101d44000000000100001ebb
2018-06-30 19:18:45 DEBUG: [B8796530: 5027 > 109.166.130.75] HEX: 00000001
2018-06-30 19:18:45  INFO: [B8796530] id: 352093084101657, time: 2018-06-30 19:18:43, lat: 44.15462, lon: 28.64361, course: 262.0
2018-06-30 19:18:47 DEBUG: [78071A16: 5027 < 109.166.138.43] HEX: 0000000000000032080100000164517d4afe000bda46911afa2a00004c00001100000007040100020103000400030900330a001f18000000000100008d90
2018-06-30 19:18:47 DEBUG: [78071A16: 5027 > 109.166.138.43] HEX: 00000001
2018-06-30 19:18:47  INFO: [78071A16] id: 356307049445793, time: 2018-06-30 19:18:43, lat: 45.26024, lon: 19.88543, course: 0.0
Anton Tananaev6 years ago

I don't see any problems with the log, but obviously you need to match what you see in the status with connect/disconnect in the log.

Sandu Ciprian Doca6 years ago

when i was using the 3.9 version it didn't have this kind of behavior.

the devices where getting the offline status after many minutes if they didn't send position.

the behavior of this version is very annoying. maybe i will switch back to the older version.
can you tell me at which version did you change this behavior?

Thank you!

Anton Tananaev6 years ago

Behaviour hasn't changed, as far as I know.

Sandu Ciprian Doca6 years ago

ok. i will switch it back to the older version.

Sandu Ciprian Doca6 years ago

i installed a new server with 3.9 version
here is a sample of logs. the device is getting disconnected but in web app doesn't become offline.

it's a different behavior than 3.15 

2018-07-02 13:44:58  INFO: [43EECBD8] connected
2018-07-02 13:44:59 DEBUG: [43EECBD8: 5027 < 109.166.132.51] HEX: 000f333536333037303439323034363436
2018-07-02 13:44:59 DEBUG: [43EECBD8: 5027 > 109.166.132.51] HEX: 01
2018-07-02 13:45:01 DEBUG: [43EECBD8: 5027 < 109.166.132.51] HEX: 00000000000000210801000001645a97920c0010b22d1f1b16123100370000090000000000000000010000bd41
2018-07-02 13:45:01 DEBUG: [43EECBD8: 5027 > 109.166.132.51] HEX: 00000001
2018-07-02 13:45:02  INFO: [43EECBD8] id: 356307049204646, time: 2018-07-02 13:44:00, lat: 45.44313, lon: 28.01124, speed: 0.0, course: 0.0
2018-07-02 13:46:08  INFO: [43EECBD8] disconnected
Anton Tananaev6 years ago

Add "status.ignoreOffline" configuration parameter with "teltonika" as a value.