# Logstash communication fails to ES with x-pack with user logstash\_internal

**URL:** https://discuss.elastic.co/t/logstash-communication-fails-to-es-with-x-pack-with-user-logstash-internal/184182
**Category:** Logstash
**Created:** [June 4, 2019, 12:50pm UTC](https://discuss.elastic.co/t/logstash-communication-fails-to-es-with-x-pack-with-user-logstash-internal/184182 "2019-06-04T12:50:13Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![dsmteam](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@dsmteam](https://discuss.elastic.co/u/dsmteam)
#### Post date: [June 4, 2019, 12:50pm UTC](https://discuss.elastic.co/t/logstash-communication-fails-to-es-with-x-pack-with-user-logstash-internal/184182/1 "2019-06-04T12:50:13Z")

</div>

I'm trying to setup latest ELK stack with x-pack but i'm failing on the last step which is communication between logstash and ES

I have put username/password in my output.conf file for logstash and it's properly created on ES with Kibana GUI. Role is setup as per documentation [https://www.elastic.co/guide/en/logstash/7.1/ls-security.html#ls-monitoring-user](https://www.elastic.co/guide/en/logstash/7.1/ls-security.html#ls-monitoring-user)

Everything is working fine if I use the default master "elastic" username but i'm getting the cryptic error as show below when using the logstash\_writer user.  
I can confirm it's not a password issue as i'm getting a 401 error when I put a wrong password in my output.conf file

This is my conf

output {  
elasticsearch {  
hosts =\> ["[http://localhost:9200](http://localhost:9200)"]  
user =\> ["logstash\_internal"]  
password =\> ["somepassword"]  
manage\_template =\> ["false"]  
template\_name =\> ["logstash"] }  
}

I'm not sure what i'm doing wrong here...

[2019-06-04T14:17:49,901][FATAL][logstash.runner] An unexpected error occurred! {:error=\>#\<LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError\>, :backtrace=\>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client/manticore\_adapter.rb:80:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:291:in`perform\_request\_to\_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:278:in `block in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:373:in`with\_connection'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:277:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:285:in`block in Pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http\_client.rb:341:in `exists?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:359:in`rollover\_alias\_exists?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/ilm.rb:91:in `maybe_create_rollover_alias'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/ilm.rb:10:in`setup\_ilm'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.1.0-java/lib/logstash/outputs/elasticsearch/common.rb:52:in `block in setup\_after\_successful\_connection'"]}  
[2019-06-04T14:17:50,097][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

---

<div class="post-metadata">

### Author: ![pastechecker](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pastechecker](https://discuss.elastic.co/u/pastechecker)
#### Post date: [June 4, 2019, 1:57pm UTC](https://discuss.elastic.co/t/logstash-communication-fails-to-es-with-x-pack-with-user-logstash-internal/184182/2 "2019-06-04T13:57:28Z")

</div>

```
input {}
filter {}

output {
elasticsearch {
hosts => ["http://localhost:9200"]
user => "logstash_internal"
password => "somepassword"
manage_template => "false"
template_name => "logstash"
}
}

```

Configuration OK  
[INFO] 2019-06-04 15:54:47.199 [LogStash::Runner] runner - Using config.test\_and\_exit mode. Config Validation Result: OK. Exiting Logstash

Can you remove the template\_name and try again?

Your problem looks similar to the: [Failed to install template logstash error](https://discuss.elastic.co/t/failed-to-install-template-logstash-error/176646/2)

---

<div class="post-metadata">

### Author: ![dsmteam](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@dsmteam](https://discuss.elastic.co/u/dsmteam)
#### Post date: [June 5, 2019, 8:17am UTC](https://discuss.elastic.co/t/logstash-communication-fails-to-es-with-x-pack-with-user-logstash-internal/184182/3 "2019-06-05T08:17:04Z")

</div>

After removing template\_name =\> same error  
Also no change without manage\_template...

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 3, 2019, 8:17am UTC](https://discuss.elastic.co/t/logstash-communication-fails-to-es-with-x-pack-with-user-logstash-internal/184182/4 "2019-07-03T08:17:04Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
