Re: [rdiff-backup-users] "Found too many current_mirror incs!"

On 04/05/2017 06:39, Dominic Raferd wrote: On 3 May 2017 at 22:28, Ron Leach wrote: I'm assuming the script should be run from the machine that initiates the backup - is that correct? Or should I be doing this differently? ​The script needs to run locally on the

[rdiff-backup-users] Exception Bad index order XXX >= ('long_filename_data', '35')' raised of class '':

Dear list, Backup was working fine until the following subsequent runs of rdiff backup occurred 1st run) Write failed: Broken pipe Fatal Error: Lost connection to the remote system -- No more logs available 2nd run) Previous backup seems to have failed, regressing destination now. Exception

Re: [rdiff-backup-users] "Found too many current_mirror incs!"

On 4 May 2017 at 09:44, Ron Leach wrote: > > > Thanks, I've done that and I think there must be, after all that, a > somewhat more-serious problem. The regress started then aborted saying > > Error 1 occurred when attempting to regress archive... > ls: cannot access

Re: [rdiff-backup-users] Exception Bad index order XXX >= ('long_filename_data', '35')' raised of class '':

Hi, > Exception '[Errno 28] No space left on device' raised of class '': -- Piotr. On Thu, May 4, 2017 at 9:26 AM, Friedrich Praus wrote: > Dear list, > > Backup was working fine until the following subsequent runs of rdiff backup > occurred > > 1st run) Write failed:

Re: [rdiff-backup-users] Exception Bad index order XXX >= ('long_filename_data', '35')' raised of class '':

On 2017-05-04 09:26, Friedrich Praus wrote: Fatal Error: Lost connection to the remote system Any comments on how to fix this? I may be wrong, but isn't the last message the likely culprit? N. ___ rdiff-backup-users mailing list at