This was working just fine before I installed it. Nothing was changed with the config. It will respond via SMS etc. The log files seem to show as connected but it does not appear as such in the webinterface. There are lots of errors in the log all of a sudden. I post a typical example
2020-08-19 17:46:17 INFO: [642f4d58: eelink > 1.126.106.240] HEX: 454c00111ecf03546790900446716767120002212c
2020-08-19 17:46:17 WARN: [642f4d58] error - readerIndex(1022) + length(1) exceeds writerIndex(1022): PooledDirectByteBuf(ridx: 1022, widx: 1022, cap: 2048) - IndexOutOfBoundsException (... < EelinkProtocolDecoder:279 < *:429 < ExtendedObjectDecoder:51 < ... < StandardLoggingHandler:43 < ...)
2020-08-19 17:47:09 INFO: [642f4d58: eelink < 1.126.106.240] HEX: 454c029249a50354679090044671676712004321315f3cf43503fc94d3760c79328a0129000000000a01f9000190330905580d2e046f118a04ec00000000ccc7086c02fe000000000000000000000000000000000000676712004321325f3cf43e03fc94d3760c79328a0129000000000901f9000190330905580d2e046f117b04ec00000000ccc7086d02ff000000000000000000000000000000000000676712004321335f3cf44703fc94d3760c79328a0129000000000901f9000190330905580d2e046f117f04ec00000000ccc7086d02ff000000000000000000000000000000000000676712004321345f3cf45303fc94d3760c79328a0129000000000901f9000190330905580d2e046f119d04ec00000000ccc7086d02ff000000000000000000000000000000000000676712004321355f3cf45c03fc94d3760c79328a0129000000000801f9000190330905580d2e046f11a304ec00000000ccc7086d02ff000000000000000000000000000000000000676712004321365f3cf46603fc94d3760c79328a0129000000000801f9000190330905580d2e046f118804df00000000ccc7086d02ff000000000000000000000000000000000000676712004321375f3cf47103fc94d3760c79328a0129000000000901f9000190330905580d2e046f119704ec00000000ccc7086d02ff000000000000000000000000000000000000676712004321385f3cf47a03fc94d3760c79328a0129000000000901f9000190330905580d2e046f118204ec00000000ccc7086e0300000000000000000000000000000000000000676712004321395f3cf48303fc94d3760c79328a0129000000000901f9000190330905580d2e046f117604df00000000ccc7086e0300000000000000000000000000000000000000
2020-08-19 17:47:09 INFO: [642f4d58: eelink > 1.126.106.240] HEX: 454c00111ed4035467909004467167671200022131
2020-08-19 17:47:09 WARN: [642f4d58] error - readerIndex(662) + length(2) exceeds writerIndex(662): PooledDirectByteBuf(ridx: 662, widx: 662, cap: 2048) - IndexOutOfBoundsException (... < EelinkProtocolDecoder:285 < *:429 < ExtendedObjectDecoder:51 < ... < StandardLoggingHandler:43 < ...)
any suggests as to how to resolve appreciated, as I say it worked just fine yesterday ....
Do you have protocol documentation?
Are you using UDP protocol?
Yes, TCP resulted in no connections at all.
And I'm assuming it's the latest version of Traccar. Is that correct?
The odd thing is every now and then a single point will work . ?
Is the fix in the latest release for download ?
I've answered my own question - seems not. Can you advise the path to the files that need patching ? I've looked but cannot see the files you have in git anywhere in the structure. I'm running traccar on linux x64.
You have to compile the binary.
Right, and how would I do that ...
You would read documentation on this website to find out.
That's really helpful. To come at it from another angle when would you expect the next release of a full installer with the fix in it ?
This was working just fine before I installed it. Nothing was changed with the config. It will respond via SMS etc. The log files seem to show as connected but it does not appear as such in the webinterface. There are lots of errors in the log all of a sudden. I post a typical example
any suggests as to how to resolve appreciated, as I say it worked just fine yesterday ....