# Generic "Something is wrong with your configuration" **URL:** \ **Category:** Logstash\ **Created:** [June 3, 2018, 11:02pm UTC](https://discuss.elastic.co/t/generic-something-is-wrong-with-your-configuration/134342 "2018-06-03T23:02:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Michael\_Hatch](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Michael\_Hatch](https://discuss.elastic.co/u/Michael_Hatch)\ **Post date:** [June 3, 2018, 11:02pm UTC](https://discuss.elastic.co/t/generic-something-is-wrong-with-your-configuration/134342/1 "2018-06-03T23:02:35Z")
I would think that if you could detect an issue with plugin configuration, you would be able to supply a useful error message, but alas...Any thoughts? Elastic 6.2 jdbc plugin conf input { jdbc { id =\> "new\_user" jdbc\_connection\_string =\> "jdbc:postgresql://host.docker.internal:32769/kunveen" jdbc\_user =\> "user\_service" jdbc\_password =\> "user\_service\_password" jdbc\_validate\_connection =\> true jdbc\_driver\_library =\> "/usr/share/logstash/lib/postgresql-42.2.2.jar" jdbc\_driver\_class =\> "org.postgresql.Driver" use\_column\_value =\> true tracking\_column =\> "updated\_at" schedule =\> "\* \* \* \* \*" statement =\> "SELECT id,email,first\_name,last\_name,deleted\_at FROM users WHERE updated\_at \> :sql\_last\_value" } } output { elasticsearch { protocol =\> http index =\> "users" document\_type =\> "user" document\_id =\> "%{id}" hosts =\> ["host.docker.internal:9200"] } } Logstash logs 2018/06/03 22:51:58 Setting 'xpack.monitoring.elasticsearch.url' from environment. Sending Logstash's logs to /usr/share/logstash/logs which is now configured via log4j2.properties [2018-06-03T22:52:14,239][INFO][logstash.modules.scaffold] Initializing module {:module\_name=\>"fb\_apache", :directory=\>"/usr/share/logstash/modules/fb\_apache/configuration"} [2018-06-03T22:52:14,253][INFO][logstash.modules.scaffold] Initializing module {:module\_name=\>"netflow", :directory=\>"/usr/share/logstash/modules/netflow/configuration"} [2018-06-03T22:52:15,055][INFO][logstash.modules.scaffold] Initializing module {:module\_name=\>"arcsight", :directory=\>"/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/x-pack-6.2.4-java/modules/arcsight/configuration"} [2018-06-03T22:52:15,209][INFO][logstash.setting.writabledirectory] Creating directory {:setting=\>"path.queue", :path=\>"/usr/share/logstash/data/queue"} [2018-06-03T22:52:15,215][INFO][logstash.setting.writabledirectory] Creating directory {:setting=\>"path.dead\_letter\_queue", :path=\>"/usr/share/logstash/data/dead\_letter\_queue"} [2018-06-03T22:52:15,658][INFO][logstash.agent] No persistent UUID file found. Generating new UUID {:uuid=\>"e06a8fab-c0bd-48ac-927a-38681e0d6ed1", :path=\>"/usr/share/logstash/data/uuid"} [2018-06-03T22:52:16,415][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"6.2.4"} [2018-06-03T22:52:16,880][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600} [2018-06-03T22:52:18,677][WARN][logstash.outputs.elasticsearch] You are using a deprecated config setting "document\_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=\>"document\_type", :plugin=\>\[[http://host.docker.internal:9200](http://host.docker.internal:9200)], bulk\_path=\>"/\_xpack/monitoring/\_bulk?system\_id=logstash&system\_api\_version=2&interval=1s", manage\_template=\>false, document\_type=\>"%{[@metadata][document\_type]}", sniffing=\>false, user=\>"logstash\_system", password=\>, id=\>"57a890619fcf9eaa48343645e54e275791b8a49a0c5c7a3b09c0444efb012629", enable\_metric=\>true, codec=\>\"plain\_6af54180-105b-4490-a4eb-ea1e42f144ac", enable\_metric=\>true, charset=\>"UTF-8"\>, workers=\>1, template\_name=\>"logstash", template\_overwrite=\>false, doc\_as\_upsert=\>false, script\_type=\>"inline", script\_lang=\>"painless", script\_var\_name=\>"event", scripted\_upsert=\>false, retry\_initial\_interval=\>2, retry\_max\_interval=\>64, retry\_on\_conflict=\>1, action=\>"index", ssl\_certificate\_verification=\>true, sniffing\_delay=\>5, timeout=\>60, pool\_max=\>1000, pool\_max\_per\_route=\>100, resurrect\_delay=\>5, validate\_after\_inactivity=\>10000, http\_compression=\>false\>} [2018-06-03T22:52:18,764][INFO][logstash.pipeline] Starting pipeline {:pipeline\_id=\>".monitoring-logstash", "pipeline.workers"=\>1, "pipeline.batch.size"=\>2, "pipeline.batch.delay"=\>50} [2018-06-03T22:52:19,260][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>[], :added=\>[[http://logstash\_system:xxxxxx@host.docker.internal:9200/](http://logstash_system:xxxxxx@host.docker.internal:9200/)]}} [2018-06-03T22:52:19,280][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://logstash\_system:xxxxxx@host.docker.internal:9200/](http://logstash_system:xxxxxx@host.docker.internal:9200/), :path=\>"/"} [2018-06-03T22:52:19,523][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://logstash\_system:xxxxxx@host.docker.internal:9200/](http://logstash_system:xxxxxx@host.docker.internal:9200/)"} [2018-06-03T22:52:19,577][INFO][logstash.outputs.elasticsearch] ES Output version determined {:es\_version=\>6} [2018-06-03T22:52:19,581][WARN][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} [2018-06-03T22:52:19,602][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=\>"LogStash::Outputs::ElasticSearch", :hosts=\>["[http://host.docker.internal:9200](http://host.docker.internal:9200)"]} [2018-06-03T22:52:19,704][INFO][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=\>{:removed=\>[], :added=\>[[http://logstash\_system:xxxxxx@host.docker.internal:9200/](http://logstash_system:xxxxxx@host.docker.internal:9200/)]}} [2018-06-03T22:52:19,705][INFO][logstash.licensechecker.licensereader] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://logstash\_system:xxxxxx@host.docker.internal:9200/](http://logstash_system:xxxxxx@host.docker.internal:9200/), :path=\>"/"} [2018-06-03T22:52:19,719][WARN][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=\>"[http://logstash\_system:xxxxxx@host.docker.internal:9200/](http://logstash_system:xxxxxx@host.docker.internal:9200/)"} [2018-06-03T22:52:19,726][INFO][logstash.licensechecker.licensereader] ES Output version determined {:es\_version=\>6} [2018-06-03T22:52:19,727][WARN][logstash.licensechecker.licensereader] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} [2018-06-03T22:52:19,846][INFO][logstash.pipeline] Pipeline started successfully {:pipeline\_id=\>".monitoring-logstash", :thread=\>"#\"} [2018-06-03T22:52:20,223][ERROR][logstash.outputs.elasticsearch] Unknown setting 'protocol' for elasticsearch [2018-06-03T22:52:20,244][ERROR][logstash.agent] Failed to execute action {:action=\>LogStash::PipelineAction::Create/pipeline\_id:main, :exception=\>"LogStash::ConfigurationError", :message=\>"Something is wrong with your configuration."... ---
**Author:** ![Michael\_Hatch](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Michael\_Hatch](https://discuss.elastic.co/u/Michael_Hatch)\ **Post date:** [June 4, 2018, 12:24am UTC](https://discuss.elastic.co/t/generic-something-is-wrong-with-your-configuration/134342/2 "2018-06-04T00:24:28Z")
Well I've narrowed it down to something wrong w/ the output. When I change the output from elasticsearch to stdout json codes, the pipeline builds fine. ---
**Author:** ![Michael\_Hatch](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Michael\_Hatch](https://discuss.elastic.co/u/Michael_Hatch)\ **Post date:** [June 4, 2018, 12:50am UTC](https://discuss.elastic.co/t/generic-something-is-wrong-with-your-configuration/134342/3 "2018-06-04T00:50:36Z")
Staring me right in the face. I should read logs better! `Unknown setting 'protocol' for elasticsearch` ---
**Author:** ![inhinyera16](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/inhinyera16/32/61625_2.png) [@inhinyera16](https://discuss.elastic.co/u/inhinyera16)\ **Post date:** [June 4, 2018, 9:16am UTC](https://discuss.elastic.co/t/generic-something-is-wrong-with-your-configuration/134342/4 "2018-06-04T09:16:47Z")
in your logstash config output.. Remove the protocol config. Theres no such protocol config in logstash elasticsearch output. [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 2, 2018, 9:16am UTC](https://discuss.elastic.co/t/generic-something-is-wrong-with-your-configuration/134342/5 "2018-07-02T09:16:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.