Jetmongod Install Errors / jetmongod Service Fails to Start

When installing JetBackup 4/5, you may run into the following error:

ERROR: Can't connect to mongodb. error: %pre(jetbackup-base-5.0.29-28.noarch) scriptlet failed, exit status 1

You can find log information for this error in the following location on the root server: /usr/local/jetapps/var/log/mongod/mongod.log

A common fix to these issues would be the following:

  1. Check that the following paths/files are owned by user mongod:mongod:
  • /usr/local/jetapps/var/log/mongod
  • /usr/local/jetapps/var/lib/mongod
  • /usr/local/jetapps/var/run/mongod/
  • /tmp/mongodb-27217.sock

    2. Verify users can access /dev/null (chmod 666).
    3. Lastly, check the file permissions for /tmp (chmod 1777).

 

 

If the above suggestions don't resolve the issue, we would recommend submitting a ticket to our FREE 24/7/365 Support Team at support@jetapps.com so we can assist with this issue.
 

  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

JetBackup 5 process stops every 10 minutes

On Cloudlinux servers, it has been reported that the jetbackup5d process is constantly being...

Manually Translating JetBackup Language Files

Both JetBackup 4 and JetBackup 5 now support overwritten language files for cPanel and...

JetBackup Auto-update fails stating package is already installed

We have received some reports of JetBackup 5 not being able to auto-update with the logs showing...

JetBackup Auto-update fails stating package is already installed

We have received some reports of JetBackup 5 not being able to auto-update with the logs showing...

Master Encryption Key Empty After Install

After installing JetBackup 5 from the instructions found at...