'Never Finished' error in JetBackup 5

'Never Finished' error in JetBackup 5

The "Never Finished" error in JetBackup happens when a backup job doesn’t complete properly, leaving the process stuck in a "never finished" state. This issue can pop up for a bunch of reasons, like JetBackup services acting up, cache problems, or misconfigurations. Below, we’ll walk you through how to spot and fix this problem.

What Does the Problem Look Like?

  • The backup job doesn’t finish and shows a "Never Finished" status in JetBackup logs.
  • The backup process seems to hang and never completes, even though backups for other users or accounts work just fine.
  • The logs don’t show any specific errors, but the backup just won’t finish.

What Usually Causes This?

  1. JetBackup Services Acting Up: Sometimes, JetBackup services can get stuck or unstable because of cached data or internal glitches.
  2. Misconfigured Settings: If your backup settings aren’t set up right, it can cause the process to fail or get stuck.
  3. Sync Issues: In some cases, the backup might fail to sync with the destination server, stopping the process from completing.

How to Fix It: Restart JetBackup Services

One of the easiest and most effective ways to fix the "Never Finished" error is to restart JetBackup services. Here’s how to do it:

  1. Log into your server via SSH using your admin credentials.
  2. Restart JetBackup services by running these commands:

# service jetmongod restart
# service jetbackup5d restart

These commands will restart JetBackup and MongoDB services, which can clear out any cached data or unstable states causing the issue.

  1. Check the backup status: After restarting the services, manually start the backup job and see if it completes successfully.

Extra Tips to Avoid This Issue

  • Check your disk space: Make sure the destination server has enough space to store your backups.
  • Double-check your backup settings: Ensure your backup configurations are optimized to avoid sync problems.
  • Keep JetBackup updated: If the issue keeps happening, consider updating JetBackup to the latest version. Updates often include bug fixes and performance improvements.

    • Related Articles

    • JetBackup 5: How to fix the Integrity Check error using CLI/SSH

      When JetBackup performs its automated integrity verification processes, they may sometimes complete partially due to network interruptions, timeouts, or communication issues with the remote storage destination. If you receive notifications indicating ...

    • Fix: Service Unavailable Error on CloudLinux Servers

      The "Service Unavailable" error is one of the most common issues on shared hosting servers running CloudLinux with CageFS and mod_lsapi. This error indicates that the server could not process the visitor's request, usually because the PHP backend ...

    • Fix MySQL Stored Procedures Import Error in cPanel

      When working with MySQL databases that include stored procedures, it's common to encounter errors during import in shared hosting environments with cPanel. These errors are usually related to the DEFINER parameter, which specifies the owner of the ...

    • How to Block IPs and Ranges in Imunify360: CLI & GUI Master Guide

      Imunify360 is the ultimate defense for web servers. While its automated firewall is excellent, manual intervention is sometimes necessary to stop botnets or targeted attacks. In this guide, you will learn how to manage blocks precisely using commands ...

    • How to Use Telnet to Test SMTP Connectivity on Port 25

      Telnet is a networking tool that allows you to test connectivity with services on other servers. By using it on port 25, you can verify whether your server is communicating correctly with an SMTP mail server, which is essential for diagnosing email ...