Error Alamalinux update / The 'leapp upgrade' process failed
Hello,
Now I just upgrate to CentOS v7.9 to Almalinux and it fails.
Specifically the leapp upgrade process
These are the logs
* 2024-04-28 20:15:17 (5905) [INFO] ====> * repository_mapping
* 2024-04-28 20:15:17 (5905) [INFO] Produces message containing repository mapping based on provided file.
* 2024-04-28 20:15:17 (5905) [INFO] ====> * xfs_info_scanner
* 2024-04-28 20:15:17 (5905) [INFO] This actor scans all mounted mountpoints for XFS information
* 2024-04-28 20:17:47 (5905) [INFO] Process Process-308:
* 2024-04-28 20:17:47 (5905) [INFO] Traceback (most recent call last):
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in _bootstrap
* 2024-04-28 20:17:47 (5905) [INFO] self.run()
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
* 2024-04-28 20:17:47 (5905) [INFO] self._target(*self._args, **self._kwargs)
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/repository/actor_definition.py", line 72, in _do_run
* 2024-04-28 20:17:47 (5905) [INFO] actor_instance.run(*args, **kwargs)
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/actors/__init__.py", line 290, in run
* 2024-04-28 20:17:47 (5905) [INFO] self.process(*args)
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/share/leapp-repository/repositories/system_upgrade/common/actors/xfsinfoscanner/actor.py", line 23, in process
* 2024-04-28 20:17:47 (5905) [INFO] scan_xfs()
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/share/leapp-repository/repositories/system_upgrade/common/actors/xfsinfoscanner/libraries/xfsinfoscanner.py", line 52, in scan_xfs
* 2024-04-28 20:17:47 (5905) [INFO] mountpoints_ftype0 = list(filter(is_xfs_without_ftype, mountpoints))
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/share/leapp-repository/repositories/system_upgrade/common/actors/xfsinfoscanner/libraries/xfsinfoscanner.py", line 25, in is_xfs_without_ftype
* 2024-04-28 20:17:47 (5905) [INFO] for l in run(['/usr/sbin/xfs_info', '{}'.format(mp)], split=True)['stdout']:
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/libraries/stdlib/__init__.py", line 203, in run
* 2024-04-28 20:17:47 (5905) [INFO] 'process-result', {'id': _id, 'parameters': args, 'result': audit_result, 'env': env}
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/utils/audit/__init__.py", line 286, in create_audit_entry
* 2024-04-28 20:17:47 (5905) [INFO] 'data': data
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/utils/audit/__init__.py", line 87, in store
* 2024-04-28 20:17:47 (5905) [INFO] with get_connection(db) as connection:
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/utils/audit/__init__.py", line 73, in get_connection
* 2024-04-28 20:17:47 (5905) [INFO] return create_connection(cfg.get('database', 'path'))
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/cli/commands/upgrade/util.py", line 33, in wrapper
* 2024-04-28 20:17:47 (5905) [INFO] return f(*args, **kwargs)
* 2024-04-28 20:17:47 (5905) [INFO] File "/usr/lib/python2.7/site-packages/leapp/utils/audit/__init__.py", line 60, in create_connection
* 2024-04-28 20:17:47 (5905) [INFO] return _initialize_database(sqlite3.connect(path))
* 2024-04-28 20:17:47 (5905) [INFO] OperationalError: unable to open database file
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO] =================================================================================================
* 2024-04-28 20:17:47 (5905) [INFO] Actor xfs_info_scanner unexpectedly terminated with exit code: 1 - Please check the above details
* 2024-04-28 20:17:47 (5905) [INFO] =================================================================================================
* 2024-04-28 20:17:47 (5905) [INFO] 2024-04-28 20:17:47.115 ERROR PID: 9986 leapp: Actor xfs_info_scanner unexpectedly terminated with exit code: 1
* 2024-04-28 20:17:47 (5905) [INFO] 2024-04-28 20:17:47.280 ERROR PID: 9986 leapp: Upgrade workflow failed, check log for details
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO] Debug output written to /var/log/leapp/leapp-upgrade.log
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO] ============================================================
* 2024-04-28 20:17:47 (5905) [INFO] REPORT
* 2024-04-28 20:17:47 (5905) [INFO] ============================================================
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO] A report has been generated at /var/log/leapp/leapp-report.json
* 2024-04-28 20:17:47 (5905) [INFO] A report has been generated at /var/log/leapp/leapp-report.txt
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO] ============================================================
* 2024-04-28 20:17:47 (5905) [INFO] END OF REPORT
* 2024-04-28 20:17:47 (5905) [INFO] ============================================================
* 2024-04-28 20:17:47 (5905) [INFO]
* 2024-04-28 20:17:47 (5905) [INFO] Answerfile has been generated at /var/log/leapp/answerfile
* 2024-04-28 20:17:47 (5922) [INFO]
* 2024-04-28 20:17:47 (5813) [INFO] Sending notification: Failed to update to AlmaLinux 8
* 2024-04-28 20:17:47 (5818) [ERROR] The elevation process failed during stage 3.
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] You can continue the process after fixing the errors by running:
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] /usr/local/cpanel/scripts/elevate-cpanel --continue
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] You can check the error log by running:
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] /usr/local/cpanel/scripts/elevate-cpanel
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] Last Error:
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] The 'leapp upgrade' process failed.
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] Please investigate, resolve then re-run the following command to continue the update:
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] /scripts/elevate-cpanel --continue
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR]
* 2024-04-28 20:17:47 (5818) [ERROR] You can read the full leapp report at: /var/log/leapp/leapp-report.txt
* 2024-04-28 20:17:47 (7390) [FATAL] The 'leapp upgrade' process failed.
Can anyone help me?
I don't know how solve this problem
-
Thanks cPRex,!!
I inform you when have the new license and the support ticket openned.1 -
Hey there! I don't believe that output shows the actual problem. Can you check the /var/log/leapp/leapp-report.txt file to see if the full error is shown there?
0 -
Hello!
The /var/log/leapp/leapp-report.txt is empty :(
I don't know how to proceed now
Whats wrong? Any solution0 -
Can you run the followings and paste here the output please?
/scripts/elevate-cpanel --check
df -h
cat /etc/fstab
cat /etc/os-releaseAndrew 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 Andrew,
Sure, this is the output.
* 2024-04-29 09:34:30 [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-29 09:34:30 [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ed994UdXxX/ea_profile.json
* 2024-04-29 09:34:31 [INFO] Backed up EA4 profile to /tmp/ed994UdXxX/ea_profile.json
* 2024-04-29 09:34:33 [INFO] There are no known blockers to start the elevation process.
You can consider running:
/scripts/elevate-cpanel --start
[root@ovho /]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.6G 0 7.6G 0% /dev
tmpfs 7.6G 4.0K 7.6G 1% /dev/shm
tmpfs 7.6G 41M 7.6G 1% /run
tmpfs 7.6G 0 7.6G 0% /sys/fs/cgroup
/dev/sda1 640G 331G 310G 52% /
/dev/loop0 3.9G 8.4M 3.7G 1% /tmp
[root@ovho /]# cat /etc/fstab#
# /etc/fstab
# Created by anaconda on Wed Apr 22 09:05:25 2020
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=6cd50e51-cfc6-40b9-9ec5-f32fa2e4ff02 / xfs defaults,uquota 0 0
/usr/tmpDSK /tmp ext3 defaults,noauto 0 0/usr/swpDSK swap swap defaults 0 0
[root@ovho /]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"Can you find something?
Thanks!0 -
Hello to all comunity users and Andrew
Anyone con help us with this problem¿ I Search on multiples forums (github, bugs.almalinux.org.. ) But nothing found.
Any contribution will be welcome
Thanks!
0 -
Well this is the problem but sadly its still not enough to advise on this further:
OperationalError: unable to open database file
Opening a ticket at cPanel for free would be the best so they can look into this for you or hiring a cPanel Professional to look into this could be the other option. The guys at cPanel are also quite active here so I'm sure they will also comment on this shortly, they might have some further advise what to do exactly.
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 Andrew,
Thanks for your help.
I try to open a support ticket with cPanel, but we have a conflict in the technical support with the licences between cPanel and OVH. cPanel says it's OVH who must give technical support on OVH as the reseller license says it's cPanel who must provide the technical support. We don't know what to do now.
We try to solve this.
Thanks again
0 -
Lets see what they say about this here in a few... :)
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 -
We'd likely need to see a ticket about this one.
0 -
Hello cPRex ;
I just open a ticket with id #95255495 asking about the possibility to revoque our OVH license and purchase a new one in cPanel Store.
After this, I can open a technical support ticket about this elevate problem?0 -
Sure thing! Although we wouldn't be able to help revoke that license - you'd have to cancel it with them and then order a new one through us.
0 -
Hello cPRex,
Great! No problema with revoke OVH license and purchase a new one in in cPanel Store.
Just one doubt: this will effect to server status? It will also be operational?Thanks!
0 -
Nothing will change on the server - you'll just have a few minutes where you wouldn't be able to log in to email accounts or the WHM/cPanel interfaces while you make the license switch.
0 -
Hello!
I just purchased a new licence in cPanel store and open a support ticket with server access.Great!
Ticket id: #95255024:Thanks!
Marc
0 -
Thanks for that - it looks like we recommended disabling jail shell on the system per this portion of the ticket:
The issue itself seems to be caused by the xfs_info process running for more than a minute and timing out due to scanning all available virtfs directories. What resolved the issue there was disabling the Apache jailed shell environment which uses virtfs and continuing the ELevate process. As such, my recommendation would be to disable Jailed shell as seen in the following link:
https://docs.cpanel.net/knowledge-base/accounts/virtfs-jailed-shell/#disable-or-remove-a-jailed-shell-environment0
Please sign in to leave a comment.
Comments
16 comments