Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traccar 4.1 - ArrayIndexOutOfBoundsException on start #4113

Closed
TwizzyDizzy opened this issue Oct 21, 2018 · 3 comments
Closed

Traccar 4.1 - ArrayIndexOutOfBoundsException on start #4113

TwizzyDizzy opened this issue Oct 21, 2018 · 3 comments

Comments

@TwizzyDizzy
Copy link

TwizzyDizzy commented Oct 21, 2018

Hi there,

I just upgraded from Traccar 4.0 to 4.1 and traccar doesn't start anymore. This issue is identical to this forum thread.

Host details:

  • OS: 64 Bit Linux, Debian Stretch, release file: traccar-linux-64-4.1.zip
  • JDK: bundled OJDK 10 (bundled with Traccar 4.1)
  • systemd version: 232
  • Database: MariaDB 10.1.26-0 (+deb9u1)

Logfile (including the error):

tracker-server.log

I would appreciate any feedback, will happily answer any question and will help debugging, if needed.

There is this issue of running traccar as root (via systemd), but I think I will file this in another issue.

Cheers
Thomas

@tananaev
Copy link
Member

I need to check it myself because I'm not able to reproduce it locally.

@castillo92
Copy link

castillo92 commented Oct 21, 2018

@tananaev

The same error:

I did a fresh install of v4.1, only changing the MySQL configuration and when I restart the entire server or the Traccar service, I cant start it in any way

I hope this logs could help to fix the problem, Anton

Log from: sudo systemctl status traccar.service

● traccar.service - traccar
   Loaded: loaded (/etc/systemd/system/traccar.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-10-21 16:55:55 CEST; 37s ago
  Process: 24525 ExecStart=/opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml (code=exited, status=1/FAILURE)
 Main PID: 24525 (code=exited, status=1/FAILURE)

oct 21 16:55:55 RasPi_Server traccar[24525]:         at liquibase.Liquibase.update(Liquibase.java:179)
oct 21 16:55:55 RasPi_Server traccar[24525]:         at liquibase.Liquibase.update(Liquibase.java:175)
oct 21 16:55:55 RasPi_Server traccar[24525]:         at org.traccar.database.DataManager.initDatabaseSchema(DataManager.java:306)
oct 21 16:55:55 RasPi_Server traccar[24525]:         at org.traccar.database.DataManager.<init>(DataManager.java:91)
oct 21 16:55:55 RasPi_Server traccar[24525]:         at org.traccar.Context.init(Context.java:382)
oct 21 16:55:55 RasPi_Server traccar[24525]:         at org.traccar.Main.run(Main.java:110)
oct 21 16:55:55 RasPi_Server traccar[24525]:         ... 1 more
oct 21 16:55:55 RasPi_Server systemd[1]: traccar.service: Main process exited, code=exited, status=1/FAILURE
oct 21 16:55:55 RasPi_Server systemd[1]: traccar.service: Unit entered failed state.
oct 21 16:55:55 RasPi_Server systemd[1]: traccar.service: Failed with result 'exit-code'.

Log from: /opt/traccar/logs/tracker-server.log

2018-10-21 16:44:56  INFO: HikariPool-1 - Starting...
2018-10-21 16:44:59  INFO: HikariPool-1 - Start completed.
2018-10-21 16:45:03  INFO: Clearing database change log checksums
2018-10-21 16:45:03  INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK
2018-10-21 16:45:04  INFO: CREATE TABLE PUBLIC.DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID))
2018-10-21 16:45:04  INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK
2018-10-21 16:45:04  INFO: DELETE FROM PUBLIC.DATABASECHANGELOGLOCK
2018-10-21 16:45:04  INFO: INSERT INTO PUBLIC.DATABASECHANGELOGLOCK (ID, LOCKED) VALUES (1, FALSE)
2018-10-21 16:45:04  INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1
2018-10-21 16:45:04  INFO: Successfully acquired change log lock
2018-10-21 16:45:04  INFO: Creating database history table with name: PUBLIC.DATABASECHANGELOG
2018-10-21 16:45:04  INFO: CREATE TABLE PUBLIC.DATABASECHANGELOG (ID VARCHAR(255) NOT NULL, AUTHOR VARCHAR(255) NOT NULL, FILENAME VARCHAR(255) NOT NULL, DATEEXECUTED TIMESTAMP NOT NULL, ORDEREXECUTED INT NOT NULL, EXECTYPE VARCHAR(10) NOT NULL, MD5SUM VARCHAR(35), DESCRIPTION VARCHAR(255), COMMENTS VARCHAR(255), TAG VARCHAR(255), LIQUIBASE VARCHAR(20), CONTEXTS VARCHAR(255), LABELS VARCHAR(255), DEPLOYMENT_ID VARCHAR(10))
2018-10-21 16:45:04  INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK
2018-10-21 16:45:04  INFO: UPDATE PUBLIC.DATABASECHANGELOG SET MD5SUM = NULL
2018-10-21 16:45:04  INFO: Successfully released change log lock
2018-10-21 16:45:04  INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK
2018-10-21 16:45:04  INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK
2018-10-21 16:45:04  INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1
2018-10-21 16:45:04  INFO: Successfully acquired change log lock
2018-10-21 16:45:22  INFO: SELECT MD5SUM FROM PUBLIC.DATABASECHANGELOG WHERE MD5SUM IS NOT NULL
...
2018-10-21 16:55:37  INFO: Successfully released change log lock
2018-10-21 16:55:37  INFO: SELECT COUNT(*) FROM traccarDB.DATABASECHANGELOGLOCK
2018-10-21 16:55:37  INFO: SELECT COUNT(*) FROM traccarDB.DATABASECHANGELOGLOCK
2018-10-21 16:55:37  INFO: SELECT `LOCKED` FROM traccarDB.DATABASECHANGELOGLOCK WHERE ID=1
2018-10-21 16:55:37  INFO: Successfully acquired change log lock
2018-10-21 16:55:54  INFO: SELECT MD5SUM FROM traccarDB.DATABASECHANGELOG WHERE MD5SUM IS NOT NULL LIMIT 1
2018-10-21 16:55:54  INFO: SELECT COUNT(*) FROM traccarDB.DATABASECHANGELOG
2018-10-21 16:55:54  INFO: Reading from traccarDB.DATABASECHANGELOG
2018-10-21 16:55:54  INFO: SELECT * FROM traccarDB.DATABASECHANGELOG ORDER BY DATEEXECUTED ASC, ORDEREXECUTED ASC
2018-10-21 16:55:55  INFO: Successfully released change log lock
2018-10-21 16:55:55 ERROR: Main method error - 1 - ArrayIndexOutOfBoundsException (... < DataManager:306 < *:91 < Context:382 < Main:110 < ...)

@TwizzyDizzy
Copy link
Author

I just applied the changes from e4bbd04 and I can confirm, that they fixed the issue.

Cheers
Thomas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants