About 3.4 version upgrade
The cleanest way to do update is to completely remove version 3.3 first and then install version 3.4. Installing 3.4 on top of an old version should work as well, but it might leave some old files.
Obviously you should keep database if you want to save data.
Dear Anton,
I have stopped 3.3 version,
I have backup my config file (traccar.xml) (for re use MySql DB)
I have removed 3.3 server.
I have installed 3.4 server.
I have copied my config file to conf directory.
I have started server without problem :
Starting traccar... Waiting for traccar...... running: PID:4553
But no way to acceed to my site (www.xxxx.xx/8082)
When i m see my logs, I read this values :
Do you have a idea ?
STATUS | wrapper | 2016/03/08 15:41:24 | --> Wrapper Started as Daemon STATUS | wrapper | 2016/03/08 15:41:24 | Java Service Wrapper Community Edition 64-bit 3.5.28 STATUS | wrapper | 2016/03/08 15:41:24 | Copyright (C) 1999-2016 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2016/03/08 15:41:24 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2016/03/08 15:41:24 | STATUS | wrapper | 2016/03/08 15:41:25 | Launching a JVM... INFO | jvm 1 | 2016/03/08 15:41:25 | WrapperManager: Initializing... INFO | jvm 1 | 2016/03/08 15:41:27 | [MLog-Init-Reporter] INFO com.mchange.v2.log.MLog - MLog clients using slf4j logging. INFO | jvm 1 | 2016/03/08 15:41:27 | [WrapperSimpleAppMain] INFO com.mchange.v2.c3p0.C3P0Registry - Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -0800; debug? true; trace: 10] INFO | jvm 1 | 2016/03/08 15:41:31 | INFO 3/8/16 3:41 PM: liquibase: Clearing database change log checksums INFO | jvm 1 | 2016/03/08 15:41:31 | INFO 3/8/16 3:41 PM: liquibase: Successfully acquired change log lock INFO | jvm 1 | 2016/03/08 15:41:31 | INFO 3/8/16 3:41 PM: liquibase: Successfully released change log lock INFO | jvm 1 | 2016/03/08 15:41:31 | INFO 3/8/16 3:41 PM: liquibase: Successfully acquired change log lock INFO | jvm 1 | 2016/03/08 15:41:32 | INFO 3/8/16 3:41 PM: liquibase: Successfully released change log lock INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp: INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: Encountered an error running main: INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: liquibase.exception.ChangeLogParseException: /opt/traccar/data/db.changelog-master.xml does not exist INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at liquibase.parser.core.xml.XMLChangeLogSAXParser.parseToNode(XMLChangeLogSAXParser.java:100) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at liquibase.parser.core.xml.AbstractChangeLogParser.parse(AbstractChangeLogParser.java:17) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:227) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at liquibase.Liquibase.update(Liquibase.java:202) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at liquibase.Liquibase.update(Liquibase.java:192) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at liquibase.Liquibase.update(Liquibase.java:188) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at org.traccar.database.DataManager.initDatabaseSchema(DataManager.java:168) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at org.traccar.database.DataManager.<init>(DataManager.java:65) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at org.traccar.Context.init(Context.java:121) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at org.traccar.Main.main(Main.java:29) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at java.lang.reflect.Method.invoke(Method.java:606) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325) INFO | jvm 1 | 2016/03/08 15:41:32 | WrapperSimpleApp Error: at java.lang.Thread.run(Thread.java:745) STATUS | wrapper | 2016/03/08 15:41:34 | <-- Wrapper Stopped
You can't just copy over the config. There were some changes in the config file. Error message indicates that "database.changelog" parameter is incorrect.
Dear Anton,
You're right, as usual :-).
It's ok now.
Hi
To upgarde my server from 3.2 to 3.4 i followed these steps:
- stop traccar daemon
- remove old version : /opt/traccar/bin/traccar remove & rm -R /opt/traccar
- install new vesrion successfully ./traccar.run
when i try to start traccar i have this error:
root@HP-Compaq# /opt/traccar/bin/traccar start
Starting traccar...
/opt/traccar/bin/./wrapper: 1: /opt/traccar/bin/./wrapper: Syntax error: word unexpected (expecting ")")
Waiting for traccar..................
WARNING: traccar may have failed to start.
Regarding mysql DB. I ask if the upgrade of traccar has effect on DB (data, schema of tables,..), and what's the recommanded command to make a backup of DB.
BR
"wrapper" is a binary executable file. Not sure why it's complaining about some character.
Any idea to resolve this serious issue.
The problem that this issue is produced when i tried to install from scratch my traccar server for both versions 3.2 and 3.3 also.
How to clean old traccar installations? remove command is enough to do that?
To remove old version:
https://www.traccar.org/linux/
If you want I can take a look at the server. Send me details by email (address on support page).
Thank you Master
Finally i identified the source of issue, but i don't have really an interpretation of this behavior.
in fact, before removing old version "rm -R /opt/traccar" i made a backup of installation folder "mv /opt/traccar /opt/traccar3.2".
so to resolve the problem i have renamed this folder and reinstall new version.
I have same/similar problem...I needed seconds from the api/positions so after noticing in another thread that 3.3 had that problem, and that it was fixed I first tried the traccar-server.jar from that thread.
I have difficulty start/stopping traccar...had this problem weeks ago as well with 3.3: ran fine, the I stopped it for some reason, failed to get it to start, and then it magically started working again.
Now today I needed to stop it (of course), and it would not restart with the new traccar-server.jar, or with my original 3.3 version either.
So I upgraded to 3.4 according to instructions. The server will not start
my wrapper output is below.
I have some sort of intermittent JVM problem...but intermittent is funny in the SW business.
STATUS | wrapper | 2016/03/23 13:02:51 | --> Wrapper Started as Daemon STATUS | wrapper | 2016/03/23 13:02:51 | Java Service Wrapper Community Edition 64-bit 3.5.28 STATUS | wrapper | 2016/03/23 13:02:51 | Copyright (C) 1999-2016 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2016/03/23 13:02:51 | http://wrapper.tanukisoftware.com STATUS | wrapper | 2016/03/23 13:02:51 | STATUS | wrapper | 2016/03/23 13:02:51 | Launching a JVM... INFO | jvm 1 | 2016/03/23 13:02:52 | WrapperManager: Initializing... INFO | jvm 1 | 2016/03/23 13:02:53 | [MLog-Init-Reporter] INFO com.mchange.v2.log.MLog - MLog clients using slf4j logging. INFO | jvm 1 | 2016/03/23 13:02:53 | [WrapperSimpleAppMain] INFO com.mchange.v2.c3p0.C3P0Registry - Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -00; debug? true; trace: 10] STATUS | wrapper | 2016/03/23 13:02:54 | JVM received a signal UNKNOWN (6). INFO | jvm 1 | 2016/03/23 13:02:54 | INFO 3/23/16 1:02 PM: liquibase: Clearing database change log checksums INFO | jvm 1 | 2016/03/23 13:02:54 | java: res_query.c:262: __libc_res_nquery: Assertion ` (hp != ((void *)0)) && (hp2 != ((void *)0))' failed. STATUS | wrapper | 2016/03/23 13:02:54 | JVM process is gone. ERROR | wrapper | 2016/03/23 13:02:54 | JVM exited while starting the application. STATUS | wrapper | 2016/03/23 13:02:58 | Launching a JVM... INFO | jvm 2 | 2016/03/23 13:02:58 | WrapperManager: Initializing... INFO | jvm 2 | 2016/03/23 13:02:59 | [MLog-Init-Reporter] INFO com.mchange.v2.log.MLog - MLog clients using slf4j logging. INFO | jvm 2 | 2016/03/23 13:02:59 | [WrapperSimpleAppMain] INFO com.mchange.v2.c3p0.C3P0Registry - Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -00; debug? true; trace: 10] STATUS | wrapper | 2016/03/23 13:03:00 | JVM received a signal UNKNOWN (6). INFO | jvm 2 | 2016/03/23 13:03:00 | INFO 3/23/16 1:03 PM: liquibase: Clearing database change log checksums INFO | jvm 2 | 2016/03/23 13:03:00 | java: res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) && (hp2 != ((void *)0))' failed. STATUS | wrapper | 2016/03/23 13:03:00 | JVM process is gone. ERROR | wrapper | 2016/03/23 13:03:00 | JVM exited while starting the application. STATUS | wrapper | 2016/03/23 13:03:04 | Launching a JVM... INFO | jvm 3 | 2016/03/23 13:03:05 | WrapperManager: Initializing... INFO | jvm 3 | 2016/03/23 13:03:05 | [MLog-Init-Reporter] INFO com.mchange.v2.log.MLog - MLog clients using slf4j logging. INFO | jvm 3 | 2016/03/23 13:03:05 | [WrapperSimpleAppMain] INFO com.mchange.v2.c3p0.C3P0Registry - Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -00; debug? true; trace: 10] INFO | jvm 3 | 2016/03/23 13:03:06 | INFO 3/23/16 1:03 PM: liquibase: Clearing database change log checksums STATUS | wrapper | 2016/03/23 13:03:06 | JVM received a signal UNKNOWN (6). INFO | jvm 3 | 2016/03/23 13:03:06 | java: res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) && (hp2 != ((void *)0))' failed. STATUS | wrapper | 2016/03/23 13:03:06 | JVM process is gone. ERROR | wrapper | 2016/03/23 13:03:06 | JVM exited while starting the application. STATUS | wrapper | 2016/03/23 13:03:11 | Launching a JVM... INFO | jvm 4 | 2016/03/23 13:03:11 | WrapperManager: Initializing... INFO | jvm 4 | 2016/03/23 13:03:11 | [MLog-Init-Reporter] INFO com.mchange.v2.log.MLog - MLog clients using slf4j logging. INFO | jvm 4 | 2016/03/23 13:03:11 | [WrapperSimpleAppMain] INFO com.mchange.v2.c3p0.C3P0Registry - Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -00; debug? true; trace: 10] STATUS | wrapper | 2016/03/23 13:03:12 | JVM received a signal UNKNOWN (6). INFO | jvm 4 | 2016/03/23 13:03:12 | INFO 3/23/16 1:03 PM: liquibase: Clearing database change log checksums INFO | jvm 4 | 2016/03/23 13:03:12 | java: res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) && (hp2 != ((void *)0))' failed. STATUS | wrapper | 2016/03/23 13:03:12 | JVM process is gone. ERROR | wrapper | 2016/03/23 13:03:12 | JVM exited while starting the application. STATUS | wrapper | 2016/03/23 13:03:17 | Launching a JVM... INFO | jvm 5 | 2016/03/23 13:03:17 | WrapperManager: Initializing... INFO | jvm 5 | 2016/03/23 13:03:18 | [MLog-Init-Reporter] INFO com.mchange.v2.log.MLog - MLog clients using slf4j logging. INFO | jvm 5 | 2016/03/23 13:03:18 | [WrapperSimpleAppMain] INFO com.mchange.v2.c3p0.C3P0Registry - Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -00; debug? true; trace: 10] INFO | jvm 5 | 2016/03/23 13:03:19 | INFO 3/23/16 1:03 PM: liquibase: Clearing database change log checksums STATUS | wrapper | 2016/03/23 13:03:19 | JVM received a signal UNKNOWN (6). INFO | jvm 5 | 2016/03/23 13:03:19 | java: res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) && (hp2 != ((void *)0))' failed. STATUS | wrapper | 2016/03/23 13:03:19 | JVM process is gone. ERROR | wrapper | 2016/03/23 13:03:19 | JVM exited while starting the application. FATAL | wrapper | 2016/03/23 13:03:19 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2016/03/23 13:03:19 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2016/03/23 13:03:19 | <-- Wrapper Stopped root@vultr:~#
Dear Anton,
One more time, congratulations about Traccar. It's really good solution.
Today, I have installed 3.3 server and I would like to migrate to 3.4.
How must I do proceed ?
Must I simply download 3.4 and :
Stop 3.3 server ?
Run traccar.run (sudo ./traccar.run)
Start daemon (sudo /opt/traccar/bin/traccar start)
How can I verify 3.4 upgrade ?
I use Mysql database, it's different ?
Thank you.