location update issue on server map

MAHESHGONDA9 years ago

i removed <!-- PROTOCOL CONFIG --> details in traccar.xml file and running server on
http://106.51.266.251:8090 (my public ip )

traccar client configuraion details are

device number :622854

server address : 106.51.266.251

server port :8090

in Tracar client its showing location update but not showing location on server map

tracker-server logs are

2015-11-26 16:13:23 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:13:23 DEBUG: AsyncSession: 900594179 destroyed: false response context: 689174334
2015-11-26 16:13:23 DEBUG: AsyncSession: 900594179 destroyed: false request context: 1573723267
2015-11-26 16:13:43 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:13:43 DEBUG: AsyncSession: 900594179 destroyed: false response context: 1573723267
2015-11-26 16:13:43 DEBUG: AsyncSession: 900594179 destroyed: false request context: 1158352017
2015-11-26 16:14:03 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:14:03 DEBUG: AsyncSession: 900594179 destroyed: false response context: 1158352017
2015-11-26 16:14:03 DEBUG: AsyncSession: 900594179 destroyed: false request context: 1483089664
2015-11-26 16:14:23 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:14:23 DEBUG: AsyncSession: 900594179 destroyed: false response context: 1483089664
2015-11-26 16:14:23 DEBUG: AsyncSession: 900594179 destroyed: false request context: 445292119
2015-11-26 16:14:43 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:14:43 DEBUG: AsyncSession: 900594179 destroyed: false response context: 445292119
2015-11-26 16:14:43 DEBUG: AsyncSession: 900594179 destroyed: false request context: 44134238
2015-11-26 16:15:03 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:15:03 DEBUG: AsyncSession: 900594179 destroyed: false response context: 44134238
2015-11-26 16:15:03 DEBUG: AsyncSession: 900594179 destroyed: false request context: 882279851
2015-11-26 16:15:23 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:15:23 DEBUG: AsyncSession: 900594179 destroyed: false response context: 882279851
2015-11-26 16:15:23 DEBUG: AsyncSession: 900594179 destroyed: false request context: 102873222
2015-11-26 16:15:43 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:15:43 DEBUG: AsyncSession: 900594179 destroyed: false response context: 102873222
2015-11-26 16:15:44 DEBUG: AsyncSession: 900594179 destroyed: false request context: 265906319
2015-11-26 16:16:04 DEBUG: AsyncSession: 900594179 destroyed: false requestTimeout
2015-11-26 16:16:04 DEBUG: AsyncSession: 900594179 destroyed: false response context: 265906319
2015-11-26 16:16:04 DEBUG: AsyncSession: 900594179 destroyed: false request context: 174034026
Anton Tananaev9 years ago

There are so many issues with your question. I don't even know where to start.

First of all, IP address contains 4 bytes. Maximum value for a byte is 255, so your address can't contain number "266".

Why did you remove "PROTOCOL CONFIG"? You need "osmand" protocol for Traccar Client.

I'm assuming that 8090 is your web interface port. If that's the case, you shouldn't use it for Traccar Client. As I said, Traccar Client uses osmand protocol (port 5055 by default).

MAHESHGONDA9 years ago

Thank you for the reply ,

Sorry IP is http://106.51.216.251:8090

my pc os is Windows 10
using postgreSQL 9.3

i was getting address bind problem so i removed 'PROTOCOL CONFIG' , but now i added 'PROTOCOL CONFIG' back to traccar.xml and started server with no errors .

one question i want to ask is, what port number i have to specify in traccar client app for mobile phones (android) ? is it depends on mobile phones or what ? because in logs i m getting something like this but location is not updated on map !

2015-11-27 09:56:16 DEBUG: [E23CA32F: 5041 < 192.168.1.157] HEX: 474554202f3f69643d3632333535352674696d657374616d703d31343438353434393833266c61743d31332e303131313535266c6f6e3d37372e36343638353333333333333333342673706565643d302e302662656172696e673d38312e373339393937383633373639353326616c7469747564653d3838372e3526626174743d36392e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f312e362e3020284c696e75783b20553b20416e64726f696420342e342e323b20697269735838204275696c642f697269735838290d0a486f73743a203139322e3136382e312e3138323a353034310d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2015-11-27 09:56:31 DEBUG: AsyncSession: 1537695916 destroyed: false requestTimeout
2015-11-27 09:56:31 DEBUG: AsyncSession: 1537695916 destroyed: false response context: 1384934454
2015-11-27 09:56:31 DEBUG: AsyncSession: 1537695916 destroyed: false request context: 1723191588
2015-11-27 09:56:51 DEBUG: AsyncSession: 1537695916 destroyed: false requestTimeout
2015-11-27 09:56:51 DEBUG: AsyncSession: 1537695916 destroyed: false response context: 1723191588
2015-11-27 09:56:51 DEBUG: AsyncSession: 1537695916 destroyed: false request context: 69643342
2015-11-27 09:57:01  INFO: [A1EF8DA8] connected
2015-11-27 09:57:01 DEBUG: [A1EF8DA8: 5041 < 192.168.1.157] HEX: 474554202f3f69643d3632333535352674696d657374616d703d31343438353434393833266c61743d31332e303131313535266c6f6e3d37372e36343638353333333333333333342673706565643d302e302662656172696e673d38312e373339393937383633373639353326616c7469747564653d3838372e3526626174743d36392e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f312e362e3020284c696e75783b20553b20416e64726f696420342e342e323b20697269735838204275696c642f697269735838290d0a486f73743a203139322e3136382e312e3138323a353034310d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2015-11-27 09:57:11 DEBUG: AsyncSession: 1537695916 destroyed: false requestTimeout
2015-11-27 09:57:11 DEBUG: AsyncSession: 1537695916 destroyed: false response context: 69643342
2015-11-27 09:57:11 DEBUG: AsyncSession: 1537695916 destroyed: false request context: 1869704253
2015-11-27 09:57:32 DEBUG: AsyncSession: 1537695916 destroyed: false requestTimeout
2015-11-27 09:57:32 DEBUG: AsyncSession: 1537695916 destroyed: false response context: 1869704253
2015-11-27 09:57:32 DEBUG: AsyncSession: 1537695916 destroyed: false request context: 1978886630
2015-11-27 09:57:46  INFO: [64C8E560] connected
2015-11-27 09:57:46 DEBUG: [64C8E560: 5041 < 192.168.1.157] HEX: 474554202f3f69643d3632333535352674696d657374616d703d31343438353434393833266c61743d31332e303131313535266c6f6e3d37372e36343638353333333333333333342673706565643d302e302662656172696e673d38312e373339393937383633373639353326616c7469747564653d3838372e3526626174743d36392e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f312e362e3020284c696e75783b20553b20416e64726f696420342e342e323b20697269735838204275696c642f697269735838290d0a486f73743a203139322e3136382e312e3138323a353034310d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2015-11-27 09:57:52 DEBUG: AsyncSession: 1537695916 destroyed: false requestTimeout
2015-11-27 09:57:52 DEBUG: AsyncSession: 1537695916 destroyed: false response context: 1978886630
2015-11-27 09:57:52 DEBUG: AsyncSession: 1537695916 destroyed: false request context: 636265480

i used hex-decoder and after that i m not able to find "matching protocol" because that's a python code and i don't know how to run that code (in windows).

Anton Tananaev9 years ago

If you read my previous reply carefully, you'll notice that I already answered your question. Port for Traccar Client is 5055.

MAHESHGONDA9 years ago

Its working ,
thank you for developing this project.