Re: [Duplicity-talk] Fwd: GPG taking many ressources

[Henrik Olsen]

On Aug 14, 2010, at 9:32 PM, Kenneth Loafman wrote:

> Henrik Olsen wrote:
>> On Aug 12, 2010, at 2:02 PM, address@hidden wrote:
>> 
>>> On 12.08.2010 13:21, Kenneth Loafman wrote:
>>>> Jacob Godserv wrote:
>>>>> On Tue, Aug 10, 2010 at 17:25, Henrik
>>>>> Olsen<address@hidden>  wrote:
>>>>>> As I'm still having the issue, I was wondering if GPG 1.4.10
>>>>>> could be the issue, and I should try 2.x instead?
>>>> There are still some interface changes that need to be made for
>>>> 2.x, but it might work.
>>> I recall having used duplicity together with gpg2 flawlessly.
>>> Worked for me.
>> 
>> Trying with gpg2 now. Took a bit to get it to compile with the many
>> dependencies, but now duplicity can use it, as long as I change
>> self.call from gpg to gpg2 in GnuPGInterface.py.
>> 
>> But... Unfortunately I still see a heavy ressource usage, exactly
>> like with gpg. Now with gpg2 as well, and as I noticed yesterday with
>> gpg, also even if only one process is running:
>> 
>> ps aux | grep gpg root     98278  95.1  0.0  2436668    804 s000  RN+
>> 8:42PM   2:28.35 gpg2 --status-fd 5 --passphrase-fd 10 --logger-fd 3
>> --batch --no-tty --no-secmem-warning --decrypt holsen   98287   0.8
>> 0.0  2435036    528 s002  S+    8:44PM   0:00.00 grep gpg
>> 
>> On non-OSX usage, do anyone ever see gpg usage like this?
> 
> Did gpg2 solve the issue of multiple gpg processes running?  From your
> example, it looks like it did.  If so, that was the issue that I was
> trying to solve.  Every gpg process that is still open is tying up 3
> file descriptors and a very small amount of memory, but no CPU.  With
> long chains of incrementals some people were running out of open files.

Is it possible that a particular backup can have been corrupted somehow, 
causing an endless loop in gpg? I have doing incrementals on another user 
account on the same machine, and here I do not see the problem. The one having 
the issue has a long history, so I would not like to flush it and start all 
over. Perhaps I should force a full backup? I already did multiple cleanup runs 
with the force option.

/Henrik