#
path.data: /var/lib/logstash
#
pipeline.workers: 2
#
# How many workers should be used per output plugin instance
#
pipeline.output.workers: 1
#
pipeline.batch.size: 125
#
#
pipeline.batch.delay: 5
# #he pipeline configuration for the main pipeline
#
path.config: /etc/logstash/conf.d/*
#
#
#
# log.level: info
path.logs: /var/log/logstash
#
# ------------ Other Settings --------------
#
# Where to find custom plugins
# path.plugins:
my error :2017-08-29T16:57:27,428][INFO ][logstash.pipeline ] Pipeline main started [2017-08-29T16:57:27,429][INFO ][logstash.inputs.udp ] Starting UDP listener {:address=>"1.1.1.55:9556"} [2017-08-29T16:57:27,445][INFO ][logstash.inputs.udp ] UDP listener started {:address=>"1.1.1.55:9556", :receive_buffer_bytes=>"106496", :queue_size=>"2000"} [2017-08-29T16:57:27,452][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600} [2017-08-29T17:01:30,404][INFO ][logstash.runner ] Using config.test_and_exit mode. Config Validation Result: OK. Exiting Logstash [2017-08-29T17:01:41,465][WARN ][logstash.runner ] SIGTERM received. Shutting down the agent. [2017-08-29T17:01:41,473][WARN ][logstash.agent ] stopping pipeline {:id=>"main"} [2017-08-29T17:01:41,832][WARN ][logstash.inputs.udp ] UDP listener died {:exception=>#<IOError: closed stream>, :backtrace=>["org/jruby/RubyIO.java:3705:in select'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-udp-3.1.1/lib/logstash/inputs/udp.rb:93:in udp_listener'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-udp-3.1.1/lib/logstash/inputs/udp.rb:56:in run'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:456:in inputworker'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:449:in start_input'"]}`
Do you mean that you see the traffic arriving into that host/port?
Test first with an console output instead of Elasticsearch (or in addition to) to see if at least it is processed.
Actually you could also check the logstash API endpoint to see if there are events processed
first :
when my elk server can't communicate with my network equipment but i can see the netflow in it network interface with tcpdump, i have no data processed
second case :
when my elk server can communicate with my network equipment and i can see the netflow in it network interface with tcpdump, i have data processed
it does not mean anything, with UDP there is not communication as in TCP
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.