Tracker in UK and South America at the same time!

philip.smith8 years ago

Hi,

I have traccar server set up and running on a server, and I have an Lk109 device reporting its position to it on port 5013.

All was well and the trackers posittion was being reported properly, I have not made any changes to the server or tracker set up but now I have the following Problem.

The tracker is in the UK but is now reporting its position in Southern Argentina Lat -34.622220 Lon -425.38705 (-425???)

BUT If I run a route report, the positions, up until the latest one are correct, Lat 50.929408 Lon -2.968387

Last few lines of the tracker-serever.log look good...

2016-11-14 00:53:29 DEBUG: [BEDE0BAE: 5013 < 82.132.216.141] HEX: 24410916147300532814111650557740060025809906001000fffffbffff000f050000003000ea0a000000001e
2016-11-14 00:53:30  INFO: [BEDE0BAE] id: 4109161473, time: 2016-11-14 00:53:28, lat: 50.92957, lon: -2.96832, speed: 1.0, course: 0.0
Anton Tananaev8 years ago
philip.smith8 years ago

Hi Anton, we had a traccar set up and running nicely as follows
nginx reverse proxy to traccar server 3.8. using MySQL
We have a number of Android and Iosclients reporting and several devices using the h02 protocol. all good except for the occasional h02 position errors reported elsewhere.

Today I uninstalled traccar 3.8 and installed traccar 3.10. preserving the config file.

It looks as though the server is working, I am getting posittions from my android client, but I an betting toaster alerts in the web client saying websockets error

Anton Tananaev8 years ago

It means that you have some problem with websocket connection. Possibly some network issue, or maybe you haven't configured proxy for websockets.

philip.smith8 years ago

So I set up nginx as a reverse proxy to fix the websockets issue with 3.8. All was working. I have not touched the nginx config, just replaced traccar 3.8 with 3.10. Are there any changes to the server which would mean I need to update my nginx config?

Anton Tananaev8 years ago

Traccar didn't show any errors for websocket connection on older versions. It doesn't mean that there were no problems.

philip.smith8 years ago

Hmmm... Network setup seems OK for websockets. Positions of trackers are being updated in web client, but on every update from an Android Client I get this in wrapper.log

FINEST|22618/0|Service traccar|17-03-01 03:26:52|[qtp20741083-57] WARN org.eclipse.jetty.servlet.ServletHandler - /api/socket
FINEST|22618/0|Service traccar|17-03-01 03:26:52|java.lang.NullPointerException
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.traccar.api.AsyncSocketServlet$1.createWebSocket(AsyncSocketServlet.java:37)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:166)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.websocket.server.WebSocketServerFactory.acceptWebSocket(WebSocketServerFactory.java:153)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.websocket.servlet.WebSocketServlet.service(WebSocketServlet.java:151)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.Server.handle(Server.java:499)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:258)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
FINEST|22618/0|Service traccar|17-03-01 03:26:52|       at java.lang.Thread.run(Thread.java:745)
Anton Tananaev8 years ago

This log message has nothing to do with receiving data from Traccar Client.

It basically means that some unauthenticated client is trying to connect to the server. Seems like you have some issue with session, if it's actually message from your browser, not some other client.