Re: missing result
On Saturday 24 March 2007, Joe Konecny wrote: Gene Heskett wrote: snip I believe, and somebody correct me if I'm wrong, but ISTR that file needs to be touched by root, 'chown'ed to 'amanda:disk' or whatever your amanda user is named: and a member of that :group, then chmod'ed to 0600, so that 'amanda' is the only normal user with rights to that file. I use amanda:disk here cause then I don't have to remember who the operator for amanda is. I left it 644 and it seems ok. Strange the whole amandates thing isn't in the docs (except for the cygwin part so you'd think it wouldn't apply) and it's not in the faq either. Seems like it should be part of the installation instructions. If it was going to be mentioned, I'd think it would be in the manpage for amdump, but you are correct, its not in there. In the src tree's docs dir, a grep shows it in 'amanda.client.conf.5.txt': amanda-client.conf.5.txt: amandates string amanda-client.conf.5.txt: Default: /etc/amandates. The file where amanda keep the last date of each amanda-client.conf.5.txt- dumplevel. And in 'whatwasnew.txt': - Since Gnu TAR does not maintain a dumpdates file itself, nor give an estimate of backup size, those need to be done within Amanda. Amanda maintains an /etc/ amandates file to track the backup dates analogously to how dump does it. NOTE: if your /etc directory is not writable by your dumpuser, you'll have to create the empty file initially by hand, and make it writable by your dumpuser ala /etc/dumpdates. NOTE: Since tar traverses the directory hierarchy and reads files as a regular user would, it must run as root. The two new Amanda programs calcsize and runtar therefore must be installed setuid root. I've made them as simple as possible to to avoid potential security holes. --- But that, it appears, does not make it into the manpages. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yevtushenko has... an ego that can crack crystal at a distance of twenty feet. -- John Cheever
Re: missing result
On Sat, Mar 24, 2007 at 12:01:16AM -0400, Joe Konecny wrote: I left it 644 and it seems ok. Strange the whole amandates thing isn't in the docs (except for the cygwin part so you'd think it wouldn't apply) and it's not in the faq either. Seems like it should be part of the installation instructions. There are two separate attempts to create the /etc/amandates file in the source code client-src/amandates.c when access to the file is first attempted. So it typically would not be an installation item. Perhaps cygwin is a special case where those creation attemps fail. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: missing result
On Saturday 24 March 2007, Jon LaBadie wrote: On Sat, Mar 24, 2007 at 12:01:16AM -0400, Joe Konecny wrote: I left it 644 and it seems ok. Strange the whole amandates thing isn't in the docs (except for the cygwin part so you'd think it wouldn't apply) and it's not in the faq either. Seems like it should be part of the installation instructions. There are two separate attempts to create the /etc/amandates file in the source code client-src/amandates.c when access to the file is first attempted. So it typically would not be an installation item. Perhaps cygwin is a special case where those creation attemps fail. ISTR it also failed here on this FC6 box and I had to touch it after installing amanda from the old installs /home/amanda tree, back in the middle of November 2006. ISTR amanda didn't have perms to touch (create) a file in the /etc dir, so I had to do it as root, then chown and chmod it. Then everybody was happy. Which at the time may have been an selinux problem. That's such a PITA its been disabled after the first week of its screwups like that. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) There are more old drunkards than old doctors.
Re: missing result
Gene Heskett wrote: snip Yes, start with howto-auth.txt in the tarballs doc directory to do it how I am, which probably isn't the ultimate model, but it works for me. This looks like it was because the file /etc/amandates was missing. Apparently the install does not create it. I found an error in the auth.log... Mar 22 00:00:01 r4p17 sendsize[90503]: error [opening /etc/amandates: No such file or directory] I don't know what /etc/amandates is for but my backups seem much happier with it. Thanks for your help!
Re: missing result
On Friday 23 March 2007, Joe Konecny wrote: Gene Heskett wrote: snip Yes, start with howto-auth.txt in the tarballs doc directory to do it how I am, which probably isn't the ultimate model, but it works for me. This looks like it was because the file /etc/amandates was missing. Apparently the install does not create it. I found an error in the auth.log... Mar 22 00:00:01 r4p17 sendsize[90503]: error [opening /etc/amandates: No such file or directory] I don't know what /etc/amandates is for but my backups seem much happier with it. Thanks for your help! I believe, and somebody correct me if I'm wrong, but ISTR that file needs to be touched by root, 'chown'ed to 'amanda:disk' or whatever your amanda user is named: and a member of that :group, then chmod'ed to 0600, so that 'amanda' is the only normal user with rights to that file. I use amanda:disk here cause then I don't have to remember who the operator for amanda is. It will then be maintained in an uptodate status from then on by the amdump supervisory utils. Its general format will resemble this: === /GenesAmandaHelper-0.6 0 1174288560 /GenesAmandaHelper-0.6 1 1174453248 /GenesAmandaHelper-0.6 2 1174541095 /GenesAmandaHelper-0.6 3 1174625228 [snip another 100k of different pathlistings] === The number after the path is the level, and I'm not sure what the last number is, possibly a timestamp, but I've NDI what notation format that represents. Swahili to this old fart. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The bureaucracy is expanding to meet the needs of an expanding bureaucracy.
Re: missing result
Gene Heskett wrote: snippage re /etc/amandates === /GenesAmandaHelper-0.6 0 1174288560 /GenesAmandaHelper-0.6 1 1174453248 /GenesAmandaHelper-0.6 2 1174541095 /GenesAmandaHelper-0.6 3 1174625228 [snip another 100k of different pathlistings] === The number after the path is the level, and I'm not sure what the last number is, possibly a timestamp, but I've NDI what notation format that represents. Swahili to this old fart. The number is a timestamp in UNIX epoch time (seconds since 1-1-1970). Your first number, 1174288560, is Mon Mar 19 07:16:00 2007 UTC You can do the conversion with the Perl function localtime, , or a C program using the system ctime function, or use one of the online javascript converters like http://dan.drydog.com/unixdatetime.html Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: missing result
On Friday 23 March 2007, Frank Smith wrote: Gene Heskett wrote: snippage re /etc/amandates === /GenesAmandaHelper-0.6 0 1174288560 /GenesAmandaHelper-0.6 1 1174453248 /GenesAmandaHelper-0.6 2 1174541095 /GenesAmandaHelper-0.6 3 1174625228 [snip another 100k of different pathlistings] === The number after the path is the level, and I'm not sure what the last number is, possibly a timestamp, but I've NDI what notation format that represents. Swahili to this old fart. The number is a timestamp in UNIX epoch time (seconds since 1-1-1970). Your first number, 1174288560, is Mon Mar 19 07:16:00 2007 UTC You can do the conversion with the Perl function localtime, , or a C program using the system ctime function, or use one of the online javascript converters like http://dan.drydog.com/unixdatetime.html Frank Thanks, Frank. I figured maybe it was Julian, but those numbers look way too old to be current. Unix epoch time format never occurred to me. But it makes perfect sense now. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) HAL 9000: Dave. Put down those Windows disks, Dave. DAVE!
Re: missing result
Gene Heskett wrote: snip I believe, and somebody correct me if I'm wrong, but ISTR that file needs to be touched by root, 'chown'ed to 'amanda:disk' or whatever your amanda user is named: and a member of that :group, then chmod'ed to 0600, so that 'amanda' is the only normal user with rights to that file. I use amanda:disk here cause then I don't have to remember who the operator for amanda is. I left it 644 and it seems ok. Strange the whole amandates thing isn't in the docs (except for the cygwin part so you'd think it wouldn't apply) and it's not in the faq either. Seems like it should be part of the installation instructions.
missing result
I upgraded from 2.4.5? to 2.5.1p3 and now have the following problem... Can anyone provide any insight? These dumps were to tape daily set1006. The next tape Amanda expects to use is: DailySet1002. FAILURE AND STRANGE DUMP SUMMARY: R4P17.rmtohio.com amrd0s1f lev 0 FAILED [missing result for amrd0s1f in R4P17.rmtohio.com response] STATISTICS: Total Full Incr. Estimate Time (hrs:min)0:00 Run Time (hrs:min) 0:00 Dump Time (hrs:min)0:00 0:00 0:00 Output Size (meg) 0.00.00.0 Original Size (meg) 0.00.00.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min)0:00 0:00 0:00 Tape Size (meg) 0.00.00.0 Tape Used (%) 0.00.00.0 Filesystems Taped 0 0 0 Chunks Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- USAGE BY TAPE: Label Time Size %NbNc DailySet1006 0:000k0.0 0 0
Re: missing result
On Thursday 22 March 2007, Joe Konecny wrote: I upgraded from 2.4.5? to 2.5.1p3 and now have the following problem... Can anyone provide any insight? The security model was changed in the middle of that transition. Did you do the appropriate changes, which I believe are explained in the FAQ? These dumps were to tape daily set1006. The next tape Amanda expects to use is: DailySet1002. FAILURE AND STRANGE DUMP SUMMARY: R4P17.rmtohio.com amrd0s1f lev 0 FAILED [missing result for amrd0s1f in R4P17.rmtohio.com response] STATISTICS: Total Full Incr. Estimate Time (hrs:min)0:00 Run Time (hrs:min) 0:00 Dump Time (hrs:min)0:00 0:00 0:00 Output Size (meg) 0.00.00.0 Original Size (meg) 0.00.00.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min)0:00 0:00 0:00 Tape Size (meg) 0.00.00.0 Tape Used (%) 0.00.00.0 Filesystems Taped 0 0 0 Chunks Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- USAGE BY TAPE: Label Time Size %NbNc DailySet1006 0:000k0.0 0 0 -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Success is relative: It is what we can make of the mess we have made of things. -- T.S. Eliot, The Family Reunion
Re: missing result
Gene Heskett wrote: On Thursday 22 March 2007, Joe Konecny wrote: I upgraded from 2.4.5? to 2.5.1p3 and now have the following problem... Can anyone provide any insight? The security model was changed in the middle of that transition. Did you do the appropriate changes, which I believe are explained in the FAQ? I've searched the faq but have turned up nothing. Is there a chance you could point me in the right direction to find the info I need to make this work?
Re: missing result
On Thursday 22 March 2007, Joe Konecny wrote: Gene Heskett wrote: On Thursday 22 March 2007, Joe Konecny wrote: I upgraded from 2.4.5? to 2.5.1p3 and now have the following problem... Can anyone provide any insight? The security model was changed in the middle of that transition. Did you do the appropriate changes, which I believe are explained in the FAQ? I've searched the faq but have turned up nothing. Is there a chance you could point me in the right direction to find the info I need to make this work? Not right at the moment but I expect a google search for amanda + bsdtcp-security might turn up something. I had to add a line to my configuration driver script which I posted in another thread on this list just this evening, and I had to create a couple of files, the exact details of which elude me as I've reached that age (72) where short term memory isn't so quick. I do see that the /home/amanda/.amandahosts file has some additions also. More aliases mainly. This line in my gh.cf file which drives the configure stage here was added: --with-bsdtcp-security \ There might be something in the docs directory of the tarball. Yes, start with howto-auth.txt in the tarballs doc directory to do it how I am, which probably isn't the ultimate model, but it works for me. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) You want brutality and heuristics? I'll give you brutality and heuristics... - Eric S. Raymond on linux-kernel
lev 0 FAILED [missing result for /usr in hvbackup response] message
I know I've seen discussion on this before - but after adding a couple of new clients I have started getting the following messages /usr lev 0 FAILED [missing result for /usr in hvbackup response] about 3 or 4 a dump - is it the estimate timeout value I've seen mentioned as a possible solution to this? None of these errors are on the new servers - they are actually all on filesystems local to the amanda server. Thanks, Chris
Re: missing result ... in ... response ???
* Paul Bijnens [EMAIL PROTECTED] [2006:05:29:14:13:00+0200] scribed: snip / Jean-Louis created a patch for 2.5.0, which break at 64K (just as 2.4.x), which fixes your problem. Yes. As I stated earlier, it is better for me to use debian packages; rather than attempting to maintain personal compilations ... It fixes it until you hit the 64Kbyte limit, at which time, 2.5.1 or 2.5.2 will have removed that limit, we hope. OK. Just to clarify, do I understand you correctly, that amanda developers are working on solution to this problem, and some expectation has been set (by them?) that these subsequent dot releases should correct this problem? If so, I shall be patient -- and wait ; Thank you, for your contributions to this problem ... -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: missing result ... in ... response ???
* On 2006:05:25:08:25:07-0500 I, Michael D Schleif [EMAIL PROTECTED], scribed: Something has changed in amanda. I have been running amanda on this lan for several years. For the most part, DLE's have been constant for at least six months. I have six linux servers, all running debian. Regarding amanda-server, my records show that I upgraded amanda to version: 2.4.5 on 16JUN05 Everything was backing up, and restoring, to my satisfaction, until last week. At that time, two servers (brono jord) were terribly old, regarding kernel and debian os. So, I upgraded via aptitude, which also upgraded amanda-client to version: 2.5.0 Since that time, many -- but, NOT all -- DLE's on brono and jord are FAIL'ing, e.g.: brono /var lev 0 FAILED [missing result for /var in brono response] jord /var lev 0 FAILED [missing result for /var in jord response] Yes, both of these servers have many DLE's; but, as stated above, this HAS been working without incident at the older version. Numbers of DLE's: brono 137 jord 219 snip / Bdale Garbee published to debian repository version 2.5.0p2. I have tried this on brono and jord, and this does NOT resolve the problem. I now have this on ALL of my boxen, except brono and jord, which I have downgraded to 2.4.4p3-3. Last night was my first completely successful backup in more than one week! I have received several private emails explaining the situation. I do understand those issues. However, amanda DOES succeed in my situation in versions _prior_ to v2.5.x -- and it FAILS in ALL v2.5.x ; This I do NOT understand. What am I missing? How will I know when a new version corrects this problem? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: missing result ... in ... response ???
On 2006-05-29 13:38, Michael D Schleif wrote: * On 2006:05:25:08:25:07-0500 I, Michael D Schleif [EMAIL PROTECTED], scribed: Something has changed in amanda. I have been running amanda on this lan for several years. For the most part, DLE's have been constant for at least six months. I have six linux servers, all running debian. Regarding amanda-server, my records show that I upgraded amanda to version: 2.4.5 on 16JUN05 Everything was backing up, and restoring, to my satisfaction, until last week. At that time, two servers (brono jord) were terribly old, regarding kernel and debian os. So, I upgraded via aptitude, which also upgraded amanda-client to version: 2.5.0 Since that time, many -- but, NOT all -- DLE's on brono and jord are FAIL'ing, e.g.: brono /var lev 0 FAILED [missing result for /var in brono response] jord /var lev 0 FAILED [missing result for /var in jord response] Yes, both of these servers have many DLE's; but, as stated above, this HAS been working without incident at the older version. Numbers of DLE's: brono 137 jord 219 snip / Bdale Garbee published to debian repository version 2.5.0p2. I have tried this on brono and jord, and this does NOT resolve the problem. I now have this on ALL of my boxen, except brono and jord, which I have downgraded to 2.4.4p3-3. Last night was my first completely successful backup in more than one week! I have received several private emails explaining the situation. I do understand those issues. However, amanda DOES succeed in my situation in versions _prior_ to v2.5.x -- and it FAILS in ALL v2.5.x ; In Amanda 2.4.x there is upper limit of 64K on the size of the request packets using the UDP. That resulted in errors once you got above the system limit. The system limit for UDP packets is on some systems only 8K or so, but most (all?) can be increased to 64K. Larger than 64K is not possible due to the layout of a UDP packet, which has only 2 bytes for the length. All text that does not fit in the 64K is discarded. In Amanda 2.5.0 there is code that breaks up the request in multiple chunks. However, that code is only implemented in the server side. The client code has not yet any provisions to re-assemble the multiple requests (or even to detect that the packet was divided!). I guess that doing this in a backward compatible way was not evident (multiple possibilities exist, some using feature bits, to extend the protocol, another way is to change the server code even more). Now, it just happens (why I don't know) that 2.5.0 breaks up those chunks in 32Kbytes, while 64Kbytes would have be good enough too (maybe because the answer needs to fit in a 1 packet too -- which it currently does, but maybe the implementor forsaw more info in the reply?). Jean-Louis created a patch for 2.5.0, which break at 64K (just as 2.4.x), which fixes your problem. It fixes it until you hit the 64Kbyte limit, at which time, 2.5.1 or 2.5.2 will have removed that limit, we hope. Setting the limit to 64K instead of 32K is perfectly fine here. But it does not solve the fundamental problem that was already present in Amanda 2.4.x either. This I do NOT understand. Or I'm confused about what exactly you do not understand... What am I missing? Or me? How will I know when a new version corrects this problem? Watching the ChangeLog and NEWS file... -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
missing result ... in ... response ???
Something has changed in amanda. I have been running amanda on this lan for several years. For the most part, DLE's have been constant for at least six months. I have six linux servers, all running debian. Regarding amanda-server, my records show that I upgraded amanda to version: 2.4.5 on 16JUN05 Everything was backing up, and restoring, to my satisfaction, until last week. At that time, two servers (brono jord) were terribly old, regarding kernel and debian os. So, I upgraded via aptitude, which also upgraded amanda-client to version: 2.5.0 Since that time, many -- but, NOT all -- DLE's on brono and jord are FAIL'ing, e.g.: brono /var lev 0 FAILED [missing result for /var in brono response] jord /var lev 0 FAILED [missing result for /var in jord response] Yes, both of these servers have many DLE's; but, as stated above, this HAS been working without incident at the older version. Numbers of DLE's: brono 137 jord 219 At first, I thought that this maybe conflict between amanda-server and amanda-client versions; so, I upgraded amanda-server: 2.5.0 on 23MAY06 NO difference. So, I searched these archives, and I googled. All I found was this URL: http://wiki.zmanda.com/index.php/Amdump:_results_missing amanda.conf has never had `etimeout' configured. Yesterday, I set it: etimeout 600 NO difference. Remember, this exact same configuration has been working WITHOUT incident at older version for eleven months! This is NOT a firewall issue, since this is only for my internal lan. Regarding maximum udp datagram size: net.inet.udp.maxdgram=63535 Apparently, sysctl on linux/debian does NOT support this. I have pinged debian-user on this issue; but, there has been NO response. I do NOT know what the current, default size is; nor do I know how to change it. I prefer NOT to combine DLE's; which will pose other challenges, not the least of which is DLE larger than tape. These DLE's are very dynamic. I cannot predict when a particular DLE will contain enormous data; and the nature of this dynamic data is already compressed ... What am I missing? This used to work; then, it b0rk; and the only change was a newer amanda version. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: missing result ... in ... response ???
Michael, If the problem is that you have too many DLE for a udp packet, try the attached patch which will double the size of the packet. Jean-Louis Michael D Schleif wrote: Something has changed in amanda. I have been running amanda on this lan for several years. For the most part, DLE's have been constant for at least six months. I have six linux servers, all running debian. Regarding amanda-server, my records show that I upgraded amanda to version: 2.4.5 on 16JUN05 Everything was backing up, and restoring, to my satisfaction, until last week. At that time, two servers (brono jord) were terribly old, regarding kernel and debian os. So, I upgraded via aptitude, which also upgraded amanda-client to version: 2.5.0 Since that time, many -- but, NOT all -- DLE's on brono and jord are FAIL'ing, e.g.: brono /var lev 0 FAILED [missing result for /var in brono response] jord /var lev 0 FAILED [missing result for /var in jord response] Yes, both of these servers have many DLE's; but, as stated above, this HAS been working without incident at the older version. Numbers of DLE's: brono 137 jord 219 At first, I thought that this maybe conflict between amanda-server and amanda-client versions; so, I upgraded amanda-server: 2.5.0 on 23MAY06 NO difference. So, I searched these archives, and I googled. All I found was this URL: http://wiki.zmanda.com/index.php/Amdump:_results_missing amanda.conf has never had `etimeout' configured. Yesterday, I set it: etimeout 600 NO difference. Remember, this exact same configuration has been working WITHOUT incident at older version for eleven months! This is NOT a firewall issue, since this is only for my internal lan. Regarding maximum udp datagram size: net.inet.udp.maxdgram=63535 Apparently, sysctl on linux/debian does NOT support this. I have pinged debian-user on this issue; but, there has been NO response. I do NOT know what the current, default size is; nor do I know how to change it. I prefer NOT to combine DLE's; which will pose other challenges, not the least of which is DLE larger than tape. These DLE's are very dynamic. I cannot predict when a particular DLE will contain enormous data; and the nature of this dynamic data is already compressed ... What am I missing? This used to work; then, it b0rk; and the only change was a newer amanda version. What do you think? diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.5.0p2.orig/server-src/amcheck.c amanda-2.5.0p2.new/server-src/amcheck.c --- amanda-2.5.0p2.orig/server-src/amcheck.c 2006-05-12 15:26:12.0 -0400 +++ amanda-2.5.0p2.new/server-src/amcheck.c 2006-05-25 10:11:46.0 -0400 @@ -1329,7 +1332,7 @@ void start_host(hostp) /* * Allow 2X for err response. */ - if(req_len + l_len MAX_PACKET / 2) { + if(req_len + l_len = MAX_PACKET) { amfree(l); break; } diff -u -r --show-c-function --exclude-from=amanda.diff amanda-2.5.0p2.orig/server-src/planner.c amanda-2.5.0p2.new/server-src/planner.c --- amanda-2.5.0p2.orig/server-src/planner.c 2006-04-24 07:16:43.0 -0400 +++ amanda-2.5.0p2.new/server-src/planner.c 2006-05-25 10:11:28.0 -0400 @@ -1338,7 +1338,7 @@ am_host_t *hostp; /* * Allow 2X for err response. */ - if(req_len + s_len MAX_PACKET / 2) { + if(req_len + s_len = MAX_PACKET) { amfree(s); break; }
Re: missing result ... in ... response ???
* Jean-Louis Martineau [EMAIL PROTECTED] [2006:05:25:10:16:56-0400] scribed: Michael, If the problem is that you have too many DLE for a udp packet, try the attached patch which will double the size of the packet. Thank you, for your participation in this matter. Yes, I can get this source, and compile it myself. However, I have two issues with that solution: [1] Did this _change_ between v2.4.5 and v2.5.x? If so, why? If so, at which version? Perhaps, I can down-grade? [2] One reason for using debian is, package management is so easy. Managing one, or dozens, or hundreds of personally compiled programs is a mess that I prefer to avoid. what do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
missing result in response
hello, we have an amanda server in an internal, nated network. now i wanted to backup a client outside this network (directly connected), but i get this from amstatus: bart.imos.net:/ 0 planner: [missing result for / in bart.imos.net response] bart.imos.net:/boot 0 planner: [missing result for /boot in bart.imos.net response] bart.imos.net:/opt 0 planner: [missing result for /opt in bart.imos.net response] is it possible to do that at all ? bye Stefan Herrmann
Re: missing result
Christoph Scheeder wrote: Iulian Topliceanu schrieb: Hi, After upgrading a client to amanda 2.4.5 on a RH9 the following problem has occured: I have 115 DLE for that client, and since upgrading, 14 volumes faile to be backuped. The *same* 14 volumes. I'm getting this: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to client timed out. client /data/data0/share1/Technik_Betrieb lev 0 FAILED [missing result for /data/data0/share1/Technik_Betrieb in client response] client /data/data0/share1/Studenten lev 0 FAILED [missing result for /data/data0/share1/Studenten in client response] The weird thing is that non of the these 14 volumes appear in sendsize.*.debug so I can't offer you any details. I've erased all the other DLE's from the 'disklist' and left only these 14 volumes. The backup went fine without any errors. What could be the problem? Regards, Iulian Topliceanu Hm, could it be a problem with the maximum UDP-packet size? you have many DLE's, so perhaps the request packet gets truncated at the client side. Christoph Yes, It what because of the maximum UDP-packet size. I've decreased the number of the DLE's and everything worked fine. Thanks for the help, Iulian begin:vcard fn:Iulian Topliceanu n:Topliceanu;Iulian org:;Operations adr:;;Moersenbroicher Weg 200;Duesseldorf;NRW;D-40470;net mobile AG email;internet:[EMAIL PROTECTED] url:http://www.net-m.de version:2.1 end:vcard
missing result
Hi, After upgrading a client to amanda 2.4.5 on a RH9 the following problem has occured: I have 115 DLE for that client, and since upgrading, 14 volumes faile to be backuped. The *same* 14 volumes. I'm getting this: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to client timed out. client /data/data0/share1/Technik_Betrieb lev 0 FAILED [missing result for /data/data0/share1/Technik_Betrieb in client response] client /data/data0/share1/Studenten lev 0 FAILED [missing result for /data/data0/share1/Studenten in client response] The weird thing is that non of the these 14 volumes appear in sendsize.*.debug so I can't offer you any details. I've erased all the other DLE's from the 'disklist' and left only these 14 volumes. The backup went fine without any errors. What could be the problem? Regards, Iulian Topliceanu begin:vcard fn:Iulian Topliceanu n:Topliceanu;Iulian org:;Operations adr:;;Moersenbroicher Weg 200;Duesseldorf;NRW;D-40470;net mobile AG email;internet:[EMAIL PROTECTED] url:http://www.net-m.de version:2.1 end:vcard
Re: missing result
Iulian Topliceanu schrieb: Hi, After upgrading a client to amanda 2.4.5 on a RH9 the following problem has occured: I have 115 DLE for that client, and since upgrading, 14 volumes faile to be backuped. The *same* 14 volumes. I'm getting this: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to client timed out. client /data/data0/share1/Technik_Betrieb lev 0 FAILED [missing result for /data/data0/share1/Technik_Betrieb in client response] client /data/data0/share1/Studenten lev 0 FAILED [missing result for /data/data0/share1/Studenten in client response] The weird thing is that non of the these 14 volumes appear in sendsize.*.debug so I can't offer you any details. I've erased all the other DLE's from the 'disklist' and left only these 14 volumes. The backup went fine without any errors. What could be the problem? Regards, Iulian Topliceanu Hm, could it be a problem with the maximum UDP-packet size? you have many DLE's, so perhaps the request packet gets truncated at the client side. Christoph
2.4.2 and 2.4.4 missing result
hello, we are running amanda for our daily backups on nearly 40 machines. tape and index server is the same machine and runs 2.4.2p2. i changed one of the client-only machines from 2.4.2.p2 to 2.4.4p1 and problems begin. the error is FAILURE AND STRANGE DUMP SUMMARY: x hd2 lev 0 FAILED [missing result for hd2 in x response] x hd1 lev 0 FAILED [missing result for hd1 in x response] for two different disks in x machine. i am pretty sure that the configuration of one of the disks is same as before, i changed the other from DUMP to GNUTAR as a test. the problem is, how can i trace this error. i looked at the x machines' /tmp/amanda directory and found a core file dated as just after sendsize file and before amandad file. the output on amandad file is as follows: ### Amanda 2.4 REQ HANDLE 023-2005C048 SEQ 1057772088 SECURITY USER dumpuser SERVICE sendsize OPTIONS maxdumps=1;hostname=x; GNUTAR hd2 0 1970:1:1:0:0:0 -1 DUMP hd1 0 1970:1:1:0:0:0 -1 amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 023-2005C048 SEQ 1057772088 amandad: time 0.012: bsd security: remote host y.cc.metu.edu.tr user dumpuse r local user dumpuser amandad: time 0.012: amandahosts security check passed amandad: time 0.012: running service /usr/local/libexec/sendsize amandad: time 0.190: sending REP packet: Amanda 2.4 REP HANDLE 023-2005C048 SEQ 1057772088 amandad: time 0.202: got packet: Amanda 2.4 ACK HANDLE 023-2005C048 SEQ 1057772088 amandad: time 0.202: pid 430168 finish time Wed Jul 9 20:30:46 2003 # note: both x and y machines are aix. server is 4.3.3 and the problemmatic client is 5.2. new 2.4.4 client is compiled with xlc without errors. any help appreciated. -caglar
Re: 2.4.2 and 2.4.4 missing result
H.Caglar Bilir wrote: the problem is, how can i trace this error. i looked at the x machines' /tmp/amanda directory and found a core file dated as just after sendsize file and before amandad file. the output on amandad file is as follows: I have no recent experience with AIX. Try file core. Some implementations of file indicate which program crashed. strings core can help too. ### Amanda 2.4 REQ HANDLE 023-2005C048 SEQ 1057772088 SECURITY USER dumpuser SERVICE sendsize OPTIONS maxdumps=1;hostname=x; GNUTAR hd2 0 1970:1:1:0:0:0 -1 DUMP hd1 0 1970:1:1:0:0:0 -1 amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 023-2005C048 SEQ 1057772088 amandad: time 0.012: bsd security: remote host y.cc.metu.edu.tr user dumpuse r local user dumpuser amandad: time 0.012: amandahosts security check passed amandad: time 0.012: running service /usr/local/libexec/sendsize amandad: time 0.190: sending REP packet: Amanda 2.4 REP HANDLE 023-2005C048 SEQ 1057772088 At this position, I would expect to see the actual sizes. The reply packet seems empty. So the core is probably from sendsize. There should be a file sendsize.aboutsamedatestamp.debug too. Any error message in that file, (maybe just before dumping core)? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: 2.4.2 and 2.4.4 missing result
Paul Bijnens wrote: H.Caglar Bilir wrote: the problem is, how can i trace this error. i looked at the x machines' /tmp/amanda directory and found a core file dated as just after sendsize file and before amandad file. the output on amandad file is as follows: I have no recent experience with AIX. Try file core. Some implementations of file indicate which program crashed. strings core can help too. ### Amanda 2.4 REQ HANDLE 023-2005C048 SEQ 1057772088 SECURITY USER dumpuser SERVICE sendsize OPTIONS maxdumps=1;hostname=x; GNUTAR hd2 0 1970:1:1:0:0:0 -1 DUMP hd1 0 1970:1:1:0:0:0 -1 amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 023-2005C048 SEQ 1057772088 amandad: time 0.012: bsd security: remote host y.cc.metu.edu.tr user dumpuse r local user dumpuser amandad: time 0.012: amandahosts security check passed amandad: time 0.012: running service /usr/local/libexec/sendsize amandad: time 0.190: sending REP packet: Amanda 2.4 REP HANDLE 023-2005C048 SEQ 1057772088 At this position, I would expect to see the actual sizes. The reply packet seems empty. So the core is probably from sendsize. There should be a file sendsize.aboutsamedatestamp.debug too. Any error message in that file, (maybe just before dumping core)? both sendsize and selfcheck programs generate core file(after some hand tests - and core files are renamed) if i look to the actual backup time : core file is because sendsize. the related sendsize file is as follows: less sendsize.20030709203046.debug sendsize: debug 1 pid 528590 ruid 211 euid 211: start at Wed Jul 9 20:30:46 200 3 sendsize: version 2.4.4p1 any ideas?
Re: Failing backup - missing result
What version of gnutar are you using? You'll need tha latest version (as just mentioned by Joshua). -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 Marriage, Caroline wrote: Hi I'm new to Amanda and am having problems working out why one of our backups is failing. We are trying to backup /var on one of our machines using dump and were initially getting lots of bread and lseek errors. I read that this was due to the disk being written to as the backup was being done - is that correct? I thought that using tar instead of dump may overcome this problem or at least would allow us to exclude directories that were being written. I have changed the config to use tar am now seeing failures which I believe are due to the client being unable get an estimate - missing result for /dev/sda7 in debussy.eu.ntt.net response. There is no size for /dev/sda7 in the sendsize file. Can anyone shed any light as to why it's failing? - apologies if I'm asking the obvious... Thanks Caroline This e-mail (and any attachments) contains information, which is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient you must not copy, distribute or use it for any purpose or disclose the contents to any person. If you have received this e-mail in error, please notify us immediately at [EMAIL PROTECTED] The information contained in this e-mail (and any attachments) is supplied in good faith, but the sender shall not be under any liability in damages or otherwise for any reliance that may be placed upon it by the recipient. Any comments or opinions expressed are those of the originator not of NTT Europe Ltd unless otherwise expressly stated. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
RE: Failing backup - missing result
We're using tar-1.13.25-4.7.1 which looks like it's the latest one. Caroline -Original Message- From: martinh [mailto:[EMAIL PROTECTED] Sent: 27 May 2003 16:50 To: Marriage, Caroline Cc: '[EMAIL PROTECTED]' Subject: Re: Failing backup - missing result What version of gnutar are you using? You'll need tha latest version (as just mentioned by Joshua). -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 Marriage, Caroline wrote: Hi I'm new to Amanda and am having problems working out why one of our backups is failing. We are trying to backup /var on one of our machines using dump and were initially getting lots of bread and lseek errors. I read that this was due to the disk being written to as the backup was being done - is that correct? I thought that using tar instead of dump may overcome this problem or at least would allow us to exclude directories that were being written. I have changed the config to use tar am now seeing failures which I believe are due to the client being unable get an estimate - missing result for /dev/sda7 in debussy.eu.ntt.net response. There is no size for /dev/sda7 in the sendsize file. Can anyone shed any light as to why it's failing? - apologies if I'm asking the obvious... Thanks Caroline This e-mail (and any attachments) contains information, which is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient you must not copy, distribute or use it for any purpose or disclose the contents to any person. If you have received this e-mail in error, please notify us immediately at [EMAIL PROTECTED] The information contained in this e-mail (and any attachments) is supplied in good faith, but the sender shall not be under any liability in damages or otherwise for any reliance that may be placed upon it by the recipient. Any comments or opinions expressed are those of the originator not of NTT Europe Ltd unless otherwise expressly stated. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** This e-mail (and any attachments) contains information, which is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient you must not copy, distribute or use it for any purpose or disclose the contents to any person. If you have received this e-mail in error, please notify us immediately at [EMAIL PROTECTED] The information contained in this e-mail (and any attachments) is supplied in good faith, but the sender shall not be under any liability in damages or otherwise for any reliance that may be placed upon it by the recipient. Any comments or opinions expressed are those of the originator not of NTT Europe Ltd unless otherwise expressly stated.
Re: Failing backup - missing result
Marriage, Caroline wrote: We're using tar-1.13.25-4.7.1 which looks like it's the latest one. Caroline -Original Message- From: martinh [mailto:[EMAIL PROTECTED] Sent: 27 May 2003 16:50 To: Marriage, Caroline Cc: '[EMAIL PROTECTED]' Subject: Re: Failing backup - missing result What version of gnutar are you using? You'll need tha latest version (as just mentioned by Joshua). OK anything in the log files and/or the messages file. The only time 'I' get bread and lseek errors are due to disk hardware problems... Also is amanda using the gnutar binary and not the built-in tar? ie did you specifically 'configure' the gnutar location or have replaced the stock tar binary with the gnu one? -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: still problem during dump: missing result reported
Hi, as this list now works again, I resend my email to get this problem finally fixed. --- original message - Dear Chris, dear John, What do you have maxduumps set to? Maybe increasing or decreasing it for this one host will help. increasing maxdumps did not help. Again I got adler / lev 0 FAILED [missing result for / in adler response] this night for the 33rd filesystem on adler. :-( No more ideas. It was just a sort of vain hope that changing maxdumps would help. Maybe the problem is with the size of the packet being exchanged with the adler host. Can you play with your disklist and combine any of your filesystems using gnutar) to get you down to 32? I tried to get some hints from amanda by digging through the source code. I found out, that the disklist itself is read in correctly (all entries are present in the program's C structure). Looking a little bit further revealed the problem: The amanda server issues the sendsize command to the clients (asking for sizes for level0 and level1 dumps in this case). This question is passed on via some protocol to the client (in this case adler). On the client side in sendsize program there is a loop reading in from (stdin), the daemon somehow I assume. The last line I get here while reading is truncated (even in case I back up 32 filesystems here; the exclude=file information is truncated which I can also see in the logfile later). The command for getting required sizes simply is too long! This also fits well with the error I get: adler does not compute the dump sizes for those filesystems it does not see. And amanda server is wondering why there are no answers for these filesystems - missing result. I saw that this is a known problem when searching through the amanda-hackers archive at egroups. There should be a patch available; in fact John already supplied me with this patch and I tried it, but it did not work. Maybe I got a broken version of the patch?? John, could be please check this again? Kind regards, Urte -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
Re: still problem during dump: missing result reported
Dear Chris, dear John, What do you have maxduumps set to? Maybe increasing or decreasing it for this one host will help. increasing maxdumps did not help. Again I got adler / lev 0 FAILED [missing result for / in adler response] this night for the 33rd filesystem on adler. :-( No more ideas. It was just a sort of vain hope that changing maxdumps would help. Maybe the problem is with the size of the packet being exchanged with the adler host. Can you play with your disklist and combine any of your filesystems using gnutar) to get you down to 32? I tried to get some hints from amanda by digging through the source code. I found out, that the disklist itself is read in correctly (all entries are present in the program's C structure). Looking a little bit further revealed the problem: The amanda server issues the sendsize command to the clients (asking for sizes for level0 and level1 dumps in this case). This question is passed on via some protocol to the client (in this case adler). On the client side in sendsize program there is a loop reading in from (stdin), the daemon somehow I assume. The last line I get here while reading is truncated (even in case I back up 32 filesystems here; the exclude=file information is truncated which I can also see in the logfile later). The command for getting required sizes simply is too long! This also fits well with the error I get: adler does not compute the dump sizes for those filesystems it does not see. And amanda server is wondering why there are no answers for these filesystems - missing result. I saw that this is a known problem when searching through the amanda-hackers archive at egroups. There should be a patch available; in fact John already supplied me with this patch and I tried it, but it did not work. Maybe I got a broken version of the patch?? John, could be please check this again? Kind regards, Urte -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
Re: still problem during dump: missing result reported
Hi Chris, hi list, What do you have maxduumps set to? Maybe increasing or decreasing it for this one host will help. increasing maxdumps did not help. Again I got adler / lev 0 FAILED [missing result for / in adler response] this night for the 33rd filesystem on adler. :-( Urte -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
Re: amdump problem: missing result reported
Hi John, I'm not sure if this will fix your problem, but it is the patch that allows requests larger than a single packet. Unfortunately this patch did not fix it. I added the patch to the source code, recompiled and reinstalled amanda. Then I added 2 of the 6 filesystems in the disklist again which I had commented out two weeks ago. Now I get the same error again in the amanda report: FAILURE AND STRANGE DUMP SUMMARY: adler /usr/export/home/adler lev 0 FAILED [missing result for /usr/export/home/adler in adler response] adler / lev 0 FAILED [missing result for / in adler response] These two are again the first two filesystems in the disklist for host adler which are missing on tape. For me it really looks like a max-32-fileystems-per-host limit. What has changed now with the patch is the /tmp/amanda/sendsize.debug output. I'm sure I found the / and home stuff in sendsize.debug before (even when they were not backed up), but now they are no longer present. ?? Kind regards, Urte P.S. I'll try to CC: the amanda list. Maybe I can get through somehow? -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
Re: amdump problem: missing result reported
What has changed now with the patch is the /tmp/amanda/sendsize.debug output. I'm sure I found the / and home stuff in sendsize.debug before (even when they were not backed up), but now they are no longer present. That's really strange: why should Amanda estimate / and /home if they aren't backed up?
Re: amdump problem: missing result reported
Great, I got through to the mailing list! :-) I had big problems reaching the list, so I talked to John directly about the problem. What has changed now with the patch is the /tmp/amanda/sendsize.debug output. I'm sure I found the / and home stuff in sendsize.debug before (even when they were not backed up), but now they are no longer present. That's really strange: why should Amanda estimate / and /home if they aren't backed up? Dont know if you know about the problem. I once again include my original email here to get you up to date: -- original email -- Hello list, I have a problem with amanda 2.4.2p2. I'm doing backups on three SUN machines with amanda for quite some time wihout any major problems. About 2 weeks ago we removed the bunch of single external disks from that host and added one big raid disk (which is of course too big to be backed up entirely on our 20gb native capacity tape). I then changed the disklist for this host from about 7 filesystems (= physical disk partitions) to 38 directory starting points. The first few days of course we had missing filesystems on tape until amanda has been able to do a level 0 dump on each of the new entries. Nevertheless 6 of the entries remain non-backuped (including the root filesystem and the user filesystem :-( ). I assume it might be a problem with the number of entries in the disklist (I saw some discussions about this in this newsgroup, but that turned out to be an error in the exclude statement). I noticed that these 6 entries are the ones which stand on top of the list. The error in the mail report says: FAILURE AND STRANGE DUMP SUMMARY: adler /usr/export/amis/raid2/disk_head_97_05 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_97_05 in adler response] adler /usr/export/amis/raid2/disk_head_96_05 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_96_05 in adler response] adler /usr/export/amis/raid2/disk_head_95_08 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_95_08 in adler response] adler /usr/export/amis/disk2 lev 0 FAILED [missing result for /usr/export/amis/disk2 in adler response] adler /usr/export/home/adler lev 0 FAILED [missing result for /usr/export/home/adler in adler response] adler / lev 0 FAILED [missing result for / in adler response] I dont see something unusual in the /tmp/amanda/-files. Just ask if you would like to see some extracts from there. -- end of original email -- John then sent me some patch, but he was not sure wheather this would help. And it did not. Thats the current state of the art. Kind regards, Urte -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
Re: still problem during dump: missing result reported
Hi Chris, I'm backing up 77 filesystems on 25 different machines. My tape host is RedHat Linux but I've also used IRIX and Solaris servers. I also have more than 32 filesystems altogether, but I have more than 32 filesystems for one single host. That's where the problem occurs. Do you have this case as well without any failures? You've tried rearranging the order of disklist entries to see if there's a problem there? I did not try rearrangement, but I commented out the directories which are not so important at the moment (so that I'm backing up exactly 32 filesystems for this host), and then the missing filesystems root and home ware backed up successfully without any problems. So this does not look like a problem on the filesystems itself. If you're using dump for the backups can your dump handle directories? My HP-UX dump will only do filesystems. My linux dump can do directories. I use tar so this should not be ok. Kind regards, Urte -- \|/ @ @ ---oOO-(_)-OOo- Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
problem during dump: missing result reported
Hello list, I have a problem with amanda 2.4.2p2. I'm doing backups on three SUN machines with amanda for quite some time wihout any major problems. About 2 weeks ago we removed the bunch of single external disks from that host and added one big raid disk (which is of course too big to be backed up entirely on our 20gb native capacity tape). I then changed the disklist for this host from about 7 filesystems (= physical disk partitions) to 38 directory starting points. The first few days of course we had missing filesystems on tape until amanda has been able to do a level 0 dump on each of the new entries. Nevertheless 6 of the entries remain non-backuped (including the root filesystem and the user filesystem :-( ). I assume it might be a problem with the number of entries in the disklist (I saw some discussions about this in this newsgroup, but that turned out to be an error in the exclude statement). I noticed that these 6 entries are the ones which stand on top of the list. The error in the mail report says: FAILURE AND STRANGE DUMP SUMMARY: adler /usr/export/amis/raid2/disk_head_97_05 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_97_05 in adler response] adler /usr/export/amis/raid2/disk_head_96_05 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_96_05 in adler response] adler /usr/export/amis/raid2/disk_head_95_08 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_95_08 in adler response] adler /usr/export/amis/disk2 lev 0 FAILED [missing result for /usr/export/amis/disk2 in adler response] adler /usr/export/home/adler lev 0 FAILED [missing result for /usr/export/home/adler in adler response] adler / lev 0 FAILED [missing result for / in adler response] I dont see something unusual in the /tmp/amanda/-files. Just ask if you would like to see some extracts from there. Thanks in advance for any kind of help, Urte Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
problem during dump: missing result reported
Hello list, I have a problem with amanda 2.4.2p2. I'm doing backups on three SUN machines with amanda for quite some time wihout any major problems. About 2 weeks ago we removed the bunch of single external disks from that host and added one big raid disk (which is of course too big to be backed up entirely on our 20gb native capacity tape). I then changed the disklist for this host from about 7 filesystems (= physical disk partitions) to 38 directory starting points. The first few days of course we had missing filesystems on tape until amanda has been able to do a level 0 dump on each of the new entries. Nevertheless 6 of the entries remain non-backuped (including the root filesystem and the user filesystem :-( ). I assume it might be a problem with the number of entries in the disklist (I saw some discussions about this in this newsgroup, but that turned out to be an error in the exclude statement). I noticed that these 6 entries are the ones which stand on top of the list. The error in the mail report says: FAILURE AND STRANGE DUMP SUMMARY: adler /usr/export/amis/raid2/disk_head_97_05 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_97_05 in adler response] adler /usr/export/amis/raid2/disk_head_96_05 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_96_05 in adler response] adler /usr/export/amis/raid2/disk_head_95_08 lev 0 FAILED [missing result for /usr/export/amis/raid2/disk_head_95_08 in adler response] adler /usr/export/amis/disk2 lev 0 FAILED [missing result for /usr/export/amis/disk2 in adler response] adler /usr/export/home/adler lev 0 FAILED [missing result for /usr/export/home/adler in adler response] adler / lev 0 FAILED [missing result for / in adler response] I dont see something unusual in the /tmp/amanda/-files. Just ask if you would like to see some extracts from there. Thanks in advance for any kind of help, Urte P.S. Sorry if I'm posting twice, but it looks as if I'm having difficulties to reach the list ?? Urte Fuerst _/_/ _/ _/_/_/ German Aerospace Center DLR _/ _/_/ _/_/ _/ _/ _/ _/_/ Institute of Aeroelasticity _/_/ _/ _/ _/_/ Bunsenstrasse 10 _/_/ _/ _/_/D - 37073 Goettingen _/_/ _/ _/ _/Phone: +49 (0)551 709 2432 _/ _/ _/ _/_/ Fax:+49 (0)551 709 2862 _/_/_/_/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
amcheck ok, but amdump fails with missing result...
Hi Everyone, I have been using amanda to do backups to a tape drive for a while, but we recently decided to start doing backups to a RAID system. I downloaded amanda-242-tapeio from sourceforge, and the compile and install went fine. The only problem is I can't get it to work... Sorry for the length of this message, but I am guessing that the best way to get help is to provide as much (possibly) relevant info as possible. Since I think the most likely source of error is my configuration, I am including the config files at the top. After that are various output from amanda software. Thanks in advance for any help... dail amanda.conf org test mailto amanda dumpcycle 21 days runspercycle 3 tapecycle 4 tapes dumpuser amanda netusage 1000 Kbps labelstr ^test_[0-9]*$ tapedev file:/raid/backup tapetype RAID-FILE infofile /usr/local/etc/amanda/test/info logdir /usr/local/etc/amanda/test/log indexdir /usr/local/etc/amanda/test/index maxdumps 4 holdingdisk hd1 { comment main holding disk directory /home/amanda/backup use 6 Gb chunksize 2 GB } define dumptype global { compress client fast dumpcycle 1 week maxdumps 4 index on } define dumptype remote { global program GNUTAR } define tapetype RAID-FILE { comment File on the raid disk length 4 mbytes filemark 0 kbytes } define interface local { comment local disk use 1000 kbps } define interface eth0 { comment 10 Mbps ethernet use 400 kbps } = disklist: raid1 /alpha1/top remote eth0 = amcheck reports: [amanda@raid1 test]$ /usr/local/sbin/amcheck test Amanda Tape Server Host Check - Holding disk /home/amanda/backup: 17427732 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape test_0 label ok WARNING: info file /usr/local/etc/amanda/test/info/raid1/_alpha1_top/info: does not exist Server check took 0.002 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.023 seconds, 0 problems found (brought to you by Amanda 2.4.2p2-tapeio) [amanda@raid1 test]$ = I assume that the warning is not meaningful??? When I do [amanda@raid1 test]$ /usr/local/sbin/amdump test it returns in a couple of seconds, and the mail report is: Date: Sat, 1 Sep 2001 11:22:05 -0400 From: Amanda Backup User [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: test AMANDA MAIL REPORT FOR September 1, 2001 These dumps were to tape test_0. The next tape Amanda expects to use is: a new tape. FAILURE AND STRANGE DUMP SUMMARY: raid1 /alpha1/top lev 0 FAILED [missing result for /alpha1/top in raid1 response] STATISTICS: Total Full Daily Estimate Time (hrs:min)0:00 Run Time (hrs:min) 0:00 Dump Time (hrs:min)0:00 0:00 0:00 Output Size (meg) 0.00.00.0 Original Size (meg) 0.00.00.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min)0:00 0:00 0:00 Tape Size (meg) 0.00.00.0 Tape Used (%) 0.00.00.0 Filesystems Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- ? NOTES: planner: Adding new disk raid1:/alpha1/top. driver: WARNING: got empty schedule from planner taper: tape test_0 kb 0 fm 0 [OK] ? DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - raid1/alpha1/top 0 FAILED --- (brought to you by Amanda version 2.4.2p2-tapeio) = Although the various files in /tmp/amanda don't show any errors that are obvious to me, I included them below in the hopes that more experienced eyes will detect the problem: amandad.20010901121415.debug: amandad: debug 1 pid 2885 ruid 505 euid 505 start time Sat Sep 1 12:14:15 2001 amandad: version 2.4.2p2-tapeio amandad: build: VERSION=Amanda-2.4.2p2-tapeio amandad:BUILT_DATE=Fri Aug 31 08:44:31 EDT 2001 amandad:BUILT_MACH=Linux raid1 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown amandad:CC=gcc amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda
Re: amcheck ok, but amdump fails with missing result...
... The only problem is I can't get it to work... The output you sent (which was just what was needed to start working on this, btw -- thanks), all looks perfectly correct, with the one minor issue that sendsize didn't do anything :-). Put these two lines: OPTIONS maxdumps=4;hostname=raid1; GNUTAR /alpha1/top 0 1970:1:1:0:0:0 0 in a temp file, then run sendsize by hand **as the Amanda user** on that client with the file as standard input. Let me know what it outputs both to stdout/stderr and the /tmp/amanda/*.debug file. dail John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
missing result
Yes, i amlabel'ed the tape i'm using. You were correct: I didn't comment out the tpchanger definition on my single-slotted server, sorry. Now i'm up to an email failure report that says: FAILURE AND STRANGE DUMP SUMMARY: dellmachin /home/amanda lev 0 FAILED [missing result for /home/amanda in dellmachine response] What causes missing results? My disklist is dellmachine /home/amanda root-tar. thx, george herson John R. Jackson wrote: Thanks for your advice below (setting changerfile) as I am much further along, past amlabel and amcheck and up to trying to use amdump. So you've amlabel'd all your tapes? Amanda seems to thinks i have a tape changer ... You've apparently told it to use chg-manual in amanda.conf. That's a manual tape changer, i.e. it uses all the Amanda changer hooks but expects to talk to a human to do the work. If you don't want to do that, comment out tpchanger and make sure tapedev points to your tape device. when i enter amdump Dell-Full I'm told to keep putting in more tapes. Why? I don't know. What's in /tmp/amanda/changer*debug? george herson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result
What causes missing results? Usually a timeout. Take a look at /tmp/amanda/sendsize*debug on the client and figure out the total time (look at the first and last lines). Amanda allows five minutes per disk. If that's not enough, crank up the etimeout value in amanda.conf. george herson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: missing result for...
8 SEQ 975476700 = -------- ----- = Thanks again for your time. -Original Message- From: John R. Jackson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 28, 2000 8:21 PM To: Joe Prochazka Cc: [EMAIL PROTECTED] Subject: Re: missing result for... In addition to what you sent, I asked whether "amcheck -c config" worked and what was in /tmp/amanda/amandad*debug. It looks like sendsize is starting but never completing. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result for...
sendsize: reading /etc/amandates: Is a directory I swear I'm going to get rid of that damned thing :-). /etc/amandates is supposed to be a file, not a directory. Do this: # rm -fr /etc/amandates # touch /etc/amandates # chown amanda-user /etc/amandates Just for curiosity, did you create (mkdir) /etc/amandates? If so, why? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result in amanda 2.4.2
Here's what's in sendsize.debug: sendsize: debug 1 pid 3614 ruid 11 euid 11 start time Mon Nov 27 23:11:42 2000 /usr/lib/amanda/sendsize: version 2.4.1p1 amandad.debug is pretty long, but also has references to 2.4.1p1. I guess the old one isn't gone. I'll try removing it "better", and then recompiling. Thanks, Dylan - Original Message - From: "John R. Jackson" [EMAIL PROTECTED] To: "Dylan Casey" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, November 28, 2000 12:36 AM Subject: Re: missing result in amanda 2.4.2 ... So, I downloaded 2.4.2, and after some stuggling with the configure command, got it setup. amcheck runs fine, but now _none_ of the disks get backed up! Here are the errors: ... What's in /tmp/amanda/sendsize*debug and amandad*debug on ettin? Dylan Casey John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result in amanda 2.4.2
Hi, Thanks for the help. I removed 2.4.1p1 and installed 2.4.2 again. I had to do a couple of tries on the configuring, but eventually got it to work. The last problem was finding out that I had to put in the amandates file. Once I did that, everthing worked just fine with gnu tar (dump still doesn't work with the big disk). Thanks again, Dylan - Dylan P. Casey email:[EMAIL PROTECTED] Michigan State University office:517-432-0216 home:810-695-8615 On Tue, 28 Nov 2000, John R. Jackson wrote: ... So, I downloaded 2.4.2, and after some stuggling with the configure command, got it setup. amcheck runs fine, but now _none_ of the disks get backed up! Here are the errors: ... What's in /tmp/amanda/sendsize*debug and amandad*debug on ettin? Dylan Casey John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result in amanda 2.4.2
Once I did that, everthing worked just fine with gnu tar ... Glad to hear it. (dump still doesn't work with the big disk). What do you mean? If you're using Linux, make sure you get the latest version of dump from SourceForge. It's maintanence was nil for a long time and it had serious problems, which have recently (months) become vastly improved. Dylan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result in amanda 2.4.2
I am running Linux. I have a dump 0.4b9-1 ... As I recall, that's **way** too old. ... Before I go to the work of installing it, are there good reasons to prefer dump to gnu-tar or vice versa? Oh, no. Here we go on this subject again :-). Yes, there are reasons. But for every one side A gives, side B has a counter, so it's mostly philosophical. Pick what you're comfortable with. I will throw in that GNU tar alters the last access time of every file backed up, and that's the main reason I don't use it. Dylan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result for...
Anyone have any ideas as to why I am getting this report back. ... localhost /var/log lev 0 FAILED [missing result for /var/log in localhost response] Does amcheck work? What's in /tmp/amanda/amandad*debug? How about sendsize*debug? Any core file in /tmp/amanda? Take a look at the amdump.1 file and see if it has anything interesting to say, especially towards the end. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result for...
In addition to what you sent, I asked whether "amcheck -c config" worked and what was in /tmp/amanda/amandad*debug. It looks like sendsize is starting but never completing. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing result in amanda 2.4.2
--- "John R. Jackson" [EMAIL PROTECTED] wrote: I am running Linux. I have a dump 0.4b9-1 ... As I recall, that's **way** too old. ... Before I go to the work of installing it, are there good reasons to prefer dump to gnu-tar or vice versa? Oh, no. Here we go on this subject again :-). Yes, there are reasons. But for every one side A gives, side B has a counter, so it's mostly philosophical. Pick what you're comfortable with. I will throw in that GNU tar alters the last access time of every file backed up, and that's the main reason I don't use it. I typed a reply, hit a key stroke and landed back in my inbox, so if this comes across twice that's why. I made note for myself that didn't include enough data for me to be able to decipher: "Tar --atime-preserve" But I do remember this keeps tar from changing the last-access time of files as it backs them up. This doesn't look like a tar option so is it an option for the configure script of AMANDA? If so does this resolve your issue with tar? I read that the amverify is much more reliable with tar than dump. That's good enough for me. Randy Cordell Dylan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Re: missing result in amanda 2.4.2
On Nov 29, 2000, Randolph Cordell [EMAIL PROTECTED] wrote: "Tar --atime-preserve" But I do remember this keeps tar from changing the last-access time of files as it backs them up. Which forces it to change the inode update time, that makes each file seem out-of-date on the next run. This doesn't look like a tar option It is a GNU tar option. so is it an option for the configure script of AMANDA? Nope. You have to tweak some define in client-src/send{size,backup-gnutar}.c for Amanda to use this option. But you don't want to do that. I read that the amverify is much more reliable with tar than dump. Yep. amverify will only check a DUMP image if it was created on a similar system as that on which you run amverify. Even then, restore will only check the dump header. tar, OTOH, will go over the whole tar image. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{cygnus.com, redhat.com} CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist*Please* write to mailing lists, not to me
missing result in amanda 2.4.2
Hi, We've been using Amanda (2.4.1p1) for our backups for about a year now, with great success. Last week, I replaced the user disk containing the home areas with a new 36 Gig disk. All the mount points are the same, it's just the disk that's different. On the very next backup run, the backup for for this disk failed, with amdump asking if it was "offline". After a little hunting around and investigation of the log files, it became clear that the failure was due to the size of the disk being reported as zero. A little more hunting revealed that this is a known problem that has been fixed. So, I downloaded 2.4.2, and after some stuggling with the configure command, got it setup. amcheck runs fine, but now _none_ of the disks get backed up! Here are the errors: FAILURE AND STRANGE DUMP SUMMARY: ettin /var/krb5kdc lev 0 FAILED [missing result for /var/krb5kdc in ettin response] ettin /etc lev 0 FAILED [missing result for /etc in ettin response] ettin /disk2/cluster lev 0 FAILED [missing result for /disk2/cluster in ettin response] ettin /disk2/home1 lev 0 FAILED [missing result for /disk2/home1 in ettin response] ettin /disk3/home2 lev 0 FAILED [missing result for /disk3/home2 in ettin response] Any ideas why this is happening now? Should I go back to 2.4.1p1? How do I fix the disk-size problem? Thanks, Dylan Casey - Dylan P. Casey email:[EMAIL PROTECTED] Michigan State University office:517-432-0216 home:810-695-8615
Re: missing result in amanda 2.4.2
... So, I downloaded 2.4.2, and after some stuggling with the configure command, got it setup. amcheck runs fine, but now _none_ of the disks get backed up! Here are the errors: ... What's in /tmp/amanda/sendsize*debug and amandad*debug on ettin? Dylan Casey John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]