Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

bind error has no bind information

Description

The error message:

Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (EADDRINUSE) Address already in use - bind - Address already in use
at org.jruby.ext.socket.RubyTCPServer.initialize(org/jruby/ext/socket/RubyTCPServer.java:118)
at org.jruby.RubyIO.new(org/jruby/RubyIO.java:879)
at RUBY.register(file:/home/kuehna/t/logstash/logstash-1.1.7-monolithic.jar!/logstash/inputs/tcp.rb:45)
at RUBY.run_input(file:/home/kuehna/t/logstash/logstash-1.1.7-monolithic.jar!/logstash/agent.rb:707)
at org.jruby.ext.thread.Mutex.synchronize(org/jruby/ext/thread/Mutex.java:149)
at RUBY.run_input(file:/home/kuehna/t/logstash/logstash-1.1.7-monolithic.jar!/logstash/agent.rb:707)
at RUBY.start_input(file:/home/kuehna/t/logstash/logstash-1.1.7-monolithic.jar!/logstash/agent.rb:367)

doesn't say what (IPORT) it tried to bind to.

discovered while testing

Gliffy Diagrams

Activity

Show:

Philippe Weber February 5, 2014 at 8:45 AM

with 1.3.3, the current output is

Raising a ConfigurationError in tcp input would permits to have a complete message as reported error. I will have a look soon

David Neudorfer July 15, 2013 at 7:06 PM

I seem to be getting the same error on 1.1.13 http://pastebin.com/L32tjCNk Any suggestions?

Jordan Sissel January 10, 2013 at 7:41 AM

Here's what it looks like now if you get a conflict:

Fixed

Details

Assignee

Reporter

Labels

Fix versions

Affects versions

Created January 9, 2013 at 12:49 PM
Updated February 14, 2015 at 2:35 AM
Resolved January 10, 2013 at 7:43 AM