Recently server seems to stuck at Backup step pre-backup-done from the log file and not able to continue.
I’m getting messages on the console :
CIFS VFS: Error 11 sending data on socket to server
Sends on sock xxx.xxxx.xxxx stuck for 15 secs.
I tried mounting via command line to the backup storage… I have not problem mounting to the NAS Storage.
Reboot a few times to test using backup-data, still getting same problem.
I tried starting the backup in command line using backup-data. It remain stuck at same step pre-backup-done… and same messages. I tried delete the duplicity folder and reboot, then issue backup-data …makes no difference.
Here’s what in last-backup.log file in /var/log
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Mon May 21 09:31:22 2018
RESTART: The first volume failed to upload before termination.
Restart is impossible…starting backup from beginning.
Reading globbing filelist /tmp/_n5ZFm1vxU
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Does it work if you change to full backup? Maybe the last full backup is not ok.
Maybe it helps to move away the last full backup.
You may try to change the backup location to see if it’s a local or a share problem…
Yes I’m doing a FULL Backup … it’s still a problem. My Nethserver is running in a VMWare 6.0 not sure if that has anything effect. I also clean the /tmp directory too…
Last night’s Last-Backup.log —
Reading globbing filelist /tmp/kuqnz8szCL
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Attempt 1 failed. IOError: [Errno 5] Input/output error
Maybe I’d try a local NAS or another connection… Thanks…
Yes… I did have IPS running… maybe that’s the problem.
meanwhile I switched to NFS protocol to my NAS Storage and that works find.
I’d find some time to test out SWITCHING OFF IPS. It could very well be that’s the problem.
I recall installing IPS a few months ago and since then the BACKUP was partially successful and off.
Thanks for the help… Appreciate it…
I wonder if the CIFS Protocol version has anything to do with the problem too… NOT Sure what version of the CIFS Protocol it’s currently using…