Updated Version for Synology
I downloaded the latest traccar-other-3.14.zip and copied those files over the existing ones except for the config file.
I copied new setting from config to the excisting config file and started the Traccar from DSM.
It is a few try and error. You might save to old database and traccar files to revert back to 3.7-011
Note that Synology package is not an official Traccar project, so you need to ask author of the package for information on updates.
Thank you both for your quick replies.
@Eddy:
I will try do it just you described, once I got spare time.
Kind regards
Talha
Hi again,
@Eddy : so far I have done what you described, however traccar is stuck on the loading screen. the circle is just circleling around.
i assume its some problem with the config file.
what i did is basically adding the new codelines to the traccar/target/conf/traccar file from the conf/default file
any clue where my mistake could be?
Basically you could use the config files from the downloaded from the traccar site ( The 'other' files).
Change the ports to 55000 etc....
Keep in mind that the synology config file might need the ';' at the end of every sql statement in the config file.
I also added a lot of sql statements and added a mail.smtp config and a few other.
Look at the config description on the traccar site.
Keep in mind that you add the 3 synology lines at the end of the condig file.
In my case:
<!-- Synology Changes -->
<entry key='web.path'>/volume1/@appstore/traccar/web</entry>
<entry key='logger.file'>/volume1/@appstore/traccar/logs/tracker-server.log</entry>
<entry key='database.changelog'>/volume1/@appstore/traccar/schema/changelog-master.xml</entry>Hi again,
thanks for you update again.
I did just the way you explained.
unfortunately it did not work out.
hence i tried to restore the backup but ended with the same problem of the grey background and no login screen.
even after a deinstallation and new installation of the traccar synology app the problem was not fixed.
has anyone a clue why this might have happened?
You should check server logs and browser console.
You should stop the traccar (DSM 6.0 and 6.1) with: synoservicecfg --stop pkgctl-traccar
Check if is stopped with: synoservicecfg --status pkgctl-traccar
Delete alle the log files in: /volume1/@appstore/traccar/logs/
Start the traccar with synoservicecfg --start pkgctl-traccar
Now check the log files, first the wrapper.log ,then the traccar-server.log for errors.
Mostly the errors are self-explainable, otherwise post the error(s) here.
Hi again,
after several attempts I can't find a solution:
I did as you told me to do.
however the application does not start. at least the login screen does not appear.
basically the "loading" circle is circling around.
the
tracker-server.log goes:
2017-10-03 13:57:11 INFO: Operating system name: Linux version: 3.10.102 architecture: amd64
2017-10-03 13:57:11 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Oracle Corporation version: 24.131-b00
2017-10-03 13:57:11 INFO: Memory limit heap: 592mb non-heap: 214mb
2017-10-03 13:57:11 INFO: Character encoding: UTF-8 charset: UTF-8
2017-10-03 13:57:11 INFO: Version: 3.14-SNAPSHOT
2017-10-03 13:57:19 WARN: Table 'traccar.server' doesn't exist - MySQLSyntaxErrorException (... < QueryBuilder:421 < *:305 < DataManager:358 < PermissionsManager:92 < ...)
2017-10-03 13:57:20 INFO: Starting server...the wrapper.log goes:
STATUS | wrapper | 2017/10/03 13:57:10 | --> Wrapper Started as Daemon
STATUS | wrapper | 2017/10/03 13:57:10 | Java Service Wrapper Community Edition 64-bit 3.5.30
STATUS | wrapper | 2017/10/03 13:57:10 | Copyright (C) 1999-2016 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2017/10/03 13:57:10 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2017/10/03 13:57:10 |
STATUS | wrapper | 2017/10/03 13:57:10 | Launching a JVM...
INFO | jvm 1 | 2017/10/03 13:57:10 | WrapperManager: Initializing...
INFO | jvm 1 | 2017/10/03 13:57:12 | [WrapperSimpleAppMain] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
INFO | jvm 1 | 2017/10/03 13:57:12 | [WrapperSimpleAppMain] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
INFO | jvm 1 | 2017/10/03 13:57:14 | INFO 10/3/17 1:57 PM: liquibase: Clearing database change log checksums
INFO | jvm 1 | 2017/10/03 13:57:14 | INFO 10/3/17 1:57 PM: liquibase: Successfully acquired change log lock
INFO | jvm 1 | 2017/10/03 13:57:14 | INFO 10/3/17 1:57 PM: liquibase: Successfully released change log lock
INFO | jvm 1 | 2017/10/03 13:57:14 | INFO 10/3/17 1:57 PM: liquibase: Successfully acquired change log lock
INFO | jvm 1 | 2017/10/03 13:57:18 | INFO 10/3/17 1:57 PM: liquibase: Reading from traccar.DATABASECHANGELOG
INFO | jvm 1 | 2017/10/03 13:57:18 | INFO 10/3/17 1:57 PM: liquibase: Reading from traccar.DATABASECHANGELOG
INFO | jvm 1 | 2017/10/03 13:57:18 | INFO 10/3/17 1:57 PM: liquibase: /volume3/@appstore/traccar/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: Can't DROP 'uk_user_token'; check that column/key exists [Failed SQL: ALTER TABLE traccar.users DROP KEY uk_user_token]
INFO | jvm 1 | 2017/10/03 13:57:18 | INFO 10/3/17 1:57 PM: liquibase: Successfully released change log lock
INFO | jvm 1 | 2017/10/03 13:57:19 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.util.log - Logging initialized @8532ms
INFO | jvm 1 | 2017/10/03 13:57:20 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.Server - jetty-9.2.22.v20170606
INFO | jvm 1 | 2017/10/03 13:57:24 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@7247ec8a{/api,null,AVAILABLE}
INFO | jvm 1 | 2017/10/03 13:57:24 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.t.w.@41512c1d{/,null,AVAILABLE}
INFO | jvm 1 | 2017/10/03 13:57:24 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.ServerConnector - Started ServerConnector@32fdd97c{HTTP/1.1}{0.0.0.0:55000}
INFO | jvm 1 | 2017/10/03 13:57:24 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.Server - Started @13487mswhat am I missing.
by the way:
when it did not work out the first time i tried to reinstall the "oringinal" synology version. that did not workout either. even with the backup files.
any help would be much appreciated.
kind regards.
talha
The version of Traccar in Synology is 3.7
After the uninstall of this original Synology version the traccar database should be remove too.
Then the original Synology traccar should work after a fresh install.
Then stop traccar in DSM.
Copy the new files from 3.14 over the the Synology files except for the config files because Synology uses ports 55000 and upwards.
Change the config file to your own settings.
Now start Traccar from DSM.
The wrapper know your version en upgrades the database step by step by processing the schema files in /volume1/@appstore/traccar/schema
until the database is up to version 3.14
You get an error because in the changelog-3.8.xml is at the end the 'DROP uk_user_token'
In version 3.7 that is normaly available, but in your version of the traccar database it is not. Proberly already removed by a previous action.
Hi again,
I did as you described Eddy.
The new Version did not workout, howevet the old version did. :-)
at least I got a working version.
thank you for your help and support tough.
best regards
talha
Hi,
I searched for an answer but could not find one in the forum,
Hence my question:
i have traccar installed on my synology nas and it works fine.
however i have noticed it is not the up to date version.
It's Version 3.7-011
Is there going to be an update on the cphub version aswell?
I am waiting eagerly on an update, as the GPS devices sometimes have location problems sending locations sometimes a frw thousand kilometers away from its real location.
Kind regards
Talha