# Logstash 7.0.1 Exception in pipelineworker

**URL:** <https://discuss.elastic.co/t/logstash-7-0-1-exception-in-pipelineworker/182760>\
**Category:** Logstash\
**Created:** [May 25, 2019, 2:50pm UTC](https://discuss.elastic.co/t/logstash-7-0-1-exception-in-pipelineworker/182760 "2019-05-25T14:50:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nobound](https://avatars.discourse-cdn.com/v4/letter/n/f07891/32.png) [@nobound](https://discuss.elastic.co/u/nobound)\
**Post date:** [May 25, 2019, 2:50pm UTC](https://discuss.elastic.co/t/logstash-7-0-1-exception-in-pipelineworker/182760/1 "2019-05-25T14:50:09Z")

</div>

I am getting the following exceptions constantly.

```
[2019-05-25T12:37:07,301][ERROR][org.logstash.execution.WorkerLoop] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.
org.jruby.exceptions.SystemCallError: (SystemCallError) Unknown error (SystemCallError) - /home/testgrp/kc/data/restccu-20190524.log
	at org.jruby.RubyIO.write(org/jruby/RubyIO.java:1472) ~[jruby-complete-9.2.7.0.jar:?]
	at org.jruby.RubyIO.write(org/jruby/RubyIO.java:1437) ~[jruby-complete-9.2.7.0.jar:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.vendor.bundle.jruby.$2_dot_5_dot_0.gems.logstash_minus_output_minus_file_minus_4_dot_2_dot_6.lib.logstash.outputs.file.write(/home/testgrp/kc/logstash-7.0.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-file-4.2.6/lib/logstash/outputs/file.rb:374) ~[?:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.vendor.bundle.jruby.$2_dot_5_dot_0.gems.logstash_minus_output_minus_file_minus_4_dot_2_dot_6.lib.logstash.outputs.file.multi_receive_encoded(/home/testgrp/kc/logstash-7.0.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-file-4.2.6/lib/logstash/outputs/file.rb:143) ~[?:?]
	at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1792) ~[jruby-complete-9.2.7.0.jar:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.vendor.bundle.jruby.$2_dot_5_dot_0.gems.logstash_minus_output_minus_file_minus_4_dot_2_dot_6.lib.logstash.outputs.file.multi_receive_encoded(/home/testgrp/kc/logstash-7.0.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-file-4.2.6/lib/logstash/outputs/file.rb:143) ~[?:?]
	at org.jruby.RubyHash.each(org/jruby/RubyHash.java:1419) ~[jruby-complete-9.2.7.0.jar:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.vendor.bundle.jruby.$2_dot_5_dot_0.gems.logstash_minus_output_minus_file_minus_4_dot_2_dot_6.lib.logstash.outputs.file.multi_receive_encoded(/home/testgrp/kc/logstash-7.0.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-file-4.2.6/lib/logstash/outputs/file.rb:135) ~[?:?]
	at org.jruby.ext.thread.Mutex.synchronize(org/jruby/ext/thread/Mutex.java:165) ~[jruby-complete-9.2.7.0.jar:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.vendor.bundle.jruby.$2_dot_5_dot_0.gems.logstash_minus_output_minus_file_minus_4_dot_2_dot_6.lib.logstash.outputs.file.multi_receive_encoded(/home/testgrp/kc/logstash-7.0.1/vendor/bundle/jruby/2.5.0/gems/logstash-output-file-4.2.6/lib/logstash/outputs/file.rb:134) ~[?:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.logstash_minus_core.lib.logstash.outputs.base.multi_receive(/home/testgrp/kc/logstash-7.0.1/logstash-core/lib/logstash/outputs/base.rb:87) ~[?:?]
	at org.logstash.config.ir.compiler.OutputStrategyExt$AbstractOutputStrategyExt.multi_receive(org/logstash/config/ir/compiler/OutputStrategyExt.java:118) ~[logstash-core.jar:?]
	at org.logstash.config.ir.compiler.AbstractOutputDelegatorExt.multi_receive(org/logstash/config/ir/compiler/AbstractOutputDelegatorExt.java:101) ~[logstash-core.jar:?]
	at home.testgrp.kc.logstash_minus_7_dot_0_dot_1.logstash_minus_core.lib.logstash.java_pipeline.start_workers(/home/testgrp/kc/logstash-7.0.1/logstash-core/lib/logstash/java_pipeline.rb:235) ~[?:?]
[2019-05-25T12:37:07,302][ERROR][org.logstash.execution.WorkerLoop] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.
org.jruby.exceptions.SystemCallError: (SystemCallError) Unknown error (SystemCallError) - /home/testgrp/kc/data/restccu-20190524.log

```

It seems the exception always happened when it tried to write the output file that was getting to the size around 2G. Is it a known issue? Any idea what could cause this?

Thanks

---

<div class="post-metadata">

**Author:** ![nobound](https://avatars.discourse-cdn.com/v4/letter/n/f07891/32.png) [@nobound](https://discuss.elastic.co/u/nobound)\
**Post date:** [June 14, 2019, 6:00pm UTC](https://discuss.elastic.co/t/logstash-7-0-1-exception-in-pipelineworker/182760/2 "2019-06-14T18:00:04Z")

</div>

No idea on what is going on. I end up rotating the output file to make sure it is not bigger than 2G. Not an ideal solution, but at least it works around the issue.

---

<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 12, 2019, 6:00pm UTC](https://discuss.elastic.co/t/logstash-7-0-1-exception-in-pipelineworker/182760/3 "2019-07-12T18:00:25Z")

</div>

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