5.3 shuting down after database migration from another server.

Test server working thanks to https://www.traccar.org/forums/topic/404-not-found-53-just-installed/ the main problem was one of the changes made on 5.x version so there was no interface available and it worked after adding one line on config file.

After that, I decided to put the production database on test server to give some use before going full prod. instance.
BUT!...

Traccar starts, takes some time and then shuts down.... (and then keeps starting and falling)

Old test database was maybe a couple hundred MB size, but production database is 1.8GB.
Server has 2.5GB RAM but I doubt traccar needs database fully ram loaded since mysql does'nt.

Could there be some key, table, field, etc.... mismatched on database that may be causing this behavior?

I got this on log...

Main method error - Duplicate column name 'fixedemail' - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)

Anton Tananaev2 years ago

it worked after adding one line on config file

Can you clarify what line was missing? Because you assured me that you've tested it with default Traccar config. I'm sure the default config is correct because it works for everyone else. So, something doesn't add up here and I want to understand what the problem was.

Richard Acosta2 years ago

Tried to answer that on the former thread and received "too many requests", So opened this new thread instead....
Then tried to answer here, and received the same message...

The missing line is the one to chose classic interface, putting that allowed me to connect.
And no, default config file had'nt that line.

Still traccar keeps going down after trying to start.

Richard Acosta2 years ago

Still stoping and restarting... Can't find the duplicate column...

2022-09-19 23:13:25  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-19 23:13:25  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2
2022-09-19 23:13:25  INFO: Memory limit heap: 466mb non-heap: 0mb
2022-09-19 23:13:25  INFO: Character encoding: UTF-8 charset: UTF-8
2022-09-19 23:13:25  INFO: Version: 5.3
2022-09-19 23:13:25  INFO: Starting server...
2022-09-19 23:13:26  INFO: HikariPool-1 - Starting...
2022-09-19 23:13:29  INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@438bad7c
2022-09-19 23:13:29  INFO: HikariPool-1 - Start completed.
2022-09-19 23:13:31  INFO: Clearing database change log checksums
2022-09-19 23:13:32  INFO: Successfully acquired change log lock
2022-09-19 23:13:33  INFO: Successfully released change log lock
2022-09-19 23:13:33  INFO: Successfully acquired change log lock
2022-09-19 23:13:33  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-09-19 23:13:33  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-09-19 23:13:41  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-19 23:13:42  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-19 23:13:43  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-09-19 23:13:43  INFO: Successfully released change log lock
2022-09-19 23:13:43 ERROR: Main method error - Duplicate column name 'fixedemail' - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)
2022-09-19 23:14:00  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-19 23:14:00  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2

Anton Tananaev2 years ago

This error probably means something went wrong with the database migration. Restore the backup and try again. Next time you need to get the first logs right after upgrade.

Richard Acosta2 years ago

Renamed traccar folder, re-renamed 4.15/old folder to traccar, started traccar and old version works, with all the imported info.
Just checked database using a browser tool and there's no corruption at all.
5.3 shuts down around 160MB memory usage, tops 170, 4.15 is using 220ish.

Richard Acosta2 years ago

The same over and over.
Just in case deleted database and reimported...
4.15 still working, 5.3 still shuting down and restarting.

First log after reimporting database.
Now duplicate entry also for a table.

2022-09-20 01:37:06  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-20 01:37:07  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2
2022-09-20 01:37:07  INFO: Memory limit heap: 466mb non-heap: 0mb
2022-09-20 01:37:07  INFO: Character encoding: UTF-8 charset: UTF-8
2022-09-20 01:37:07  INFO: Version: 5.3
2022-09-20 01:37:07  INFO: Starting server...
2022-09-20 01:37:08  INFO: HikariPool-1 - Starting...
2022-09-20 01:37:10  INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@438bad7c
2022-09-20 01:37:11  INFO: HikariPool-1 - Start completed.
2022-09-20 01:37:12  INFO: Clearing database change log checksums
2022-09-20 01:37:14  INFO: Successfully acquired change log lock
2022-09-20 01:37:14  INFO: Successfully released change log lock
2022-09-20 01:37:15  INFO: Successfully acquired change log lock
2022-09-20 01:37:15  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:37:15  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:37:21  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:37:23  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:37:23  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-09-20 01:37:24  INFO: Columns disablereports(BOOLEAN) added to tc_servers
2022-09-20 01:37:24  INFO: Columns disablereports(BOOLEAN) added to tc_users
2022-09-20 01:37:24  INFO: Column tc_orders.toAddress renamed to toaddresstmp
2022-09-20 01:37:24  INFO: Column tc_orders.fromAddress renamed to fromaddresstmp
2022-09-20 01:37:24  INFO: Column tc_orders.toaddresstmp renamed to toaddress
2022-09-20 01:37:24  INFO: Column tc_orders.fromaddresstmp renamed to fromaddress
2022-09-20 01:37:24  INFO: ChangeSet changelog-5.0::changelog-5.0::author ran successfully in 219ms
2022-09-20 01:37:24  INFO: Index idx_drivers_uniqueid created
2022-09-20 01:37:24  INFO: Index idx_devices_uniqueid created
2022-09-20 01:37:24  INFO: Index idx_users_email created
2022-09-20 01:37:24  INFO: Index idx_users_login created
2022-09-20 01:37:24  INFO: Index idx_users_token created
2022-09-20 01:37:24  INFO: Columns overlayurl(VARCHAR(512)) added to tc_servers
2022-09-20 01:37:24  INFO: ChangeSet changelog-5.1::changelog-5.1::author ran successfully in 243ms
2022-09-20 01:37:24  INFO: Columns status(CHAR(8)) added to tc_devices
2022-09-20 01:37:24  INFO: Columns geofenceIds(VARCHAR(128)) added to tc_devices
2022-09-20 01:37:24  INFO: ChangeSet changelog-5.2::changelog-5.2::author ran successfully in 62ms
2022-09-20 01:37:24  INFO: Columns fixedemail(BOOLEAN) added to tc_servers
2022-09-20 01:37:24  INFO: Columns fixedemail(BOOLEAN) added to tc_users
2022-09-20 01:37:24  INFO: Columns expirationtime(TIMESTAMP) added to tc_devices
2022-09-20 01:37:24  INFO: Successfully released change log lock
2022-09-20 01:37:24 ERROR: Main method error - Table 'tc_keystore' already exists - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)
2022-09-20 01:37:40  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-20 01:37:41  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2
2022-09-20 01:37:41  INFO: Memory limit heap: 466mb non-heap: 0mb
2022-09-20 01:37:41  INFO: Character encoding: UTF-8 charset: UTF-8
2022-09-20 01:37:41  INFO: Version: 5.3
2022-09-20 01:37:41  INFO: Starting server...
2022-09-20 01:38:57  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-20 01:38:57  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2
2022-09-20 01:38:57  INFO: Memory limit heap: 466mb non-heap: 0mb
2022-09-20 01:38:57  INFO: Character encoding: UTF-8 charset: UTF-8
2022-09-20 01:38:57  INFO: Version: 5.3
2022-09-20 01:38:57  INFO: Starting server...
2022-09-20 01:38:58  INFO: HikariPool-1 - Starting...
2022-09-20 01:39:01  INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@438bad7c
2022-09-20 01:39:01  INFO: HikariPool-1 - Start completed.
2022-09-20 01:39:02  INFO: Clearing database change log checksums
2022-09-20 01:39:03  INFO: Successfully acquired change log lock
2022-09-20 01:39:04  INFO: Successfully released change log lock
2022-09-20 01:39:05  INFO: Successfully acquired change log lock
2022-09-20 01:39:05  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:39:05  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:39:11  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:39:13  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:39:13  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-09-20 01:39:13  INFO: Successfully released change log lock
2022-09-20 01:39:13 ERROR: Main method error - Duplicate column name 'fixedemail' - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)
2022-09-20 01:39:29  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-20 01:39:30  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2
2022-09-20 01:39:30  INFO: Memory limit heap: 466mb non-heap: 0mb
2022-09-20 01:39:30  INFO: Character encoding: UTF-8 charset: UTF-8
2022-09-20 01:39:30  INFO: Version: 5.3
2022-09-20 01:39:30  INFO: Starting server...
2022-09-20 01:39:31  INFO: HikariPool-1 - Starting...
2022-09-20 01:39:34  INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@438bad7c
2022-09-20 01:39:34  INFO: HikariPool-1 - Start completed.
2022-09-20 01:39:35  INFO: Clearing database change log checksums
2022-09-20 01:39:36  INFO: Successfully acquired change log lock
2022-09-20 01:39:37  INFO: Successfully released change log lock
2022-09-20 01:39:38  INFO: Successfully acquired change log lock
2022-09-20 01:39:38  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:39:38  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:39:46  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:39:47  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:39:48  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-09-20 01:39:48  INFO: Successfully released change log lock
2022-09-20 01:39:48 ERROR: Main method error - Duplicate column name 'fixedemail' - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)
2022-09-20 01:40:04  INFO: Operating system name: Linux version: 5.9.0-arm-64 architecture: aarch64
2022-09-20 01:40:04  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 11.0.12+7-post-Debian-2
2022-09-20 01:40:04  INFO: Memory limit heap: 466mb non-heap: 0mb
2022-09-20 01:40:05  INFO: Character encoding: UTF-8 charset: UTF-8
2022-09-20 01:40:05  INFO: Version: 5.3
2022-09-20 01:40:05  INFO: Starting server...
2022-09-20 01:40:06  INFO: HikariPool-1 - Starting...
2022-09-20 01:40:08  INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@438bad7c
2022-09-20 01:40:08  INFO: HikariPool-1 - Start completed.
2022-09-20 01:40:10  INFO: Clearing database change log checksums
2022-09-20 01:40:11  INFO: Successfully acquired change log lock
2022-09-20 01:40:12  INFO: Successfully released change log lock
2022-09-20 01:40:12  INFO: Successfully acquired change log lock
2022-09-20 01:40:12  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:40:12  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-09-20 01:40:19  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:40:21  INFO: Reading from rastreo.DATABASECHANGELOG
2022-09-20 01:40:22  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-09-20 01:40:22  INFO: Successfully released change log lock
2022-09-20 01:40:22 ERROR: Main method error - Duplicate column name 'fixedemail' - SQLSyntaxErrorException (... < DatabaseModule:96 < <gener:-1 < *:-1 < ... < Main:126 < ...)

Anton Tananaev2 years ago

How come you already have this table in your 4.15 version?

Table 'tc_keystore' already exists

Richard Acosta2 years ago

¿Is it created on 5.x?
Will try to delete and reimport database to see.
Database came from 4.x production server, if table is created on 5.x maybe I messed the order when doing something.

Richard Acosta2 years ago

I made some mistakes in the way.
It was not 4.15, it was 5.xx (can't remember which) already on test server.
I just imported some tables from production server's dump but it seems dump was not correct, or witing the database partially does not work.

I managed to repeat the behavior and finally just dumped the whole database and imported the whole database instead of some tables. Once done, traccar started. It seems to be working perfect.
But since this time there's a new version, I'll still wait to go production with 5.xx until I test the new latest.
Still didn't see much of new features altough found some i liked a lot.

Thanks for your time.