-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Elasticsearch can't start on my laptop and on some ci nodes #77126
Labels
>bug
:Core/Infra/Node Lifecycle
Node startup, bootstrapping, and shutdown
Team:Core/Infra
Meta label for core/infra team
Comments
nik9000
added
>bug
:Core/Infra/Node Lifecycle
Node startup, bootstrapping, and shutdown
labels
Sep 1, 2021
Pinging @elastic/es-core-infra (Team:Core/Infra) |
here is an example in CI:
|
@pugnascotia It looks like cgroups are using symlinks? We may need a recursive permission on |
@pugnascotia has reverted the v2 cgroup handling in 33c4129 to unbreak me and the rare CI machines that break on it. |
@rjernst oh man - I totally meant to add that. Epic facepalm. |
pugnascotia
added a commit
that referenced
this issue
Sep 3, 2021
Closes #76812. Closes #77126. OsProbe was only capable of handle cgroup data in the v1 format. However, Debian 11 uses cgroups v2 by default, and Elasticsearch isn't capable of reporting any cgroup information. Therefore, add support for the v2 layout. Note that we have to open access to all of /sys/fs/cgroup because with cgroups v2, the files we need are in an unpredictably location.
pugnascotia
added a commit
to pugnascotia/elasticsearch
that referenced
this issue
Sep 6, 2021
Closes elastic#76812. Closes elastic#77126. OsProbe was only capable of handle cgroup data in the v1 format. However, Debian 11 uses cgroups v2 by default, and Elasticsearch isn't capable of reporting any cgroup information. Therefore, add support for the v2 layout. Note that we have to open access to all of /sys/fs/cgroup because with cgroups v2, the files we need are in an unpredictably location.
elasticsearchmachine
pushed a commit
that referenced
this issue
Sep 6, 2021
* Handle cgroups v2 in `OsProbe` (#77128) Closes #76812. Closes #77126. OsProbe was only capable of handle cgroup data in the v1 format. However, Debian 11 uses cgroups v2 by default, and Elasticsearch isn't capable of reporting any cgroup information. Therefore, add support for the v2 layout. Note that we have to open access to all of /sys/fs/cgroup because with cgroups v2, the files we need are in an unpredictably location. * Handle a max memory value of 'max' (#77289) * Handle a max memory value of 'max' * Update docs/changelog/77289.yaml * Delete 77289.yaml * Fixes to backport * Fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Core/Infra/Node Lifecycle
Node startup, bootstrapping, and shutdown
Team:Core/Infra
Meta label for core/infra team
Elasticsearch version (
bin/elasticsearch --version
): 54d4737OS version (
uname -a
if on a Unix-like system):Steps to reproduce:
Anything that starts Elasticsearch fails.
./gradlew run
should do it.Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: