{"id":14306,"date":"2025-10-11T05:59:53","date_gmt":"2025-10-11T11:59:53","guid":{"rendered":"https:\/\/www.supportpro.com\/blog\/?p=14306"},"modified":"2025-10-11T05:59:56","modified_gmt":"2025-10-11T11:59:56","slug":"why-jetbackup-backup-jobs-fail-and-how-to-troubleshoot-them","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/why-jetbackup-backup-jobs-fail-and-how-to-troubleshoot-them\/","title":{"rendered":"Why JetBackup backup jobs fail and how to troubleshoot them"},"content":{"rendered":"\n

If you\u2019ve ever worked with JetBackup 5<\/strong>, you\u2019ve probably seen at least one error that makes your heart sink. For me, one of the trickiest was this MongoDB connection issue:<\/p>\n\n\n\n

Fatal error: Uncaught MongoDB\\Driver\\Exception\\ConnectionTimeoutException:\u00a0
No suitable servers found (serverSelectionTryOnce` set):\u00a0
[connection refused calling hello on ‘localhost:27217’]<\/p>\n\n\n\n

Looks ugly, right? But here\u2019s the truth: it\u2019s basically JetBackup saying, \u201cHey, I tried to talk to MongoDB on port 27217, but it wouldn\u2019t answer.\u201d<\/em> I\u2019ve run into this a few times, and the good news is \u2014 there are clear steps you can take to sort it out. Let me walk you through how I usually troubleshoot it.<\/p>\n\n\n\n\n\n\n\n

Start with the Obvious: Are the Services Running?<\/strong><\/h2>\n\n\n\n

Most of the time, this error pops up because JetBackup or MongoDB just isn\u2019t running. Check them with:<\/p>\n\n\n\n

service jetmongod status<\/p>\n\n\n\n

service jetbackup5d status<\/p>\n\n\n\n

One quick warning: if a backup or reindex job is running, restarting services will stop them. So, if the job is important, wait until it finishes. If everything starts fine, reload the JetBackup GUI. Sometimes, that\u2019s all it takes.<\/p>\n\n\n\n

Disk Space Can Be the Culprit<\/strong><\/h2>\n\n\n\n

MongoDB is picky about storage. If your server\u2019s out of space, it won\u2019t run. Run this command:<\/p>\n\n\n\n

df -h<\/p>\n\n\n\n

If you see a partition at 100%, clean up some files. Logs and temp files usually eat a lot of space. Once you\u2019ve freed up some room, restart:<\/p>\n\n\n\n

service jetmongod restart   # give it ~10 seconds<\/p>\n\n\n\n

service jetbackup5d restart<\/p>\n\n\n\n

Socket File & Permissions<\/strong><\/h2>\n\n\n\n

MongoDB relies on a socket file \u2014 you\u2019ll find it at \/tmp\/mongodb-27217.sock. It needs to belong to mongod:mongod.<\/p>\n\n\n\n

Also check the \/tmp folder itself:<\/p>\n\n\n\n

ls -ld \/tmp<\/p>\n\n\n\n

It should show drwxrwxrwt (that \u201ct\u201d at the end means sticky bit, aka permissions set to 1777).<\/p>\n\n\n\n

The \/etc\/hosts Gotcha (IPv6 vs IPv4)<\/strong><\/h2>\n\n\n\n

This one has caught me before. Sometimes MongoDB fails because localhost points to IPv6 instead of IPv4.<\/p>\n\n\n\n

Open \/etc\/hosts and look for something like this:<\/p>\n\n\n\n

::1 \u00a0 localhost localhost.localdomain localhost6 localhost6.localdomain6<\/code><\/p>\n\n\n\n

If that\u2019s the only localhost entry, you\u2019ll run into issues. Add the IPv4 line back:<\/p>\n\n\n\n

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4<\/code><\/p>\n\n\n\n

::1 \u00a0 \u00a0 \u00a0 localhost localhost.localdomain localhost6 localhost6.localdomain6<\/code><\/p>\n\n\n\n

Save, restart JetBackup, and you\u2019re good.<\/p>\n\n\n\n

Check Port 27217<\/strong><\/h2>\n\n\n\n

JetBackup talks to MongoDB on port 27217<\/strong>. Make sure nothing\u2019s blocking it:<\/p>\n\n\n\n

nc -v localhost 27217<\/code><\/p>\n\n\n\n

If you see \u201cConnected,\u201d you\u2019re fine. If you see \u201cConnection refused,\u201d the port\u2019s blocked or MongoDB isn\u2019t listening \u2014 time to dig deeper (or get your sysadmin involved).<\/p>\n\n\n\n

When All Else Fails: Look at the Logs<\/strong><\/h2>\n\n\n\n

Logs don\u2019t lie. Check:<\/p>\n\n\n\n

cat \/usr\/local\/jetapps\/var\/log\/mongod\/mongod.log<\/code><\/p>\n\n\n\n

If you spot corruption errors or MongoDB refusing to start properly, the install might be broken. At this point, you\u2019ll probably need to reinstall JetBackup.<\/p>\n\n\n\n

Reinstalling JetBackup 5 (Last Resort)<\/strong><\/h2>\n\n\n\n

Before wiping it out, save your config exports<\/strong> so you don\u2019t lose everything:<\/p>\n\n\n\n

cp \/usr\/local\/jetapps\/usr\/jetbackup\/dailybackup \/root\/jetbackup<\/code><\/p>\n\n\n\n

Then remove the packages (for CentOS\/CloudLinux\/AlmaLinux\/Rocky):<\/p>\n\n\n\n

yum remove jetbackup5-base jetbackup5-directadmin jetmongod<\/p>\n\n\n\n

Reinstall with:<\/p>\n\n\n\n

jetapps --install jetbackup5-directadmin stable<\/code><\/p>\n\n\n\n

Finally, import your config:<\/p>\n\n\n\n

jetbackup --import \/root\/jetbackup\/jetbackup5_export_000000.tar.gz<\/code><\/p>\n\n\n\n

(Replace the filename with your actual export.)<\/em><\/p>\n\n\n\n

You\u2019ll also need to reindex your destinations:<\/p>\n\n\n\n

for id in $(jetbackup5api -F listDestinations | grep '_id: ' | awk '{print $2}'); do\u00a0<\/code><\/p>\n\n\n\n

\u00a0\u00a0\u00a0\u00a0jetbackup5api -F reindexDestination -D \"_id=$id\" ;\u00a0<\/code><\/p>\n\n\n\n

done<\/p>\n\n\n\n

It takes a few minutes, but once that\u2019s done, JetBackup should be back in business.<\/p>\n\n\n\n

Wrapping It Up<\/strong><\/h2>\n\n\n\n

So, what looks like a scary MongoDB connection error usually boils down to a few common issues: services not running, disk space full, wrong localhost config, or port problems. And in the rare case MongoDB is truly corrupted, reinstalling JetBackup fixes it.<\/p>\n\n\n\n

The key is to start simple and work your way down the list. Nine times out of ten, you won\u2019t need to reinstall. But it\u2019s good to know that option is there if nothing else works. And here\u2019s the real takeaway: don\u2019t let that giant wall of error text freak you out. With SupportPRO<\/a>‘s help, you can get JetBackup talking to MongoDB again and your backups running smoothly.<\/p>\n\n\n\n

\n

Facing issues? <\/p>\n\n\n\n

Our technical support
engineers can solve it. <\/p>\n\n\n\n\"Contact<\/a><\/span>