Server doesn't process all points
There was an issue in the protocol decoder. Fixed it now.
Hello. Thank you for fixing protocol, I'll check it in the field tomorrow.
But I've got 2 more difficulties after making server from sources:
- Wrapper stopped with errors:
STATUS | wrapper | 2016/08/29 00:29:18 | --> Wrapper Started as Service STATUS | wrapper | 2016/08/29 00:29:18 | Java Service Wrapper Community Edition 64-bit 3.5.28 STATUS | wrapper | 2016/08/29 00:29:18 | Copyright (C) 1999-2016 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2016/08/29 00:29:18 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2016/08/29 00:29:18 | STATUS | wrapper | 2016/08/29 00:29:18 | Launching a JVM... INFO | jvm 1 | 2016/08/29 00:29:18 | WrapperManager: Initializing... INFO | jvm 1 | 2016/08/29 00:29:20 | [WrapperSimpleAppMain] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started. INFO | jvm 1 | 2016/08/29 00:29:24 | INFO 8/29/16 12:29 AM: liquibase: Clearing database change log checksums INFO | jvm 1 | 2016/08/29 00:29:25 | INFO 8/29/16 12:29 AM: liquibase: Successfully acquired change log lock INFO | jvm 1 | 2016/08/29 00:29:25 | INFO 8/29/16 12:29 AM: liquibase: Successfully released change log lock INFO | jvm 1 | 2016/08/29 00:29:25 | INFO 8/29/16 12:29 AM: liquibase: Successfully acquired change log lock INFO | jvm 1 | 2016/08/29 00:29:32 | INFO 8/29/16 12:29 AM: liquibase: Reading from PUBLIC.DATABASECHANGELOG INFO | jvm 1 | 2016/08/29 00:29:32 | INFO 8/29/16 12:29 AM: liquibase: Reading from PUBLIC.DATABASECHANGELOG INFO | jvm 1 | 2016/08/29 00:29:33 | INFO 8/29/16 12:29 AM: liquibase: Successfully released change log lock INFO | jvm 1 | 2016/08/29 00:29:33 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.util.log - Logging initialized @15076ms INFO | jvm 1 | 2016/08/29 00:29:36 | WrapperSimpleApp: INFO | jvm 1 | 2016/08/29 00:29:36 | WrapperSimpleApp Error: Encountered an error running main: INFO | jvm 1 | 2016/08/29 00:29:36 | WrapperSimpleApp Error: org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:5005 INFO | jvm 1 | 2016/08/29 00:29:36 | WrapperSimpleApp Error: at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
<some INFO strings>
STATUS | wrapper | 2016/08/29 00:29:38 | <-- Wrapper Stopped
I've disabled 5005 port in config and wrapper started ok. What is wrong, if previous version of server (downloaded from the site) worked fine?
- Now I have this warning in server log:
2016-08-29 01:08:12 DEBUG: [033883CB: 5057 < 213.87.163.230] HEX: 24474d323231383633303731303134343435343034543238303831363232303830304e3535343831353937453033373239323539343030303235343830353330323937230d 2016-08-29 01:08:12 WARN: Parameter "#3" is not set; SQL statement: UPDATE devices SET status = ?, lastUpdate = ?, motion = ? WHERE id = ?; [90012-192] - JdbcSQLException (... < QueryBuilder:443 < DataManager:218 < DeviceManager:177 < ...) 2016-08-29 01:08:12 INFO: [033883CB] id: 863071014445404, time: 2016-08-29 01:08:00, lat: 55.80266, lon: 37.48766, speed: 0.0, course: 254.0
What is "Parameter "#3" and how can I get rid of this warning?
Thank you.
It's already fixed.
Status and motion parameters have been removed.
Hello.
Today I've tried GPS Marker M130 to track my way. But not all points were processed by Traccar Server. Here is part of tracker-server.log:
There are a lot of DEBUG strings, but not all of them are followed by INFO strings. Tracker ID is registered on server. Please help me to find out what is wrong.