# Can't parse Linux OS generated log files in windows environment with file input plugin

**URL:** https://discuss.elastic.co/t/cant-parse-linux-os-generated-log-files-in-windows-environment-with-file-input-plugin/43209
**Category:** Logstash
**Created:** [March 2, 2016, 8:11am UTC](https://discuss.elastic.co/t/cant-parse-linux-os-generated-log-files-in-windows-environment-with-file-input-plugin/43209 "2016-03-02T08:11:27Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![guojingjing](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guojingjing/32/8205_2.png) [@guojingjing](https://discuss.elastic.co/u/guojingjing)
#### Post date: [March 3, 2016, 8:16am UTC](https://discuss.elastic.co/t/cant-parse-linux-os-generated-log-files-in-windows-environment-with-file-input-plugin/43209/3 "2016-03-03T08:16:04Z")

</div>

Thanks for the detailed reply.

It turns out the cause to my problem is the fact that my log files are too old. The post I stumbled into helped:

> [@Logstash not showing any output (SOLVED)](https://discuss.elastic.co/t/logstash-not-showing-any-output-solved/28636):
>
> I'm starting off with Logstash, working through the tutorials. I find the plugin documentation very lacking for someone with no experience with logstash. Here is the config file I am starting with: input { file { path =\> "/Users/brad/Workspaces/unirisk.python/logstash/files/perflog.csv" start\_position =\> beginning } } output { stdout { } } I am running logstash on a Macbook Pro, version 1.5.4, installed via homebrew. My startup is: logstash -f test.conf This s…

As @Wayne_Taylor pointed out, the file plugin seems to have a default setting to not read any log events that are more than 24 hours old.

Is there any way to work around it?

Thanks!

---

_[View the full topic](https://discuss.elastic.co/t/cant-parse-linux-os-generated-log-files-in-windows-environment-with-file-input-plugin/43209)._