Duplicity

Bug #394629
Comment #9

Comment 9 for bug 394629

Revision history for this message

Cristian Klein (cristiklein) wrote on 2009-07-03: Re: [Bug 394629] Re: Hang on first collection-status

Kenneth Loafman a écrit :
> Cristian KLEIN wrote:
>> Kenneth Loafman a écrit :
>>> Cristian KLEIN wrote:
>>>> Kenneth Loafman a écrit :
>>>>> Cristian KLEIN wrote:
>>>>>> Kenneth Loafman a écrit :
>>>>>>> Is there any way to reproduce this? Does it happen all the time, or
>>>>>>> just sometimes?
>>>>>>>
>>>>>>> I'm having a hard time replicating the problem.
>>>>>> Try to „rm -rf ~/.cache/duplicity” the run duplicity without
>>>>>> „--archive-dir” nor „--name”.
>>>>> No problem with that. It just recreates the dirs, does the resync, then
>>>>> the collection status, no delay anywhere.
>>>> Strange. I can reproduce it every time. At the end, I have three GnuPG
>>>> processes which are:
>>>>
>>>> gpg --status-fd 4 --passphrase-fd 8 --logger-fd 3 --batch --no-tty
>>>> --no-secmem-warning --use-agent --decrypt
>>>> gpg --status-fd 4 --passphrase-fd 9 --logger-fd 3 --batch --no-tty
>>>> --no-secmem-warning --use-agent --decrypt
>>>> gpg --status-fd 4 --passphrase-fd 10 --logger-fd 3 --batch --no-tty
>>>> --no-secmem-warning --use-agent --decrypt
>>>>
>>>> If I kill them by hand, duplicity resumes.
>>>>
>>>> I also tried removing everything duplicity-related and installing it
>>>> from the PPA, but the problem persists.
>>> If you start off with a working archive, does it do the same thing? In
>>> other words, if the first run fails and you rerun, does the second run
>>> fail as well? Or, is it just the first run with an empty archive?
>> It's just the first run with an empty archive. The second time it runs
>> flawlessly.
>
> Here's a patch, no guarantees, but it will change the order of the
> initial collection status and sync. It's possible you've encountered
> some sort of race condition, but who knows.
>
> Apply this to /usr/bin/duplicity, or wherever your have duplicity.
>
>
> ** Attachment added: "duplicity-coll-status-hang.patch"
> http://launchpadlibrarian.net/28656433/duplicity-coll-status-hang.patch
>

Sorry, it doesn't solve the problem. Same effect: 3 GPG processes which,
if killed, duplicity resumes.

Kenneth Loafman a écrit :
> Cristian KLEIN wrote:
>> Kenneth Loafman a écrit :
>>> Cristian KLEIN wrote:
>>>> Kenneth Loafman a écrit :
>>>>> Cristian KLEIN wrote:
>>>>>> Kenneth Loafman a écrit :
>>>>>>> Is there any way to reproduce this?  Does it happen all the time, or
>>>>>>> just sometimes?
>>>>>>>
>>>>>>> I'm having a hard time replicating the problem.
>>>>>> Try to „rm -rf ~/.cache/duplicity” the run duplicity without
>>>>>> „--archive-dir” nor „--name”.
>>>>> No problem with that.  It just recreates the dirs, does the resync, then
>>>>> the collection status, no delay anywhere.
>>>> Strange. I can reproduce it every time. At the end, I have three GnuPG
>>>> processes which are:
>>>>
>>>> gpg --status-fd 4 --passphrase-fd 8 --logger-fd 3 --batch --no-tty
>>>> --no-secmem-warning --use-agent --decrypt
>>>> gpg --status-fd 4 --passphrase-fd 9 --logger-fd 3 --batch --no-tty
>>>> --no-secmem-warning --use-agent --decrypt
>>>> gpg --status-fd 4 --passphrase-fd 10 --logger-fd 3 --batch --no-tty
>>>> --no-secmem-warning --use-agent --decrypt
>>>>
>>>> If I kill them by hand, duplicity resumes.
>>>>
>>>> I also tried removing everything duplicity-related and installing it
>>>> from the PPA, but the problem persists.
>>> If you start off with a working archive, does it do the same thing?  In
>>> other words, if the first run fails and you rerun, does the second run
>>> fail as well?  Or, is it just the first run with an empty archive?
>> It's just the first run with an empty archive. The second time it runs
>> flawlessly.
> 
> Here's a patch, no guarantees, but it will change the order of the
> initial collection status and sync.  It's possible you've encountered
> some sort of race condition, but who knows.
> 
> Apply this to /usr/bin/duplicity, or wherever your have duplicity.
> 
> 
> ** Attachment added: "duplicity-coll-status-hang.patch"
>    http://launchpadlibrarian.net/28656433/duplicity-coll-status-hang.patch
>

Sorry, it doesn't solve the problem. Same effect: 3 GPG processes which,
if killed, duplicity resumes.