Hi,
After updating to version 3.15, I got this error
C:\Program Files\Traccar>java -jar tracker-server.jar conf/traccar.xml
[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
Wed Jan 24 17:20:29 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's
identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an
d 5.7.6+ requirements SSL connection must be established by default if explicit
option isn't set. For compliance with existing applications not using SSL the ve
rifyServerCertificate property is set to 'false'. You need either to explicitly
disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f
or server certificate verification.
INFO 1/24/18 5:20 PM: liquibase: Clearing database change log checksums
INFO 1/24/18 5:20 PM: liquibase: Successfully acquired change log lock
INFO 1/24/18 5:20 PM: liquibase: Successfully released change log lock
INFO 1/24/18 5:20 PM: liquibase: Successfully acquired change log lock
INFO 1/24/18 5:20 PM: liquibase: Reading from ayun_db.DATABASECHANGELOG
INFO 1/24/18 5:20 PM: liquibase: Reading from ayun_db.DATABASECHANGELOG
INFO 1/24/18 5:20 PM: liquibase: ./schema/changelog-master.xml: changelog-3.8::c
hangelog-3.8-dropuniquetoken::author: Change set changelog-3.8::changelog-3.8-dr
opuniquetoken::author failed, but failOnError was false. Error: Can't DROP 'uk_
user_token'; check that column/key exists [Failed SQL: ALTER TABLE ayun_db.users
DROP KEY uk_user_token]
SEVERE 1/24/18 5:20 PM: liquibase: ./schema/changelog-master.xml: changelog-3.15
::changelog-3.15::author: Change Set changelog-3.15::changelog-3.15::author fail
ed. Error: Table 'ayun_db.attribute_aliases' doesn't exist [Failed SQL: ALTER T
ABLE ayun_db.attribute_aliases DROP FOREIGN KEY fk_attribute_aliases_deviceid]
INFO 1/24/18 5:20 PM: liquibase: changelog-3.15::changelog-3.15::author: Success
fully released change log lock
Exception in thread "main" liquibase.exception.MigrationFailedException: Migrati
on failed for change set changelog-3.15::changelog-3.15::author:
Reason: liquibase.exception.DatabaseException: Table 'ayun_db.attribute_ali
ases' doesn't exist [Failed SQL: ALTER TABLE ayun_db.attribute_aliases DROP FORE
IGN KEY fk_attribute_aliases_deviceid]
at liquibase.changelog.ChangeSet.execute(ChangeSet.java:619)
at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:51
)
at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:79)
at liquibase.Liquibase.update(Liquibase.java:214)
at liquibase.Liquibase.update(Liquibase.java:192)
at liquibase.Liquibase.update(Liquibase.java:188)
at org.traccar.database.DataManager.initDatabaseSchema(DataManager.java:
300)
at org.traccar.database.DataManager.<init>(DataManager.java:87)
at org.traccar.Context.init(Context.java:333)
at org.traccar.Main.main(Main.java:35)
Caused by: liquibase.exception.DatabaseException: Table 'ayun_db.attribute_alias
es' doesn't exist [Failed SQL: ALTER TABLE ayun_db.attribute_aliases DROP FOREIG
N KEY fk_attribute_aliases_deviceid]
at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStat
ement(JdbcExecutor.java:309)
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55)
at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:113)
at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.
java:1277)
at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdb
cDatabase.java:1259)
at liquibase.changelog.ChangeSet.execute(ChangeSet.java:582)
... 9 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'ayu
n_db.attribute_aliases' doesn't exist
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou
rce)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
at com.mysql.jdbc.Util.getInstance(Util.java:408)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:944)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2527)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2680)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2480)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2438)
at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:845)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:745)
at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStat
ement(JdbcExecutor.java:307)
... 14 more
any help?
thanks in advance
It probably means that you didn't have official version installed before.
I am only installing from your website, maybe I did some changes by mistake.
What can I do to solve this issue?
You can re-create database and start from scratch.
Hi,
After updating to version 3.15, I got this error
C:\Program Files\Traccar>java -jar tracker-server.jar conf/traccar.xml [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting... Wed Jan 24 17:20:29 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. Wed Jan 24 17:20:30 GST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ an d 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the ve rifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore f or server certificate verification. INFO 1/24/18 5:20 PM: liquibase: Clearing database change log checksums INFO 1/24/18 5:20 PM: liquibase: Successfully acquired change log lock INFO 1/24/18 5:20 PM: liquibase: Successfully released change log lock INFO 1/24/18 5:20 PM: liquibase: Successfully acquired change log lock INFO 1/24/18 5:20 PM: liquibase: Reading from ayun_db.DATABASECHANGELOG INFO 1/24/18 5:20 PM: liquibase: Reading from ayun_db.DATABASECHANGELOG INFO 1/24/18 5:20 PM: liquibase: ./schema/changelog-master.xml: changelog-3.8::c hangelog-3.8-dropuniquetoken::author: Change set changelog-3.8::changelog-3.8-dr opuniquetoken::author failed, but failOnError was false. Error: Can't DROP 'uk_ user_token'; check that column/key exists [Failed SQL: ALTER TABLE ayun_db.users DROP KEY uk_user_token] SEVERE 1/24/18 5:20 PM: liquibase: ./schema/changelog-master.xml: changelog-3.15 ::changelog-3.15::author: Change Set changelog-3.15::changelog-3.15::author fail ed. Error: Table 'ayun_db.attribute_aliases' doesn't exist [Failed SQL: ALTER T ABLE ayun_db.attribute_aliases DROP FOREIGN KEY fk_attribute_aliases_deviceid] INFO 1/24/18 5:20 PM: liquibase: changelog-3.15::changelog-3.15::author: Success fully released change log lock Exception in thread "main" liquibase.exception.MigrationFailedException: Migrati on failed for change set changelog-3.15::changelog-3.15::author: Reason: liquibase.exception.DatabaseException: Table 'ayun_db.attribute_ali ases' doesn't exist [Failed SQL: ALTER TABLE ayun_db.attribute_aliases DROP FORE IGN KEY fk_attribute_aliases_deviceid] at liquibase.changelog.ChangeSet.execute(ChangeSet.java:619) at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:51 ) at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:79) at liquibase.Liquibase.update(Liquibase.java:214) at liquibase.Liquibase.update(Liquibase.java:192) at liquibase.Liquibase.update(Liquibase.java:188) at org.traccar.database.DataManager.initDatabaseSchema(DataManager.java: 300) at org.traccar.database.DataManager.<init>(DataManager.java:87) at org.traccar.Context.init(Context.java:333) at org.traccar.Main.main(Main.java:35) Caused by: liquibase.exception.DatabaseException: Table 'ayun_db.attribute_alias es' doesn't exist [Failed SQL: ALTER TABLE ayun_db.attribute_aliases DROP FOREIG N KEY fk_attribute_aliases_deviceid] at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStat ement(JdbcExecutor.java:309) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:113) at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase. java:1277) at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdb cDatabase.java:1259) at liquibase.changelog.ChangeSet.execute(ChangeSet.java:582) ... 9 more Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'ayu n_db.attribute_aliases' doesn't exist at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou rce) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.mysql.jdbc.Util.handleNewInstance(Util.java:425) at com.mysql.jdbc.Util.getInstance(Util.java:408) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:944) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2527) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2680) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2480) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2438) at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:845) at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:745) at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStat ement(JdbcExecutor.java:307) ... 14 moreany help?
thanks in advance