jetmongod service is down / Jetbackup isn't working

jetmongod service is down

This tutorial was done on a cPanel server

If you get an error like that when you open jetbackup plugin in WHM panel:

Fatal error: Uncaught MongoDB\Driver\Exception\ConnectionTimeoutException: No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling ismaster on 'localhost:27217'] in /usr/local/jetapps/var/lib/jetcore/data/Mongo.inc:131 Stack trace: #0 /usr/local/jetapps/var/lib/jetcore/data/Mongo.inc(131): MongoDB\Driver\Manager->executeQuery('jetbackup.confi...', Object(MongoDB\Driver\Query)) #1 /usr/local/jetapps/var/lib/jetcore/data/MongoCollection.inc(91): nss\core\data\Mongo->_execute_query('jetbackup.confi...', Object(MongoDB\Driver\Query)) #2 /usr/local/jetapps/var/lib/jetcore/data/MongoCollection.inc(104): nss\core\data\MongoCollection->_find(Array, NULL, NULL, 1, 0) #3 /usr/local/jetapps/var/lib/jetcore/data/MongoCollection.inc(116): nss\core\data\MongoCollection->find(Array, NULL, NULL, 1, 0) #4 /usr/local/jetapps/var/lib/jetcore/data/MongoObject.inc(141): nss\core\data\MongoCollection->findOne(Array, NULL) #5 /usr/local/jetapps/var/lib/JetBackup/Core/Config/BinaryLocation.inc(63): nss\core\data\Mon in /usr/local/jetapps/var/lib/jetcore/data/Mongo.inc on line 131

Then it's likely that your jetmongod service is down.

Let's check what's wrong, Run the following command

service jetmongod status

If you get an output like that, Then you have nothing wrong with jetmongod

Redirecting to /bin/systemctl status jetmongod.service

? jetmongod.service - High-performance, schema-free document-oriented database

   Loaded: loaded (/usr/lib/systemd/system/jetmongod.service; enabled; vendor preset: disabled)

   Active: active (running) since Sun 2021-08-15 09:48:38 EDT; 2min 4s ago

If the command doesn't say that the service is running. Then continue the tutorial.

Let's try to start it. Run this command:

service jetmongod start;

Then let's try to check if it's now running. Run:

service jetmongod status

If it's still not running. Then most likely you will have incorrect permissions for mongod socket, You can correct it using the following command:

chmod +X /tmp/mongodb-27217.sock;chmod +X /tmp/;chown mongod:mongod  /tmp/mongodb-27217.sock;

After that let's restart the jetmongod service using:

service jetmongod restart;

Let's check if it's now running.

service jetmongod status;

The output now should contain:

   Active: active (running) since Sun 2021-08-15 09:48:38 EDT; 2min 4s ago

The problem should be now fixed