# Logstash struck after Pipeline main started.. No output printed and nothing sent to elastic search
**URL:** https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559
**Category:** Logstash
**Created:** [June 21, 2016, 7:27pm UTC](https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559 "2016-06-21T19:27:09Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@sandeep\_vuppula](https://discuss.elastic.co/u/sandeep_vuppula)
#### Post date: [June 21, 2016, 7:27pm UTC](https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559/1 "2016-06-21T19:27:09Z")
I am using logstash-2.3.3. when i run "logstash -f logstash-workday.conf" it is struck and no output is being displayed.
C:\logstash-2.3.3\bin\>logstash -f logstash-workday.conf
io/console not supported; tty will not be manipulated
Settings: Default pipeline workers: 8
Pipeline main started
logstash-workday.conf : (Input is an file containing some log information and XML content.)
input {
file {
```
path => "C:\logstash-2.3.3\bin\test.xml"
codec => multiline {
# Grok pattern names are valid! :)
pattern => "^%{...}"
negate => true
what => previous
}
}
```
}
filter{
xml{
}
}
output{
stdout {
codec =\> rubydebug
}
}
When i ran "logstash -f logstash-workday.conf --debug" I found these in the logs :
{:timestamp=\>"2016-06-21T11:03:07.383000-0700", :message=\>"Reading config file", :config\_file=\>"C:/logstash-2.3.3/bin/logstash-workday.conf", :level=\>:debug, :file=\>"/logstash-2.3.3/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.3-java/lib/logstash/config/loader.rb", :line=\>"69", :method=\>"local\_config"}
{:timestamp=\>"2016-06-21T11:03:07.709000-0700", :message=\>"Plugin not defined in namespace, checking for plugin file", :type=\>"codec", :name=\>"multiline", :path=\>"logstash/codecs/multiline", :level=\>:debug, :file=\>"/logstash-2.3.3/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.3-java/lib/logstash/plugin.rb", :line=\>"76", :method=\>"lookup"}..... (Its a very long log file ☹ )
Thanks in advance.
---
### Author:  [@marke72](https://discuss.elastic.co/u/marke72)
#### Post date: [June 21, 2016, 10:06pm UTC](https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559/2 "2016-06-21T22:06:53Z")
Is `C:\logstash-2.3.3\bin\test.xml` constantly being updated? Because the `file` plugin reads anything new that is appended to the file. If you want to start from the beginning of the file you need to use the directive `start_position => "beginning"`.
Also seeing as you have already run this config, logstash creates a `.sincedb_` file that you will need to delete. Logstash uses this file to remember where it left off if you were to restart the program.
---
### Author:  [@sandeep\_vuppula](https://discuss.elastic.co/u/sandeep_vuppula)
#### Post date: [June 21, 2016, 10:09pm UTC](https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559/3 "2016-06-21T22:09:15Z")
No the file is not being constantly updated. So i added
ignore\_older =\> 0
the directive start\_position =\> "beginning" is already present and
each time I am deleting the .sincedb\_file before i execute the logstash.
---
### Author:  [@sandeep\_vuppula](https://discuss.elastic.co/u/sandeep_vuppula)
#### Post date: [June 21, 2016, 10:25pm UTC](https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559/4 "2016-06-21T22:25:24Z")
I found the issue.
The test.xml file has only one event.
Now when the codec is executed in the input plugin, it waits for the next event then only the previous one will be published/printed.
codec =\> multiline {
# Grok pattern names are valid! 🙂
pattern =\> "^%{...}"
negate =\> true
what =\> previous
}
As soon as I added one more event, BOOM the output appeared.
Thank you 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:51am UTC](https://discuss.elastic.co/t/logstash-struck-after-pipeline-main-started-no-output-printed-and-nothing-sent-to-elastic-search/53559/5 "2017-07-06T04:51:22Z")