-
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
[Auditbeat] error: system/socket dataset setup failed: unable to guess one or more required parameters: guess_struct_creds failed: timeout while waiting for event #36905
Comments
We'd say that there are two commits as being of interest in the kernel code: It's clear how the v6.3 can result in what we are seeing but not that obvious for versions 6.1 as Beats isn't setting AT_EACCESS, access_override_creds should be called and thus prepare_creds should be called). |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
@jmbass I've gone through the relevant kernel code for v6.0 and v6.5.9 and I agree that the change in 981ee95c does look like it would explain this behaviour. There is no change in the type definition of Something that I'm unclear about in your discussion, I don't see where v6.1 comes in. In "but not that obvious for versions 6.1 as Beats isn't setting AT_EACCESS, access_override_creds should be called and thus prepare_creds should be called", this looks to me like a description of the state where the guess works. Am I missing something? I've taken a look at other places in v6.5.9 where |
I've suggested @efd6 to tap into
|
Version: Auditbeat 8.4.3 - Auditbeat 8.10.4
Operating System:
CentOS Linux release 8.8 (Green Obsidian)
Kernel 6.3.6-1.el8.x86_64
Beats fails to start with error:
Exiting: 1 error: system/socket dataset setup failed: unable to guess one or more required parameters: guess_struct_creds failed: timeout while waiting for event
I think the
struct_creds
definition changed / was removed around the 6.1.Using the kernel version 6.1.38-1.el8.x86_64 works alright.
The text was updated successfully, but these errors were encountered: