Closed harveymonster closed 3 years ago
I'm seeing this exact same issue with the Puppet pdk cask.
brew -v
Homebrew 3.0.4
Homebrew/homebrew-core (git revision 54ea21; last commit 2021-03-04)
Homebrew/homebrew-cask (git revision 36d6b; last commit 2021-03-04)
sudo: 4294967295: invalid value
sudo: error initializing audit plugin sudoers_audit
==> Purging files for version 2.0.0.0 of Cask pdk
Error: puppetlabs/puppet/pdk: Failure while executing; `/usr/bin/sudo -E -- /bin/rmdir -- /opt/puppetlabs/pdk/private/puppet/ruby/2.5.0/gems/puppet-6.17.0/bin` exited with 1. Here's the output:
sudo: 4294967295: invalid value
sudo: error initializing audit plugin sudoers_audit
Pinging @reitermarkus, who may know of a recent change.
here's my version of sudo:
sudo --version
Sudo version 1.9.5p2
Sudoers policy plugin version 1.9.5p2
Sudoers file grammar version 48
Sudoers I/O plugin version 1.9.5p2
Sudoers audit plugin version 1.9.5p2
It looks like the audit plugin is a relatively new concept in sudo
https://github.com/sudo-project/sudo/releases/tag/SUDO_1_9_0
I wonder if this is also the root of the problem I reported in https://github.com/Homebrew/homebrew-cask/pull/101360#issuecomment-802876871?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This is still happening for me. Not sure what to do so the issue doesn't go stale though.
Not sure what to do so the issue doesn't go stale though.
Try to find the cause or / and a solution. Is this an issue with homebrew or sudo
? Can you run git bisect
and find where the issue was introduced? What else could it be?
This is a volunteer-run project. If you dump a bug report and expect maintainers to do all the work of diagnosing and fixing, you’re at the mercy of when those volunteers have time and want to look at the particular bug you care about. Which might be never.
Do or find someone else to do the work or part of it. That’s how you get the resolution going.
For me this was fixed with the help of brew update-reset && brew update
Running brew update-reset && brew update
seems to have fixed it for the first cask that needs to be upgraded or if the upgrade targets only a single cask. If I run brew upgrade
multiple times, you can eventually get all upgrades installed. So at least I now have a workaround to get the upgrades.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
I haven't done enough cask upgrade operations to be 100% sure, but putting Set group_source dynamic
in /etc/sudo.conf as described at https://bugzilla.sudo.ws/show_bug.cgi?id=946#c5 seems to have fixed it for me.
This is apparently the new default setting in sudo 1.9.6, but my system (10.15.17) still only has 1.9.5p2. I would encourage anyone else encountering this error to give this a try.
General troubleshooting steps
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
Trying to upgrade any cask that needs sudo causes a sudo error for an invalid value when initializing the audit plugin. I thought this was cask specific but have now started to encounter the issue for multiple casks.
Command that failed
Output of command with
--verbose --debug
Output of
brew doctor --verbose
Output of
brew tap