Updated to 3.10 on windows getting some exceptions in log file
@pRob3, which device you are using?
I need a fragment of the log file which includes full connection session. It can be identified by the number in the square brackets.
I have seen the same thing happening on my server. Here are the logs from a couple of the devices this occurred on:
2017-02-25 07:35:37 INFO: [E7698E9A] connected
2017-02-25 07:35:37 DEBUG: [E7698E9A: 81 < 91.87.217.71] HEX: 2a48512c343130383031313737322c56312c3037333731372c412c323735382e313135332c4e2c30383234382e313031302c572c3030302e30302c3030302c3235303231372c46464646464246462c3331302c3236302c302c302c3623
2017-02-25 07:35:37 INFO: [E7698E9A] id: 4108011772, time: 2017-02-25 07:37:17, lat: 27.96859, lon: -82.80168, speed: 0.0, course: 0.0
2017-02-25 07:35:38 DEBUG: [E7698E9A: 81 < 91.87.217.71] HEX: 24410801177207371725021727581150060824810106000000fffffbffff000e0b0000000001361a00000000042a48512c343130383031313737322c56392c3037333731372c412c323735382e313135332c4e2c30383234382e313031302c572c3030302e30302c3030302c3235303231372c2c2c464646464642464623
2017-02-25 07:35:38 INFO: [E7698E9A] id: 4108011772, time: 2017-02-25 07:37:17, lat: 27.96858, lon: -82.80168, speed: 0.0, course: 0.0
2017-02-25 07:35:39 INFO: [E7698E9A] id: 4108011772, time: 2017-02-25 07:37:17, lat: 27.96859, lon: -82.80168, speed: 0.0, course: 0.0
2017-02-25 07:36:24 DEBUG: [E7698E9A: 81 < 91.87.217.71] HEX: 24410801177207380225021727581160060824809906000000fffffbffff000d0b0000000001361a0000000005
2017-02-25 07:36:24 INFO: [E7698E9A] id: 4108011772, time: 2017-02-25 07:38:02, lat: 27.96860, lon: -82.80165, speed: 0.0, course: 0.0
2017-02-25 07:36:24 WARN: [E7698E9A] error - IllegalArgumentException (H02FrameDecoder:84 < ...)
2017-02-25 07:36:24 INFO: [E7698E9A] disconnected2017-02-25 14:38:57 INFO: [256716C2] connected
2017-02-25 14:38:57 DEBUG: [256716C2: 81 < 91.87.217.76] HEX: 2a48512c343130383031333337382c56312c3134343033382c412c323735382e313037372c4e2c30383234382e313135392c572c3030302e30302c3030302c3235303231372c46464646464246462c3331302c3236302c302c302c3623
2017-02-25 14:38:57 INFO: [256716C2] id: 4108013378, time: 2017-02-25 14:40:38, lat: 27.96846, lon: -82.80193, speed: 0.0, course: 0.0
2017-02-25 14:38:58 DEBUG: [256716C2: 81 < 91.87.217.76] HEX: 24410801337814403825021727581070060824811506000000fffffbffff000b0b0000000001361a00000000092a48512c343130383031333337382c56392c3134343033382c412c323735382e313037372c4e2c30383234382e313135392c572c3030302e30302c3030302c3235303231372c2c2c464646464642464623
2017-02-25 14:38:58 INFO: [256716C2] id: 4108013378, time: 2017-02-25 14:40:38, lat: 27.96845, lon: -82.80192, speed: 0.0, course: 0.0
2017-02-25 14:38:58 INFO: [256716C2] id: 4108013378, time: 2017-02-25 14:40:38, lat: 27.96846, lon: -82.80193, speed: 0.0, course: 0.0
2017-02-25 14:39:12 DEBUG: [256716C2: 81 < 91.87.217.76] HEX: 24410801337814405325021727581070060824811506000000fffffbffff000b0a0000000001361a000000000a
2017-02-25 14:39:13 INFO: [256716C2] id: 4108013378, time: 2017-02-25 14:40:53, lat: 27.96845, lon: -82.80192, speed: 0.0, course: 0.0
2017-02-25 14:39:13 WARN: [256716C2] error - IllegalArgumentException (H02FrameDecoder:84 < ...)
2017-02-25 14:39:13 INFO: [256716C2] disconnectedThis is version 3.10 and I am using port 81 for H02 input from LK-108 GPS trackers.
Try setting "h02.messageLength" to 45 in the config file.
@Anton does this setting works for version 3.9 as well? And what does it do actually?
Yes, it does.
Thanks. I made the change and I am going to let it run for a while and let you know if it handles the problem.
After having run this for a while, I can say that the setting reduced the number of errors. I have only had 2 or 3 since then. But then I had something else funny happen. On 2 March around 7am UTC, I started having less devices report in and by today there was only a handful of devices reporting at all, mostly one device. I usually have over 300 different devices report per hour and have something on the order of 3800 active devices in my system. I do not know if this was related to the change, but I reverted the configuration back and restarted traccar.
Unfortunately I was out of town and did not catch the problem until about 3 1/2 hours ago. I don't see any errors in the log, so I am not sure why devices stopped logging locations. I can tell that they were sending data via my phone service portal and when I restarted traccar I got something on the order of 3800 disconnects so it appears that connections were hanging.
No idea if the change of configuration caused this or not. If anyone has a clue as to why this occured, I would definitely want to know.
If you have large number of connection, you might want to set connection timeouts. Check this page:
Good point. I changed servers when I upgraded Traccar and I recall having set these limits higher before on my old server. So I have done the same again on the new server. I imagine that will handle the problem.
still not working for me. Here are samples of messages from logs
1. 2442101695420418140603173043988006076423590e037233ffffdfffff0021 2. 2a48512c343231303133353135382c56312c3034313831342c412c323833312e313033352c4e2c30373732382e303530352c452c3030302e30302c3030302c3036303331372c464646464642464623 3. 2a48512c343231303136393738372c4e42522c3032323631352c3430352c31382c302c312c302c302c35392c3036303331372c46464646464246462c3623
these are 3 different messages length, after this setting should it consider just messages with length of 45?
Length applies only to binary messages (start with "24"). In your case length seems to be 32.
@Anton, I am trying to implement this protocol in Node. I am getting these messages in the buffer.
connection data from ::ffff:101.57.250.95:27034: {"type":"Buffer","data":[42,72,81,44,52,50,49,48,49,54,57,55,56,55,44,86,49,44,48,54,50,51,50,55,44,65,44,51,48,52,49,46,56,51,48,55,44,78,44,48,55,54,52,49,46,50,54,52,50,44,69,44,48,48,48,46,48,48,44,48,48,48,44,48,54,48,51,49,55,44,70,70,70,70,70,66,70,70,35]}
connection data from ::ffff:101.57.250.95:27034: {"type":"Buffer","data":[52,50,49,48,49,54,57,55,56,55]}what should I do with this raw buffer data? Do I need to convert these in Hex directly? Or is there some other steps to follow, please give me a link where conversion happens in the Traccar.
Please no off-topic. If you want to ask something that's not related to the topic, create another thread. As for the question itself, it's a mixed protocol. Some messages are binary, some text.