Knowledgebase

We've received a lot of interest from clients wanting to use the ELevate option to upgrade to AlmaLinux 8 / Rocky Linux 8 in advance of the CentOS 7 End-of-Life date of July 1st, 2024. Here are the most common questions regarding the ELevate process and JetBackup 5.

IMPORTANT: It is your responsibility to follow all best practices and ensure you have backups/whole-system snapshots of the live system before you proceed with an in-place OS upgrade with Elevate.

Can I use ELevate with JetBackup 4?

No, JetBackup 4 does not support AlmaLinux/Rocky Linux 8/9 Operating systems so Elevate with JB4 is not possible. However, the ELevate process will automatically detect JB4 as a blocker. For more information on migrating to JB5 from JB4, please review the following:

https://blog.jetapps.com/jetbackup-4-end-of-life-announcement/

JB4 can be uninstalled using the documentation here:

https://docs.jetbackup.com/manual/whm/GeneralInformation/uninstall.html

Can I use ELevate with JetBackup 5?

If you use cPanel/WHM, JetBackup 5 is supported with the cPanel ELevate procedure, so you’re able to use cPanel ELevate to upgrade to AlmaLinux 8 before the CentOS 7 EOL. Please be sure to follow all pre-upgrade recommendations and take careful note of any risks, including generating a whole-system image or snapshot before using ELevate.

If using the cPanel Elevate, the upgrade will be performed seamlessly as cPanel ELevate performs the needed post-upgrade steps for you. For more information, please visit https://go.cpanel.net/ELevate

If you use a control panel such as Plesk, DirectAdmin, or Linux (No-Panel),

Please exercise extreme caution and review the official documentation for your panel to confirm whether this is supported. Almalinux Elevate does NOT have customizations in place for external control panels or plugins, such as JetBackup.  

Please use the following commands to ensure JB5 has the correct packages post-elevate on non-cPanel servers:

yum install jetbackup5-base jetbackup5-$PANEL --enablerepo=jetapps,jetapps-stable
yum update 'jet*' --disablerepo=* --enablerepo=jetapps,jetapps-stable && service jetbackup5d restart

If you encounter any JB5 issues after upgrading, please feel free to open a support ticket so we can investigate further. 

JB Config shows "Never Finished" after ELevate, how do I fix this?

We have received some reports of an error occurring for JB Config backups after using ELevate. The error occurs because the JetBackup 5 RPM's were not updated to their proper AlmaLinux/EL8 versions.

The error Error: Failed to export private key. error:0E079065:configuration file routines:DEF_LOAD_BIO:missing equal sign simply indicates that the relevant jetphp81* package that controls export of the private key does not have the proper RPM for AlmaLinux 8.

AlmaLinux 8/EL8 RPM's were changed in v5.3 to ensure newer OS' always have a higher RPM version number, so jetphp81-parallel-8.1.20.0-2.x86_64 (CentOS 7) becomes jetphp81-parallel-8.1.20.0-102.x86_64. (AlmaLinux 8 packages have -10X, AmaLinux9 prefixed -20X)

As a temporary workaround if JB Config is failing with the following error:

[22/Jan/2024 23:57:20 +0000] [PID 478945] Starting jetbackup config backup
[22/Jan/2024 23:57:21 +0000] [PID 1831727] [ERROR] Item Never Finished
[22/Jan/2024 23:57:21 +0000] [PID 1831727] Failed

Please run the update command below to fetch the proper versions:

yum install jetbackup5-base jetbackup5-cpanel --enablerepo=jetapps,jetapps-stable
yum update 'jet*' --disablerepo=* --enablerepo=jetapps,jetapps-stable && service jetbackup5d restart

Why JetBackup 5 can disappear after Elevate, and how to prevent it. 

JetBackup 5 is sometimes removed during AlmaLinux Elevate, even though the cPanel-specific Elevate project was customized to avoid this. It occurs when the Elevate process removes certain RPM dependencies that JB5 or some related package requires. 

Most commonly, this is a consequence of Elevate removing libzip.so.2 (EL7) library which jethphp81-zip relies on before replacing with libzip.so.5 (EL8). The jetbackup5-base and panel packages are removed as dependent packages. 

To prevent this behavior from occurring, follow these steps:

Step 1: (PRE-ELEVATE) 

Remove the jetphp81-zip package manually without dependencies. WARNING: If you remove the jetphp81-zip package and do not proceed with Step 2, JB5 will not function properly.

/usr/bin/rpm -e --nodeps jetphp81-zip

Step 2: (POST-ELEVATE)

Update all JetBackup 5 related packages to their AlmaLinux 8 equivalents. 

yum install jetphp81-zip --enablerepo=jetapps,jetapps-stable && yum update 'jet*' --disablerepo=* --enablerepo=jetapps,jetapps-stable && service jetbackup5d restart

[Patched] Error "uncaught exception: Error: No User or Password" after cPanel Elevate

NOTICE: This issue is now resolved with JetBackup v5.3.9+ which includes a jetmongod package upgrade. Please verify you're using the latest version prior to ELevate to avoid this issue. 

You may notice a MongoDB authentication error after cPanel Elevate due to yum re-naming one of the mongoDB authentication files. If you see this warning/error in `/var/log/elevate-cpanel.log`. 

2024-01-25 19:44:24 (4335) [[32mINFO[0m] Upgrading : jetmongod-4.4.0.1-7.x86_64 29/66
2024-01-25 19:44:24 (4335) [[32mINFO[0m] warning: /usr/local/jetapps/etc/.mongod.auth saved as /usr/local/jetapps/etc/.mongod.auth.rpmsave

This can be resolved by replacing the original .mongod.auth file:

mv /usr/local/jetapps/etc/.mongod.auth.rpmsave /usr/local/jetapps/etc/.mongod.auth

This also solves the following update-related error. MongoDB indexes help increase the performance of JB5 API calls. 

* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] Running scriptlet: jetbackup5-base-5.3.8-102.x86_64 32/66
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] ERROR with mongodb indexes!!!
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] uncaught exception: Error: No User or Password :
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] _init@/usr/local/jetapps/usr/lib/mongod/MongoClient.mo:25:41
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] MongoClient@/usr/local/jetapps/usr/lib/mongod/MongoClient.mo:5:27
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] @/usr/local/jetapps/install/jetbackup5/indexes.mongo:7:15
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] @/usr/local/jetapps/install/jetbackup5/indexes.mongo:1:2
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] failed to load: /usr/local/jetapps/install/jetbackup5/indexes.mongo
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] exiting with code -3
* 2024-01-25 19:44:32 (4335) [[32mINFO[0m] warning: %post(jetbackup5-base-5.3.8-102.x86_64) scriptlet failed, exit status 1