Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System requirements #80

Closed
SteveClement opened this issue Jun 28, 2019 · 3 comments
Closed

System requirements #80

SteveClement opened this issue Jun 28, 2019 · 3 comments
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@SteveClement
Copy link

SteveClement commented Jun 28, 2019

Description

When running the docker container, under low memory circumstances, elasticsearch never comes up.

Environment

  1. Ubuntu 18.04
  2. OpenCTI version: https://releases.opencti.io/opencti-20190627.tar.gz
  3. OpenCTI client: n/a
  4. Other environment details: 2GB RAM (cloud VM)

Endless loop: opencti_1 | Waiting ElasticSearch to launch...

Additionally, as per Elastic docker docs, perhaps mention:

Important

The vm.max_map_count kernel setting needs to be set to at least 262144 for production use. Depending on your platform
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Jun 28, 2019
@SamuelHassine SamuelHassine self-assigned this Jun 28, 2019
@swedishmike
Copy link

swedishmike commented Jun 28, 2019

I had the same issue on Ubuntu 18.04

By executing sysctl -w vm.max_map_count=262144 and trying again I got it all to start. Should that possibly be added to the documentation?

Alternatively, a link to this information could be added to the documentation? https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-cli-run-prod-mode

@SteveClement
Copy link
Author

I also had the issue that some containers exited with error 137, but that was before the sysctl. Let's see if that fixed it too.

@SamuelHassine
Copy link
Member

SamuelHassine commented Jun 28, 2019

Hello @SteveClement, @swedishmike,

Thank you for your bug report. The documentation has been updated to take into account the need to use sysctl -w vm.max_map_count=262144 before running the docker-compose.

Cheers,
Sam

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

3 participants