Skip to content

SystemD NotifyAll to not timeout exit ES #6534

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.

Sign up for GitHub

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

Merged
stefnestor merged 3 commits into from
May 20, 2026
Merged

SystemD NotifyAll to not timeout exit ES #6534

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e80f30e
SystemD NotifyAll to not timeout exit ES
stefnestor May 16, 2026
54e5a28
Apply suggestion from @github-actions[bot]
marciw May 20, 2026
42cd2ed
Merge branch 'main' into stef_systemdEsNotifyAccess
marciw May 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion deploy-manage/deploy/self-managed/_snippets/systemd-startup-timeout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ Versions of `systemd` prior to 238 do not support the timeout extension mechanis
[2022-01-31T01:22:31,077][INFO ][o.e.n.Node ] [instance-0000000123] starting ...
...
[2022-01-31T01:37:15,077][INFO ][o.e.n.Node ] [instance-0000000123] stopping ...
[2022-01-31T01:37:15,079][INFO ][o.e.n.Node ] [instance-0000000123] closing ...
[2022-01-31T01:37:15,080][INFO ][o.e.n.Node ] [instance-0000000123] closed
```

However the `systemd` logs will report that the startup timed out:
Expand All @@ -21,6 +23,6 @@ Jan 31 01:37:15 debian systemd[1]: elasticsearch.service: Failed with result 'ti
Jan 31 01:37:15 debian systemd[1]: Failed to start Elasticsearch.
```

To avoid this, upgrade your `systemd` to at least version 238. You can also temporarily work around the problem by extending the `TimeoutStartSec` parameter.
To avoid this, upgrade your `systemd` to at least version 238. You can also temporarily work around the problem by extending the `TimeoutStartSec` parameter. If the timeout error persists after upgrading, set `NotifyAccess=all` in your [systemd override configuration](../setting-system-settings.md#systemd).

::::
1 change: 1 addition & 0 deletions deploy-manage/deploy/self-managed/setting-system-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,7 @@ Environment="MY_VAR=my-value"
LimitNOFILE=65535
LimitNPROC=4096
LimitMEMLOCK=infinity
NotifyAccess=all
```

Replace the directives with those required for your deployment.
Expand Down
Loading