Re: [Duplicity-talk] duplicity backup problem "ETA Stalled!"

[sirmacik]

address@hidden dixit (2014-02-15, 15:24):

> never used --progress, but it reads from the merged branch that only s3 is 
> currently supported
> https://code.launchpad.net/~juan-f/duplicity/progress/+merge/144944
> 
> i cannot reach the author Juan though, his old email is dead.

I might be able to look at it and try to fix it in following weeks. 

> On 15.02.2014 15:07, Echo Nolan wrote:
> > Edgar et al,
> > 
> > --progress is definitely broken with file backup and asymmetric encryption 
> > on bzr head on my machine. Here's a log:
> > 
> > enolan at enolan-desktop in ~/mystuff/code/duplicity 
> > $ ./bin/duplicity --progress --encrypt-key=A8BBA610 --sign-key=A8BBA610 
> > ~/mystuff/ file:///home/enolan/junk/backuptest
> > Synchronizing remote metadata to local cache...
> > Deleting local 
> > /home/enolan/.cache/duplicity/1a3711ce1fcc213849f05d15d3719b31/duplicity-full-signatures.20140215T140100Z.sigtar.gz
> >  (not authoritative at backend).
> > Deleting local 
> > /home/enolan/.cache/duplicity/1a3711ce1fcc213849f05d15d3719b31/duplicity-full.20140215T140100Z.manifest
> >  (not authoritative at backend).
> > Last full backup date: none
> > GnuPG passphrase:
> > GnuPG passphrase for signing key:
> > No signatures found, switching to full backup.
> > 0.0KB 00:00:03 [0.0KB/s] [>                                        ] 0% ETA 
> > 3sec
> > 0.0KB 00:00:06 [0.0KB/s] [>                                        ] 0% ETA 
> > 6sec
> > 0.0KB 00:00:09 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:12 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:15 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:18 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:21 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:24 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:27 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:30 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:33 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:36 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:39 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:42 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:45 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:48 [0.0B/s] [>                                        ] 0% ETA 
> > Stalled!
> > 0.0KB 00:00:51 [0.0KB/s] [========================================>] 100% 
> > ETA 0sec
> > --------------[ Backup Statistics ]--------------
> > StartTime 1392473040.30 (Sat Feb 15 06:04:00 2014)
> > EndTime 1392473088.99 (Sat Feb 15 06:04:48 2014)
> > ElapsedTime 48.69 (48.69 seconds)
> > SourceFiles 15196
> > SourceFileSize 1051870934 (1003 MB)
> > NewFiles 15196
> > NewFileSize 1051870934 (1003 MB)
> > DeletedFiles 0
> > ChangedFiles 0
> > ChangedFileSize 0 (0 bytes)
> > ChangedDeltaSize 0 (0 bytes)
> > DeltaEntries 15196
> > RawDeltaSize 1051256470 (1003 MB)
> > TotalDestinationSizeChange 522858967 (499 MB)
> > Errors 0
> > -------------------------------------------------
> > 
> > 
> > 
> > On Sat, Feb 15, 2014 at 5:53 AM, <address@hidden <mailto:address@hidden>> 
> > wrote:
> > 
> >     hmm.. that would be a first!
> > 
> >     first, make sure you're running the latest duplicity.
> > 
> >     if the problem persists, please run your backup command with '-v9' and 
> > post the complete terminal output here. zip and attach if big. check for 
> > private strings in it you might want to obfuscate first.
> > 
> >     give it some time to run, say 1h or so. try a file:// target to make 
> > sure it is not remote backend related.
> > 
> >     ..ede/duply.net <http://duply.net>
> > 
> > 
> >     On 15.02.2014 14:36, sirmacik wrote:
> >     > Echo Nolan dixit (2014-02-15, 02:13):
> >     >
> >     >> On further investigation, --progress is broken. To check the 
> > progress of
> >     >> your backup you can sftp manually to the destination server and 
> > watch the
> >     >> duplicity-*.gpg files get created. Or you could pass -v8 to 
> > duplicity, but
> >     >> this may slow things down due to the overhead of printing every 
> > single
> >     >> filename to stdout.
> >     >
> >     > ETA gets really stalled. There isn't a single file created. With
> >     > --progress or without. Also while ysing any other backend.
> >     >
> >     >> On Fri, Feb 14, 2014 at 7:52 PM, sirmacik <address@hidden 
> > <mailto:address@hidden>> wrote:
> >     >>
> >     >>> Echo Nolan dixit (2014-02-14, 19:10):
> >     >>>
> >     >>>> Hi Marcin. This is probably a problem with your destination 
> > server. The
> >     >>>> size of the files you're backing up shouldn't matter, the "vol1" 
> > in the
> >     >>>> filename it is trying to upload means it's the first 25mb chunk. 
> > Try
> >     >>> using
> >     >>>> sftp directly and uploading something else.
> >     >>>
> >     >>> Thanks for your response! I understand that the number also should 
> > not
> >     >>> be an issue? It works with plain sftp. I've uploaded files to that
> >     >>> directory without any problems. That ETA stalled occurs also while
> >     >>> trying to back up that directory to file:///home/username/ and other
> >     >>> directories.
> >     >>>
> >     >>>> On Fri, Feb 14, 2014 at 7:01 AM, sirmacik <address@hidden 
> > <mailto:address@hidden>>
> >     >>> wrote:
> >     >>>>
> >     >>>>> Hi there!
> >     >>>>>
> >     >>>>> I've got a bit of a problem here using duplicity. I'm trying to 
> > backup
> >     >>>>> directory ~/Mail which consists of 3 maildirs (about 90 000 
> > messages -
> >     >>> 17G)
> >     >>>>> + git repo which is a versioning of those in case of any fuckup by
> >     >>>>> offlineimap (and those sometimes happen). Duplicity starts its 
> > work and
> >     >>>>> nothing happens. I've added --progress option and this is what I 
> > get:
> >     >>>>>
> >     >>>>>> duplicity --progress --encrypt-key=DBAB60F2 --sign-key=DBAB60F2
> >     >>> ~/Mail/
> >     >>>>> sftp://address@hidden//home/sirmacik/Mail_bak 
> > <http://address@hidden//home/sirmacik/Mail_bak>
> >     >>>>> Local and Remote metadata are synchronized, no sync needed.
> >     >>>>> Warning, found incomplete backup sets, probably left from aborted
> >     >>> session
> >     >>>>> Last full backup date: none
> >     >>>>> GnuPG passphrase:
> >     >>>>> GnuPG passphrase for signing key:
> >     >>>>> Nie odnaleziono sygnatur, zmiana na pełną kopię zapasową.
> >     >>>>> 0.0KB 00:00:03 [0.0KB/s] [>                                       
> >  ] 0%
> >     >>>>> ETA 3sec
> >     >>>>> 0.0KB 00:00:06 [0.0KB/s] [>                                       
> >  ] 0%
> >     >>>>> ETA 6sec
> >     >>>>> 0.0KB 00:00:09 [0.0B/s] [>                                        
> > ] 0%
> >     >>> ETA
> >     >>>>> Stalled!
> >     >>>>> 0.0KB 00:00:12 [0.0B/s] [>                                        
> > ] 0%
> >     >>> ETA
> >     >>>>> Stalled!
> >     >>>>> 0.0KB 00:00:15 [0.0B/s] [>                                        
> > ] 0%
> >     >>> ETA
> >     >>>>> Stalled!
> >     >>>>> 0.0KB 00:00:18 [0.0B/s] [>                                        
> > ] 0%
> >     >>> ETA
> >     >>>>> Stalled!
> >     >>>>> 0.0KB 00:00:21 [0.0B/s] [>                                        
> > ] 0%
> >     >>> ETA
> >     >>>>> Stalled!
> >     >>>>> ^Csftp put of /tmp/duplicity-y5GaLz-tempdir/mktemp-cY64Cf-2 (as
> >     >>>>> duplicity-full.20140214T145706Z.vol1.difftar.gpg) failed: Server
> >     >>> connection
> >     >>>>> dropped:  (Try 1 of 5) Will retry in 10 seconds.
> >     >>>>> 0.0KB 00:00:24 [0.0B/s] [>                                        
> > ] 0%
> >     >>> ETA
> >     >>>>> Stalled!
> >     >>>>>
> >     >>>>> Am I doing something wrong or duplicity has a problem with such a 
> > large
> >     >>>>> group of files?
> >     >>>>>

-- 
Marcin

pgpo5aNSaOy1J.pgp
Description: PGP signature