# Operation not permitted \<= New Beat

**URL:** https://discuss.elastic.co/t/operation-not-permitted-new-beat/147459
**Category:** Beats
**Tags:** beats-development
**Created:** [September 5, 2018, 6:33pm UTC](https://discuss.elastic.co/t/operation-not-permitted-new-beat/147459 "2018-09-05T18:33:38Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)
#### Post date: [September 5, 2018, 7:10pm UTC](https://discuss.elastic.co/t/operation-not-permitted-new-beat/147459/2 "2018-09-05T19:10:53Z")

</div>

The simplest solution IMO would be to disable the seccomp protections provided by libbeat that prohibit the beat from executing anything. You can add

`seccomp.enabed: false`

to your config file or add

`-E seccomp.enabled=false`

to your CLI args.

You can read more about the seccomp feature in any one of the Beat's documentation. [https://www.elastic.co/guide/en/beats/metricbeat/6.4/linux-seccomp.html](https://www.elastic.co/guide/en/beats/metricbeat/6.4/linux-seccomp.html)

And there is more developer level info in the readme at [https://github.com/elastic/beats/tree/master/libbeat/common/seccomp](https://github.com/elastic/beats/tree/master/libbeat/common/seccomp).

---

_[View the full topic](https://discuss.elastic.co/t/operation-not-permitted-new-beat/147459)._