Front page

ERROR R3E151X. generation does not have file...

8775b7507e874ff5b415e76fc477ca63
NEPTUNE IMPARTIAL SEABIRD

From: Damien Couroussé <damien.courousse@gmail.com>
Date: Sat, 27 May 2017 00:19:00 +0200

   hello,
   
   I get this error on one backupped machine:
   
   ERROR: R3E151X: Client machine.local, generation 107022 does not have
   file /var/mail/damien
   
   The backup terminates correctly (at least it seems so) but returns an
   error, and the faulty generation (here, 107022) is not listed in the
   list of available generations for this machine :
   
   $ obnam --config configs/obnam@machine.local@all.conf generations
   (...)	
   106147	2017-05-12 13:22:25 +0100 .. 2017-05-12 13:28:11 +0100 (111751
   files, 93978275440 bytes)
   106740	2017-05-18 22:54:36 +0100 .. 2017-05-18 23:02:53 +0100 (112417
   files, 93729403777 bytes)
   107374	2017-05-23 14:53:35 +0100 .. 2017-05-23 14:57:59 +0100 (112352
   files, 94437334752 bytes)
   
   
   I tried running the command 'fsck --fsck-fix', but the command has been
   running for four days now, with no luck.
   
   
   Any advices anyone? Help much appreciated!
   
   regards,
   Damien
   
   _______________________________________________
   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: Sun, 25 Jun 2017 19:12:28 +0300

   What version of Obnam is this? Does the following FAQ entry help?
   
   https://obnam.org/faq/missing-node/
   
   
   
   On Sat, May 27, 2017 at 12:19:00AM +0200, Damien Couroussé wrote:
   > hello,
   > 
   > I get this error on one backupped machine:
   > 
   > ERROR: R3E151X: Client machine.local, generation 107022 does not have
   > file /var/mail/damien
   > 
   > The backup terminates correctly (at least it seems so) but returns an
   > error, and the faulty generation (here, 107022) is not listed in the
   > list of available generations for this machine :
   > 
   > $ obnam --config configs/obnam@machine.local@all.conf generations
   > (...)	
   > 106147	2017-05-12 13:22:25 +0100 .. 2017-05-12 13:28:11 +0100 (111751
   > files, 93978275440 bytes)
   > 106740	2017-05-18 22:54:36 +0100 .. 2017-05-18 23:02:53 +0100 (112417
   > files, 93729403777 bytes)
   > 107374	2017-05-23 14:53:35 +0100 .. 2017-05-23 14:57:59 +0100 (112352
   > files, 94437334752 bytes)
   > 
   > 
   > I tried running the command 'fsck --fsck-fix', but the command has been
   > running for four days now, with no luck.
   > 
   > 
   > Any advices anyone? Help much appreciated!
   > 
   > regards,
   > Damien
   > 
   > _______________________________________________
   > obnam-support mailing list
   > obnam-support@obnam.org
   > http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
   >
From: Damien Couroussé <damien.courousse@gmail.com>
Date: Sun, 2 Jul 2017 23:52:47 +0200

   hello Lars,
   
   Sorry for my late answer.
   Actually the culprit was an error in my config file.  I specified a
   backup directory that did not exist: /var/mail/mail...  I have no
   explanation for the error message returned by obnam.  Fixing the
   directory to /var/mail fixed the error message.
   
   best,
   Damien
   
   Using obnam-1.12-1 in Debian / i386.
   
   
   On 25/06/2017 18:12, Lars Wirzenius wrote:
   > What version of Obnam is this? Does the following FAQ entry help?
   > 
   > https://obnam.org/faq/missing-node/
   > 
   > 
   > 
   > On Sat, May 27, 2017 at 12:19:00AM +0200, Damien Couroussé wrote:
   >> hello,
   >>
   >> I get this error on one backupped machine:
   >>
   >> ERROR: R3E151X: Client machine.local, generation 107022 does not have
   >> file /var/mail/damien
   >>
   >> The backup terminates correctly (at least it seems so) but returns an
   >> error, and the faulty generation (here, 107022) is not listed in the
   >> list of available generations for this machine :
   >>
   >> $ obnam --config configs/obnam@machine.local@all.conf generations
   >> (...)	
   >> 106147	2017-05-12 13:22:25 +0100 .. 2017-05-12 13:28:11 +0100 (111751
   >> files, 93978275440 bytes)
   >> 106740	2017-05-18 22:54:36 +0100 .. 2017-05-18 23:02:53 +0100 (112417
   >> files, 93729403777 bytes)
   >> 107374	2017-05-23 14:53:35 +0100 .. 2017-05-23 14:57:59 +0100 (112352
   >> files, 94437334752 bytes)
   >>
   >>
   >> I tried running the command 'fsck --fsck-fix', but the command has been
   >> running for four days now, with no luck.
   >>
   >>
   >> Any advices anyone? Help much appreciated!
   >>
   >> regards,
   >> Damien
   >>
   >> _______________________________________________
   >> obnam-support mailing list
   >> obnam-support@obnam.org
   >> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
   >>
   > 
   
   
   _______________________________________________
   obnam-support mailing list
   obnam-support@obnam.org
   http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org