-
Notifications
You must be signed in to change notification settings - Fork 4.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
Fix permissions at systemd unit file #7873
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
@ppanagiotis Would you mind systemd_unit_permissions_test.patch.txt
|
It looks like this is your first contribution. 👏 As such, can you please sign the Contributor License Agreement? |
Systemd unit has wrong permissions. So systemd logs: `Configuration file /lib/systemd/system/auditbeat.service is marked executable. Please remove executable permission bits. Proceeding anyway`
Done. |
Systemd unit has wrong permissions. So systemd logs: `Configuration file /lib/systemd/system/auditbeat.service is marked executable. Please remove executable permission bits. Proceeding anyway` (cherry picked from commit 2b6d468)
Systemd unit has wrong permissions. So systemd logs: `Configuration file /lib/systemd/system/auditbeat.service is marked executable. Please remove executable permission bits. Proceeding anyway` (cherry picked from commit 2b6d468)
Systemd unit has wrong permissions. So systemd logs: `Configuration file /lib/systemd/system/auditbeat.service is marked executable. Please remove executable permission bits. Proceeding anyway` (cherry picked from commit 9dba758)
Systemd unit has wrong permissions. So systemd logs:
Configuration file /lib/systemd/system/auditbeat.service is marked executable. Please remove executable permission bits. Proceeding anyway