# Logstash ERROR \`block in controlled\_read'

**URL:** https://discuss.elastic.co/t/logstash-error-block-in-controlled-read/275269
**Category:** Logstash
**Created:** [June 8, 2021, 9:01am UTC](https://discuss.elastic.co/t/logstash-error-block-in-controlled-read/275269 "2021-06-08T09:01:53Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![oduvancheg666](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oduvancheg666/32/89979_2.png) [@oduvancheg666](https://discuss.elastic.co/u/oduvancheg666)
#### Post date: [June 8, 2021, 9:01am UTC](https://discuss.elastic.co/t/logstash-error-block-in-controlled-read/275269/1 "2021-06-08T09:01:53Z")

</div>

Hello. Logstash version 7.3.0 gets the error:

```auto
[2021-06-08T10:13:48,304][ERROR][filewatch.tailmode.handlers.grow] read_to_eof: general error reading //PC/C$/inetpub/logs/LogFiles/W3SVC2/u_ex210608.log {"error"=>"#<SystemCallError: Unknown error (SystemCallError) - No message available>", "backtrace"=>["org/jruby/RubyIO.java:3014:in `sysread'", "E:/logstash-7.3.0/logstash-7.3.0/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/watched_file.rb:218:in `file_read'", "E:/logstash-7.3.0/logstash-7.3.0/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-.4.1.10/lib/filewatch/watched_file.rb:230:in `read_extract_lines'", "E:/logstash-7.3.0/logstash-7.3.0/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/tail_mode/handlers/base.rb:52:in `block in controlled_read'"]}

```

I restart logstash and the logs work fine until the next day. What does this error mean and how to fix it?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2021, 9:02am UTC](https://discuss.elastic.co/t/logstash-error-block-in-controlled-read/275269/2 "2021-07-06T09:02:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
