# Logstash 2.1.1 Fresh ELK Install Errors

**URL:** <https://discuss.elastic.co/t/logstash-2-1-1-fresh-elk-install-errors/38370>\
**Category:** Logstash\
**Created:** [January 5, 2016, 5:50am UTC](https://discuss.elastic.co/t/logstash-2-1-1-fresh-elk-install-errors/38370 "2016-01-05T05:50:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ninjada](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@ninjada](https://discuss.elastic.co/u/ninjada)\
**Post date:** [January 5, 2016, 5:50am UTC](https://discuss.elastic.co/t/logstash-2-1-1-fresh-elk-install-errors/38370/1 "2016-01-05T05:50:26Z")

</div>

Hi Guys,

Presently updating my ELK stack a few versions behind to new servers running the latest versions.

At first I got some error:

> you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with lock\_jars command

> no such file to load -- org/apache/httpcomponents/httpclient/4.5/httpclient-4.5 (LoadError)

Theres another thread: [Logstash 2.1 fails to start after logstash-output-elasticsearch update](https://discuss.elastic.co/t/logstash-2-1-fails-to-start-after-logstash-output-elasticsearch-update/38330) -- with some suggestions which I tried amongst other things but that did not fix the problem for me...

I deployed everything from scratch again without running '/opt/logstash/bin/plugin update' and the above error is gone but i get the following error upon starting logstash:

> :timestamp=\>"2016-01-05T15:58:34.881000+1100", :message=\>"Connection refused", :class=\>"Manticore::SocketException", :level=\>:error}

It doesn't appeared to have stopped things, as logs start ingesting ok as far as I can tell.. but I'm just wondering what it relates to and whats happening etc... so I can get rid of this error. Hadn't had an issue with Manticore previously.

Cheers!

---

<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:** [January 5, 2016, 6:40am UTC](https://discuss.elastic.co/t/logstash-2-1-1-fresh-elk-install-errors/38370/2 "2016-01-05T06:40:35Z")

</div>

The latter error messages suggests that you've configured Logstash (probably the elasticsearch output) to connect to a port where nothing was listening, at least not at the time. Perhaps you started Logstash before Elasticsearch had started up completely?

---

<div class="post-metadata">

**Author:** ![ninjada](https://avatars.discourse-cdn.com/v4/letter/n/5daacb/32.png) [@ninjada](https://discuss.elastic.co/u/ninjada)\
**Post date:** [January 7, 2016, 3:12am UTC](https://discuss.elastic.co/t/logstash-2-1-1-fresh-elk-install-errors/38370/3 "2016-01-07T03:12:24Z")

</div>

ah yep looks like it was just temporary, hasn't appeared again!

---

<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 6, 2017, 5:16am UTC](https://discuss.elastic.co/t/logstash-2-1-1-fresh-elk-install-errors/38370/4 "2017-07-06T05:16:36Z")

</div>