Traccar doesnt track. I dont undestand the errors.

ybru6 years ago

Hi Anton!

I need help again. I did reinstall various Traccar version but I can't make it to work any of them, I have errors in all of them. My OS is old (windows server 2003) and when something goes wrong... is very hard to make it work again.
Now I have running the same old version that I had before the internet provider crashed some days ago, but I'm doing something wrong and I don't know what it is. I think is something about the JRE (7) version but, I'm not sure.
I apreciate your time.

Here is the wrapper´s log:

WARNING|wrapper|Service traccar|18-11-25 14:08:32|YAJSW: yajsw-beta-12.07
WARNING|wrapper|Service traccar|18-11-25 14:08:32|OS   : Windows 2003/5.2/x86
WARNING|wrapper|Service traccar|18-11-25 14:08:32|JVM  : Oracle Corporation/1.7.0_80/C:\Archivos de programa\Java\jre7/32
INFO|wrapper|Service traccar|18-11-25 14:08:32|start delay: 0
INFO|wrapper|Service traccar|18-11-25 14:08:32|started process with pid 1236
INFO|1236/0|Service traccar|18-11-25 14:08:33|[INFO] StandardFileSystemManager - Using "C:\WINDOWS\TEMP\vfs_cache" as temporary files store.
INFO|1236/0|Service traccar|18-11-25 14:08:33|!! WARNING !! Windows JDK7 should set -Djava.net.preferIPv4Stack=true (see java bug 7179799 )
INFO|1236/0|Service traccar|18-11-25 14:08:33|[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started.
INFO|1236/0|Service traccar|18-11-25 14:08:34|INFO 11/25/18 2:08 PM: liquibase: Clearing database change log checksums
INFO|1236/0|Service traccar|18-11-25 14:08:34|INFO 11/25/18 2:08 PM: liquibase: Successfully acquired change log lock
INFO|1236/0|Service traccar|18-11-25 14:08:34|INFO 11/25/18 2:08 PM: liquibase: Successfully released change log lock
INFO|1236/0|Service traccar|18-11-25 14:08:34|INFO 11/25/18 2:08 PM: liquibase: Successfully acquired change log lock
INFO|1236/0|Service traccar|18-11-25 14:08:35|INFO 11/25/18 2:08 PM: liquibase: Reading from PUBLIC.DATABASECHANGELOG
INFO|1236/0|Service traccar|18-11-25 14:08:36|INFO 11/25/18 2:08 PM: liquibase: Reading from PUBLIC.DATABASECHANGELOG
INFO|1236/0|Service traccar|18-11-25 14:08:36|INFO 11/25/18 2:08 PM: liquibase: ./schema/changelog-master.xml: changelog-3.8::changelog-3.8-dropuniquetoken::author: Change set changelog-3.8::changelog-3.8-dropuniquetoken::author failed, but failOnError was false.  Error: Constraint "UK_USER_TOKEN" not found; SQL statement:
INFO|1236/0|Service traccar|18-11-25 14:08:36|ALTER TABLE PUBLIC.users DROP CONSTRAINT uk_user_token [90057-193] [Failed SQL: ALTER TABLE PUBLIC.users DROP CONSTRAINT uk_user_token]
INFO|1236/0|Service traccar|18-11-25 14:08:36|INFO 11/25/18 2:08 PM: liquibase: Successfully released change log lock
INFO|1236/0|Service traccar|18-11-25 14:08:36|[main] INFO org.eclipse.jetty.util.log - Logging initialized @3344ms
INFO|1236/0|Service traccar|18-11-25 14:08:36|[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.19.v20160908
INFO|1236/0|Service traccar|18-11-25 14:08:37|[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@1332203{/api,null,AVAILABLE}
INFO|1236/0|Service traccar|18-11-25 14:08:37|[main] INFO org.eclipse.jetty.server.ServerConnector - Started ServerConnector@195d3e9{HTTP/1.1}{0.0.0.0:4990}
INFO|1236/0|Service traccar|18-11-25 14:08:37|[main] INFO org.eclipse.jetty.server.Server - Started @5156ms
Anton Tananaev6 years ago

Why are you using Java 7? It's no longer supported by anyone and you should upgrade as soon as possible.

ybru6 years ago

I can't upgrade OS until january and I can't install java 8 in server 2003 because is not compatible... But the Tracccar was working fine until some days ago. I'm triying to make it work for this months, until I can upgrade the server

Anton Tananaev6 years ago

It should be compatible. If Oracle version is not compatible, try some alternative.

ybru6 years ago

Hi Anton!

I did what you just suggest: I found a way to install jre 8, so I did it and reinstalled Traccar too, but the system still doesn't track the devices. I saved a log from some days ago, before the internet provider crash, and I when compare the old wrapper´s log and thenew one and I can't find any differences.

I really apreceate your time!

2018-11-27 00:11:25  INFO: Operating system name: Windows 2003 version: 5.2 architecture: x86
2018-11-27 00:11:25  INFO: Java runtime name: Java HotSpot(TM) Client VM vendor: Oracle Corporation version: 25.11-b03
2018-11-27 00:11:25  INFO: Memory limit heap: 247mb non-heap: 0mb
2018-11-27 00:11:25  INFO: Character encoding: UTF-8 charset: UTF-8
2018-11-27 00:11:25  INFO: Version: 3.9-SNAPSHOT
2018-11-27 00:11:39  INFO: Starting server...
2018-11-27 00:12:43  INFO: Shutting down server...
2018-11-27 00:14:04  INFO: Operating system name: Windows 2003 version: 5.2 architecture: x86
2018-11-27 00:14:04  INFO: Java runtime name: Java HotSpot(TM) Client VM vendor: Oracle Corporation version: 25.11-b03
2018-11-27 00:14:04  INFO: Memory limit heap: 247mb non-heap: 0mb
2018-11-27 00:14:04  INFO: Character encoding: UTF-8 charset: UTF-8
2018-11-27 00:14:04  INFO: Version: 3.9-SNAPSHOT
2018-11-27 00:14:07  INFO: Starting server...
WARNING|wrapper|Service traccar|18-11-27 00:14:02|YAJSW: yajsw-beta-12.07
WARNING|wrapper|Service traccar|18-11-27 00:14:02|OS   : Windows 2003/5.2/x86
WARNING|wrapper|Service traccar|18-11-27 00:14:02|JVM  : Oracle Corporation/1.8.0_11/C:\Archivos de programa\Java\jre8/32
INFO|wrapper|Service traccar|18-11-27 00:14:02|start delay: 0
INFO|wrapper|Service traccar|18-11-27 00:14:03|started process with pid 3336
INFO|3336/0|Service traccar|18-11-27 00:14:03|[INFO] StandardFileSystemManager - Using "C:\WINDOWS\TEMP\vfs_cache" as temporary files store.
INFO|3336/0|Service traccar|18-11-27 00:14:04|[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started.
INFO|3336/0|Service traccar|18-11-27 00:14:05|INFO 11/27/18 12:14 AM: liquibase: Clearing database change log checksums
INFO|3336/0|Service traccar|18-11-27 00:14:05|INFO 11/27/18 12:14 AM: liquibase: Successfully acquired change log lock
INFO|3336/0|Service traccar|18-11-27 00:14:05|INFO 11/27/18 12:14 AM: liquibase: Successfully released change log lock
INFO|3336/0|Service traccar|18-11-27 00:14:05|INFO 11/27/18 12:14 AM: liquibase: Successfully acquired change log lock
INFO|3336/0|Service traccar|18-11-27 00:14:06|INFO 11/27/18 12:14 AM: liquibase: Reading from PUBLIC.DATABASECHANGELOG
INFO|3336/0|Service traccar|18-11-27 00:14:06|INFO 11/27/18 12:14 AM: liquibase: Reading from PUBLIC.DATABASECHANGELOG
INFO|3336/0|Service traccar|18-11-27 00:14:06|INFO 11/27/18 12:14 AM: liquibase: ./schema/changelog-master.xml: changelog-3.8::changelog-3.8-dropuniquetoken::author: Change set changelog-3.8::changelog-3.8-dropuniquetoken::author failed, but failOnError was false.  Error: Constraint "UK_USER_TOKEN" not found; SQL statement:
INFO|3336/0|Service traccar|18-11-27 00:14:06|ALTER TABLE PUBLIC.users DROP CONSTRAINT uk_user_token [90057-193] [Failed SQL: ALTER TABLE PUBLIC.users DROP CONSTRAINT uk_user_token]
INFO|3336/0|Service traccar|18-11-27 00:14:06|INFO 11/27/18 12:14 AM: liquibase: Successfully released change log lock
INFO|3336/0|Service traccar|18-11-27 00:14:06|[main] INFO org.eclipse.jetty.util.log - Logging initialized @3813ms
INFO|3336/0|Service traccar|18-11-27 00:14:07|[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.19.v20160908
INFO|3336/0|Service traccar|18-11-27 00:14:08|[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@aa3bfc{/api,null,AVAILABLE}
INFO|3336/0|Service traccar|18-11-27 00:14:08|[main] INFO org.eclipse.jetty.server.ServerConnector - Started ServerConnector@a8fcf3{HTTP/1.1}{0.0.0.0:4990}
INFO|3336/0|Service traccar|18-11-27 00:14:08|[main] INFO org.eclipse.jetty.server.Server - Started @5592ms
Anton Tananaev6 years ago

Logs look fine. Traccar is running.

ybru6 years ago

Is it possible that some cache file could be involved? I'm looking the screen but no devices appears in it

Anton Tananaev6 years ago

No, it has nothing to do with any caches.

ybru6 years ago

Ok. I'll keep searching the problem. When I find it, I'll post results for future references.
Thank you so much Anton!
BR