SocketError: send: name or service not known - logstash 2.3.4 version

Elastic Stack Logstash
1

Logstash agent configuration:

input {
heartbeat {
type => "heartbeat"
interval => 60
add_field => { "app.name" => "esper" }
}
file {
path => "/home/pg/pg-services/esper/log/json/esper.json"
codec => json
sincedb_path => "/home/release/release_independent/elk/logstash/data/sincedb/.sincedb"
}
}
output {
udp {
host => "10.166.184.133"
port => 7400
codec => json
}
}

This configuration was working fine for some time and suddenly we are getting the below exception and logstash agenent if getting killed.
Any idea what is going wrong.

SocketError: send: name or service not known
send at org/jruby/ext/socket/RubyUDPSocket.java:318
register at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-output-udp-2.0.4/lib/logstash/outputs/udp.rb:24
call at org/jruby/RubyProc.java:281
encode at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-codec-json-2.1.4/lib/logstash/codecs/json.rb:42
receive at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-output-udp-2.0.4/lib/logstash/outputs/udp.rb:31
multi_receive at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:83
each at org/jruby/RubyArray.java:1613
multi_receive at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/outputs/base.rb:83
worker_multi_receive at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output_delegator.rb:130
multi_receive at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/output_delegator.rb:114
output_batch at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:301
each at org/jruby/RubyHash.java:1342
output_batch at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:301
worker_loop at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:232
start_workers at /home/release/release_independent/elk/logstash/logstash-2.3.4/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.4-java/lib/logstash/pipeline.rb:201

2

we identified the root cause for the problem.
As json file getting generated by application and with the recent changes in application is logging very huge data in single line. When agent tries to send this line to UDP server, it failing throwing the exception. Because of this exception logstash agent is getting killed.

3

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