Updating CentOS7 at Linode
Have been running a Centos7 box @ Linode since 2008, and since that distro is EOL, it's time to migrate.
Am leaning toward sticking with a RHEL variant, probably Rocky, even given the drama at Big Blue these days.
Curious how use of the Elevate project has worked out for other users here, especially those on Linode.
Would much rather do an in-place upgrade than (temporarily) starting a new node with a new cPanel license and migrating everything over.
What's been the experience of other cPanel users who host @ Linode? Did the in-place upgrade work, or did you have to backup, wipe the box (or start a new one), then restore?
-
Hey hey! I have personally performed one ELevate on a Linode system and that went well. As long as you follow the steps outlined in the pre-flight check, you shouldn't break anything, but *always* have backups available in case something goes wrong. I have found that you may want to disable any server monitoring you have enabled, as you don't want any unintended reboots to happen. The system will reboot several times during the process and will appear completely offline to monitoring tools for an extended period of time. 0 -
Will give it a shot. The elevate dry run spit out a few warnings, one about grubby. Have reached out to cPanel, haven't heard back yet. Am a little hazy on the VPS boot process. My node's config says /dev/sda is "CentOS 7"; unclear whether that's just a label, or an actual image that gets spun up when the node is rebooted. If the latter, not sure how the upgrade could actually work, as after rebooting I'd start with CentOS again, not Rocky. It also said I need to remove CalDav, let yum update, and remove Python 3. I know CalDav uses Python 2 (and have a couple of users that may or may not still be syncing Outlook to their IOS devices), but am unaware of anything needing v3. In any event, thanks for the reply, and the tip on disabling monitoring. -- Carl 0 -
Sorry to belabor this, but can I safely ignore the grubby warning? It's the only one still unresolved. There is no grub2 dir in /boot, only grub, and all it has in it is an archive - splash.xpm.gz Since there are no "standard" grub config files, it makes sense why grubby is failing. Just don't know what to do about it. Please advise. Thanks! 0 -
Thanks, will investigate. Honestly, still a little hazy how Linode boots a distro; the thing's been running 15 years, and I've slept since then. ;) Thanks for the link! 0 -
You could always reach out to them directly about that portion of the server, as that would be deeper than the cPanel tools. I've found their support to be great when I've used them for one of my personal systems. 0
Please sign in to leave a comment.
Comments
6 comments