You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[8.18 changelog] add known issue for restart_on_cert_change panic (#46406)
* changelog: add known issue for restart_on_cert_change panic
* fix version
* update link, use tagged region
---------
Co-authored-by: Colleen McGinnis <[email protected]>
(cherry picked from commit ad4bde6)
Copy file name to clipboardExpand all lines: CHANGELOG.asciidoc
+165Lines changed: 165 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,6 +148,147 @@ seccomp:
148
148
====
149
149
// end::known-issue-8.19-restart_on_cert_change[]
150
150
151
+
==== Known issues
152
+
153
+
// tag::known-issue-8.18-restart_on_cert_change[]
154
+
- `restart_on_cert_change` causes panic due to seccomp policy. In versions 8.18.0 and later, enabling this option causes the Beat to panic on restart. This is due to the `eventfd2` syscall missing from the default seccomp policy. To fix this, add `eventfd2` to a custom seccomp policy. To fix this, add `eventfd2` to a custom seccomp policy. For more details, refer to {filebeat-ref}/linux-seccomp.html[Use Linux Secure Computing Mode (seccomp)].
0 commit comments