# Fatal in logstash 6.0.0 **URL:** https://discuss.elastic.co/t/fatal-in-logstash-6-0-0/114469 **Category:** Logstash **Created:** [January 8, 2018, 8:53am UTC](https://discuss.elastic.co/t/fatal-in-logstash-6-0-0/114469 "2018-01-08T08:53:12Z") **Posts on this page:** 1 **Showing post:** 4
### Author: ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje) #### Post date: [January 8, 2018, 9:23am UTC](https://discuss.elastic.co/t/fatal-in-logstash-6-0-0/114469/4 "2018-01-08T09:23:46Z")
There are known problems with the file input and NFS. > [@Logstash vs NFS (null characters)](https://discuss.elastic.co/t/logstash-vs-nfs-null-characters/25918/3): > > I had the same problem. Couldn't find a way around it. Our (dirty) hack/workaround is to have a scheduled task running every 5 minutes to: shutdown logstash indexer copy the file restart logstash and index file This is okay for us as we don't need perfectly real-time indexing at least it works reliably since a couple of months. It also solved the problems with locked resources we encountered before... [Missing event - file input plugin / NFS - #19 by steffens](https://discuss.elastic.co/t/missing-event-file-input-plugin-nfs/107838/19) (with input from the LS and Beats teams) You should put Filebeat on the machine that the NFS share points at. --- _[View the full topic](https://discuss.elastic.co/t/fatal-in-logstash-6-0-0/114469)._