# Logstash talking to rubygems.org during running?

**URL:** <https://discuss.elastic.co/t/logstash-talking-to-rubygems-org-during-running/40424>\
**Category:** Logstash\
**Created:** [January 28, 2016, 11:19pm UTC](https://discuss.elastic.co/t/logstash-talking-to-rubygems-org-during-running/40424 "2016-01-28T23:19:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vnagendra](https://avatars.discourse-cdn.com/v4/letter/v/ecd19e/32.png) [@vnagendra](https://discuss.elastic.co/u/vnagendra)\
**Post date:** [January 28, 2016, 11:19pm UTC](https://discuss.elastic.co/t/logstash-talking-to-rubygems-org-during-running/40424/1 "2016-01-28T23:19:32Z")

</div>

Is there a scenario under which AFTER the configuration files have been checked and plugins are downloaded, logstash would try to talk to [rubygems.org](http://rubygems.org)?

I have logstash version `logstash 2.1.0`. I have checked the configuration files with `--configtest` option and it checks out okay ..

```auto
/opt/logstash/bin/logstash --configtest -f logstash
DEBUG: exec /opt/logstash/vendor/jruby/bin/jruby --1.9 -J-XX:+UseParNewGC -J-XX:+UseConcMarkSweepGC -J-Djava.awt.headless=true -J-XX:CMSInitiatingOccupancyFraction=75 -J-XX:+UseCMSInitiatingOccupancyOnly -J-XX:+HeapDumpOnOutOfMemoryError -J-XX:HeapDumpPath=/opt/logstash/heapdump.hprof -J-Xmx1g /opt/logstash/lib/bootstrap/environment.rb logstash/runner.rb agent --configtest -f logstash
Configuration OK

```

However once logstash is started, it exits saying this

```auto
DEBUG: exec /opt/logstash/vendor/jruby/bin/jruby --1.9 -J-XX:+UseParNewGC -J-XX:+UseConcMarkSweepGC -J-Djava.awt.headless=true -J-XX:CMSInitiatingOccupancyFraction=75 -J-XX:+UseCMSInitiatingOccupancyOnly -J-XX:+HeapDumpOnOutOfMemoryError -J-XX:HeapDumpPath=/opt/logstash/heapdump.hprof -J-Xmx1g /opt/logstash/lib/bootstrap/environment.rb logstash/runner.rb agent -f /opt/logstash
The error reported is:
  initialize: name or service not known

```

The plugins that I am using in the configuration are installed (as verified by `plugin list`) - In case it helps, I am using `logstash-input-sqs, logstash-output-sns, logstash-output-tcp, logstash-filter-mutate`. They are all installed

I understand the error "initialize: name or service not known" has to do with connectivity from my docker container to [rubygems.org](http://rubygems.org). That's cool - except if all the preconditions above are satisfied, it should NOT talk to rubygems.

Is there a dependency that is obvious and I am missing it?

Thanks for any new ideas on what to look at.

Edit: I just verified, connectivity to [rubygems.org](http://rubygems.org) is broken (my entire docker container is having connectivity issues). I fully intend to fix the underlying problem of connectivity - but curious to understand _why_ logstash would be trying to talk to [rubygems.org](http://rubygems.org) during running...

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 28, 2016, 11:36pm UTC](https://discuss.elastic.co/t/logstash-talking-to-rubygems-org-during-running/40424/2 "2016-01-28T23:36:07Z")

</div>

> [@vnagendra](#):
>
> I understand the error "initialize: name or service not known" has to do with connectivity from my docker container to [rubygems.org](http://rubygems.org). That's cool - except if all the preconditions above are satisfied, it should NOT talk to rubygems.

How do you know it's rubygems, did you do any packet sniffing to see or is it just a guess?

I'd suggest that it's probably something in your config that cannot resolve the network address in there.

---

<div class="post-metadata">

**Author:** ![vnagendra](https://avatars.discourse-cdn.com/v4/letter/v/ecd19e/32.png) [@vnagendra](https://discuss.elastic.co/u/vnagendra)\
**Post date:** [January 29, 2016, 1:47am UTC](https://discuss.elastic.co/t/logstash-talking-to-rubygems-org-during-running/40424/3 "2016-01-29T01:47:00Z")

</div>

Brilliant thinking! It was a guess. It was one of the other things in my configuration - which happened to have hosts for ES, some TCP hosts, and a bunch of other things. The problem was network connectivity, it just was NOT to [rubygems.org](http://rubygems.org) ..

@Mark - thanks! Appreciate your suggestion, which helped me trace 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:** [July 6, 2017, 5:13am UTC](https://discuss.elastic.co/t/logstash-talking-to-rubygems-org-during-running/40424/4 "2017-07-06T05:13:50Z")

</div>

Closed on July 6, 2017, 5:13am UTC