{"action":"closed","issue":{"url":"https://api.github.com/repos/elastic/logstash/issues/1745","labels_url":"https://api.github.com/repos/elastic/logstash/issues/1745/labels{/name}","comments_url":"https://api.github.com/repos/elastic/logstash/issues/1745/comments","events_url":"https://api.github.com/repos/elastic/logstash/issues/1745/events","html_url":"https://github.com/elastic/logstash/issues/1745","id":42913961,"number":1745,"title":"Bad dns/hosts entry for elasticsearch_http output causes Logstash to crash with no error logged","user":{"login":"jerrac","id":910764,"avatar_url":"https://avatars.githubusercontent.com/u/910764?v=3","gravatar_id":"","url":"https://api.github.com/users/jerrac","html_url":"https://github.com/jerrac","followers_url":"https://api.github.com/users/jerrac/followers","following_url":"https://api.github.com/users/jerrac/following{/other_user}","gists_url":"https://api.github.com/users/jerrac/gists{/gist_id}","starred_url":"https://api.github.com/users/jerrac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jerrac/subscriptions","organizations_url":"https://api.github.com/users/jerrac/orgs","repos_url":"https://api.github.com/users/jerrac/repos","events_url":"https://api.github.com/users/jerrac/events{/privacy}","received_events_url":"https://api.github.com/users/jerrac/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2014-09-16T18:11:31Z","updated_at":"2015-05-16T18:12:26Z","closed_at":"2015-05-16T18:12:26Z","body":"I had elasticsearch_http pointing at a nonexistant dns/hosts entry. This caused logstash to crash. Upstart kept trying to restart it, leading me to wonder why the logstash.log file was being filled with start up entries over an over again. Eventually, thanks to torrancew on IRC, I tried stopping it, then running it manually. Got this:\r\n\r\n```\r\nroot@hostname:/opt/logstash# bin/logstash -f /etc/logstash/conf.d/ \r\nUsing milestone 2 filter plugin 'kv'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see http://logstash.net/docs/1.4.2/plugin-milestones {:level=>:warn}\r\nUsing milestone 2 input plugin 'file'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see http://logstash.net/docs/1.4.2/plugin-milestones {:level=>:warn}\r\nUsing milestone 1 input plugin 'lumberjack'. This plugin should work, but would benefit from use by folks like you. Please let us know if you find bugs or have suggestions on how to improve this plugin.  For more information on plugin milestones, see http://logstash.net/docs/1.4.2/plugin-milestones {:level=>:warn}\r\nUsing milestone 2 output plugin 'elasticsearch_http'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see http://logstash.net/docs/1.4.2/plugin-milestones {:level=>:warn}\r\nThe 'grep' plugin is no longer necessary now that you can do if/elsif/else in logstash configs. This plugin will be removed in the future. If you need to drop events, please use the drop filter. If you need to take action based on a match, use an 'if' block and the mutate filter. See the following URL for details on how to use if/elsif/else in your logstash configs:http://logstash.net/docs/1.4.2/configuration {:level=>:warn}\r\nSocketError: gethostbyname: name or service not known\r\n  gethostbyname at org/jruby/ext/socket/RubySocket.java:286\r\n        resolve at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/dns/dns.rb:13\r\n        resolve at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/dns.rb:38\r\n           each at org/jruby/RubyArray.java:1613\r\n         inject at org/jruby/RubyEnumerable.java:865\r\n        resolve at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/dns.rb:37\r\n        connect at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/connection.rb:137\r\n        connect at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/agent.rb:406\r\n           call at org/jruby/RubyProc.java:271\r\n          fetch at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/pool.rb:48\r\n        connect at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/agent.rb:403\r\n        execute at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/agent.rb:319\r\n           get! at /opt/logstash/vendor/bundle/jruby/1.9/gems/ftw-0.0.39/lib/ftw/agent.rb:217\r\n       register at /opt/logstash/lib/logstash/outputs/elasticsearch_http.rb:109\r\n           each at org/jruby/RubyArray.java:1613\r\n   outputworker at /opt/logstash/lib/logstash/pipeline.rb:220\r\n  start_outputs at /opt/logstash/lib/logstash/pipeline.rb:152\r\n```\r\n\r\nWhy wasn't that error logged in logstash.log or syslog when upstart was bouncing it?"}}