Everything seems OK as far as I can see. The only problem is that JVM is slow. How many devices do you have and what are the hardware specs of the server?
our server is
Intel Core i7-920 Quad Core
24 GB DDR3 RAM
2x 1500 GB SATA II HDD
We have about 220 GT06 on our system and total about 400
Did i miss someting do we need to recompile when we change the conf file ?
It seams that no positions is coming to our system
Michael
You don't need to re-compile when you change config.
I suspect you are reaching connection limit (around 1000 by default on Linux).
No I just enabled logs and got this
2015-07-27 13:14:24 INFO: Version: 3.0-SNAPSHOT
2015-07-27 13:14:25 DEBUG: [A22807BB: 37593 <- 94.144.63.93] - HEX: 78780d0103588990509042780000ee4e0d0a
2015-07-27 13:14:25 DEBUG: [71A46AF0: 37593 <- 94.144.63.104] - HEX: 78780d010358899051299629000384b50d0a
2015-07-27 13:14:25 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:25 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:25 DEBUG: [7417631A: 37593 <- 80.62.116.100] - HEX: 78780d010358899054557866000a39490d0a
2015-07-27 13:14:25 DEBUG: [B1A4031D: 37593 <- 80.62.116.19] - HEX: 78780d01035889905455799900037ec00d0a
2015-07-27 13:14:25 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:25 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:26 DEBUG: [602C4914: 37593 <- 80.62.117.57] - HEX: 78780d0103588990545579730003041b0d0a
2015-07-27 13:14:26 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:26 DEBUG: [F831F197: 37593 <- 80.62.117.90] - HEX: 78780d010358899051724964002dcdcf0d0a
2015-07-27 13:14:26 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:27 DEBUG: [D480548C: 37593 <- 94.144.63.104] - HEX: 78780d010358899051294877000073ec0d0a
2015-07-27 13:14:27 WARN: '89314404000054159935' in column '1' is outside valid range for the datatype BIGINT. - MySQLDataException (... < QueryBuilder.java:343 < *:339 < *:389 < $
2015-07-27 13:14:27 DEBUG: [4AD07A80: 37593 <- 80.62.116.7] - HEX: 78780d010358899051720673002f43030d0a
We are on a enterprise version
Can I see your config?
I just remove the devices we dont use
?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>
<properties>
<!-- SERVER CONFIG -->
<entry key='web.enable'>false</entry>
<entry key='geocoder.enable'>false</entry>
<entry key='geocoder.type'>google</entry>
<entry key='logger.enable'>true</entry>
<entry key='logger.level'>all</entry>
<entry key='logger.file'>/opt/traccar/logs/tracker-server.log</entry>
<!-- DATABASE CONFIG -->
<entry key='database.driver'>com.mysql.jdbc.Driver</entry>
<entry key='database.url'>jdbc:mysql://localhost:3306/gts?allowMultiQueries=true</entry>
<entry key='database.user'>root</entry>
<entry key='database.password'>****</entry>
<entry key='database.selectDevicesAll'>
SELECT imeiNumber AS id, imeiNumber AS uniqueId FROM Device WHERE imeiNumber REGEXP '^[0-9]+$';
</entry>
<entry key='database.insertPosition'>
START TRANSACTION;
UPDATE Device SET lastValidLatitude = :latitude, lastValidLongitude = :longitude, lastGPSTimestamp = UNIX_TIMESTAMP(:time), lastUpdateTime = UNIX_TIMESTAMP(NOW()) WHERE$
SELECT @accountID := accountID, @deviceID := deviceID FROM Device WHERE imeiNumber = RIGHT(CONCAT('000000000000000', :deviceId), 15);
INSERT INTO EventData (accountID, deviceID, timestamp, statusCode, latitude, longitude, speedKPH, heading, altitude, rawData, creationTime, address)
VALUES (@accountID, @deviceID, UNIX_TIMESTAMP(:time), 0, :latitude, :longitude, :speed * 1.852, :course, :altitude, '', UNIX_TIMESTAMP(NOW()), :address);
COMMIT;
</entry>
<!-- PROTOCOL CONFIG -->
<entry key='detector.port'>5000</entry>
<entry key='gt06.port'>37593</entry>
</properties>
please delete 1094 as my password is there ;-(
Looks like you have an imeiNumber that is way too long.
What's the output of the following query:
SELECT imeiNumber AS id, imeiNumber AS uniqueId FROM Device WHERE imeiNumber REGEXP ‘^[0-9]+$';
Hi Anton
Where do you want me to input this?
In the script our direct into mysql?
If I run it in command line I get no result? maybe i am doing someting wrong!
You need to run it in your MySQL database.
I get nothing?
We use uniqueId as imeiNumber in our DB!!!
Your IMEI number is too long - 89314404000054159935.
On GTS IMEI number= IMEI number from Simcard not from the Device
The device IMEI number is only in UniqueID
Hi My log file says this?
I am on a ubuntu system where we run GTS enterprise - but want to use carrack as a device server for GT06 - but after install we got this
STATUS | wrapper | 2015/07/26 21:02:21 | --> Wrapper Started as Daemon
STATUS | wrapper | 2015/07/26 21:02:21 | Java Service Wrapper Community Edition 64-bit 3.5.26
STATUS | wrapper | 2015/07/26 21:02:21 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2015/07/26 21:02:21 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2015/07/26 21:02:21 |
STATUS | wrapper | 2015/07/26 21:02:22 | Launching a JVM...
INFO | jvm 1 | 2015/07/26 21:02:22 | WrapperManager: Initializing...
INFO | jvm 1 | 2015/07/26 21:02:26 | log4j:WARN No appenders could be found for logger (com.mchange.v2.log.MLog).
INFO | jvm 1 | 2015/07/26 21:02:26 | log4j:WARN Please initialize the log4j system properly.
INFO | jvm 1 | 2015/07/26 21:02:26 | log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
STATUS | wrapper | 2015/07/26 21:52:29 | JVM appears hung: Timed out waiting for signal from JVM. Restarting JVM.
ERROR | wrapper | 2015/07/26 21:53:03 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2015/07/26 21:53:03 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2015/07/26 21:53:03 | JVM received a signal SIGKILL (9).
STATUS | wrapper | 2015/07/26 21:53:03 | JVM process is gone.
STATUS | wrapper | 2015/07/26 21:53:03 | JVM exited after being requested to terminate.
STATUS | wrapper | 2015/07/26 21:53:08 | Launching a JVM...
INFO | jvm 2 | 2015/07/26 21:53:08 | WrapperManager: Initializing...
INFO | jvm 2 | 2015/07/26 21:53:09 | log4j:WARN No appenders could be found for logger (com.mchange.v2.log.MLog).
INFO | jvm 2 | 2015/07/26 21:53:09 | log4j:WARN Please initialize the log4j system properly.
INFO | jvm 2 | 2015/07/26 21:53:09 | log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 129 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 125 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 121 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 117 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 112 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 108 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 104 seconds to respond.
STATUS | wrapper | 2015/07/26 22:00:01 | Pinging the JVM took 100 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 256 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 252 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 248 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 244 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 240 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 236 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 232 seconds to respond.
STATUS | wrapper | 2015/07/26 22:36:46 | Pinging the JVM took 228 seconds to respond.
regards Michael