# Logstash vs NFS (null characters)

**URL:** https://discuss.elastic.co/t/logstash-vs-nfs-null-characters/25918
**Category:** Logstash
**Created:** [July 20, 2015, 1:50pm UTC](https://discuss.elastic.co/t/logstash-vs-nfs-null-characters/25918 "2015-07-20T13:50:33Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![markus](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@markus](https://discuss.elastic.co/u/markus)
#### Post date: [November 6, 2015, 6:38pm UTC](https://discuss.elastic.co/t/logstash-vs-nfs-null-characters/25918/3 "2015-11-06T18:38:19Z")

</div>

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...

---

_[View the full topic](https://discuss.elastic.co/t/logstash-vs-nfs-null-characters/25918)._