[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Fwd: Re: Duplicity process killed
From: |
Chris Vanden Berghe |
Subject: |
Re: [Duplicity-talk] Fwd: Re: Duplicity process killed |
Date: |
Fri, 15 Jul 2016 17:45:39 +0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 |
Scrolling down was too obvious, I guess ;-) I have attached a screenshot
of what I see a second before Duplicity is killed.
The source files are ~82 GB. The last successful backup:
# /usr/bin/duplicity collection-status --archive-dir=/root/Backup/cache/
gs://bobo-backup/
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Mon Jul 4 17:11:39 2016
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /root/Backup/cache/01f81df3eb37282f76c93fb89a3708f5
Found 0 secondary backup chains.
Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Mon Jul 4 17:11:39 2016
Chain end time: Mon Jul 4 17:11:39 2016
Number of contained backup sets: 1
Total number of contained volumes: 254
Type of backup set: Time: Num volumes:
Full Mon Jul 4 17:11:39 2016 254
-------------------------
No orphaned or incomplete backup sets found.
Regards,
Chris.
---
On 15/07/2016 15:36, edgar.soldin--- via Duplicity-talk wrote:
>> On 15.07.2016 05:39, Chris Vanden Berghe via Duplicity-talk wrote:> 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).
>> hehe, read into how htop works. you can scroll the list w/ the cursor keys.
>>
> sort by tree _and_ memory are mutually exclusive. so you have to sort by tree
> and scroll to duplicity, make the terminal big enough to see all it's sub
> processes and look out for the culprit yourself.
>
> btw. how big is your backup. size of data, number/size of volumes per
> full/chain.
>
> ..ede
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
duplicity.png
Description: PNG image
- Re: [Duplicity-talk] Duplicity process killed, (continued)
- Re: [Duplicity-talk] Duplicity process killed, Chris Vanden Berghe, 2016/07/12
- Re: [Duplicity-talk] Duplicity process killed, Mark Grandi, 2016/07/12
- Re: [Duplicity-talk] Duplicity process killed, Nate Eldredge, 2016/07/12
- Re: [Duplicity-talk] Duplicity process killed, Chris Vanden Berghe, 2016/07/13
- Re: [Duplicity-talk] Duplicity process killed, edgar . soldin, 2016/07/13
- Re: [Duplicity-talk] Duplicity process killed, Chris Vanden Berghe, 2016/07/13
- Re: [Duplicity-talk] Duplicity process killed, edgar . soldin, 2016/07/14
- Re: [Duplicity-talk] Duplicity process killed, Chris Vanden Berghe, 2016/07/14
- Re: [Duplicity-talk] Duplicity process killed, edgar . soldin, 2016/07/15
- [Duplicity-talk] Fwd: Re: Duplicity process killed, edgar . soldin, 2016/07/15
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed,
Chris Vanden Berghe <=
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed, edgar . soldin, 2016/07/15
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed, edgar . soldin, 2016/07/15
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed, Kenneth Loafman, 2016/07/15
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed, Chris Vanden Berghe, 2016/07/16
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed, covici, 2016/07/16
- Re: [Duplicity-talk] Fwd: Re: Duplicity process killed, Chris Vanden Berghe, 2016/07/16