Missing certificate and/or key IDs breaks JetBackup (5) backups.

Symptoms

When running JetBackup 5, the following error or similar is noted in the logs:

Failed fetching certificate id example_com_a4c71_04f03_1693887256_510fd58fce33e672b2a1c864695d98da. Error: Key file not found for certificate id "example_com_a4c71_04f03_1693887256_510fd58fce33e672b2a1c864695d98da"

Description

Corruption in the SQLite database "/var/cpanel/ssl/apache_tls/.index.sqlite" is the main cause for

the issue to occur. This often happens in servers with high IO (Input/Output) wait times. 

We've opened an internal case for our development team to investigate this further. For reference, the case number is CPANEL-42130. Follow this article to receive an email notification when a solution is published in the product. 

Workaround

The issue can be resolved by rebuilding the SSL Certificates and Keys databases. To do this, the following steps need to be performed via Terminal as the root user:

1. Set the "$user" variable by replacing "$cpuser" with the actual cPanel username:

user=$cpuser

2. Create a directory to store the old SSL database in:

mkdir /home/$user/ssl/old

3. Move the current SSL database to the newly created directory:

mv /home/$user/ssl/ssl.db* /home/$user/ssl/old/

4. Move the index SQlite file:

mv /var/cpanel/ssl/apache_tls/.index.sqlite /var/cpanel/ssl/apache_tls/.index.sqlite.orig2

5. Rebuild the SSL database:

whmapi1 rebuildinstalledssldb

Note: In some cases, the SSL database needs to be rebuilt for the user specifically. This can be done by using the uapi and a built-in script:

uapi --user=$user SSL rebuildssldb

/scripts/rebuilduserssldb