Elastic Cluster on Azure Cloud - Linux - one server fails to startup while the other is successful

Here is a configuration of a 2 node elastic cluster:

node.max_local_storage_nodes: 2
cluster.name: elasticsearch
node.name: server2
path.data: /etc/elasticsearch/data
path.logs: /etc/elasticsearch/logs
discovery.seed_hosts: ["IPServer1","IPServer 2"]
network.host: IPServer 2
network.bind_host: IPServer2
node.master: true
http.port: PORT

node.max_local_storage_nodes: 2
cluster.name: elasticsearch
node.name: server1
path.data: /etc/elasticsearch/data
path.logs: /etc/elasticsearch/logs
discovery.seed_hosts: ["IPServer1","IPServer 2"]
network.host: IPServer1
network.bind_host: IPServer1
node.master: true
http.port: PORT

While Server 1 launched successfully, the second server failed to start with this exception:
'> # ERROR: [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
ERROR: Elasticsearch did not exit normally - check the logs at /etc/elasticsearch/logs/elasticsearch.log'

The logs do not indicate anything other than what is shared above..
What could possibly be wrong with the above for a production setup..?
@dadoonet, any suggestions or point me in a direction?

That would be this one https://www.elastic.co/guide/en/elasticsearch/reference/current/_system_call_filter_check.html

Thank you for the response.
I had seen this earlier as well.

'To pass the system call filter check you must either fix any configuration errors on your system that prevented system call filters from installing'

What does "system" mean here? Is it Elasticsearch or the OS or JVM?

The OS.

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