[GH-ISSUE #235] Trouble starting up -- Ambar_es keeps crashing #230

New issue

Closed

opened 2026-02-27 15:55:44 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 15:55:44 +03:00

Owner

Originally created by @csgnyc on GitHub (May 10, 2019).
Original GitHub issue: https://github.com/RD17/ambar/issues/235

Installed Ambar through the instructions on https://ambar.cloud/docs/installation/. When I start Ambar up, the db, rabbit, and redis containers start up normally, but the es container repeatedly crashes. When I look at the log, I see

ERROR: [2] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk | stdout
-- | --

Then it closes and restarts and has the same error.

I can see that "262144" matches a suggested change in the installation process to the /etc/sysctl.conf file so I checked that file to make sure that change went through.

Any thoughts on what I'm doing wrong?

Originally created by @csgnyc on GitHub (May 10, 2019). Original GitHub issue: https://github.com/RD17/ambar/issues/235 Installed Ambar through the instructions on https://ambar.cloud/docs/installation/. When I start Ambar up, the db, rabbit, and redis containers start up normally, but the es container repeatedly crashes. When I look at the log, I see ``` ERROR: [2] bootstrap checks failed [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144] [2]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk | stdout -- | -- ``` Then it closes and restarts and has the same error. I can see that "262144" matches a suggested change in the installation process to the /etc/sysctl.conf file so I checked that file to make sure that change went through. Any thoughts on what I'm doing wrong?

kerem

2026-02-27 15:55:44 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-27 15:55:44 +03:00

Author

Owner

@stale[bot] commented on GitHub (May 25, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (May 25, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.