# ES 5.2 node validation exception bootstrap checks failed - no other error

**URL:** <https://discuss.elastic.co/t/es-5-2-node-validation-exception-bootstrap-checks-failed-no-other-error/77922>\
**Category:** Elasticsearch\
**Created:** [March 9, 2017, 1:41am UTC](https://discuss.elastic.co/t/es-5-2-node-validation-exception-bootstrap-checks-failed-no-other-error/77922 "2017-03-09T01:41:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [March 9, 2017, 5:29am UTC](https://discuss.elastic.co/t/es-5-2-node-validation-exception-bootstrap-checks-failed-no-other-error/77922/4 "2017-03-09T05:29:12Z")

</div>

> [@Bob\_Metelsky](#):
>
> But Its seems the system call is giving an exception without an explanation.

It's there, it's higher in the logs.

> [@Bob\_Metelsky](#):
>
> Now its just giving me an meaningless error "check your logs"... I'm reading the log! - this error is IN the log!

You need to check higher in the logs. You'll see something like:

```auto
[2017-02-01T10:46:10,639][WARN][o.e.b.JNANatives] unable to install syscall filter:
java.lang.UnsupportedOperationException: seccomp unavailable: CONFIG_SECCOMP not compiled into kernel, CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER are needed
        at org.elasticsearch.bootstrap.SystemCallFilter.linuxImpl(SystemCallFilter.java:363) ~[elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.SystemCallFilter.init(SystemCallFilter.java:638) ~[elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.JNANatives.tryInstallSystemCallFilter(JNANatives.java:215) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Natives.tryInstallSystemCallFilter(Natives.java:99) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:110) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:203) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:121) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:112) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.cli.SettingCommand.execute(SettingCommand.java:54) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.cli.Command.main(Command.java:88) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:89) [elasticsearch-5.2.0.jar:5.2.0]
        at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:82) [elasticsearch-5.2.0.jar:5.2.0]

```

This is telling you _why_ the system call filter failed to install. The docs that @dadoonet pointed you to explain the purpose of this check. You can either address whatever log message you have similar to the above, or just skip the system call filter check by setting `bootstrap.system_call_filter` to `false`.

> [@Bob\_Metelsky](#):
>
> Even the links in the config file don't work

I want to fix this. Which link in the config file does not work?

> [@Bob\_Metelsky](#):
>
> 50% of the settings are deprecated.

I want to fix this. Which settings in the config file are deprecated?

---

_[View the full topic](https://discuss.elastic.co/t/es-5-2-node-validation-exception-bootstrap-checks-failed-no-other-error/77922)._