Elevate errors converting from CentOS7 to Rocky

[sp3ctre69]

I just upgraded one of my DNSOnly boxes from CentOS to Rocky. Along the way I got the following error:

can't use an undefined value as a HASH reference.... and then a line number. I couldn't find any info about it so I went to the line number and just added a "return;" at the start of the function. It was (if I remember correctly) the function to re-install Immunify. It also did it on quite a few other lines (Litespeed check was one).

All appears to be working now but I am a bit nervous to upgrade my other boxes without knowing what these errors were about or how to correct them.

 

[cPRex]

Hey there! I'm not sure that gives me enough to go on to help with the issue, but if you can consistently recreate the problem could you submit a ticket to our team so we can check it out?

 

[sp3ctre69]

Hey there! I'm not sure that gives me enough to go on to help with the issue, but if you can consistently recreate the problem could you submit a ticket to our team so we can check it out?

One of the examples was referencing this line:

my $data = read_stage_file('reinstall')->{'jetbackup'};

Each time the error happened it was a similar line to this one.

Another example:

return unless read_stage_file('reinstall')->{'influxdb'};

 

[cPRex]

Thanks for that - I have let our developers know, but it's unlikely I'm going to hear back for a few days about this due to the holiday weekend. The ELevate tools are also still experimental, so it's possible this is just something that hasn't been resolved yet. If I hear back with more details, I'll be sure to post a reply!

 

[sp3ctre69]

Thanks for that - I have let our developers know, but it's unlikely I'm going to hear back for a few days about this due to the holiday weekend. The ELevate tools are also still experimental, so it's possible this is just something that hasn't been resolved yet. If I hear back with more details, I'll be sure to post a reply!

Nice one... I can dig out more examples if required, but I think they all have similar code in them. Hopefully something simple... was just keen to get on with the conversion as I'd forgotten to snapshot the VM first so didn't pay too much attention.

 

[sp3ctre69]

Just to add, I found someone else with a similar issue:

Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2470. · Issue #144 · cpanel/elevate

Hello, I just used this script to elevate a DNS Only install from CentOS 7.9 to AlmaLinux 8.6. cPanel version 106.9. Even with this error message on the script: The elevation process failed during ...

github.com

Interesting that his issue was also a DNSOnly instance... could be a coincidence but thought it was worth mentioning.

 

[cPRex]

I spoke with the team, and we actually have an area to report these issues here:

Issues · cpanel/elevate

elevate your cPanel&WHM CentOS 7 server to Almalinux 8 - Issues · cpanel/elevate

github.com

Can you include as many details as you can there with your report?

 

[Steini Petur]

@cPRex, man that "Issues" page you posted here, it has stopped me in my TRACKS to update our Main system, its Centos 7.9 and I was always going to just upgrade it at the end of its EOL but the Elevate started to intrigue me but the issues page just is a show stopper for me to do this on a very much so LIVE env.. Seems like this is still quite the Experimental phase? 25 cases open 83 closed, maybe I should hold off on this until maybe 2024?

 

[cPRex]

@Steini Petur - it's important to note these are reported issues by end-users. For example, this specific one was just the user not waiting long enough for his system to perform the updates:

Possible locale issues makes upgrade behave unexpectedly? (Lost bash after the 4th reboot, elevate won't continue) · Issue #197 · cpanel/elevate

Hi. Around the 4th reboot, the bash stop working and the elevate process can't continu. Basic commands like "ls" aren't working: `Last login: Sat Feb 18 20:36:02 2023 ------------------------------...

github.com

so they aren't all directly related to problems with the product.

The evaluation script you run first is exhaustive, and will tell you anything odd that could be happening on the system that would prevent things from working well. Of course, like with anything, you're always welcome to submit a ticket to our team and we can check things on our end before you get started.