Couldn't resolve hostname
I am trying to backup a machine that used to be an amanda server, but now needs to be a client. I'm also using kerberos. I've added the appropriate lines to inetd.conf and services file and restarted inetd. I've added the new client to the disklist on the server. I've been assured that the client is in our KDC. I still get the error: Amanda Backup Client Hosts Check ERROR: host.comp.bogus: couldn't resolve hostname Client check: 5 hosts checked in 0.266 seconds, 1 problem found. What might be the problem: * I need to recompile amanda for a client or * the version of Amanda that's on the new client is different than on the server or * amanda has not been compiled for kerberos support on this client Or I am just hopelessly confused?
Re: Couldn't resolve hostname
On Wed, 30 Jan 2002, John R. Jackson wrote: > >ERROR: host.comp.bogus: couldn't resolve hostname > > What version of Amanda are you running? I cannot find this error message > text in 2.4.2 or beyond. The server is 2.4.1p1 with special local kerberos goop. > However, I suspect this message comes from the server, not the client, > i.e. the server is saying it has a problem making the request to client > "host.comp.bogus". It is... during amcheck. Anyway, I found out that 2 of the 3 problems I listed in my original post were the actual problems. I'm attempting to newly build amanda now. Thanks, --Ruth Anne
Error building changer-src
I am getting the following error when building Amanda 2.4.1p1 with special kerberos goop on a NetBSD 1.5.1_ALPHA machine: Making all in changer-src gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../server-src -g -c scsi-hpux.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../server-src -g -c scsi-chio.c scsi-chio.c: In function `isempty': scsi-chio.c:160: structure has no member named `ces_type' scsi-chio.c:161: structure has no member named `ces_data' scsi-chio.c:170: structure has no member named `ces_data' scsi-chio.c:172: structure has no member named `ces_data' scsi-chio.c: In function `find_empty': scsi-chio.c:189: structure has no member named `ces_type' scsi-chio.c:190: structure has no member named `ces_data' scsi-chio.c:200: structure has no member named `ces_data' scsi-chio.c:202: structure has no member named `ces_data' scsi-chio.c: In function `drive_loaded': scsi-chio.c:219: structure has no member named `ces_type' scsi-chio.c:220: structure has no member named `ces_data' scsi-chio.c:229: structure has no member named `ces_data' scsi-chio.c:231: structure has no member named `ces_data' scsi-chio.c: In function `unload': scsi-chio.c:241: storage size of `move' isn't known scsi-chio.c: In function `load': scsi-chio.c:265: storage size of `move' isn't known *** Error code 1 Stop. *** Error code 1 I even tried to configure with --without-server to no avail. Regards...
Re: Error building changer-src
On Wed, 30 Jan 2002, John R. Jackson wrote: > >I am getting the following error when building Amanda 2.4.1p1 ... > > Help with such an old release is going to be difficult, however ... Alas, the newer versions don't seem to work with our Kerberos setup. :( > >scsi-chio.c: In function `isempty': > >scsi-chio.c:160: structure has no member named `ces_type' > >scsi-chio.c:161: structure has no member named `ces_data' > >... > > As long as you don't need that changer (which you probably don't) > then I'd just go into config/config.h and #undef'ing HAVE_CHIO_H and > HAVE_SYS_CHIO_H. That should effectively disable that part of the build. HAVE_CHIO_H was #undef'ed, but HAVE_SYS_CHIO_H was #defined, so #undef'ing it (and commenting it out for good measure) produced the desired results. Thanks. Now, if I could just get authentication working properly... --Ruth Anne
'mutual-authentication failed' error
I am getting the following error when doing an amcheck from the server to a client running Amanda 2.4.1p1 with special kerberos goop on a NetBSD 1.5.1_ALPHA machine: begin amcheck- Amanda Tape Server Host Check - /stor1/amanda/holding: 1548827 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape COMDLT09 label ok. Server check took 16.080 seconds. pkt->security is NULL Amanda Backup Client Hosts Check ERROR: client1.comp.bogus [mutual-authentication failed] Client check: 5 hosts checked in 0.329 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) end amcheck An check through archives and such shows that the error is usually caused by a large enough time skew between machines or a problem with the .klogin file. Neither of those problems appears to exist. The amandad.debug file on the client shows the following: start client1 debug got packet: Amanda 2.4 REQ HANDLE 003-004C0508 SEQ 101248 SECURITY TICKET "$04$07$05COMP.BOGUS$008 $0Bf$94dZ$CE$0F$A1$9Dw$F8`$BF62$0E5$16$C9$ 95z#$BC$97]$1E$FF8$07q0$12_' *$A1$98$A8?$8A$F9$0F$86$160$C3L$B60$BE
Re: 'mutual-authentication failed' error
On Thu, 31 Jan 2002, John R. Jackson wrote: > The output for client2 that you posted says the former (krb4). My guess > is the output for client1 says the latter (bsd). It looks like you need > "-krb4" on your amandad line in inetd.conf to get krb4 security turned on > (check client2 and see how it is started). Well, that's the way it was. The real problem turned out to be a cascade of problems which I will not go into here. kerberos was upgraded, and amanda was upgraded to amanda-2.4.2p2 (with the krb4 patches). I'm still getting the 'mutual-authentication failed' error from the server (which is 2.4.1p1). The amandad*debug file on the client is showing that it is using krb4 security but has the following error: amandad: sending REP packet: Amanda 2.4 REP HANDLE 004-804C0508 SEQ 1012591699 ERROR [kerberos error: Can't decode authenticator (krb_rd_req)] Your continued assistance is much appreciated, --Ruth Anne
Re: 'mutual-authentication failed' error
On Fri, 1 Feb 2002, Ruth Anne wrote: > I'm still getting the 'mutual-authentication failed' error from the > server (which is 2.4.1p1). The amandad*debug file on the > client is showing that it is using krb4 security but has the following > error: > > > amandad: sending REP packet: > > Amanda 2.4 REP HANDLE 004-804C0508 SEQ 1012591699 > ERROR [kerberos error: Can't decode authenticator (krb_rd_req)] ^^ I should learn to read for content. This is a *kerberos* error, having nothing to do with amanda. I took amanda out of my google search, discovered that this error is usually caused by lack of an /etc/srvtab (or in my case /etc/kerberosIV/srvtab). I LARTed the person who didn't mentioned this when I recomiled for krb4 support and added the file. Voila! amcheck is very happy! Thanks all who helped, --Ruth Anne
Skipping a tape
Is there any way to skip a tape? My server has crashed while doing a partition for 2 nights running, and tonight's backup is supposed to overwrite my last level 0 of this partition. Regards, --Ruth Anne
RE: Skipping a tape
On Tue, 5 Feb 2002, Bort, Paul wrote: > You have a few choices: > > 1. Add a new tape to the rotation. It will be used before any other. > > 2. You can prevent a tape from being used for backups with a command like > this: > > amanda@tape$ amadmin YourConfig no-reuse YourGoodTape OK, But won't this remove any logs, indexes, etc? I don't really want to remove this tape for good, just for right now. As for the crashes, yeah, we're working on it. Coming in before the sun comes up to reboot servers is not my idea of fun. --Ruth Anne
RE: Skipping a tape
On Tue, 5 Feb 2002, Bort, Paul wrote: > The only thing that no-reuse changes is tapelist. No logs or indexes are > deleted, and you can still restore from the tape. It just won't be written > to. My most humble apologies. Yes, no-reuse will do what I want. > NB: I don't remember if this causes AMANDA to prompt for a new tape if > taking the tape out of rotation takes you below tapecycle. I guess I will find out. Thanks to all, --Ruth Anne
closing tape: Input/output error
I've not seen the following error in 2.5 years of minding Amanda backups, nor have I found it in the archives: *** THE DUMPS DID NOT FINISH PROPERLY! *** A TAPE ERROR OCCURRED: [[closing tape: Input/output error]]. *** PERFORMED ALL DUMPS TO HOLDING DISK. THESE DUMPS WERE TO DISK. Flush them onto tape DLT07 or a new tape. Tonight's dumps should go onto 1 tape: DLT08. FAILURE AND STRANGE DUMP SUMMARY: shell da0s1f lev 0 FAILED ["data write: Broken pipe"] shell da0s1f lev 0 FAILED [out of tape] taper: FATAL syncpipe_get: w: unexpected EOF shell da0s1f lev 0 FAILED [dump to tape failed] I found the following in the server's messages file: Feb 8 07:25:48 storage /kernel: (sa0:bt0:0:1:0): CCB 0xcde9e300 - timed out Feb 8 07:25:50 storage /kernel: (sa0:bt0:0:1:0): CCB 0xcde9e300 - timed out Feb 8 07:25:50 storage /kernel: bt0: No longer in timeout Feb 8 07:25:50 storage /kernel: (sa0:bt0:0:1:0): failed to write terminating filemark(s) Feb 8 07:25:55 storage /kernel: (sa0:bt0:0:1:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. Now, this sort of looks like a bad tape. Or is the [out of tape] error true? If so, I thought amanda was supposed to be able to figure things so everything fits on a tape. I know I've seen amanda do incs when a full would have been too much for a tape. Regards, --Ruth Anne
Re: closing tape: Input/output error
On Fri, 8 Feb 2002, John R. Jackson wrote: > >*** A TAPE ERROR OCCURRED: [[closing tape: Input/output error]]. > > This comes from a couple of places in Amanda, but the most likely is that > Amanda was all done and was just finishing up. The tape is *probably* > OK, but I wouldn't bet everything on it. Depending on the the comments after I fill in some blanks, it'll probably get repleaced anyway. > > taper: FATAL syncpipe_get: w: unexpected EOF > > I think this is fixed in the current sources. Noted. > > > >Feb 8 07:25:48 storage /kernel: (sa0:bt0:0:1:0): CCB 0xcde9e300 - timed out > > > >Now, this sort of looks like a bad tape. ... > > Or some other kind of hardware problem. Timeouts are a bad thing. Other staff put the tape drive on a buslogic scsi card last night, to hopefully solve a crash problem we were having. Could it be causing the problem? (I probably should have mentioned that in the initial email.) If our problem happens again tonight, we'll probably know where the issue lies. > You left out one important line from the E-mail. The one in the NOTES > section that shows how much data taper wrote before it got into trouble. > If that's close to your tape size, then you may have just banged into > the end. If it's way short, then it's a hardware or media problem. Beg pardon, here's the missing bit: taper: tape NOMDLT06 kb 3012224 fm 17 writing file: Input/output error The tapes are AIT-1 25/50M, no compression that I can tell. Thanks, --Ruth Anne
Re: closing tape: Input/output error
On Fri, 8 Feb 2002, John R. Jackson wrote: > >Other staff put the tape drive on a buslogic scsi card last night, to > >hopefully solve a crash problem we were having. Could it be causing > >the problem? ... > > Aha! The truth finally comes out :-). Hey, I didn't do this so I didn't remember until after I sent the original email. :) > Sure, it could be causing the problem. Any number of things could have > gone wrong during that swap -- too much or not enough termination, cable > not seated well enough, bent pins, bad controller, full reset needed, etc. > > > taper: tape NOMDLT06 kb 3012224 fm 17 writing file: Input/output error > > > >The tapes are AIT-1 25/50M, no compression that I can tell. > > So you weren't anywhere close to the tape capacity, which puts this > squarely in the hardware error (as compared to end of media) problem > arena. OK, I thought as much by this time, with your help. :) I'll be watching things tonight... if there's another failure, I can pretty much pin it on the new scsi controller. Thanks, --Ruth Anne
make fails building krb4 support
I am attempting to make Amanda 2.4.2pl2 with krb4 support server/client on NetBSD1.5.1_ALPHA; KerberosV 1.2.3 While Making all in common-src: ... gcc -g -O2 -I/usr/local/krb5/include -I/usr/local/krb5/include/kerberosIV -L/usr/local/krb5/lib -o genversion genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lm -ltermcap -lkrb4 -lkrb5 -lcrypto -ldes425 -lcom_err /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `init_common': init_ctx.o(.text+0x13c): undefined reference to `krb5_c_random_seed' /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `krb5_set_default_in_tkt_ktypes': init_ctx.o(.text+0x3de): undefined reference to `valid_enctype' /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `get_profile_etype_list': init_ctx.o(.text+0x647): undefined reference to `krb5_string_to_enctype' /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `krb5_set_default_tgs_enctypes': init_ctx.o(.text+0x75e): undefined reference to `valid_enctype' collect2: ld returned 1 exit status *** Error code 1 Stop. *** Error code 1 Any suggestions? Thanks, --Ruth Anne
Re: make fails building krb4 support
On Mon, 4 Mar 2002, Ruth Anne wrote: I know it's bad form to followup your own message, but... > > I am attempting to make Amanda 2.4.2pl2 with krb4 support > server/client on NetBSD1.5.1_ALPHA; KerberosV 1.2.3 > > While Making all in common-src: > > ... > gcc -g -O2 -I/usr/local/krb5/include > -I/usr/local/krb5/include/kerberosIV -L/usr/local/krb5/lib -o genversion >genversion.o versuff.o alloc.o debug.o error.o util.o file.o -lm -ltermcap -lkrb4 >-lkrb5 -lcrypto -ldes425 -lcom_err > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `init_common': > init_ctx.o(.text+0x13c): undefined reference to `krb5_c_random_seed' > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function >`krb5_set_default_in_tkt_ktypes': > init_ctx.o(.text+0x3de): undefined reference to `valid_enctype' > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function `get_profile_etype_list': > init_ctx.o(.text+0x647): undefined reference to `krb5_string_to_enctype' > /usr/local/krb5/lib/libkrb5.a(init_ctx.o): In function >`krb5_set_default_tgs_enctypes': > init_ctx.o(.text+0x75e): undefined reference to `valid_enctype' > collect2: ld returned 1 exit status > *** Error code 1 > > Stop. > *** Error code 1 I got my answer from the kerberos mailing list. At least in KerberosV 1.2.3, there was a library name change; crypto changed to k5crypto. So in the following lines in the configure file: KRB4LIBS="-lkrb4 -lkrb5 -lcrypto -ldes425 -lcom_err" KRB4LIBS="-lkrb4 -lcrypto -ldes425" change lcrypto to lk5crypto. This is in addition to the change that needs to be made in the configure file of libcrypto to libk5crypto. --Ruth Anne
Build dies trying to make amoverview
I am attempting to make amanda 2.4.2p2 on a NetBSD 1.5_ALPHA system The make dies with the following message: cat amcheckdb.sh > amcheckdb chmod a+x amcheckdb cat amcleanup.sh > amcleanup chmod a+x amcleanup cat amdump.sh > amdump chmod a+x amdump make: don't know how to make amoverview. Stop *** Error code 1 I googled, and discovered that this is fixed in the pkgsrc for amanda, but I can't use the pkgsrc because I need to build amanda with kerberos. Any idea what I need to make this work, or how I can not build amoverview, as I am unlikely to use it? Thanks for any help, --Ruth Anne
Re: Build dies trying to make amoverview
On Wed, 6 Mar 2002, Bernhard R. Erdmann wrote: > > I am attempting to make amanda 2.4.2p2 on a NetBSD 1.5_ALPHA system > > The make dies with the following message: > > > > cat amcheckdb.sh > amcheckdb > > chmod a+x amcheckdb > > cat amcleanup.sh > amcleanup > > chmod a+x amcleanup > > cat amdump.sh > amdump > > chmod a+x amdump > > make: don't know how to make amoverview. Stop > > *** Error code 1 > > Use GNU make (gmake) Thanks, it worked! --Ruth Anne
Re: Documentation (Yes, post it!)
On Thu, 14 Mar 2002, Eric Trager wrote: > On Thu, 14 Mar 2002, Doug Silver wrote: > > > On 14 Mar 2002, Brad Tilley wrote: > > > > > I'll send you a copy once it's complete. I wouldn't want to send it the > > > whole list. Apparently, only a handful are interested in it. > > > > I disagree -- one of the things that I (and others I've talked to) have > > noticed is that while Amanda is feature rich, it's documentation is > > lacking. Why not post it somewhere so other's can read through it and > > potentially add to it. Even if it's just from the client/end-user > > perspective, I think it's better than nothing. > > Well put. Anything documenting successes and failures along the way that > ends up searchable in the archives is a Good Thing. I've searched for > issues with all kinds of programs on deja.com for years and sometimes it's > a lone reply in a single thread that gives me a solution. > If you don't have the web space for it, I'd be willing to put it up. Or maybe amanda.org would like it. I've been having massive problems with using amanda with kerberos, in large part due to lack of documentation. You'd better believe that when I finally get all done, I am going to put up a document telling how to do it. --Ruth Anne
Skipping a tape
Is there any way to skip a tape? My server has crashed while doing a partition for 2 nights running, and tonight's backup is supposed to overwrite my last level 0 of this partition. Regards, --Ruth Anne
"DUMP: rawread: lseek fails" errors on /amanda0
Amanda 2.4.1p1 server with krb4 stuff, on a NetBSD 1.5ZC machine.
(yes, we're going to upgrade, but not just yet.)
We've been getting these errors occassionly. We got similar errors on
on /amanda0 previous version of NetBSD (DUMP: bread: lseek fails).
May I presume that the rawread errors are also caused by dump finding
a change?
Regards and thanks,
--Ruth Anne
--Error Message
These dumps were to tape NOMAIT08.
Tonight's dumps should go onto 1 tape: NOMAIT09.
FAILURE AND STRANGE DUMP SUMMARY:
vault.nomi sd0g lev 0 STRANGE
storage.no da0s1h lev 3 FAILED [/sbin/dump returned 3]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)2:18 1:00 0:35 (0:25 start, 0:18 idle)
Output Size (meg) 13451.6 7790.7 5660.9
Original Size (meg) 13451.6 7790.7 5660.9
Avg Compressed Size (%) -- -- --
Tape Used (%) 61.8 35.8 26.0 (level:#disks ...)
Filesystems Dumped 19 12 7 (1:4 2:3)
Avg Dump Rate (k/s) 1824.0 1736.6 1959.7
Avg Tp Write Rate (k/s) 2417.3 2216.6 2761.4
?
FAILED AND STRANGE DUMP DETAILS:
/-- vault.nomi sd0g lev 0 STRANGE
sendbackup: start [vault.nominum.com:sd0g level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Wed Oct 30 03:39:21 2002
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/rsd0g (/amanda0) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 1173823 tape blocks.
| DUMP: Volume 1 started at: Wed Oct 30 03:39:51 2002
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 31.68% done, finished in 0:10
? DUMP: rawread: lseek fails
? DUMP: rawread: lseek2 fails: Undefined error: 0!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek fails
? DUMP: rawread: lseek2 fails: Undefined error: 0!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: rawread: lseek2 fails: No message of desired type!
? DUMP: read error from /dev/rsd0g: Invalid argument: [block
1681940544]:
count=4096
? DUMP: read error from /dev/rsd0g: Invalid argument: [sector
1681940544]:
count=512: Invalid argument
? DUMP: read error from /dev/rsd0g: Invalid argument: [sector
1681940545]:
count=512: Invalid argument
? DUMP: read error from /dev/rsd0g: Invalid argument: [sector
1681940546]:
[etc... snipped]
