No events in client but there are events in the logs - StringOutOfBounds Exception

mbos 5 years ago

Hello
Very new to Traccar.
Using Android client - Traccar Server on Windows 10 . 5055 is open, no web server (that I know of).

the logs are getting:

2021-03-16 08:51:39  INFO: [aec84de9] connected
2021-03-16 08:51:39  INFO: [aec84de9: gps103 < 1.136.105.210] HEX: 504f5354202f3f69643d3339303635322674696d657374616d703d31363135383435313030266c61743d2d33382e33333930363636266c6f6e3d3134352e313733333431312673706565643d302e302662656172696e673d39302e3026616c7469747564653d31342e3133303730323833383237353237342661636375726163793d342e39303030303030393533363734333226626174743d39302e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420393b20414e452d4c58324a204275696c642f485541574549414e452d4c31324a290d0a486f73743a203230332e3230362e3232362e39373a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2021-03-16 08:51:39  WARN: [aec84de9] error - begin 21, end 24, length 3 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-03-16 08:51:39  WARN: [aec84de9] error - begin 21, end 24, length 11 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-03-16 08:51:39  WARN: [aec84de9] error - begin 21, end 24, length 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-03-16 08:51:39  WARN: [aec84de9] error - begin 21, end 24, length 19 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-03-16 08:51:39  WARN: [aec84de9] error - begin 21, end 24, length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-03-16 08:51:39  INFO: [aec84de9] disconnected

The device isn't showing as connected in the interface. Any help?

Regards
Michael

vmedrano 5 years ago

wrong port

: [aec84de9: gps103 < 1.136.105.210] HEX:

must be

 osmand > 10.0.0.29] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2021-03-15 18:10:38  INFO: [e72205a6] id: 181470, time: 2021-03-15 17:52:48, lat: 18.45858, lon: -69.91777, course: 0.0, accuracy: 20433.0
2021-03-15 18:10:38  INFO: [e72205a6: osmand < 10.0.0.29] HEX: 504f5354202f3f69643d3138313437302674696d657374616d703d31363135383435323838266c61743d31382e343538353833373838323036383032266c6f6e3d2d36392e39313737373335343831373035332673706565643d302e302662656172696e673d302e3026616c7469747564653d302e302661636375726163793d32323437332e3026626174743d37392e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420393b204b464d555749204275696c642f505337333138290d0a486f73743a2031302e302e302e39303a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
mbos 5 years ago

I tried but can't figure out what wrong port means, sorry.

Anton Tananaev 5 years ago

Have you changed ports? Because gps103 uses port 5001 by default, not 5055.

vmedrano 5 years ago

in the folder /conf you will find a file name default.xml at the botton you will see osmand.port entry key.

mbos 5 years ago

Thanks very much guys ! - Yes I had forwarded to 5001 as I thought any port from 5001-5099 could listen.

vmedrano 5 years ago

ports are diferent for diferent devices.

mbos 5 years ago

Ok, interesting. That could be a lot of port forwarding, wonder why it's done this way?

vmedrano 5 years ago

there will be a new protocol every day. you cant use same port with all devices, because protocols are diferents. you ca use 80 in an http server because is on protocol, but 443 to ssl because is another protocol.

mbos 5 years ago

I get that, but why couldn't all say non encrypted traffic goto a single port and a software processes decode?

Anton Tananaev 5 years ago

How would the software know which format to expect if you use same port for everything?

vmedrano 5 years ago

Thats IMPOSIBLE, and some are encrypted and two way direcctions.

vmedrano 5 years ago

You should check the source code for answers.

mbos 5 years ago

Yes, I should stick to what I do. Thanks a lot guys, have a great day.

vmedrano 5 years ago

Same for you