Front page

lock timeout, client does not exist, force-lock doesn't work

4354e38c3de14c31adff432ee36f0ca3
CRUCIAL EQUATION TISSUE

From: obnamsupport <obnamsupport@infopower.nl>
Date: Sun, 3 Apr 2016 16:45:08 +0000

   Well, the subject says it already.
   
   I wasn't aware that gpg-agent should be running before doing my first
   backup, so my guess is that the first attempt set the lock (for the
   client?) and exited on a not running gpg-agent.
   So I started gpg-agent, ran a 'force-lock' and got the warning that
   client doesn't exist. Any new attempt to backup ended in a lock-timeout.
   
   What now? Manually remove the lock? Simply looking for a file 'lock'
   and remove it by hand?
   
   
   Thanks,
   
   joe
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: obnamsupport <obnamsupport@infopower.nl>
Date: Sun, 3 Apr 2016 17:14:29 +0000

   Ok, I just removed the lock because the whole repository is still empty
   anyway so no harm can be done.
   Now gpg-agent is running as daemon with ssh-support but the result is
   that obnam says 
   
   "adding clientERROR: gpg: can't query passphrase in batch mode
   gpg: decryption failed: secret key not available"
   
   I might suppose here that somehow gpg-agent isn't configured correctly.
   Could anyone hint me in the right direction please?
   
   
   thanks,
   
   joe
   
   
   
   On Sun, 3 Apr 2016 16:45:08 +0000
   obnamsupport <obnamsupport@infopower.nl> wrote:
   
   > Well, the subject says it already.
   > 
   > I wasn't aware that gpg-agent should be running before doing my first
   > backup, so my guess is that the first attempt set the lock (for the
   > client?) and exited on a not running gpg-agent.
   > So I started gpg-agent, ran a 'force-lock' and got the warning that
   > client doesn't exist. Any new attempt to backup ended in a
   > lock-timeout.
   > 
   > What now? Manually remove the lock? Simply looking for a file 'lock'
   > and remove it by hand?
   > 
   > 
   > Thanks,
   > 
   > joe
   > 
   
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Lars Wirzenius <liw@liw.fi>
Date: Tue, 12 Apr 2016 09:39:02 +0300

   On Sun, Apr 03, 2016 at 05:14:29PM +0000, obnamsupport wrote:
   > Ok, I just removed the lock because the whole repository is still empty
   > anyway so no harm can be done.
   > Now gpg-agent is running as daemon with ssh-support but the result is
   > that obnam says 
   > 
   > "adding clientERROR: gpg: can't query passphrase in batch mode
   > gpg: decryption failed: secret key not available"
   > 
   > I might suppose here that somehow gpg-agent isn't configured correctly.
   > Could anyone hint me in the right direction please?
   
   My first guess would be that the gpg that Obnam runs somehow can't
   access the gpg-agent you're running. But someone who's more familiar
   with how the agents work should answer this. I just use GNOME on
   Debian and things work out of the box for me.
From: obnamsupport <obnamsupport@infopower.nl>
Date: Tue, 12 Apr 2016 12:04:13 +0000

   On Tue, 12 Apr 2016 09:39:02 +0300
   Lars Wirzenius <liw@liw.fi> wrote:
   
   > On Sun, Apr 03, 2016 at 05:14:29PM +0000, obnamsupport wrote:
   > > Ok, I just removed the lock because the whole repository is still
   > > empty anyway so no harm can be done.
   > > Now gpg-agent is running as daemon with ssh-support but the result
   > > is that obnam says 
   > > 
   > > "adding clientERROR: gpg: can't query passphrase in batch mode
   > > gpg: decryption failed: secret key not available"
   > > 
   > > I might suppose here that somehow gpg-agent isn't configured
   > > correctly. Could anyone hint me in the right direction please?
   > 
   > My first guess would be that the gpg that Obnam runs somehow can't
   > access the gpg-agent you're running. But someone who's more familiar
   > with how the agents work should answer this. I just use GNOME on
   > Debian and things work out of the box for me.
   > 
   
   Yes, sorry again, my mistake. Obnam was able to access gpg-agent, but
   gpg-agent wasn't able to access gpg because in the ~/.gnupg/gpg.conf
   the setting 'use-agent' was still commented out. I posted this
   somewhere else in this or another thread.
   
   The other problem 'couldn't file or directory' when I did 
   $ obnam backup ~/someFile
   appeared because apparently obnam isn't able to backup a single file
   when pointed to it at the command line.
   
   The problem was that I used this command for a first test to see
   whether or not obnam was working. I should have pointed it to a
   directory instead, as I found out.
   
   Thanks.
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Lars Wirzenius <liw@liw.fi>
Date: Tue, 12 Apr 2016 15:16:14 +0300

   On Tue, Apr 12, 2016 at 12:04:13PM +0000, obnamsupport wrote:
   > The other problem 'couldn't file or directory' when I did 
   > $ obnam backup ~/someFile
   > appeared because apparently obnam isn't able to backup a single file
   > when pointed to it at the command line.
   
   Yeah, that's true. It's a bit of a bug in Obnam, since it's an obvious
   thing for people to want to do, but it needs a bit of reworking of the
   internals to implement properly. It'll happen some day.