Re: Problem backing up: "no backup size line"
On Fri, Oct 27, 2017 at 07:55:31AM -0400, Jean-Louis Martineau ([email protected]) wrote: > Jobst, > > Every good bug report should include the version of the software you are > using. > Which amanda version are you using? On amanda server an client? > > Also tell us more information, you just tell us 'no backup size line"' on > nothing more. > Which program or application are you using to do the backup? > Post the relevant debug files. Yes, I am aware of "providing more information" I have been around long enough, wrote bug reports for a large number of softwares I use, helped the communities by adding/changing code for the variety of software so I think I am aware of whats required - well I should ;-). Also, most of the time I fix things myself - as other users before me have reported similar issues and googling most of the times helps ... but this issue had a domino effect of errors, everytime I changed to fix one I received other errors - never had this before. This one had me stumped - It actually started by moving the tape server to another machine, a task that should be relatively straight forward and would have been. When the error "[disk /, all estimate timed out]" showed up I thought it was due to the tape move and I made a mistake configuring the new solution ... but then I found it was due to a mounted partition that has lots of small (source) files (I develop software for the company I work for). But before I realized that I had a domini effect of other errors, as I was trying to fix this by upgrading/downgrading/clearing - making sure all config files are in order etc. I also saw when people had the problem "no backup line ..." the version really did not matter so I tried to debug "process_dumpline(line);" and trying to find the regexp that was causing it - maybe ... well by than everything was a real mess. So what I have done two days ago: I started fresh meaning reset all tapes, backups, index files, dump states. gnutar-lists - you name it everything. I basically was doing a backup of all machines for the first time using a fresh start. So far it works - but I also went back to a 3.3.X version of amanda for ALL machines (I do not have windows boxen to backup) and I always run the same amanda version on all machines. I am currently upgrading slowly to a higher number amanda ... keeping a snapshot of all amanda dirs so I can go back to the previous working state. Jobst -- "XP: If you are nine years old you are just going to love it. If you're a few years older you'll resent the choking paternalistic atmosphere of vapid gee-whiz kiddie entertainment (babysitting), euphemism and fake-friendly bullying." | |0| | Jobst Schmalenbach, General Manager | | |0| Barrett & Sales Essentials |0|0|0| +61 3 9533 , POBox 277, Caulfield South, 3162, Australia
Re: Problem backing up: "no backup size line"
Jobst, Every good bug report should include the version of the software you are using. Which amanda version are you using? On amanda server an client? Also tell us more information, you just tell us 'no backup size line"' on nothing more. Which program or application are you using to do the backup? Post the relevant debug files. Jean-Louis On 27/10/17 12:30 AM, Jobst Schmalenbach wrote: > On Thu, Oct 26, 2017 at 01:16:35PM +0200, Michael M?skens ([email protected]) > wrote: >> hi, >>> But I also do not know how to check this: GNU tar state file >>> /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted. >> did you solve that problem by now? I???m not sure, but deleting the >> .new-file in /var/lib/amanda/gnutar-lists/ could help you with that. >> > Darn. Should have explained better. > > I have a snapshot system that takes a snapshot every 3 hours including the > amanda dirs. > So I went back (on all machines that amanda is involved backing up) to > restore the amanda stuff to a time I new it works ... then start a backup > again ... this still happened. > > In my spare time I am currently reading the source to learn/research what is > going on but it's not the .new file. > > Jobst > > This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do not copy or deliver this message to anyone. Instead, destroy it and notify me by reply e-mail
Re: Problem backing up: "no backup size line"
On Thu, Oct 26, 2017 at 01:16:35PM +0200, Michael M?skens ([email protected]) wrote: > hi, > > > > But I also do not know how to check this: GNU tar state file > > /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted. > > did you solve that problem by now? I???m not sure, but deleting the .new-file > in /var/lib/amanda/gnutar-lists/ could help you with that. > Darn. Should have explained better. I have a snapshot system that takes a snapshot every 3 hours including the amanda dirs. So I went back (on all machines that amanda is involved backing up) to restore the amanda stuff to a time I new it works ... then start a backup again ... this still happened. In my spare time I am currently reading the source to learn/research what is going on but it's not the .new file. Jobst -- 186,262 miles/second : Not just a good idea, it's the LAW. | |0| | Jobst Schmalenbach, General Manager | | |0| Barrett & Sales Essentials |0|0|0| +61 3 9533 , POBox 277, Caulfield South, 3162, Australia
Re: Problem backing up: "no backup size line"
hi, > Now I get the following error: "no backup size line", in the log it looks > like this > > FAIL dumper 192.168.0.1 /boot 20171024230002 1 [no backup size line] >sendbackup: start [192.168.0.1:/boot level 1] >sendbackup: info BACKUP=/bin/tar >sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ... >sendbackup: info end >sendbackup: error [no backup size line] > PARTIAL chunker 192.168.0.1 /boot 20171024230002 1 [sec 0.174 kb 11 kps > 246.4] > > But I also do not know how to check this: GNU tar state file > /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted. did you solve that problem by now? I’m not sure, but deleting the .new-file in /var/lib/amanda/gnutar-lists/ could help you with that. greets, Michael — Michael Müskens Cologne, Germany signature.asc Description: Message signed with OpenPGP using GPGMail
