Search our documentation...

Simply enter what you are looking for!

NOTICE: THIS IS OLD LEGACY DOCUMENTATION FOR JETBACKUP 3.1 (EOL), FOR THE NEWER MOST UPDATED DOCUMENTATION PLEASE VISIT: http://docs.jetbackup.com

Job failed with “lve_suwrapper – No such file or directory” error

When cloudlinux support enabled ( JBM > Settings > Performance Settings ), you will also activate cloudlinux’s security functions.Since the backup / restore job will be running inside virtual LVE user, it will be restricted by cloudlinux security limits.Example output from log file –

[14/Jan/2016 14:12:02 +0800] JBM Version 3.0.64
[14/Jan/2016 14:12:02 +0800] Server process id "516370"
[14/Jan/2016 14:12:02 +0800] This restore was flagged from the IP Address "1.1.1.1"
[14/Jan/2016 14:12:02 +0800] Restore for the account fooboo...
[14/Jan/2016 14:12:02 +0800] Backup date "01 Jan 2016 02:14 AM"
[14/Jan/2016 14:12:02 +0800] Retrieving server accesshash...DONE
[14/Jan/2016 14:12:02 +0800] Retrieving account information...
[14/Jan/2016 14:12:02 +0800] Retrieving account homedir...DONE
[14/Jan/2016 14:12:02 +0800] Searching for account IP information...SAME AS MAIN SHARED
[14/Jan/2016 14:12:02 +0800] Searching for account SSL Certificates...NOT FOUND
[14/Jan/2016 14:12:02 +0800] Connecting to backup destination...DONE
[14/Jan/2016 14:12:03 +0800] Checking server load...(limit is 5)
[14/Jan/2016 14:12:03 +0800] Server load: 1.98
[14/Jan/2016 14:12:03 +0800] Copying backup files to local workspace...FAILED - lve_suwrapper: /etc/serverbackupsmanager/workspace/bash/jbm_1cb64a6128f9421ddb91dfb6cf167a4c_1452752124: No such file or directory
[14/Jan/2016 14:15:25 +0800] Unable to copy files from backup destination - lve_suwrapper: /etc/serverbackupsmanager/workspace/bash/jbm_1cb64a6128f9421ddb91dfb6cf167a4c_1452752124: No such file or directory

To resolve this issue, your backup folder should be included in mountpoint list of CageFS (http://docs.cloudlinux.com/index.html?mount_points.html)

echo "/my_mount_point" >> /etc/cagefs/cagefs.mp
cagefsctl --remount-all

* Running the job while cloudlinux support is disabled should resolve this issue