Pushing flush onto pipeline error

Elastic Stack Logstash
1

i want to start logstash with a custom configuration and showing the result in stdout but I've alwyas this logs ..Ididn't understand the probllem .. can anyone help me thanks

[2018-07-11T11:46:32,944][INFO ][logstash.pipeline ] Pipeline started successfully {:pipeline_id=>"main", :thread=>"#<Thread:0x2af1a27a run>"}
[2018-07-11T11:46:33,041][INFO ][logstash.agent ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}
[2018-07-11T11:46:33,110][DEBUG][logstash.agent ] Starting puma
[2018-07-11T11:46:33,128][DEBUG][logstash.agent ] Trying to start WebServer {:port=>9600}
[2018-07-11T11:46:33,188][DEBUG][logstash.inputs.file ] _globbed_files: /home/ubuntu/LOG/logbotool/log27-04-2016/log: glob is: ["/home/ubuntu/LOG/logbotool/log27-04-2016/log"]
[2018-07-11T11:46:33,193][DEBUG][logstash.inputs.file ] _discover_file: /home/ubuntu/LOG/logbotool/log27-04-2016/log: new: /home/ubuntu/LOG/logbotool/log27-04-2016/log (exclude is [])
[2018-07-11T11:46:33,197][DEBUG][logstash.api.service ] [api-service] start
[2018-07-11T11:46:33,348][DEBUG][logstash.inputs.file ] _open_file: /home/ubuntu/LOG/logbotool/log27-04-2016/log: opening
[2018-07-11T11:46:33,364][DEBUG][logstash.inputs.file ] /home/ubuntu/LOG/logbotool/log27-04-2016/log: sincedb last value 376, cur size 376
[2018-07-11T11:46:33,375][DEBUG][logstash.inputs.file ] /home/ubuntu/LOG/logbotool/log27-04-2016/log: sincedb: seeking to 376
[2018-07-11T11:46:33,461][DEBUG][logstash.agent ] Trying to start WebServer {:port=>9601}
[2018-07-11T11:46:33,463][DEBUG][logstash.api.service ] [api-service] start
[2018-07-11T11:46:33,478][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9601}
[2018-07-11T11:46:33,806][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
[2018-07-11T11:46:33,810][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
[2018-07-11T11:46:37,969][DEBUG][logstash.pipeline ] Pushing flush onto pipeline {:pipeline_id=>"main", :thread=>"#<Thread:0x2af1a27a sleep>"}
[2018-07-11T11:46:38,818][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
[2018-07-11T11:46:38,819][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
[2018-07-11T11:46:42,971][DEBUG][logstash.pipeline ] Pushing flush onto pipeline {:pipeline_id=>"main", :thread=>"#<Thread:0x2af1a27a sleep>"}
[2018-07-11T11:46:43,824][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
[2018-07-11T11:46:43,824][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
[2018-07-11T11:46:47,446][DEBUG][logstash.inputs.file ] _globbed_files: /home/ubuntu/LOG/logbotool/log27-04-2016/log: glob is: ["/home/ubuntu/LOG/logbotool/log27-04-2016/log"]
[2018-07-11T11:46:47,971][DEBUG][logstash.pipeline ] Pushing flush onto pipeline {:pipeline_id=>"main", :thread=>"#<Thread:0x2af1a27a sleep>"}
[2018-07-11T11:46:48,830][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
[2018-07-11T11:46:48,831][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
[2018-07-11T11:46:52,972][DEBUG][logstash.pipeline ] Pushing flush onto pipeline {:pipeline_id=>"main", :thread=>"#<Thread:0x2af1a27a sleep>"}

2

"Pushing flush onto pipeline" isn't an error message, it's a debug-level message that's rarely something to pay attention to.

Logstash is currently waiting for more data to be added to the end of /home/ubuntu/LOG/logbotool/log27-04-2016/log.

2 Likes
3

thank you

4

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