Elevation Blocker detected: /sbin/grubby reported error code 1 when it ended
Hi all, we are blocked at this point and we don't know how to proceed.
----------------------------------------
2023-10-12 20:09:41 [WARN] *** Elevation Blocker detected: ***
Unable to determine running and boot kernels due to the following error:
(XID 47emaf) "/sbin/grubby" inform" del c"digo de error "1" cuando finaliz":
"/sbin/grubby" reported error code "1" when it ended
----------------------------------------
CentOS v7.9.2009 STANDARD kvm
cPanel Version 110.0.12
Thanks in advance,
Banthar
-
Hey there! Do you see any issues with the /sbin/grubby file on your system? Typically I would expect that to have 755 permissions and root:root ownership. I do see it is owned by the grubby RPM package: # rpm -qf /sbin/grubby grubby-8.28-26.el7.x86_64
and reinstalling that didn't totally destroy anything, so you could try running "yum reinstall grubby" to see if that resolves the issue. Here is the file as I see it on a CentOS 7 test machine:# ll /sbin/grubby -rwxr-xr-x 1 root root 72984 Jun 10 2019 /sbin/grubby
0 -
Hello cPRex, thanks a lot for your help. We follow your suggestions with the same result: # rpm -qf /sbin/grubby grubby-8.28-26.el7.x86_64
rpm -qf /sbin/grubby grubby-8.28-26.el7.x86_64 [root@andromeda ~]# yum reinstall grubby
ll /sbin/grubby -rwxr-xr-x 1 root root 72984 Aug 9 2019 /sbin/grubby
* 2023-10-13 07:42:33 [WARN] *** Elevation Blocker detected: *** Unable to determine running and boot kernels due to the following error: (XID q5qnkc) "/sbin/grubby" inform" del c"digo de error "1" cuando finaliz": "/sbin/grubby" reported error code "1" when it ended: * 2023-10-13 07:42:34 [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/
We can do a Graceful Reboot without any issue. Thanks in advance, Banthar0 -
That's definitely the right size on that file, so the issue isn't with the file itself. Can you run this command on the machine? grubby --default-index I'm guessing that will say something like "Could not find bootloader" If it does, can you see if this file is present on your system? stat /etc/grub2.cfg If not, you'll need to install the grub2 RPM with the "yum install grub2" command and then configure the loader using the details here: Setting the default kernel in CentOS 7 Please be careful, as this is editing the bootloader, so if not done properly the server may not boot. 0 -
Hello again cPRex, thanks a lot for your help. We will try carefully... 0 -
Hello again, yum install grub2 sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.10.0-1160.99.1.el7.x86_64 Found initrd image: /boot/initramfs-3.10.0-1160.99.1.el7.x86_64.img Found linux image: /boot/vmlinuz-3.10.0-1160.90.1.el7.x86_64 Found initrd image: /boot/initramfs-3.10.0-1160.90.1.el7.x86_64.img Found linux image: /boot/vmlinuz-3.10.0-1160.80.1.el7.x86_64 Found initrd image: /boot/initramfs-3.10.0-1160.80.1.el7.x86_64.img Found linux image: /boot/vmlinuz-3.10.0-693.11.1.el7.x86_64 Found initrd image: /boot/initramfs-3.10.0-693.11.1.el7.x86_64.img Found linux image: /boot/vmlinuz-0-rescue-72863e389b584a4dab36fae7f3bffda2 Found initrd image: /boot/initramfs-0-rescue-72863e389b584a4dab36fae7f3bffda2.img done
/scripts/elevate-cpanel --check *** Elevation Blocker detected: *** The running kernel version (6.2.9-x86_64-linode160) does not match that of the default boot entry (3.10.0-1160.99.1.el7.x86_64). This could be due to the kernel being changed by an update, meaning that a reboot should resolve this. However, this also could indicate that the system does not have control over which kernel and early boot environment (initrd) is used upon reboot, which is required to upgrade the operating system with this script. If this message remains after a reboot, your server may have been configured to boot into a particular kernel directly rather than to an instance of the GRUB2 boot loader. This often happens to virtualized servers, but physical servers also can have this problem under certain configurations. Your provider may have a solution to allow booting into GRUB2; contact them for further information. * 2023-10-18 10:06:27 [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/
Changed boot to GRRUB 2 > Boot failsgrep "^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2 CentOS Linux (3.10.0-1160.99.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.90.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-1160.80.1.el7.x86_64) 7 (Core) CentOS Linux (3.10.0-693.11.1.el7.x86_64) 7 (Core) CentOS Linux (0-rescue-72863e389b584a4dab36fae7f3bffda2) 7 (Core)
grep DEFAULT /etc/default/grub GRUB_DEFAULT=saved
grub2-set-default 0 grub2-editenv list saved_entry=0
nano /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="vconsole.keymap=es crashkernel=auto rhgb console=ttyS0,19200n8 net.ifnames=0" GRUB_DISABLE_RECOVERY="true" GRUB_DISABLE_OS_PROBER=true GRUB_DISABLE_LINUX_UUID=true GRUB_GFXPAYLOAD_LINUX=text GRUB_ENABLE_BLSCFG=false
touch /.autorelabel
At this point we can boot the server with GRUB2uname -r 3.10.0-1160.99.1.el7.x86_64
/scripts/elevate-cpanel --check * 2023-10-20 18:31:04 [ERROR] /boot/grub/grub.cfg exists but is not a symlink which ultimately links to /boot/grub2/grub.cfg. * 2023-10-20 18:31:04 [WARN] *** Elevation Blocker detected: *** The configuration of the GRUB2 bootloader does not match the expectations of this script. For more information, see the output of the script when run at the console: /scripts/elevate-cpanel --check If your GRUB2 configuration has not been customized, you may want to consider reaching out to cPanel Support for assistance: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2023-10-20 18:31:04 [WARN] *** Elevation Blocker detected: *** Disabling the BLS boot entry format prevents the resulting system from adding kernel updates to any boot loader configuration, because the old utility responsible for maintaining native GRUB2 boot loader entries was removed and replaced with a wrapper around the new utility, which only understands BLS format. This means that the old kernel will be used on reboot, unless the GRUB2 configuration file is manually edited to load the new kernel. Furthermore, after a few kernel updates, the DNF package manager may begin to remove old kernels, including the one still used in the configuration file. If that happens, the system will fail to come back after a subsequent reboot. The safe option is to remove the following line in /etc/default/grub: GRUB_ENABLE_BLSCFG=false or to change it so that it is set to "true" instead. * 2023-10-20 18:31:05 [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/
GRUB_ENABLE_BLSCFG=false or to change it so that it is set to "true" instead.nano /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="vconsole.keymap=es crashkernel=auto rhgb console=ttyS0,19200n8 net.ifnames=0" GRUB_DISABLE_RECOVERY="true" GRUB_DISABLE_OS_PROBER=true GRUB_DISABLE_LINUX_UUID=true GRUB_GFXPAYLOAD_LINUX=text GRUB_ENABLE_BLSCFG=true
/scripts/elevate-cpanel --check [ERROR] /boot/grub/grub.cfg exists but is not a symlink which ultimately links to /boot/grub2/grub.cfg. * 2023-10-20 18:45:06 [WARN] *** Elevation Blocker detected: *** The configuration of the GRUB2 bootloader does not match the expectations of this script. For more information, see the output of the script when run at the console: /scripts/elevate-cpanel --check If your GRUB2 configuration has not been customized, you may want to consider reaching out to cPanel Support for assistance: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2023-10-20 18:45:07 [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/
Can you share the expectations is talking about? :-D Thanks! Banthar0 -
Is the file still not a symlink after all that work? That's the expectation it is complaining about currently. 0 -
No, any suggestion? 0 -
If things are working well *and* that file isn't a symlink, we'd likely need to see a ticket about this specific machine so we can either advise you on what may need to change, or adjust the ELevate script accordingly. 0
Please sign in to leave a comment.
Comments
8 comments