# Problem with cipher in beat input

**URL:** <https://discuss.elastic.co/t/problem-with-cipher-in-beat-input/67841>\
**Category:** Logstash\
**Created:** [December 2, 2016, 10:36am UTC](https://discuss.elastic.co/t/problem-with-cipher-in-beat-input/67841 "2016-12-02T10:36:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jess\_571](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jess_571/32/13894_2.png) [@jess\_571](https://discuss.elastic.co/u/jess_571)\
**Post date:** [December 14, 2016, 9:52pm UTC](https://discuss.elastic.co/t/problem-with-cipher-in-beat-input/67841/5 "2016-12-14T21:52:00Z")

</div>

Had this issue with a system, and found the problem was /tmp was mounted with noexec option.

Removing the noexec option and rebooting fixed the issue on my system.

It looks like logstash puts a copy of the libnetty-tcnative dynamic library so in /tmp and tries to load it from there which the noexec option blocks. Loading code from /tmp seems like a security risks.

EDIT: the code putting the library in TMP is in netty which is used by logstash.

EDIT 2: maybe the tmp path can be made more sane in logstash's jvm.options file by adding a line  
-Dio.netty.native.workdir=some path

---

_[View the full topic](https://discuss.elastic.co/t/problem-with-cipher-in-beat-input/67841)._