Problem with elevate script on stage 3
I'm trying to use elevate script to upgrade from Cednt OS 7 to Roky 8.
But I'm getting the following error
* 2024-04-09 09:54:53 (5629) [[32mINFO[0m] Error: leapp-data-almalinux conflicts with leapp-data-rocky-0.2-5.el7.1.noarch
After that, I'm getting many errors like.
* 2024-04-09 09:55:01 (5629) [[32mINFO[0m] cpanel-perl-536-algorithm-dependency-1.112-1.cp108~el7.noarch has missing requires of cpanel-perl-536
And gone and gone.
And them, on end off file, I get.
* 2024-04-09 09:55:02 (5545) [[31mERROR[0m]
* 2024-04-09 09:55:02 (5545) [[31mERROR[0m] /usr/local/cpanel/scripts/elevate-cpanel
* 2024-04-09 09:55:02 (5545) [[31mERROR[0m]
* 2024-04-09 09:55:02 (5545) [[31mERROR[0m] Last Error:
* 2024-04-09 09:55:02 (5545) [[31mERROR[0m]
* 2024-04-09 09:55:02 (5545) [[31mERROR[0m] command failed. Fix it and run command. at /usr/local/cpanel/scripts/elevate-cpanel line 5610.
* 2024-04-09 09:55:02 (7209) [[1;31mFATAL[0m] command failed. Fix it and run command. at /usr/local/cpanel/scripts/elevate-cpanel line 5610.
This was the second time I'm trying to upgrade the server. On the frist, I needed to rebuild server. But Hostgator only offers cPanel With Cent OS 7, so I need to catch the server on Cent OS 7 and upgrade it to Alma or Roky.
Below are the complete log
https://download.jonassmarques.com/elevate-cpanel.log
Any help will be appreciated.
-
I cant comment on the actual issue but I would personally never start an upgrade process if there were blockers detected :( and I think you would be better upgrading to Alma instead of Rocky fyi.
Andrew N. - cPanel Plesk VMWare Certified Professional
Do you need immediate assistance? 20 minutes response time!* Open a ticket
EmergencySupport - Professional Server Management and One-time Services0 -
I would also recommend trying with Alma instead.
0 -
Hi cPRex
How I Can revert back to stage 1 to start upgrade with AAlma? I used Roky on various upgrade processes, and everything worked fine, but no on that server.
Unnamed UserThe upgrade process do not detected any blockers. I just received the confirmation to run script. No lokers are detected.0 -
Also on Leap log I found the follwing.
Risk Factor: high (inhibitor)
Title: Missing required answers in the answer file
Summary: One or more sections in answerfile are missing user choices: remove_pam_pkcs11_module_check.confirm
For more information consult https://leapp.readthedocs.io/en/latest/dialogs.html
Remediation: [hint] Please register user choices with leapp answer cli command or by manually editing the answerfile.
[command] leapp answer --section remove_pam_pkcs11_module_check.confirm=True
If I fix that the script can be run again? How to fix that?
For more0 -
From where did you get this script? is it from /scripts/cpanel-elevate or you downloaded it from git?
Andrew N. - cPanel Plesk VMWare Certified Professional
Do you need immediate assistance? 20 minutes response time!* Open a ticket
EmergencySupport - Professional Server Management and One-time Services0 -
Hello all;
If anyone has the same error and ends up here, I'll describe how I solved it.
However, keep in mind that these are complex commands and uncertified processes. Execute at your own risk.
First of all, after checking all the logs, I noticed that the problem was only with the Rocky Linux repositories. So I decided to redo the update process, but now for Alma Linux.
So I ran the following:
/scripts/elevate-cpanel clean
then the new update command./scripts/elevate-cpanel --start --upgrade-to=almalinux
The update started again and went to stage 5, everything was fine.
Now you need to log into cPanel and perform the version update. Do this through WHM or the command line using
/scripts/upcp --force
However, on the first update, the script disables MYSQL on the server. So we need to rehabilitate it.
If you use MYSQL, run.
/usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0
If using Maria DB, run.
/usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.11
Done! Server running.
0
Please sign in to leave a comment.
Comments
6 comments