max size virtual memory [-1] for user [1001030000] is too low

[zausel23]

Elasticsearch Version

8.15.5

Installed Plugins

No response

Java Version

java --version openjdk 21.0.5 2024-10-15 LTS OpenJDK Runtime Environment (Red_Hat-21.0.5.0.11-1) (build 21.0.5+11-LTS) OpenJDK 64-Bit Server VM (Red_Hat-21.0.5.0.11-1) (build 21.0.5+11-LTS, mixed mode, sharing)

OS Version

ubi9 container s390x (OpenShift)

Problem Description

We built a s390x version with the patches from IBM:

https://github.com/linux-on-ibm-z/scripts/tree/master/Elasticsearch/8.15.2

fixed issue:

#113705

will not working for us.

Steps to Reproduce

When start the Node in single node, evertyhing is fine. When we listening on 0.0.0.0 the checks will be failed.

Logs (if relevant)

[2025-01-20T09:36:37,160][INFO ][o.e.t.TransportService ] [elasticsearch-0] publish_address {192.168.8.176:9300}, bound_addresses {[::]:9300}
[2025-01-20T09:36:37,255][INFO ][o.e.b.BootstrapChecks ] [elasticsearch-0] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2025-01-20T09:36:37,256][WARN ][o.e.n.NativeAccess ] [elasticsearch-0] Cannot get process limits because native access is not available
[2025-01-20T09:36:37,257][WARN ][o.e.n.NativeAccess ] [elasticsearch-0] Cannot get process limits because native access is not available
[2025-01-20T09:36:37,257][WARN ][o.e.n.NativeAccess ] [elasticsearch-0] Cannot get process limits because native access is not available
[2025-01-20T09:36:37,257][WARN ][o.e.n.NativeAccess ] [elasticsearch-0] Cannot get process limits because native access is not available
[2025-01-20T09:36:37,257][WARN ][o.e.n.NativeAccess ] [elasticsearch-0] Cannot get process limits because native access is not available
[2025-01-20T09:36:37,257][WARN ][o.e.n.NativeAccess ] [elasticsearch-0] Cannot get process limits because native access is not available
[2025-01-20T09:36:37,261][ERROR][o.e.b.Elasticsearch ] [elasticsearch-0] node validation exception
[2] bootstrap checks failed. You must address the points described in the following [2] lines before starting Elasticsearch. For more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.15/bootstrap-checks.html]
bootstrap check failure [1] of [2]: max size virtual memory [-1] for user [1001030000] is too low, increase to [unlimited]; for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.15/max-size-virtual-memory-check.html]
bootstrap check failure [2] of [2]: max file size [-1] for user [1001030000] is too low, increase to [unlimited]; for more information see [https://www.elastic.co/guide/en/elasticsearch/reference/8.15/_max_file_size_check.html]
ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/elasticsearch-cluster.log
[2025-01-20T09:36:37,268][INFO ][o.e.n.Node ] [elasticsearch-0] stopping ...
[2025-01-20T09:36:37,283][INFO ][o.e.n.Node ] [elasticsearch-0] stopped
[2025-01-20T09:36:37,283][INFO ][o.e.n.Node ] [elasticsearch-0] closing ...
[2025-01-20T09:36:37,336][INFO ][o.e.n.Node ] [elasticsearch-0] closed

[DaveCTurner]

Thank you very much for your interest in Elasticsearch. Unfortunately the issue you have reported relates to the s390x platform which is not supported by this team. We will not investigate issues related to unsupported versions here on Github, so I am closing this to indicate that no action is needed from the Elasticsearch development team. It's possible that you will find a volunteer to help you with this issue on the community forums, or at the supplier of any patches you've used to build Elasticsearch on an unsupported platform, but our strong recommendation would be to use a supported platform. If you can reproduce your issue on a supported platform then please open a fresh bug report.

Quoting the bug report form:

Please also check your OS is supported, and that the version of Elasticsearch has not passed end-of-life. If you are using an unsupported OS or an unsupported version then the issue is likely to be closed.