Error in log about Concox GT06N trackers
More logs?
yes sure
2020-06-02 16:10:19 TRACE: [DEBUG] Released scope instance {0} on thread {1}
2020-06-02 16:10:19 INFO: [b328dae1: gt06 < 154.105.67.158] HEX: 78781f121406020f0833cf03f081b0011c009211d4db025d030086002f640675b64d0d0a
2020-06-02 16:10:19 INFO: [b328dae1: gt06 > 154.105.67.158] HEX: 787805120675d25e0d0a
2020-06-02 16:10:19 INFO: [2d4348b9] connected
2020-06-02 16:10:19 TRACE: [DEBUG] Released scope instance {0} on thread {1}
2020-06-02 16:10:19 INFO: [b328dae1] id: 353701093047054, time: 2020-06-02 16:08:51, lat: 36.71860, lon: 10.34021, speed: 9.2, course: 219.0
2020-06-02 16:10:19 TRACE: [DEBUG] Released scope instance {0} on thread {1}
2020-06-02 16:10:19 INFO: [c4ef1fad: meitrack < 197.6.208.123] HEX: 24246a3137362c3836333833353032363837303732302c4141412c33322c33362e3039303630352c392e3336353935302c3230303630323135303835302c412c31322c32312c31352c3332312c302e372c3433322c3130363836363537332c37373632363338302c3630357c327c314634307c30323543424438352c303230302c303030307c303030307c303030307c303141417c304144432c2c2c332c303030302c3030303837462c3433362c3433
2020-06-02 16:10:19 INFO: [c4ef1fad: meitrack < 197.6.208.123] HEX: 302a39450d0a
2020-06-02 16:10:19 WARN: [c4ef1fad] error - BufferOverflowException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-06-02 16:10:19 INFO: [c4ef1fad] disconnected
2020-06-02 16:10:19 INFO: [848ef4e4] connected
2020-06-02 16:10:19 INFO: [efd09c29] connected
2020-06-02 16:10:19 WARN: [c4ef1fad] error - For input string: "ALM1=F5;ALM2=D5;ALM3=DF;STA1=40;DYD=01;SOS=28145431" - NumberFormatException (... < MeitrackFrameDecoder:37 < BaseFrameDecoder:29 < ... < WrapperInboundHandler:50 < ...)
2020-06-02 16:10:19 INFO: [e6428fd8: gt06 < 196.186.93.163] HEX: 787823121406020f0834d303e2c4c0011693284ad4d3025d0200170056440db1573005419bdb0d0a
2020-06-02 16:10:19 INFO: [e6428fd8: gt06 > 196.186.93.163] HEX: 7878051205418f910d0a
2020-06-02 16:10:19 TRACE: [DEBUG] Released scope instance {0} on thread {1}
2020-06-02 16:10:19 INFO: [e6428fd8] id: 353701090390770, time: 2020-06-02 16:08:52, lat: 36.21842, lon: 10.14260, speed: 40.0, course: 211.0
2020-06-02 16:10:19 INFO: [4cb4c1e4: gt06 < 41.228.40.162] HEX: 787823121406020f0834d103d71ac000e8efb413d4aa025d0305c300526409737a5003debbc70d0a
2020-06-02 16:10:19 INFO: [815e1dff] timed out
2020-06-02 16:10:19 TRACE: [DEBUG] Released scope instance {0} on thread {1}
2020-06-02 16:10:19 INFO: [4aa65a86] connected
2020-06-02 16:10:19 INFO: [d599ca64] timed out
2020-06-02 16:10:19 INFO: [4cb4c1e4: gt06 > 41.228.40.162] HEX: 7878051203deb73f0d0aWeird, the string doesn't seem to match.
Sorry,
You mean, the string is for GT06 but it's being parsed via Meitrack decoder?
Just if it helps, the string seems to be sent when an alarm occurs on GT06, like vibration, power cut, etc.
Yes, I'm not sure how that's possible.
Last thing, I'm using the code from master branch and modified the MeitrackProtocolDecoder.java
After these existing lines:
int event = parser.nextInt();
position.set(Position.KEY_EVENT, event);
position.set(Position.KEY_ALARM, decodeAlarm(event));I inserted these lines to support ignition for my meitrack trackers:
switch (event) {
case 2:
case 3:
case 4:
position.set(Position.KEY_IGNITION, true);
break;
case 10:
case 11:
case 12:
position.set(Position.KEY_IGNITION, false);
break;
default:
break;
}then comes your code again:
position.setLatitude(parser.nextDouble());
position.setLongitude(parser.nextDouble());I don't know if it breaks anything, it just build fine and then deployed without problem.
Hello again,
is the commit [1] "Workaround for zeroed LBS data" related to this problem?
Some time ago, I did the same code change in 4.2 and it worked, now I'm willing to use the last master-branch code and I've noticed high CPU + all the errors in log (70% of my trackers are GT06).
Do you think it's safe to use the current master-branch in production?
Thank you,
[1] https://github.com/traccar/traccar/commit/71f894ef66fe8ce84eaa32c2771efb53cfd47de4
Installed current master-branch and the problem is still here:
2020-06-08 17:40:26 WARN: [0c00711f] error - An existing connection was forcibly closed by the remote host - IOException (...)
2020-06-08 17:40:26 WARN: [165b2c5f] error - BufferOverflowException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-06-08 17:40:26 WARN: [165b2c5f] error - For input string: "ALM1=F5;ALM2=D5;ALM3=5F;STA1=40;DYD=01;SOS=06215437" - NumberFormatException (... < MeitrackFrameDecoder:37 < BaseFrameDecoder:29 < ... < WrapperInboundHandler:50 < ...)
2020-06-08 17:40:28 WARN: [bb957812] error - An existing connection was forcibly closed by the remote host - IOException (...)The error doesn't exisit in old 4.2 version.
Is this error something we've to worry about, or we could simply ignore?
You are getting an error on Meitrack port. I don't really see how it's related to the GT06 change.
I downgraded to 4.2 and run it for 3 days on +1k connected trackers and haven't noticed the error.
Now I've just compiled master branch (mvn package) and deployed it, the error appeared again.
I've checked the config for the trackers causing the error and they're configured on GT06 port.
This error can only happen if a device is sending to the Meitrack port, unless you have some customization.
I see, the only cutomization, is the code I've shown to detect meitrack ignition.
I'm using url forward too which is IMO a standard usage of traccar.
I'll try to investigate more and report any findings.
Thank you,
Hello,
I've activated WARNING level and I'm getting this error
The device is a concox GT06N tracker and it's working correctly, but some times I'm getting this error.
Should I ignore it or it means something was wrong.
Regards,