Error initializing audit plugin sudoers_audit

[pato]

Is this something to worry about?

(24/28) Looking for Pacnew/Pacsave created.
sudo: unknown user reboot
sudo: error initializing audit plugin sudoers_audit
error: command failed to execute correctly

[soundofthunder]

@pato

@pato

Is this something to worry about?

Yes, probably, but it’s impossible to know without context.

---

Quick tip:-

Always show the complete command output, including the command(s) that were used, and place the output in a pre-formatted scrollable text box (use the </> button, not a quote box).

---

Please provide your system information as described (below) to help others to help you.

I’m sure someone will assist when they are able.

Regards.

---

Your post has been moved to dedicated topic.

---

What follows is from a standard template.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading

• Forum Rules
• Strict Forum Rules and Guidelines

Highly Recommended

• How to Post
• How to Request Support
• How to Post Command Output as Preformatted Text

---

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

The thread/topic title is not meant to be the sole description of a problem – use a brief descriptive title – and then fully describe your issue in the body of your first post.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.

---

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):

inxi -zv8	(short-form)
inxi --filter --verbosity=8	(long-form)
inxi man pages	(manual)

Running `inxi` within a `chroot` environment

• Add --color=0 to the long-form command, or…
• Change the short-form command to inxi -zv8c0

Your privacy is respected

When inxi is run using --filter or -z parameters, any personally identifiable information is filtered from the resulting output.

---

Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

• Stable Updates
• Testing Updates
• Unstable Updates

---

Technical Resources

• Manjaro Linux Wiki
• Arch Linux Wiki
• Tutorials

---

Notice- The above content is partially pre-prepared as an introduction for new or returning forum Users. Please take the time to follow any links given and discover how to use the forum effectively.

[Nachlese]

@pato

error: command failed to execute correctly

Which command failed to execute correctly?
(maybe it was just a typo on the command line?)
What was the command which lead to this error?

[Teo]

I find these errors strange in any case, but it will be hard to debug without some information for the history of the machine. For example, audit framework is installed by default but i do not think it is really activated. So how was it activated to check the sudoers? Why does it fail? What does the audit logs say? Etc.
The other one for the reboot seems even more strange. I do not even understand if a real reboot is meant, or a user called “reboot”. Is there such user in the list of users? (cat /etc/passwd |grep reboot) What process created it and why?

[dmt]

@pato

(24/28) Looking for Pacnew/Pacsave created.

It seems to have happened at the end of an update (during a hook). Is that correct?

@pato

sudo: unknown user reboot
sudo: error initializing audit plugin sudoers_audit

Please check /etc/sudoers and each file in /etc/sudoers.d for errors.

I may be wrong, but I suspect there’s a reference to a user called ‘reboot’ in one of them, however it’s probably just a typo (presumably that user doesn’t exist).

Please read the link below before editing any files. If in doubt - ask.

Sudo - ArchWiki

[Teo]

I think the error is from audit network and not actually in the sudoers. The module/rules to check sudoers cannot start. Not installed, not configured - i do not know, i do not use audit since i only have a personal computer with 1 user and not a server.

[dmt]

Maybe you’re right, it seems to be possible.

But a quick search for “error initializing audit plugin sudoers_audit” brings up results about errors in sudoers, and passwd.

One about a deleted user with matching errors but for root.

Also:

$ sudo -u reboot echo hello
sudo: unknown user reboot
sudo: error initializing audit plugin sudoers_audit

So looks to me like either:

1. Error in sudoers
2. Missing user

However I think I’ll change my vote to a hook which runs a command as a non-existent user. Just seems like an odd username.

EDIT:

Last one, fixed the link and reworded.