There have been some reports of JetBackup 5 Backups Aborting with the following error:
[ERROR] Backup job aborted from hook.
[ERROR] sh: /usr/local/jetapps/var/lib/jetbackup5/Core/Addon/JetBackupMC/Events/Backup_onStart: Permission denied
We have identified this issue as a bug when reinstalling the JBMC Backward Compatible Plugin (v1.0.0) after it is already installed. The Plugin Event Scripts, which are used to send information to a registered JetBackup MC Server, lose their Executable permissions on the reinstall. This results in the above error. In order to resolve this issue currently, please run the following command while the plugin is installed:
chmod +x /usr/local/jetapps/var/lib/jetbackup5/Core/Addon/JetBackupMC/Events/*
This will give each event the proper permissions and will allow backup jobs to continue.
If you see the error message:
[05/Jun/2025 11:19:38 +0000] [PID 1988942] Executing pre backup hook [05/Jun/2025 11:19:39 +0000] [PID 1988942] [ERROR] Backup job aborted from hook. [05/Jun/2025 11:19:39 +0000] [PID 1988942] [ERROR] thrown in /usr/local/jetapps/var/lib/jetbackup5/Core/Web/JetHttp.inc on line 0 (Status Code: 255)
The error thrown in /usr/local/jetapps/var/lib/jetbackup5/Core/Web/JetHttp.inc on line 0 (Status Code: 255) This is a known regression with the JBMC Legacy Plugin and the new JetHttp changes in 5.3.15+ that occurs when there is an error with the connection to JBMC. We have an open case (#JB5-Base-2206) to fix the error message and ensure it's non-fatal in a future release.
In the meantime, there are 2 options to solve the issue:
Option 1 - Disable the JBMC Backward Compatible Plugin
- You can disable the plugin under "JB5 > Plugins > Find the "JetBackup MC Backward Compatible Plugin" and click the toggle under "Enable/Disable"
Option 2 - Fix the Connection Issue to your configured JetBackup MC Server
- You can find the configured JBMC Hostname using the command
jetbackup5api -F Plugin/JetBackupMC/GetSettings - Look for the "
mc_hostname" - you should notice JB5 pushes data to your MC over port 3032 - Try a CURL to the MC Hostname to identify any connection problems:
[root@qa56 ~]# curl https://10.110.50.1:3032 -k curl: (7) Failed to connect to 10.110.50.1 port 3032: Connection timed out
