# Seccomp is present, but bootstrap check fails (Centos 7 / ES 6.4.2)

**URL:** <https://discuss.elastic.co/t/seccomp-is-present-but-bootstrap-check-fails-centos-7-es-6-4-2/154364>\
**Category:** Elasticsearch\
**Created:** [October 29, 2018, 2:47am UTC](https://discuss.elastic.co/t/seccomp-is-present-but-bootstrap-check-fails-centos-7-es-6-4-2/154364 "2018-10-29T02:47:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jose\_Ramierez](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@Jose\_Ramierez](https://discuss.elastic.co/u/Jose_Ramierez)\
**Post date:** [October 29, 2018, 2:47am UTC](https://discuss.elastic.co/t/seccomp-is-present-but-bootstrap-check-fails-centos-7-es-6-4-2/154364/1 "2018-10-29T02:47:43Z")

</div>

CentOS Linux release 7.5.1804 (Core)

Configuring a production cluster, and ES refuses to start:

```
1:33:56,454][INFO][o.e.t.TransportService] [node-68795-C] publish_address {192.168.200.162:9300}, bound_addresses {192.168.200.162:9300}
[2018-10-28T21:33:56,467][INFO][o.e.b.BootstrapChecks] [node-68795-C] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2018-10-28T21:33:56,494][ERROR][o.e.b.Bootstrap] [node-68795-C] node validation exception
[1] bootstrap checks failed
[1]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk

```

OK, so I go to check the presence of seccomp:

```
[$]# cat /boot/config-`uname -r` | grep CONFIG_SECCOMP=
CONFIG_SECCOMP=y
[$]# CONFIG_SECCOMP=y

```

Hmm, still having problems, let's dig deeper:

```
[$]# grep SECCOMP /boot/config-$(uname -r)
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_SECCOMP=y

```

So, looks and smells like seccomp is present.

What next?

---

<div class="post-metadata">

**Author:** ![Jose\_Ramierez](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@Jose\_Ramierez](https://discuss.elastic.co/u/Jose_Ramierez)\
**Post date:** [October 29, 2018, 8:05pm UTC](https://discuss.elastic.co/t/seccomp-is-present-but-bootstrap-check-fails-centos-7-es-6-4-2/154364/2 "2018-10-29T20:05:32Z")

</div>

RESOLVED

The root case: /tmp was mounted as noexec

It turns out that two or thee bootstrap checks fail if /tmp is noexec.

Solve for /tmp, and all the other issues are resolved!

---

<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:** [November 26, 2018, 8:05pm UTC](https://discuss.elastic.co/t/seccomp-is-present-but-bootstrap-check-fails-centos-7-es-6-4-2/154364/3 "2018-11-26T20:05:35Z")

</div>

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