# Logstash 5 installation and configuration problem

**URL:** <https://discuss.elastic.co/t/logstash-5-installation-and-configuration-problem/65624>\
**Category:** Logstash\
**Created:** [November 10, 2016, 10:09am UTC](https://discuss.elastic.co/t/logstash-5-installation-and-configuration-problem/65624 "2016-11-10T10:09:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pavel\_Amorok](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pavel_amorok/32/13087_2.png) [@Pavel\_Amorok](https://discuss.elastic.co/u/Pavel_Amorok)\
**Post date:** [November 10, 2016, 10:09am UTC](https://discuss.elastic.co/t/logstash-5-installation-and-configuration-problem/65624/1 "2016-11-10T10:09:47Z")

</div>

java -version  
java version "1.8.0\_73"  
Java(TM) SE Runtime Environment (build 1.8.0\_73-b02)  
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)

CentOS Linux release 7.2.1511 (Core)

**/usr/share/logstash/bin/logstash --configtest**  
INFO: Logstash requires a setting file which is typically located in $LS\_HOME/config or /etc/logstash. If you installed Logstash through a package and are starting it manually please specify the location to this settings file by passing in "--path.settings=/path/.."  
ERROR: Failed to load settings file from "path.settings". Aborting... path.setting=/usr/share/logstash/config, exception=Errno::ENOENT, message=\>No such file or directory - /usr/share/logstash/config/logstash.yml

**[root@kibana ~]# /etc/logstash/conf.d/config.conf -f /etc/logstash/conf.d/config.conf --configtest --debug**  
-bash: /etc/logstash/conf.d/config.conf: Permission denied

**/etc/logstash/conf.d/config.conf**

input {  
udp {

port =\> 5514  
type =\> "syslog"  
}  
}  
output {  
elasticsearch {  
hosts =\> ["localhost:9200"]  
sniffing =\> true  
manage\_template =\> false  
index =\> "mikrotik-%{+YYYY.MM.dd}"  
document\_type =\> "%{type}"  
}  
}

**[root@kibana ~]# netstat -ntulp | grep 5514**  
udp6 213440 0 :::5514 :::\* 616/java

**logstash-plain.log**  
[2016-11-10T12:40:05,256][WARN][logstash.outputs.elasticsearch] UNEXPECTED POOL ERROR {:e=\>#\<LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError: No Available connections\>}  
[2016-11-10T12:40:05,257][WARN][logstash.outputs.elasticsearch] Elasticsearch output attempted to sniff for new connections but cannot. No living connections are detected. Pool contains the following current URLs {:url\_info=\>{}}  
[2016-11-10T12:40:08,012][WARN][logstash.outputs.elasticsearch] UNEXPECTED POOL ERROR {:e=\>#\<LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError: No Available connections\>}  
[2016-11-10T12:40:08,013][ERROR][logstash.outputs.elasticsearch] Attempted to send a bulk request to elasticsearch, but no there are no living connections in the connection pool. Perhaps Elasticsearch is unreachable or down? {:error\_message=\>"No Available connections", :class=\>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError", :will\_retry\_in\_seconds=\>16}  
[2016-11-10T12:40:10,259][WARN][logstash.outputs.elasticsearch] UNEXPECTED POOL ERROR {:e=\>#\<LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError: No Available connections\>}

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [November 12, 2016, 6:10pm UTC](https://discuss.elastic.co/t/logstash-5-installation-and-configuration-problem/65624/2 "2016-11-12T18:10:47Z")

</div>

Disabling sniffing should work around the problem.

---

<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:** [December 10, 2016, 6:11pm UTC](https://discuss.elastic.co/t/logstash-5-installation-and-configuration-problem/65624/3 "2016-12-10T18:11:06Z")

</div>

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