Front page

get_node error, please help

6a606517330d4b14b65903e6ebc71bc6
GEIGER FORTITUDE FRACTURE

From: Ton Boelens <ton.boelens@gmail.com>
Date: Sun, 03 Apr 2016 06:19:36 +0000

   Hi, I use Obnam version 1.19.1. Prior to this, I have used Obnam for more
   than a year. When I try to do a backup, I see the following message:
   
   2016-04-03 08:08:14 CRITICAL Node 0x17e6 cannot be found in the node store
   10127227003257480415: None: None: None
   Traceback (most recent call last):
     File "/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 208, in
   process_args
       cliapp.Application.process_args(self, args)
     File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 567, in
   process_args
       method(args[1:])
     File
   "/usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py", line
   166, in backup
       self.start_generation()
     File
   "/usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py", line
   242, in start_generation
       self.new_generation = self.repo.create_generation(self.client_name)
     File "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/repo_fmt_6.py",
   line 440, in create_generation
       client_name, open_client_info)
     File "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/repo_fmt_6.py",
   line 404, in _refresh_open_client_info_cached_generation_ids
       for gen_number in client_info.client.list_generations()]
     File
   "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/clientmetadatatree.py",
   line 250, in list_generations
       genid = self._get_generation_id_or_None(t)
     File
   "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/clientmetadatatree.py",
   line 286, in _get_generation_id_or_None
       return self.get_generation_id(tree)
     File
   "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/clientmetadatatree.py",
   line 282, in get_generation_id
       return self._lookup_int(tree, self.genkey(self.GEN_ID))
     File
   "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/clientmetadatatree.py",
   line 209, in _lookup_int
       return struct.unpack('!Q', tree.lookup(key))[0]
     File "/usr/lib/python2.7/dist-packages/larch/tree.py", line 142, in lookup
       node = self._get_node(node[k])
     File "/usr/lib/python2.7/dist-packages/larch/tree.py", line 111, in
   _get_node
       return self.node_store.get_node(node_id)
     File "/usr/lib/python2.7/dist-packages/larch/nodestore_disk.py", line
   240, in get_node
       raise larch.NodeMissing(self.dirname, node_id, error=e)
   NodeMissing: Node 0x17e6 cannot be found in the node store
   10127227003257480415: None: None: None
From: Ton Boelens <ton.boelens@gmail.com>
Date: Tue, 12 Apr 2016 07:11:41 +0000

   No problem, I understand. Thanks Lars for your great service and product.
   
   Kind regards,
   
   Ton
   
   Op di 12 apr. 2016 om 09:09 schreef Lars Wirzenius <liw@liw.fi>:
   
   > On Sun, Apr 03, 2016 at 06:19:36AM +0000, Ton Boelens wrote:
   > > Hi, I use Obnam version 1.19.1. Prior to this, I have used Obnam for more
   > > than a year. When I try to do a backup, I see the following message:
   > >
   > > 2016-04-03 08:08:14 CRITICAL Node 0x17e6 cannot be found in the node
   > store
   > > 10127227003257480415: None: None: None
   >
   > I'm afraid it looks like the backup repository has been corrupted, and
   > Obnam can't deal with that situation. You're going to have to start
   > over from scratch. Sorry.
   >
   > --
   > Schrödinger's backup hypothesis: the condition of any backup is
   > undefined until a restore is attempted. -- andrewsh
   >
From: Lars Wirzenius <liw@liw.fi>
Date: Tue, 12 Apr 2016 09:34:28 +0300

   On Sun, Apr 03, 2016 at 06:19:36AM +0000, Ton Boelens wrote:
   > Hi, I use Obnam version 1.19.1. Prior to this, I have used Obnam for more
   > than a year. When I try to do a backup, I see the following message:
   > 
   > 2016-04-03 08:08:14 CRITICAL Node 0x17e6 cannot be found in the node store
   > 10127227003257480415: None: None: None
   
   I'm afraid it looks like the backup repository has been corrupted, and
   Obnam can't deal with that situation. You're going to have to start
   over from scratch. Sorry.