MS SQL server driver issue
Looks similar to the problem here:
Hi Anton,
Are u referring to schema files, config strings, or traccar official version?
I am referring to the error message. By the way, version 3.8 includes MS SQL driver, so try to remove "driverFile" parameter.
tried it, not working.
i installed mysql 5.7 and reconfigured the config file.
now i get tracccar server started, but cannot open web server at localhost 8082. here is the log:
WARNING|wrapper|Service traccar|16-11-24 05:02:37|YAJSW: yajsw-beta-12.07 WARNING|wrapper|Service traccar|16-11-24 05:02:37|OS : Windows Server 2012 R2/6.3/amd64 WARNING|wrapper|Service traccar|16-11-24 05:02:37|JVM : Oracle Corporation/1.8.0_111/C:\Program Files\Java\jre1.8.0_111/64 INFO|wrapper|Service traccar|16-11-24 05:02:37|start delay: 0 INFO|wrapper|Service traccar|16-11-24 05:02:38|started process with pid 1888 INFO|1888/0|Service traccar|16-11-24 05:02:41|[INFO] StandardFileSystemManager - Using "C:\Windows\TEMP\vfs_cache" as temporary files store. INFO|1888/0|Service traccar|16-11-24 05:02:43|[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started.
my config file:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>
<properties>
<entry key='database.driver'>com.mysql.jdbc.Driver</entry>
<entry key='database.url'>jdbc:mysql://localhost/traccar?allowMultiQueries=true&autoReconnect=true&useSSL=false&useUnicode=yes&characterEncoding=UTF-8&sessionVariables=sql_mode=''</entry>
<entry key='database.user'>traccar</entry>
<entry key='database.password'>password</entry>
</properties>
i got root password but i believe this shouldn't be specified in config file
if i remove useSSL=false from config i get this in wrapper:
WARNING|wrapper|Service traccar|16-11-24 10:51:18|YAJSW: yajsw-beta-12.07 WARNING|wrapper|Service traccar|16-11-24 10:51:18|OS : Windows Server 2012 R2/6.3/amd64 WARNING|wrapper|Service traccar|16-11-24 10:51:18|JVM : Oracle Corporation/1.8.0_111/C:\Program Files\Java\jre1.8.0_111/64 INFO|wrapper|Service traccar|16-11-24 10:51:18|start delay: 0 INFO|wrapper|Service traccar|16-11-24 10:51:19|started process with pid 668 INFO|668/0|Service traccar|16-11-24 10:51:20|[INFO] StandardFileSystemManager - Using "C:\Windows\TEMP\vfs_cache" as temporary files store. INFO|668/0|Service traccar|16-11-24 10:51:21|[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 10:51:22|Thu Nov 24 10:51:22 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:20:53|Thu Nov 24 11:20:53 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:20:53|Thu Nov 24 11:20:53 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. INFO|668/0|Service traccar|16-11-24 11:21:23|Thu Nov 24 11:21:23 PST 2016 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 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 verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
I suspect there is some problem with connection to your MySQL database.
if i enter wrong password it raises otger errors. so in fact it sees the database and passes authentication.
however no tables were created. woukd it be an option if i manually create tables using xml file?
Wait, I know why. You removed "config.default" parameter from your config file. Why? Please put it back.
u did it! my bad. i just copied the strings from the oage describing instructions on how to set up mysql config. replaced them.
now its loading schema.
but i can't start web ui.
log file says its waiting for changlog lock. any idea what it means?
log file is here:
WARNING|wrapper|Service traccar|16-11-24 13:59:06|YAJSW: yajsw-beta-12.07 WARNING|wrapper|Service traccar|16-11-24 13:59:06|OS : Windows Server 2012 R2/6.3/amd64 WARNING|wrapper|Service traccar|16-11-24 13:59:06|JVM : Oracle Corporation/1.8.0_111/C:\Program Files\Java\jre1.8.0_111/64 INFO|wrapper|Service traccar|16-11-24 13:59:06|start delay: 0 INFO|wrapper|Service traccar|16-11-24 13:59:07|started process with pid 1656 INFO|1656/0|Service traccar|16-11-24 13:59:09|[INFO] StandardFileSystemManager - Using "C:\Windows\TEMP\vfs_cache" as temporary files store. INFO|1656/0|Service traccar|16-11-24 13:59:12|[main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started. INFO|1656/0|Service traccar|16-11-24 13:59:13|INFO 11/24/16 1:59 PM: liquibase: Clearing database change log checksums INFO|1656/0|Service traccar|16-11-24 13:59:14|INFO 11/24/16 1:59 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 13:59:24|INFO 11/24/16 1:59 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 13:59:34|INFO 11/24/16 1:59 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 13:59:44|INFO 11/24/16 1:59 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 13:59:54|INFO 11/24/16 1:59 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 14:00:04|INFO 11/24/16 2:00 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 14:00:14|INFO 11/24/16 2:00 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 14:00:24|INFO 11/24/16 2:00 PM: liquibase: Waiting for changelog lock.... INFO|1656/0|Service traccar|16-11-24 14:00:34|INFO 11/24/16 2:00 PM: liquibase: Waiting for changelog lock....
Now your database is locked... I guess because you stopped service in the middle of database migration. If you don't have any valuable information in the database, you can just recreate it.
man u are great. thank u so much.
everything is working now. now i can go and get some sleep.
appreciate ur help and i hope to donate when things work out.
hi, i only have few fays to get project done, but traccar is not working with ms sql.
my system: 64bit Windows server 2012, MS sql server 2012.
Traccar 3.8 clean install on Java8.
Placed sqljdbc42.jar in traccar/lib directory.
my traccar configuration file:
error that i get is:
i have tried to set ms sql server remote connection timout to 0 no result still getting this error.