-
Notifications
You must be signed in to change notification settings - Fork 187
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
“Unable to find driver class” when use jdbc_driver_library => “/home/ubuntu/ojdbc6.jar” after upgrade to Logstash 6.8.4 #357
Comments
Hi @JerseyGood loading of drivers has changed recently, please could you try with 4.3.18 version and report here if the problem persists? |
@andsel Thanks for the reply, will give it a try with 4.3.18 of jdbc-input-plugin and share the result. But we are installing Logstash through https://www.elastic.co/guide/en/logstash/6.8/logstash-6-8-4.html Do you know when will logstash bump up the version to use jdbc-input-plugin 4.3.18 |
I've run into a very similar-looking problem with Logstash 7.4, installed on Ubuntu 18.0.4 with the "apt-get" instructions listed here: https://www.elastic.co/guide/en/logstash/current/installing-logstash.html
Trying to connect to a MySQL database with the JDBC connector
This is a very tricky problem to diagnose! 4.3.18 should be made the default plugin version ASAP, to avoid this bug, AFAICS. |
I can confirm this is fixed with logstash 6.8.5 |
This was fixed by #355 and is fixed by the latest release of the jdbc input. Running
Version >=4.3.19 will be shipped in 7.5.1 |
The latest release of Logstash 6.8.4 with jdbc-input-plugin 4.3.16 give us following error in syslog
our pipeline config looks like
OS Info
JDK info
It was fine when running Logstash 6.8.2 and 6.8.3 with jdbc-input-plugin 4.3.13.
So I guess something wrong with the Driver loading modification for jdbc-input-plugin 4.3.14. and 4.3.15 release
A workaround for us is to not using jdbc_driver_library but place the ojdbc6.jar in logstash-core lib path
The text was updated successfully, but these errors were encountered: