3.1 to 3.2 Upgrade

jaimzj9 years ago

Dear Atnon,

I am planning to upgrade my live server 3.1 to 3.2 new release. Have few queries.

  1. I am using mysql db, so if I run the update script you have shared, will it be enough? as far as db is concerned, I plan to run that query on phpmyadmin.

  2. The server application, Shall I just download and overwrite, or do I need to uninstall 3.1 and install 3.2

  3. Anything else I need to be careful about while I upgrade? please do advice.

diggah9 years ago

Used : https://www.traccar.org/update-from-3-1-to-3-2/

but it is not working. users not avaiable.

jaimzj9 years ago

Dear Anton,

Adding some more info.

a. I have my own GUI/Front end (I dont use the default web) so I am not much worried about web front, as I can figure out the changes in the DB and update my UI as required.

b. However I am worried about the existing data in the db. if I run the mysql script. (Am i supposed to then after that fresh install 3.2 or just overwrire certain fiels on 3.1)

Anton Tananaev9 years ago

If you are using default Traccar database schema, then you can use script from the following page (it's a MySQL specific script):

https://www.traccar.org/update-from-3-1-to-3-2/

Script just updates some fields. It doesn't touch the data, so it should be safe. Don't forget to make a backup of course.

jaimzj9 years ago

Basically I am using default traccar database schema (No changes to anything) except I do have additional tables and certain tables such as user/device have some additional columns added as well. would that be okay?

And how about, updating the server app itself? right now 3.1 is running, do I just download and overwrite? or re-install?

Anton Tananaev9 years ago

Database should be OK.

As for the app, I would recommend to save your config file first, then remove old version and install new one. Installing it over the old one should be fine as well, but it will probably keep some old files that are not required any more.

jaimzj9 years ago

Perfect thanks a lot, Gonna try it in some time :) and see how that goes.. in the process of backing up DB right now.

jaimzj9 years ago

Dear Anton,

I upgraded, it returns these errors in the log, Please guide? help... the deviceTime line with 1970 as the year. unable to identify wht that is.

Anton Tananaev9 years ago

Can you please fix the formatting of the log.

jaimzj9 years ago

sorry about that, now copying from log direct, hope this is viewable. mainly i am refering to the deviceTime error with 1970 as year.

2015-11-15 01:49:03 DEBUG: [5EB24616: 5023 < 101.57.60.185] HEX: 78780a13440601000200019b800d0a
2015-11-15 01:49:03 DEBUG: [5EB24616: 5023 > 101.57.60.185] HEX: 787805130001e9f10d0a
2015-11-15 01:49:03  WARN: Data truncation: Incorrect datetime value: '1970-01-01 05:30:00' for column 'deviceTime' at row 1 - MysqlDataTruncation (... < QueryBuilder:428 < DataManager:345 < DefaultDataHandler:27 < ...)
2015-11-15 01:49:03  INFO: [5EB24616] id: 10, time: 1970-01-01 05:30:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2015-11-15 01:49:03  INFO: [EEF2408C] timed out
2015-11-15 01:49:03  INFO: [EEF2408C] disconnected
2015-11-15 01:49:04 DEBUG: [F78E5F6D: 5023 < 106.208.94.162] HEX: 78781f120f0b0e090824c80147d0ea0890397000548b01945e002100aa5b000283700d0a
2015-11-15 01:49:04 DEBUG: [F78E5F6D: 5023 > 106.208.94.162] HEX: 78780512000281b60d0a
2015-11-15 01:49:04  INFO: [F78E5F6D] id: 5, time: 2015-11-14 14:38:36, lat: 11.93542, lon: 79.81645, speed: 0.0, course: 139.0
2015-11-15 01:49:04 DEBUG: [CC7ECF29: 5023 < 101.222.246.187] HEX: 78781f120f0b0e12333bca020d966007d17550005448019525006900854a0002c20e0d0a
2015-11-15 01:49:04 DEBUG: [CC7ECF29: 5023 > 101.222.246.187] HEX: 78780512000281b60d0a
2015-11-15 01:49:04  INFO: [CC7ECF29] id: 75, time: 2015-11-15 00:21:59, lat: 19.13605, lon: 72.87087, speed: 0.0, course: 72.0
2015-11-15 01:49:04 DEBUG: [5EB24616: 5023 < 101.57.60.185] HEX: 78781f120f0b0e10271ac6027f3ce8078a9d500054e101950617c1002815000297a00d0a
2015-11-15 01:49:04 DEBUG: [5EB24616: 5023 > 101.57.60.185] HEX: 78780512000281b60d0a
2015-11-15 01:49:04  INFO: [5EB24616] id: 10, time: 2015-11-14 22:09:26, lat: 23.27394, lon: 70.29153, speed: 0.0, course: 225.0
2015-11-15 01:49:06  INFO: [404C45F2] connected
2015-11-15 01:49:06 DEBUG: [404C45F2: 5023 < 101.222.182.42] HEX: 78780d01035889905484311800001d770d0a
2015-11-15 01:49:06 DEBUG: [404C45F2: 5023 > 101.222.182.42] HEX: 787805010000c8550d0a
2015-11-15 01:49:06  INFO: [920B515C] connected
2015-11-15 01:49:06 DEBUG: [920B515C: 5023 < 223.176.144.223] HEX: 787811010358739050476119202000010003f5240d0a
2015-11-15 01:49:06 DEBUG: [920B515C: 5023 > 223.176.144.223] HEX: 787805010003face0d0a
2015-11-15 01:49:06 DEBUG: [404C45F2: 5023 < 101.222.182.42] HEX: 78780a1344060400020001bdd40d0a
2015-11-15 01:49:06 DEBUG: [404C45F2: 5023 > 101.222.182.42] HEX: 787805130001e9f10d0a
2015-11-15 01:49:06  WARN: Data truncation: Incorrect datetime value: '1970-01-01 05:30:00' for column 'deviceTime' at row 1 - MysqlDataTruncation (... < QueryBuilder:428 < DataManager:345 < DefaultDataHandler:27 < ...)
2015-11-15 01:49:06  INFO: [404C45F2] id: 11, time: 1970-01-01 05:30:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2015-11-15 01:49:06  INFO: [F53A6456] connected
Anton Tananaev9 years ago

This is a new feature in version 3.2. It decodes status messages from GT06 and appends latest known location. In your case I guess there was no previous location, so it appends 1970 year (unix epoch).

jaimzj9 years ago

So Can I safely ignore that? and continue to run the server app?

  1. The last error is for device id 11 : (I do have locations as recent as few hours back for that particular device in the position table.)

  2. For GT06 how do I check GT06 status if its capturing now? as all my devices work on gt06 protocol itself.

Anton Tananaev9 years ago

  1. I guess there was some problem with loading previous GPS location.

  2. It will show as usual position.

jaimzj9 years ago

Thank you for the amazing and quick responses :) I tested 3.2 and now I am deploying the same on to my live server as well..

  1. Okay in that case I will keep the app running, and see what happens :) so far when I kept it running for a little while new positions were stored pretty neatly without any problem.

  2. Usual position, I checked (last position is still the old record) no updates on them or in attributes column, is it linked to (lastUpdate) value in device table.

Andrei9 years ago

Hello,

I'm new to Traccar and just installed version 3.1 two days ago with the default database.
Now I see 3.2 was released so I went ahead and downloaded the installer and run it (stopped the Traccar service first), but now Traccar gives me the "Wrong database schema version.".
How can I update the default database schema from 3.1 to 3.2?

Regards,
Andrei.