I'm running a VPS with Alma Linux 8.8.0 with WHM/cPanel and 60 or so users, multiple websites etc.
I'm regularly seeing these in the server 'messages' log:
Nov 16 11:39:01 ark grub2-set-bootflag: Error setuid(0) failed: Operation not permitted Nov 16 11:39:01 ark systemd: grub-boot-success.service: Main process exited, code=exited, status=1/FAILURE Nov 16 11:39:01 ark systemd: grub-boot-success.service: Failed with result 'exit-code'.
This seems to have been a known issue with grub in the past - I found this developer discussion from 2020 where a resolution is discussed:
They suggest changing a line in file
ExecStart=/usr/bin/pkexec /usr/sbin/grub2-set-bootflag boot_success
But later in the discussion say that this resolution triggers a password input request (which is no good to me as this is a system run command) and go on to mention that this bug has been resolved.
My system is running GRUB2:
[root@myserver systemd]# grub2-install --version grub2-install (GRUB) 2.03
a) Should I upgrade Grub to 2.06 (which I believe is the latest version) and if so how can I safely do this - of course I don't want anything at all to risk my system becoming unbootable.
b) Should I edit those files to the 'correct?' alternate line or will that just make the system need password input? (I tried it and saw in the log Nov "Main process exited, code=exited, status=127/n/a" meaning 'command not found')
c) Should I do nothing and it'll be fine?