Symptoms

JetBackup will not start, and messages similar to the following may be found in the system log.

May 30 21:39:17 server jetbackupdready: JetMongo is not ready. Error: No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling ismaster on 'localhost:27217']
May 30 21:39:17 server systemd: jetbackup5d.service: control process exited, code=exited status=1
May 30 21:39:17 server systemd: Failed to start JetBackup Service.

 

Description

JetBackup cannot start if the jetmongod service is not running. Restarting the jetmongod service will allow JetBackup to start.

 

Workaround

  1. Access the server's command line as the 'root' user via SSH or "Terminal" in WHM.
  2. Restart the jetmongod service. 
    systemctl restart jetmongod
  3. Restart the jetbackup5d service. 
    systemctl restart jetbackup5d