Re: [Duplicity-talk] Duplicity process killed

[Chris Vanden Berghe]

Hi Edgar,

I was unsuccessful in getting useful data from htop. It seems like tree
view and sorting on memory usage features are mutually exclusive in
htop... so when I enable tree view I no longer see the duplicity process
(off screen) and when I sort on memory I do not see Duplicity's children
(if any).

I did manage to do a 'ps aux' just before the process was killed
(attached). Again it seems that only duplicity is shown... I cannot find
gpg in the process list.

I have version 1.4.18 of GnuPG installed on my server.

Anything more I can do?

Regards,
Chris.

---
On 14/07/2016 18:46, edgar.soldin--- via Duplicity-talk wrote:
> Chris,
>
> the gpg.py looks good. 
>
> can you run your duplicity command in in another terminal htop and enable 
> tree view. than you can observe in real time which processes duplicity starts 
> and what memory is used by whom. goal is to find out whether duplicity itself 
> amasses memory or if there gpg processes keep lingering around or whatever 
> eats up the memory.
>
> ..ede/duply.net
>
>
> On 14.07.2016 03:43, Chris Vanden Berghe via Duplicity-talk wrote:
>> Hi Edgar,
>>
>> I installed Duplicity from
>> http://ppa.launchpad.net/duplicity-team/ppa/ubuntu. I have attached my
>> gpg.py.
>>
>> Boto might have been upgraded, but difficult to say for sure. I
>> currently have 2.38.0 from
>> https://launchpad.net/ubuntu/+source/python-boto installed. To test I
>> have installed 2.34.0 and 2.40.0, and both yield the same result.
>>
>> Regards,
>> Chris.
>>
>> ---
>> On 13/07/2016 17:26, edgar.soldin--- via Duplicity-talk wrote:
>>> On 13.07.2016 08:54, Chris Vanden Berghe via Duplicity-talk wrote:
>>>> But what about the root cause? Version 0.6.x has worked without issue
>>>> for many months (years?).
>>>>
>>>> Is there a particular reason why memory usage has increased
>>>> significantly with version 0.7.x? Is Duplicity 0.7.x expected to use
>>>> more than 1.4GB for a backup?
>>> nope. not at all. in the past memory leakage happened due to a patched 
>>> duplicity by maintainers. where did you get you duplicity? can you post 
>>> 'duplicity/gpg.py' of your installation?
>>>
>>> as you are the first with that issue, maybe it is not duplicity at all but 
>>> your boto library. did you change it's version during the upgrade as well?
>>>
>>> ..ede/duply.net
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> address@hidden
>>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk

duplicity.txt
Description: Text document