Front page

Error Message

0c8d5eb722204cd3af692fcc22f2dae3
AMMO MICROSCOPE EYEGLASS

From: Tom Nickels <tomnickels@klaya.com>
Date: Tue, 5 Apr 2016 15:35:19 +0200

   -----BEGIN PGP SIGNED MESSAGE-----
   Hash: SHA1
   
   Hi everybody,
   
   sorry encryption happend by accident.
   
   Out of the blue I am getting this error. Backup before was without any
   problems. Did not change anything:
   
   > 2016-04-03 01:00:01 INFO obnam version 1.6.1 starts
   > 2016-04-03 01:00:01 INFO Backup starts
   > 2016-04-03 01:00:01 INFO [chan obnam SSHChannelAdapter] Opened sftp
   connection (server version 3)
   > 2016-04-03 01:02:04 CRITICAL Traceback (most recent call last):
   >   File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 190, in _run
   >     self.process_args(args)
   >   File "/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 175,
   in process_args
   >     cliapp.Application.process_args(self, args)
   >   File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 539, in
   process_args
   >     method(args[1:])
   >   File
   "/usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py",
   line 281, in backup
   >     self.repo.lock_client(client_name)
   >   File "/usr/lib/python2.7/dist-packages/obnamlib/repo.py", line 438,
   in lock_client
   >     self.lockmgr.lock([client_dir])
   >   File "/usr/lib/python2.7/dist-packages/obnamlib/lockmgr.py", line
   81, in lock
   >     self._lock_one(dirname)
   >   File "/usr/lib/python2.7/dist-packages/obnamlib/lockmgr.py", line
   68, in _lock_one
   >     raise obnamlib.LockFail('Lock timeout: %s' % lock_name)
   > LockFail: Lock timeout: 17843015698803854189/lock
   
   Anybody any idea what could be wrong?
   
   Cheers,
   
   Tom
   
   -----BEGIN PGP SIGNATURE-----
   Version: GnuPG v2.0.22 (GNU/Linux)
   
   iQIcBAEBAgAGBQJXA78XAAoJEOVlDn+QDwnSBLcP/jxKEULlb71Rqq+uyFS871uw
   x+U5hAwgcVm5e7nPTDCc3O5FXiFpgSWHV0by/2IjzIEXIP98V+cwYjfCcb3G85pl
   +Qqao0xHByXo0okk3tO8tZHEdwcJa92ULNX0muhBKd3AaFq2+xeqmW6s3tahf/7j
   EMm9L5gzwPSRv6h4VQbsWqlA1Q9PUBeO8v7mrx13yiUvyfNUj9n8zm2ohnzlrJBS
   Hp1CnxbsZ5wc5I3Ib+clohf5Gk3+kFrIWxOKSOPaY7wzsokmudXCi61TT6KAAqWX
   /Xh6bypmCp7z7ZrAmlRDUlHkbC+/k5/oK0X18oOa4w3vbg38CRu5FtYs6Lq4S8kG
   x2wvgbrzkEKdnszRI9BB/uLLPmT8h0GjrDdWQGFnrdHvVmtZgDsQKWI4NEyQDyHL
   Lm1Uv0oRet378Ws3Ro/pefHeNLexqKUaA6KUc++S4WcLMm4l2nms2jbSCr20lCjp
   TMzg3cRHSaU4aPFZ3beLYHVRA+PI2i5OKcUThkseR7iB3SQu3gLaV4GUJepflzo/
   wiqMd5OBAI33aHzJQn7/OHeuDdUewcCSN16qDgSCURrm3O5kqH7VuQBQwceMOYE+
   bhHLrSre1sSn+DohlwfuBbHUW8ts8pAzSQMmKNVTI8nvKXfbjgqVYJK91EOEIQDE
   jiZPZrfMySqLWX45Ceic
   =EucB
   -----END PGP SIGNATURE-----
From: Lars Wirzenius <liw@liw.fi>
Date: Thu, 7 Apr 2016 10:19:21 +0300

   On Tue, Apr 05, 2016 at 03:35:19PM +0200, Tom Nickels wrote:
   > Out of the blue I am getting this error. Backup before was without any
   > problems. Did not change anything:
   ...
   > > LockFail: Lock timeout: 17843015698803854189/lock
   
   This would indicate that a previous run of obnam didn't finish
   successfully, and left a lock file. If you're sure no obnam process is
   now using that backup repository, then "obnam force-lock" should
   remove all lock files and then you can run "obnam backup" again.
From: Lars Wirzenius <liw@liw.fi>
Date: Thu, 7 Apr 2016 18:46:54 +0300

   On Thu, Apr 07, 2016 at 10:36:55AM +0200, Tom Nickels wrote:
   > Am 07.04.2016 um 09:19 schrieb Lars Wirzenius:
   > > On Tue, Apr 05, 2016 at 03:35:19PM +0200, Tom Nickels wrote:
   > >> Out of the blue I am getting this error. Backup before was without any
   > >> problems. Did not change anything:
   > > ...
   > >>> LockFail: Lock timeout: 17843015698803854189/lock
   > > This would indicate that a previous run of obnam didn't finish
   > > successfully, and left a lock file. If you're sure no obnam process is
   > > now using that backup repository, then "obnam force-lock" should
   > > remove all lock files and then you can run "obnam backup" again.
   > >
   > Ok, after doing that I am getting the following error:
   > 
   > starting new GenerationERROR :no backup roots specified
   
   You need to give one or more directories (which are the backup roots)
   on the command line, or add the root=foo setting to your config file.