Front page

obnam v1.19.1 forgets clients and or generations after a while

c5bf405aa2f8430baf12051f605e9067
SOLO REBELLION CRACKDOWN

From: Markus Dauberschmidt <daubsi@bigigloo.de>
Date: Mon, 3 Oct 2016 21:07:50 +0200

   Hi,
   
   I have severe problems with obnam v1.19.1 trying to backup my home 
   directories to a mounted NFS share on a daily basis. obnam is installed 
   from the Ubuntu 16.04 LTS package repository.
   
   The NFS share is mounted as
   
   192.168.0.25:/volume1/storage on /nas/storage type nfs 
   (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.25,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=192.168.0.25)
   
   The share and server is always on. There is no downtime and the share is 
   in use around the clock.
   
   obnam works perfectly for a while, but after some weeks it somehow 
   forgot all generations, showing nothing for "obnam generations" anymore.
   I've had like 20 generations according to my "forgot" policy and now 
   they are all gone :-(
   
   Lately obnam gives me this error when I execute "obnam generations":
   ERROR: R1CA00X: Client bigigloo does not exist in repository 
   /nas/storage/Backups/bigigloo
   
   Thank god, the latest repository still seems to be on the NAS, having ~ 
   23 GB of used disk space below that directory tree.
   
   My config looks like that:
   
   /etc/obnam.conf:
   ---
   [config]
   repository = /nas/storage/Backups/bigigloo
   log = /var/log/obnam.log
   root = /root, /home/abc, /home/def, /var/www/owncloud
   one-file-system = no
   client-name = bigigloo
   keep = 7d,15w,12m,1y
   ---
   and I call the following script every night at 02 a.m.
   
   /root/obnam_backup:
   ---
   #!/bin/bash
   
   /usr/bin/obnam force-lock --config=/etc/obnam.conf
   /usr/bin/obnam backup --config=/etc/obnam.conf
   /usr/bin/obnam force-lock --config=/etc/obnam.conf
   /usr/bin/obnam forget --config=/etc/obnam.conf
   ---
   
   These are the last lines from the log, showing the successful backup 
   creation this night:
   
   2016-10-03 02:44:12 INFO Backing up /var/www/owncloud/db_structure.xml
   2016-10-03 02:44:12 INFO Backing up /var/www/owncloud/cron.php
   2016-10-03 02:44:12 INFO Backing up /var/www/owncloud/COPYING-AGPL
   2016-10-03 02:44:12 INFO Backing up /var/www/owncloud/console.php
   2016-10-03 02:44:12 INFO Backing up /var/www/owncloud/AUTHORS
   2016-10-03 02:44:12 INFO Backing up /var/www/owncloud
   2016-10-03 02:45:12 INFO Unlocking client bigigloo
   2016-10-03 02:45:38 INFO Locking client bigigloo
   2016-10-03 02:45:38 INFO Unlocking client bigigloo
   2016-10-03 02:45:38 INFO Backup performance statistics:
   2016-10-03 02:45:38 INFO * files found: 113815
   2016-10-03 02:45:38 INFO * files backed up: 113815
   2016-10-03 02:45:38 INFO * uploaded chunk data: 7830114 bytes (7 MiB)
   2016-10-03 02:45:38 INFO * total uploaded data (incl. metadata): 
   164711002 bytes (157 MiB)
   2016-10-03 02:45:38 INFO * total downloaded data (incl. metadata): 
   9917031993 bytes (9 GiB)
   2016-10-03 02:45:38 INFO * transfer overhead: 10073912881 bytes (9 GiB)
   2016-10-03 02:45:38 INFO * duration: 2717.00568295 s (45m17s)
   2016-10-03 02:45:38 INFO * average speed: 2.81434659895 KiB/s
   2016-10-03 02:45:38 INFO Backup finished.
   2016-10-03 02:45:38 INFO obnam version 1.19.1 ends normally
   2016-10-03 02:45:39 INFO obnam version 1.19.1 starts
   2016-10-03 02:45:39 INFO Forcing lock
   2016-10-03 02:45:39 INFO Repository: /nas/storage/Backups/bigigloo
   2016-10-03 02:45:39 INFO Opening repository: /nas/storage/Backups/bigigloo
   2016-10-03 02:45:39 INFO Forcing client lock open for bigigloo
   2016-10-03 02:45:39 INFO obnam version 1.19.1 ends normally
   2016-10-03 02:45:39 INFO obnam version 1.19.1 starts
   2016-10-03 02:45:39 INFO Opening repository: /nas/storage/Backups/bigigloo
   2016-10-03 02:45:39 INFO Locking client bigigloo
   2016-10-03 02:45:40 INFO Unlocking client bigigloo
   2016-10-03 02:45:40 INFO obnam version 1.19.1 ends normally
   2016-10-03 20:54:58 INFO obnam version 1.19.1 starts
   2016-10-03 20:54:58 INFO Opening repository: /nas/storage/Backups/bigigloo
   2016-10-03 20:54:59 CRITICAL R1CA00X: Client bigigloo does not exist in 
   repository /nas/storage/Backups/bigigloo
   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 589, in 
   process_args
        method(args[1:])
      File 
   "/usr/lib/python2.7/dist-packages/obnamlib/plugins/show_plugin.py", line 
   106, in generations
        self.open_repository()
      File 
   "/usr/lib/python2.7/dist-packages/obnamlib/plugins/show_plugin.py", line 
   95, in open_repository
        client=client, repo=self.app.settings['repository'])
   ClientDoesNotExistError: R1CA00X: Client bigigloo does not exist in 
   repository /nas/storage/Backups/bigigloo
   
   
   I added the calls to "force-lock" in the backup script:
   /usr/bin/obnam force-lock --config=/etc/obnam.conf
   
   because it seemed to run more stable. The "lost generations" were gone 
   for a while but then the problems reappeared.
   
   What can I do to get hold of my repository again?
   
   Thanks
   Markus
   
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
From: Adam Porter <adam@alphapapa.net>
Date: Tue, 04 Oct 2016 00:38:27 -0500

   Markus Dauberschmidt <daubsi@bigigloo.de> writes:
   
   Hi Markus,
   
   > 2016-10-03 02:45:39 INFO obnam version 1.19.1 ends normally
   > 2016-10-03 02:45:39 INFO obnam version 1.19.1 starts
   > 2016-10-03 02:45:39 INFO Opening repository: /nas/storage/Backups/bigigloo
   > 2016-10-03 02:45:39 INFO Locking client bigigloo
   > 2016-10-03 02:45:40 INFO Unlocking client bigigloo
   > 2016-10-03 02:45:40 INFO obnam version 1.19.1 ends normally
   > 2016-10-03 20:54:58 INFO obnam version 1.19.1 starts
   > 2016-10-03 20:54:58 INFO Opening repository: /nas/storage/Backups/bigigloo
   > 2016-10-03 20:54:59 CRITICAL R1CA00X: Client bigigloo does not exist
   
   This might be completely irrelevant, but I wonder why there was a nearly
   10 minute gap between the second force-lock and the forget command in
   the log file.  Since the commands are in the script in sequence, it
   seems like there should have been no delay between them.  This might be
   a clue to something abnormal going on.
   
   You're right that sometimes force-lock is needed.  For example, I backup
   to an old netbook that I keep running as a little server, but its wifi
   driver is slightly buggy, and sometimes it drops off the network
   randomly.  When this happens during a backup, the repo is left locked,
   and the backup jobs fail until I notice and force-lock it.
   
   So it makes sense to do that, but at the same time, I wonder if there
   could be an issue with doing it every time, no matter what.  For
   example, if the backup run gets interrupted, then the force-lock runs,
   and then the forget runs...  I guess Obnam should be able to handle that
   all right, but bugs like that can be really obscure.
   
   Anyway, have you tried running "obnam fsck"?  You might want to run that
   from the NAS if possible, rather than over the network, because the man
   page says that it can be slow.  But if there are any problems with the
   repo, it should report them.
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org