[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Sigh

From: jonathan . w . smith
Subject: Re: [Duplicity-talk] Sigh
Date: Wed, 03 Aug 2005 23:43:17 +0000

Thanks for the replies everyone. I saw what I did wrong. I needed to run 
ssh-add to have a proper identity to avoid the repeated prompting for 

This will work for debugging the homebrew script and hopefully achieving a full 
backup on the backup server. I certainly will have time in the meanwhile to 
consider your suggestions since I want the script to work as a cron job.

Again, thanks for the quick response. 

P.S. Talking about "eyes glazing over rapidly; --verbosity 9 sure does it to 
these tired eyes.
 -------------- Original message ----------------------
From: Nick Austin <address@hidden>

--- Begin Message --- Subject: Re: [Duplicity-talk] Sigh Date: Wed, 3 Aug 2005 20:44:00 +0000
On Wed, Aug 03, 2005 at 04:33:56PM -0400, JonathanSmith wrote:
> I was hoping for some competency, so that it would be unnecessary to 
> subscribe to yet another list. No such luck, so now I have to ask for 
> help. I currently am being prompted "Enter passphrase for key 
> '/root/.ssh/id_rsa':" for each segment of a backup that goes to the 
> backup server.

You need to have an ssh-agent setup for this to work.

Check this out for an easy way to get this setup:

> Backup ran for about 35 hours and then stopped without indication of a 
> successful full backup. 

You should run one with --verbosity 9 set.

Let that run in a terminal, and when it fails, you will know what it was
doing right before the failure happened.

> following message: "Warning, found incomplete backup sets, probably left 
> from aborted session No signatures found, switching to full backup."

This is just to let you know that the last backup did not work.


Attachment: pgppKZQrsIGKP.pgp
Description: PGP signature

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]