Traccar Server Stop Abrubtly suddenly Version 3.2

jaimzj8 years ago

Dear Anton,

I am using one instance of 3.2 Traccar, Since months it was working fine, Suddenly it stopped, and I restarted service, but Would like to figure out why it went off. so sharing (the wrapper) before the server stopped.

Please do help a bit

INFO   | jvm 1    | 2016/07/16 10:46:17 | Jul 16, 2016 10:46:17 AM org.jboss.netty.util.HashedWheelTimer
INFO   | jvm 1    | 2016/07/16 10:46:17 | WARNING: An exception was thrown by TimerTask.
INFO   | jvm 1    | 2016/07/16 10:46:17 | java.lang.NullPointerException
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at org.traccar.database.ConnectionManager.updateDevice(ConnectionManager.java:84)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at org.traccar.database.ConnectionManager$1.run(ConnectionManager.java:99)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:556)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at org.jboss.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:632)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:369)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 	at java.lang.Thread.run(Thread.java:745)
INFO   | jvm 1    | 2016/07/16 10:46:17 | 
INFO   | jvm 1    | 2016/07/16 10:47:32 | Jul 16, 2016 10:47:32 AM org.jboss.netty.util.HashedWheelTimer
INFO   | jvm 1    | 2016/07/16 10:47:32 | WARNING: An exception was thrown by TimerTask.
INFO   | jvm 1    | 2016/07/16 10:47:32 | java.lang.NullPointerException
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at org.traccar.database.ConnectionManager.updateDevice(ConnectionManager.java:84)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at org.traccar.database.ConnectionManager$1.run(ConnectionManager.java:99)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:556)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at org.jboss.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:632)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:369)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 	at java.lang.Thread.run(Thread.java:745)
INFO   | jvm 1    | 2016/07/16 10:47:32 | 
INFO   | jvm 1    | 2016/07/16 11:40:18 | [Thread-14] INFO org.eclipse.jetty.server.ServerConnector - Stopped ServerConnector@4c5896b7{HTTP/1.1}{0.0.0.0:8067}
INFO   | jvm 1    | 2016/07/16 11:40:18 | [Thread-14] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2134100c{/api,null,UNAVAILABLE}
STATUS | wrapper  | 2016/07/16 11:40:20 | <-- Wrapper Stopped
Anton Tananaev8 years ago

I would recommend to update to the latest version. Also, it doesn't seems like you are using version 3.2 because exception stack points to an empty line.

jaimzj8 years ago

Dear Anton, its 3.1 Sorry, I have not updated to latest, because of major changes between 3.1 and 3.2's DB structure, this slows me down as my front end is custom and i have lots of scripts handling events etc. since then,. I do have plans to upgrade but not sure when. (I am using on different servers, instances version 3.6 already :) )

Any advice as to what could possible have gone wrong here?

Anton Tananaev8 years ago

Version 3.1 is very old and a lot of bugs have been fixed since that release. You don't have to change the database if you are using your own front-end. You just need to update back-end.