# Class JDBC not found **URL:** \ **Category:** Logstash\ **Created:** [May 12, 2019, 3:33pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700 "2019-05-12T15:33:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![KashiPashoria\_Tonny](https://avatars.discourse-cdn.com/v4/letter/k/d07c76/32.png) [@KashiPashoria\_Tonny](https://discuss.elastic.co/u/KashiPashoria_Tonny)\ **Post date:** [May 12, 2019, 3:33pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/1 "2019-05-12T15:33:53Z")
I'm trying to ingest data using **logstash 1.5** to an **ES 1.5 index**. Every time I run logstash gives error **D:\ES\logstash-1.5.1\bin\>logstash -f logstash\_conf.conf** **io/console not supported; tty will not be manipulated** **The error reported is:** \*\* Couldn't find any input plugin named 'jdbc'. Are you sure this is correct? Trying to load the jdbc input plugin resulted in this error: no such file to load -- logstash/inputs/jdbc\*\* I've set **classpath** env variable but no use. I tried to install Jdbc plugin in logstash using command **plugin install logstash-input-jdbc** It gives me error: **io/console not supported; tty will not be manipulated** **Validating logstash-input-jdbc** **Unable to download data from [https://rubygems.org/](https://rubygems.org/) - Received fatal alert: protocol\_version ([https://api.rubygems.org/latest\_specs.4.8.gz](https://api.rubygems.org/latest_specs.4.8.gz))** **ERROR: Installation aborted, verification failed for logstash-input-jdbc** Then I tried to install it manually. I download **latest\_specs.4.8.gz** from **[https://api.rubygems.org/latest\_specs.4.8.gz](https://api.rubygems.org/latest_specs.4.8.gz)** and tried to install it using command **plugin install "path\latest\_specs.4.8.gz"** or **plugin install file:\\D:\ES\latest\_specs.4.8.gz** both give me same following error: **io/console not supported; tty will not be manipulated** **Validating file:\\D:\ES\latest\_specs.4.8.gz** **Unable to download data from [https://rubygems.org/](https://rubygems.org/) - Received fatal alert: protocol\_version ([https://api.rubygems.org/latest\_specs.4.8.gz](https://api.rubygems.org/latest_specs.4.8.gz))** **ERROR: Installation aborted, verification failed for file:\\D:\ES\latest\_specs.4.8.gz** I'm messing with it like for 2 days rolling between rivers and logstash. Any help would be appreciated. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 12, 2019, 7:00pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/2 "2019-05-12T19:00:47Z")
Use a more recent version of Logstash. As long as you manage mappings yourself I think it is backwards compatible. ---
**Author:** ![KashiPashoria\_Tonny](https://avatars.discourse-cdn.com/v4/letter/k/d07c76/32.png) [@KashiPashoria\_Tonny](https://discuss.elastic.co/u/KashiPashoria_Tonny)\ **Post date:** [May 12, 2019, 7:19pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/3 "2019-05-12T19:19:00Z")
@Christian_Dahlqvist thnx for replying Would logstash 5.x or higher be suitable to ingest data in ES 1.5 cluster? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 12, 2019, 7:23pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/4 "2019-05-12T19:23:38Z")
I would take the latest version and see if it works. I have not used such old version in ages so can not tell for sure. ---
**Author:** ![KashiPashoria\_Tonny](https://avatars.discourse-cdn.com/v4/letter/k/d07c76/32.png) [@KashiPashoria\_Tonny](https://discuss.elastic.co/u/KashiPashoria_Tonny)\ **Post date:** [May 12, 2019, 7:25pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/5 "2019-05-12T19:25:31Z")
Ok I'll check latest logstash ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 12, 2019, 7:27pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/6 "2019-05-12T19:27:08Z")
If the latest does not work try version 6.7. ---
**Author:** ![KashiPashoria\_Tonny](https://avatars.discourse-cdn.com/v4/letter/k/d07c76/32.png) [@KashiPashoria\_Tonny](https://discuss.elastic.co/u/KashiPashoria_Tonny)\ **Post date:** [May 12, 2019, 10:14pm UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/7 "2019-05-12T22:14:47Z")
I tried logstash 6.7 it read input from sql server successfully but it couldn't ingest it into my cluster. Here my logstash logs: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/c/7ca7a225c1444bce67224e83e1e318ec203452ae.png) Do they make you understand anything? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [May 13, 2019, 5:17am UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/8 "2019-05-13T05:17:19Z")
It sounds like your cluster is overloaded or that you are indexing into a large number of shards. Without knowing anything about your cluster or usecase it is hard to be more precise. Have a look at [this blog post](https://www.elastic.co/blog/why-am-i-seeing-bulk-rejections-in-my-elasticsearch-cluster) for more information on bulk rejections (429 responses as mentioned in the logs). How did you configure Logstash? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 10, 2019, 5:19am UTC](https://discuss.elastic.co/t/class-jdbc-not-found/180700/9 "2019-06-10T05:19:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.