fix(service): Add systemd unit option that prevents service from failing to start on Debian and Elasticsearch 8.x (sous-chefs#826) #819
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
@ahpnils any chance you can rebase please. |
ahpnils
force-pushed
the
notifyaccess_all
branch
from
98d29f3 to
9ff46be
Compare
Contributor
Author
|
@damacus done ! Sorry for the late reply. |
ahpnils
force-pushed
the
notifyaccess_all
branch
from
9ff46be to
1f77064
Compare
ahpnils
changed the title
…ing to start on Debian and Elasticsearch 8.x (#826)
ahpnils
force-pushed
the
notifyaccess_all
branch
from
1f77064 to
bd53c56
Compare
ahpnils
changed the title
damacus
approved these changes
Nov 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds the "NotifyAccess: all" setting to the systemd unit for managing Elasticsearch.
Issues Resolved
When using this cookbook with Debian (tested on 11 and 12) and ES 8.x (test on 8.11.x), the service does not start, complaining about getting notification from a PID but reception only permitted for another. This has been reported as issue 826. This PR aims at fixing this issue.
Check List
## Unreleased