# Ther is no output being shown on the command prompt even after clearing .sincedb file **URL:** \ **Category:** Logstash\ **Created:** [June 18, 2019, 7:43am UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198 "2019-06-18T07:43:28Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![deepanshu\_goel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepanshu_goel/32/48061_2.png) [@deepanshu\_goel](https://discuss.elastic.co/u/deepanshu_goel)\ **Post date:** [June 18, 2019, 7:43am UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/1 "2019-06-18T07:43:28Z")
configuration file: input { file { ```auto path=>"\E:\kibana\logstash-7.1.1\logstash-7.1.1\data\event-data\apache_access.log" type => "apache-access" start_position=> "beginning" } ``` } output { stdout { ```auto codec=>rubydebug } ``` } after running the logstash this is showig on the command prompt E:\kibana\logstash-7.1.1\logstash-7.1.1\>bin\logstash -f E:\kibana\logstash-7.1.1\logstash-7.1.1\config\pipeline.conf --config.reload.automatic Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.jruby.runtime.encoding.EncodingService (file:/E:/kibana/logstash-7.1.1/logstash-7.1.1/logstash-core/lib/jars/jruby-complete-9.2.7.0.jar) to field java.io.Console.cs WARNING: Please consider reporting this to the maintainers of org.jruby.runtime.encoding.EncodingService WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Sending Logstash logs to E:/kibana/logstash-7.1.1/logstash-7.1.1/logs which is now configured via log4j2.properties [2019-06-13T15:45:30,346][WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified [2019-06-13T15:45:30,367][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"7.1.1"} [2019-06-13T15:45:33,523][INFO][logstash.javapipeline] Starting pipeline {:pipeline\_id=\>"main", "pipeline.workers"=\>4, "pipeline.batch.size"=\>125, "pipeline.batch.delay"=\>50, "pipeline.max\_inflight"=\>500, :thread=\>"#\"} [2019-06-13T15:45:34,761][INFO][logstash.inputs.file] No sincedb\_path set, generating one based on the "path" setting {:sincedb\_path=\>"E:/kibana/logstash-7.1.1/logstash-7.1.1/data/plugins/inputs/file/.sincedb\_0a875bbe5a2659163ba803e0c598bcbc", :path=\>["\E:\kibana\logstash-7.1.1\logstash-7.1.1\data\event-data\apache\_access.log"]} [2019-06-13T15:45:34,812][INFO][logstash.javapipeline] Pipeline started {"pipeline.id"=\>"main"} [2019-06-13T15:45:34,882][INFO][logstash.agent] Pipelines running {:count=\>1, :running\_pipelines=\>[:main], :non\_running\_pipelines=\>} [2019-06-13T15:45:34,911][INFO][filewatch.observingtail] START, creating Discoverer, Watch with file and sincedb collections [2019-06-13T15:45:35,297][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600} (there is no incoming output) ---
**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\ **Post date:** [June 18, 2019, 8:53am UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/2 "2019-06-18T08:53:07Z")
Hi deepanshu, Please format code with the ``` notations, as mentioned in the guidelines or using the editor window. ---
**Author:** ![deepanshu\_goel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepanshu_goel/32/48061_2.png) [@deepanshu\_goel](https://discuss.elastic.co/u/deepanshu_goel)\ **Post date:** [June 18, 2019, 11:34am UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/3 "2019-06-18T11:34:01Z")
Please, can you elaborate. I tried using that but was not able to implement it. ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [June 18, 2019, 1:48pm UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/4 "2019-06-18T13:48:53Z")
> [@deepanshu\_goel](#): > > path=\>"\E:\kibana\logstash-7.1.1\logstash-7.1.1\data\event-data\apache\_access.log" Use forward slash, not backslash, in the path option of a file input. ---
**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\ **Post date:** [June 19, 2019, 4:00am UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/5 "2019-06-19T04:00:47Z")
For windows the notations should be fine, right? Should there be a slash before the drive letter `E`? Try this as path: ```auto E:\kibana\logstash-7.1.1\logstash-7.1.1\data\event-data\apache_access.log ``` ---
**Author:** ![deepanshu\_goel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deepanshu_goel/32/48061_2.png) [@deepanshu\_goel](https://discuss.elastic.co/u/deepanshu_goel)\ **Post date:** [June 19, 2019, 4:46am UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/6 "2019-06-19T04:46:15Z")
I already tried what you are saying but there is no difference and the problem remains the same . ---
**Author:** ![Beer\_Comehere](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/beer_comehere/32/49100_2.png) [@Beer\_Comehere](https://discuss.elastic.co/u/Beer_Comehere)\ **Post date:** [June 30, 2019, 6:54pm UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/7 "2019-06-30T18:54:35Z")
Hi, I had the same problem. Problem is in Windows, you have to use / in path definition, as user Badger have already advised to you. This conf works for me perfectly: input { file { path=\>"e:/Dropbox/\_development\_other/Kibana/MOCK\_DATA1.csv" start\_position =\> "beginning" sincedb\_path =\> "nul" } } output { elasticsearch { hosts =\> ["[http://localhost:9200](http://localhost:9200)"] index =\> "contacts" } stdout{} } ---
**Author:** ![Beer\_Comehere](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/beer_comehere/32/49100_2.png) [@Beer\_Comehere](https://discuss.elastic.co/u/Beer_Comehere)\ **Post date:** [June 30, 2019, 6:55pm UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/8 "2019-06-30T18:55:41Z")
Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 28, 2019, 6:55pm UTC](https://discuss.elastic.co/t/ther-is-no-output-being-shown-on-the-command-prompt-even-after-clearing-sincedb-file/186198/9 "2019-07-28T18:55:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.