JetBackUp Installation Fails With "Can't connect to mongodb"

Symptoms

Trying to install the latest version of JetBackUp initially fails with the following error: 

jetapps —install jetbackup-cpanel stable
Log file: /usr/local/jetapps/var/log/jetapps/20210712.163528_9148.log

Installing jetbackup-cpanel version 5.1.12-10…Failed
Please see the log file /usr/local/jetapps/var/log/jetapps/20210712.163528_9148.log for more details

Looking at the referenced log file in the above snippet, you will see the actual cause of the failure: 

package jetbackup-base is not installed
Can’t connect to mongodb.
error: %pre(jetbackup5-base-5.1.12-11.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package jetbackup5-base-5.1.12-11.x86_64
error: jetbackup5-base-5.1.12-11.x86_64: install failed
package jetbackup-cpanel is not installed
Installing : jetbackup5-cpanel-5.1.12-10.x86_64 2/2
jetbackup5 registered
Plugin installed ok

Installed:
jetbackup5-cpanel.x86_64 0:5.1.12-10
Failed:
jetbackup5-base.x86_64 0:5.1.12-11

Description 

As a part of the installation scripts for the jetbackup-base package, the package needs to be able to connect to MongoDB before the installation is complete and it seems that the script is not able to connect to MongoDB for some reason. 

You should run all of the following commands to determine why MongoDB is not available/accessible. First you need to make sure that the service is actually running with the following command: 

 systemctl status jetmongod.service

After confirming that the service is indeed running you need to make suer you are able to connect to MongoDB port from localhost: (Port 27217)

telnet localhost 27217

/usr/local/jetapps/usr/bin/mongo --quiet --port 27217

Workaround

If the service is not running it must be first started. And in case the port 27217 is filtered/blocked for whatever reason, it must be opened up in your firewall.