# Logstash Pipeline Main Started, yet no output
**URL:** https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375
**Category:** Logstash
**Created:** [July 13, 2016, 6:10am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375 "2016-07-13T06:10:05Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Rohit\_Shukla](https://discuss.elastic.co/u/Rohit_Shukla)
#### Post date: [July 13, 2016, 6:10am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375/1 "2016-07-13T06:10:05Z")
Hi,
Yesterday I was able to read the file sent it to Elasticsearch and view it in Kibana using below config:
```
input {
file {
path => "C:/ELK/logstash/bin/data/TestSysData"
start_position => beginning
}
}
filter {
multiline {
pattern => "^\A%{SYSLOG5424SD}"
negate => true
what => previous
}
grok{
match => { "message" => "\A%{JAVALOGMESSAGE}"}
}
}
output {
stdout { codec => rubydebug }
}
```
Today I tried to ran the same config again to read older as well as newer file - all i get is "Pipeline main started" and nothing happens.
Things I already tried:
1. setting ignore\_older and sincedb\_path =\> "NUL" in input.
2. manually pressing ENTER at end of log file so logstash gets the file end (lot if online resources talked about this)
This worked flawless since I started learning logstash a week ago but this abrupt break is derailing me.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 13, 2016, 6:12am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375/2 "2016-07-13T06:12:18Z")
Increase logging verbosity by starting Logstash with `--verbose` or even `--debug` will provide clues.
---
### Author:  [@Rohit\_Shukla](https://discuss.elastic.co/u/Rohit_Shukla)
#### Post date: [July 13, 2016, 6:40am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375/3 "2016-07-13T06:40:28Z")
Well, -v or -verbose were not helpful
But in vis --debug I saw few line kept repeating itself
←[36mPushing flush onto pipeline {:level=\>:debug, :file=\>"/ELK/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.3-java/lib/logstash/pipeline.rb", :line=\>"458", :method=\>"flush"}←[0m
←[36mPushing flush onto pipeline {:level=\>:debug, :file=\>"/ELK/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.3-java/lib/logstash/pipeline.rb", :line=\>"458", :method=\>"flush"}←[0m
←[36mPushing flush onto pipeline {:level=\>:debug, :file=\>"/ELK/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.3-java/lib/logstash/pipeline.rb", :line=\>"458", :method=\>"flush"}←[0m
←[36m\_globbed\_files: C:/ELK/logstash/bin/data/new5.log: glob is: [] {:level=\>:debug, :file=\>"/ELK/logstash/vendor/bundle/jruby/1.9/gems/filewatch-0.8.1/lib/filewatch/watch.rb", :line=\>"346", :method
=\>"\_globbed\_files"}←[0m
entire debug info here:
[Doc](https://docs.google.com/document/d/1P4InHbVYArSppoauYfGzbfYjSPFIAqjI7PiNa917e_s/edit?usp=sharing)
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [July 13, 2016, 7:18am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375/4 "2016-07-13T07:18:25Z")
```
_globbed_files: C:/ELK/logstash/bin/data/new5.log: glob is: [] {:level=>:debug, :file=>"/ELK/logstash/vendor/bundle/jruby/1.9/gems/filewatch-0.8.1/lib/filewatch/watch.rb", :line=>"346", :method =>"_globbed_files"}
```
Logstash doesn't think C:/ELK/logstash/bin/data/new5.log exists. Either that's the case or lack of permissions is stopping Logstash from accessing one of the directories leading up to the file.
---
### Author:  [@Rohit\_Shukla](https://discuss.elastic.co/u/Rohit_Shukla)
#### Post date: [July 13, 2016, 9:09am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375/5 "2016-07-13T09:09:33Z")
Oh that is so silly of me.
I messed up the file extension name. Fixed and working as before,
Thanks 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:48am UTC](https://discuss.elastic.co/t/logstash-pipeline-main-started-yet-no-output/55375/6 "2017-07-06T04:48:15Z")