# Getting a warning "seccomp unavailable: 's390x' architecture unsupported" while starting service on s390x

**URL:** https://discuss.elastic.co/t/getting-a-warning-seccomp-unavailable-s390x-architecture-unsupported-while-starting-service-on-s390x/148416
**Category:** Elasticsearch
**Created:** [September 13, 2018, 7:11am UTC](https://discuss.elastic.co/t/getting-a-warning-seccomp-unavailable-s390x-architecture-unsupported-while-starting-service-on-s390x/148416 "2018-09-13T07:11:04Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![chakravarthy\_G](https://avatars.discourse-cdn.com/v4/letter/c/f04885/32.png) [@chakravarthy\_G](https://discuss.elastic.co/u/chakravarthy_G)
#### Post date: [September 13, 2018, 7:11am UTC](https://discuss.elastic.co/t/getting-a-warning-seccomp-unavailable-s390x-architecture-unsupported-while-starting-service-on-s390x/148416/1 "2018-09-13T07:11:04Z")

</div>

**Elasticsearch version** (`bin/elasticsearch --version`): 6.4.0

**JVM version** (`java -version`): adoptOpenJDK 10

**OS version** (`uname -a` if on a Unix-like system): Linux abc8c2c59c04 4.4.132-94.33-default #1 SMP Tue May 29 20:09:56 UTC 2018 (76aae3b) s390x s390x s390x GNU/Linux

**Description of the problem including expected versus actual behavior** :

Built ES6.4.0 from the source, build and TC execution are successful but I am getting below warning message after starting Elastic search service on s390x,

> [2018-08-22T12:21:45,517][WARN][o.e.b.JNANatives] unable to install syscall filter:  
> java.lang.UnsupportedOperationException: seccomp unavailable: 's390x' architecture unsupported

Even though the service is started, we want to resolve the warning by adding below line to `elasticsearch/server/src/main/java/org/elasticsearch/bootstrap/SystemCallFilter.java`

> m.put("s390x", new Arch(0x80000016, 0xFFFFFFFF, 1, 190, 11, 354, 348));

According to my observation, after adding the patch the test suit execution speed reduced drastically and many test cases failed.

1. Anyone experiencing the same behavior on non-intel architectures ?
2. what would be the effect of that warning message "seccomp unavailable: 's390x' architecture " on ES service if we don't resolve ?

---

<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: [October 11, 2018, 7:11am UTC](https://discuss.elastic.co/t/getting-a-warning-seccomp-unavailable-s390x-architecture-unsupported-while-starting-service-on-s390x/148416/2 "2018-10-11T07:11:06Z")

</div>

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