One more thing: Try using the paramiko+sftp backend instead of the
pexpect+sftp backend.
On Thu, Nov 12, 2020 at 10:55 AM M <email address hidden> wrote:
> Updated to 0.8.17 - no difference!
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1895353
>
> Title:
> Unable to restore backup due to FD_SETSIZE
>
> Status in Duplicity:
> Incomplete
>
> Bug description:
> trying to restore a backup shows the following error:
> ValueError: filedescriptor out of range in select()
>
> and then nothing else happens.
>
>
> You can see, ~170 instances of gpg were spawned in order to restore the
> backup. It was not "ideal" having incremental backups for 2 month, but
> still it should be possible to recover backups like this
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1895353/+subscriptions
>
One more thing: Try using the paramiko+sftp backend instead of the
pexpect+sftp backend.
On Thu, Nov 12, 2020 at 10:55 AM M <email address hidden> wrote:
> Updated to 0.8.17 - no difference! /bugs.launchpad .net/bugs/ 1895353 /bugs.launchpad .net/duplicity/ +bug/1895353/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https:/
>
> Title:
> Unable to restore backup due to FD_SETSIZE
>
> Status in Duplicity:
> Incomplete
>
> Bug description:
> trying to restore a backup shows the following error:
> ValueError: filedescriptor out of range in select()
>
> and then nothing else happens.
>
>
> You can see, ~170 instances of gpg were spawned in order to restore the
> backup. It was not "ideal" having incremental backups for 2 month, but
> still it should be possible to recover backups like this
>
> To manage notifications about this bug go to:
> https:/
>