[Partially Resolved] Please Help: Tried to "Elevate" to Almalinux and my server is now unreachable.
I don't know what to do at this point but I cannot access my server or SSH at all.
I was able to get the network team to help me get back online. Had to be manually rebooted for some reason but it didn't upgrade. I'm not seeing any update for the Roundcube vulnerabilities, which is why I attempted this in the first place. Frustrating. Any advice on why this may have happened? Should I have uninstalled CSF first? I did see (and lose) a thread mentioned a problem might exist with that. :confused:
-
Hey there! CSF wouldn't be related to an ELevate issue. You'd want to check the ELevate log data to see why the upgrade failed. That can be accessed with the "/scripts/elevate-cpanel --log" command or directly at /var/log/leapp/leapp-report.txt Reviewing that data will be the best way to proceed, otherwise anyone would be purely guessing on what may have happened. It's also worth noting that some of the reboots during the ELevate process can take an extended period of time. Unless the machine is offline for 1-2 hours or more, no manual intervention should happen to get the system online. 0 -
Hey there! CSF wouldn't be related to an ELevate issue. You'd want to check the ELevate log data to see why the upgrade failed. That can be accessed with the "/scripts/elevate-cpanel --log" command or directly at /var/log/leapp/leapp-report.txt Reviewing that data will be the best way to proceed, otherwise anyone would be purely guessing on what may have happened. It's also worth noting that some of the reboots during the ELevate process can take an extended period of time. Unless the machine is offline for 1-2 hours or more, no manual intervention should happen to get the system online.
Hi, I actually hired a SysAdmin from the company I lease my dedicated server from to have a look. Even though all of the blockers were taken care of, it was still failing. We had to have DC manually reboot the machine twice. We worked all night trying to figure out how to get it to work and never could. The problem seems to be stemming from an error I received via email after one of the failed attempts. (He confirmed the same.)- Unable to determine running and boot kernels due to the following error: (XID 9v35zd) Cannot determine startup kernel version.
0 -
That's a relatively common error, even without cPanel or ELevate. What happens if you run this command on the system? stat /etc/grub2.cfg If that file doesn't exist, can you run this to see if the tool is even present on the machine? rpm -qa | grep grubby Additional details about configuring this can be found here, but it's worth noting that any kernel issues are deeper than the cPanel software: Setting the default kernel in CentOS 7 0 -
That's a relatively common error, even without cPanel or ELevate. What happens if you run this command on the system? stat /etc/grub2.cfg If that file doesn't exist, can you run this to see if the tool is even present on the machine? rpm -qa | grep grubby Additional details about configuring this can be found here, but it's worth noting that any kernel issues are deeper than the cPanel software: [REDACTED]:~# stat /etc/grub2.cfg File: "/etc/grub2.cfg" -> "../boot/grub2/grub.cfg" Size: 22 Blocks: 0 IO Block: 4096 symbolic link Device: [REDACTED] Inode: 536871302 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2023-10-28 04:41:57.932884220 -0500 Modify: 2023-03-09 05:24:24.050812913 -0600 Change: 2023-03-09 05:24:24.050812913 -0600 Birth: - "If that file doesn't exist, can you run this to see if the tool is even present on the machine?" Ran it, even though I did get a readout from the last command and I get the following: grubby-8.28-26.el7.x86_64
0 -
That all looks good to me - we might need to see a ticket on this one to see if we can get more detail from the ELevate logs and your system about what specifically it doesn't like. In the past, it has given the error because that file wasn't a link or didn't exist at all, but that obviously isn't the case here. 0 -
That all looks good to me - we might need to see a ticket on this one to see if we can get more detail from the ELevate logs and your system about what specifically it doesn't like. In the past, it has given the error because that file wasn't a link or didn't exist at all, but that obviously isn't the case here.
Will do. Thank you.0 -
If you get a ticket number from us, post it here so I can follow along! 0 -
If you get a ticket number from us, post it here so I can follow along!
Id #95146324 I've linked them to this thread as well.0 -
Thanks - I'm following along with that now. 0 -
Thanks - I'm following along with that now.
Appreciate it. Thank you!0
Please sign in to leave a comment.
Comments
10 comments