RE: amanda in aix
> -Mensaje original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 29 de enero de 2002 22:23
> Para: Monserrat Seisdedos Nunez
> CC: Amanda-Users (E-mail)
> Asunto: Re: amanda in aix
>
>
>
>
>
>
> >I'm trying to compile amanda 2.4.2p2 in a 4.3.3 aix system.
> >i installed gtar,gawk, gsed, perl and readline.
>
> When you say you installed these packages, did you build them
> from source
> or did you find binaries someplace?
I installed them from the rpm's packages
>
> >i run the configure script, but when i do make i receive the
> next error:
> >
> >make[1]: Entering directory
> `/home/software/amanda-2.4.2p2/client-src'
> >/usr/bin/sh ../libtool --mode=link gcc -g -O2-o amandad
> amandad.o
> >../common-src/libamanda.la libamclient.la
> ../common-src/libamanda.la
> >-lm -lreadline -lcurses -lnsl -lintl
> >gcc -g -O2 -o amandad amandad.o ../common-src/.libs/libamanda.a -lm
> >-lreadline -lcurses -lnsl -lintl .libs/libamclient.a -lm -lreadline
> -lcurses
> >-lnsl -lintl ../common-src/.libs/libamanda.a -lm -lreadline
> -lcurses -lnsl
> >-lintl -lm -lreadline -lcurses -lnsl -lintl
> >ld: 0711-317 ERROR: Undefined symbol: .__main
> >...
>
> I just tried this on a 4.3.3 system here using gcc 2.95.3 and it
> worked OK. What version of gcc are you using ("gcc --version")?
2.9-aix43-010414
>
> Was your version of gcc built for 4.3.3 ("gcc --verbose")?
>
> My build is using -ltermcap rather than -lcurses. Did you do
> something
> special to change that?
>
> Prior to building amandad, make should have built and run
> ./genversion.
> I assume, since you didn't say anything, that that went OK, i.e. you
> didn't get load errors and it ran?
i didn't run amandad because i couldn't compile the sources.
Thanks for yor answers
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
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: FAILURE AND STRANGE DUMP SUMMARY:
On Tue, 29 Jan 2002 16:12:17 -0500 "John R. Jackson" <[EMAIL PROTECTED]> wrote: [..] > I looked at the code and that error only comes from one place, when driver > has tried doing a dump once and it failed but was requeued to "TRYAGAIN", > then the second attempt also failed. I'm not sure the message means what > it says, that there really was a problem connecting to the host. That may > have been what it originally meant, but now it might mean other things > (in case it isn't obvious, this code gets a little confusing to navigate). > > I'm pretty sure it has nothing to do with starting a new tapecycle, > except in an indirect way (if at all). My best guess is it has something > to do with the amount of holding disk space you have, or possibly other > activity going on in the holding disk at the same time Amanda is running > (e.g. Amanda thought it had N MBytes but when it actually tried to use > the space, less than that was really there). > > I would need to see the corresponding amdump. file that goes along > with one of these errors, and possibly all the client logs for that same > run. If you want to contact me offline of the list for this, that's OK. > > In the meantime, you might try dropping maxdumps back to 1. That may > or may not help -- it's just a guess. Hi John, you are right about the "TRYAGAIN", take a look ath an excerpt of /var/log/amanda/DailySet1/amdump.3 at the backup server ---cut-on--- driver: adding holding disk 0 dir /amanda_holding_disk size 512000 reserving 512000 out of 512000 for degraded-mode dumps driver: start time 27.648 inparallel 10 bandwidth 600 diskspace 512000 dir OBSOLETE datestamp 20020126 driver: drain-ends tapeq LFFO big-dumpers 7 driver: result time 27.648 from taper: TAPER-OK driver: send-cmd time 27.648 to dumper0: FILE-DUMP 00-1 /amanda_holding_disk/20020126/heiner.buero-till.de._usr_samba1_ing__buero.1 heiner.buero-till.de /usr/s amba1/ing_buero 1 2002:1:23:23:46:49 1073741824 GNUTAR 96 |;bsd-auth;compress-fast;index;exclude-list=/etc/amanda/exclude.gtar; driver: state time 27.649 free kps: 590 space: 511904 taper: idle idle-dumpers: 9 qlen tapeq: 0 runq: 13 roomq: 0 wakeup: 15 driver-idle: start-wait driver: interface-state time 27.649 if : free 590 driver: hdisk-state time 27.649 hdisk 0: free 511904 dumpers 1 driver: send-cmd time 42.641 to dumper1: FILE-DUMP 01-2 /amanda_holding_disk/20020126/heiner.buero-till.de._usr_samba_fax__eingang.1 heiner.buero-till.de /usr/ samba/fax_eingang 1 2002:1:23:23:45:48 1073741824 GNUTAR 96 |;bsd-auth;compress-fast;index;exclude-list=/etc/amanda/exclude.gtar; driver: state time 42.642 free kps: 580 space: 511808 taper: idle idle-dumpers: 8 qlen tapeq: 0 runq: 12 roomq: 0 wakeup: 15 driver-idle: start-wait driver: interface-state time 42.642 if : free 580 driver: hdisk-state time 42.642 hdisk 0: free 511808 dumpers 2 driver: result time 42.643 from dumper1: TRY-AGAIN 01-2 nak error:amandad busy dumper: stream_client: connected to 192.168.1.25.41043 ---cut-off--- Your guess about the holding disk might be right, because I have only about 500 MB space left which is configured for this amount at amanda.conf. The data to backup are a few :) GB, is there a calculation for the size of the holding disk corresponding to the amount of data to backup? Sorry, I haven't found any amdump.* file neither at the server nor at the client. Well, don't blame me as I am a new user, but what do you mean with "dropping maxdumps back to 1" and how to do that? BTW, the server is a debian with a pentium II cpu at 400 MHz and amanda been installed from source, because debian doesn't have packages for the actual bugfixed release and it has no other jobs to do at night than amanda. ... I hope, that you can tell me to get a bigger holding disk and that this would fix my "could not connect to client" - problem. ... if not, I'll have to ask my boss, if he agrees about giving more information to your hands if you are willing to get them to help me :) :) adTHANXvance Sascha
su - amanda -c "/usr/local/libexec/amandad"
Hi, I had backup working on both the host and the guest. Then I got an email saying: FAILURE AND STRANGE DUMP SUMMARY: pc16 hda6 lev 0 FAILED [Request to vg16 timed out.] pc21 hda6 lev 0 FAILED [Request to vg21 timed out.] So I tried su - amanda -c "/usr/local/libexec/amandad" and I get this msg in my message log: amandad[5826]: error receiving message: timout What's happened? -- Steve Szmidt V.P. Information Video Group Distributors, Inc.
Dump disk size and backup failure
We have been experiencing a lot of failures on full backup with a large dump
disk.
Our dump disk devices are:
/dev/dsk/c0t13d0s0 83143932708 8145398 1%/usr13
/dev/dsk/c2t1d0s317413250 10 17239108 1%/usr14
The holdingdisk definitions are:
holdingdisk hd1 {
comment "main holding disk"
directory "/usr13/amanda_holding_disk" # where the holding disk is
use -2500 mb# how much space can we use on it
chunksize 0 mb
}
holdingdisk hd2 {
comment "main holding disk"
directory "/usr14/amanda_holding_disk" # where the holding disk is
use -2500 mb# how much space can we use on it
chunksize 0 mb
}
All backups work fine using hd1, but when using hd2, the disk fills; backups
go into degraded mode and several fail. Is there some limit on the size of
holding disk that amanda can manage?
All parameters for the two dumps are identical and the amount of data backed
up using each backup set is very similar.
Has anyone else seen this issue?
---
Wayne Richards e-mail: [EMAIL PROTECTED]
Re: su - amanda -c "/usr/local/libexec/amandad"
On Wed, 30 Jan 2002 at 8:49am, Steve wrote > Hi, > > I had backup working on both the host and the guest. > Then I got an email saying: > > FAILURE AND STRANGE DUMP SUMMARY: >pc16 hda6 lev 0 FAILED [Request to vg16 timed out.] >pc21 hda6 lev 0 FAILED [Request to vg21 timed out.] So you're saying that it *was* working, and now it isn't. And, let me guess, you didn't touch anything, right? ;) > So I tried > su - amanda -c "/usr/local/libexec/amandad" > > and I get this msg in my message log: > amandad[5826]: error receiving message: timout > That's normal when starting amandad by hand -- it waits for messages from the tape server and, when it doesn't get any, times out. The question is what's in the amandad*debug (it if exists) from the time at which the backup failed (find it via the timestamps). Do these hosts still pass amcheck? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: amanda in aix
> -Mensaje original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Enviado el: martes 29 de enero de 2002 22:23
> Para: Monserrat Seisdedos Nunez
> CC: Amanda-Users (E-mail)
> Asunto: Re: amanda in aix
>
>
>
>
>
>
> >I'm trying to compile amanda 2.4.2p2 in a 4.3.3 aix system.
> >i installed gtar,gawk, gsed, perl and readline.
>
> When you say you installed these packages, did you build them
> from source
> or did you find binaries someplace?
>
> >i run the configure script, but when i do make i receive the
> next error:
> >
> >make[1]: Entering directory
> `/home/software/amanda-2.4.2p2/client-src'
> >/usr/bin/sh ../libtool --mode=link gcc -g -O2-o amandad
> amandad.o
> >../common-src/libamanda.la libamclient.la
> ../common-src/libamanda.la
> >-lm -lreadline -lcurses -lnsl -lintl
> >gcc -g -O2 -o amandad amandad.o ../common-src/.libs/libamanda.a -lm
> >-lreadline -lcurses -lnsl -lintl .libs/libamclient.a -lm -lreadline
> -lcurses
> >-lnsl -lintl ../common-src/.libs/libamanda.a -lm -lreadline
> -lcurses -lnsl
> >-lintl -lm -lreadline -lcurses -lnsl -lintl
> >ld: 0711-317 ERROR: Undefined symbol: .__main
> >...
>
> I just tried this on a 4.3.3 system here using gcc 2.95.3 and it
> worked OK. What version of gcc are you using ("gcc --version")?
>
> Was your version of gcc built for 4.3.3 ("gcc --verbose")?
>
> My build is using -ltermcap rather than -lcurses. Did you do
> something
> special to change that?
>
> Prior to building amandad, make should have built and run
> ./genversion.
> I assume, since you didn't say anything, that that went OK, i.e. you
> didn't get load errors and it ran?
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
ok, i think a solved my problem, i set the LIBPATH variable to the gnu
library directory.
Now i have another problem, when i make the source i get the next error:
collect2: ../common-src/libamanda.a:not a COFF file
can any body helpme??
Re: Newbie first questions
THANK YOU all for your thoughtful replies. So often when I ask questions, I end up with the dissonance of dueling paradigms...like a telepathic blind person talking with someone with a 'normal' sensorium. My experience on restoring machines has been with Microsoft, which doesn't rebuild very cleanly at all, and IBM's AIX which does it magically well, particularly with Sysback (which costs money, but is supported under the AIX service contract once you've purchased it). So the core of my worry is basically, 'Surely you can't just boot off the distribution media, get a barebones TTY window and then Amanda will restore everything with an under-the-covers tar -xvf rmt0 /' There are two problems, right away 1) I guess you have to reconstruct the partitions first (in Linux too?) 2) What do you do about boot records, hidden system files and sparsely-written data (you *don't* restore Oracle from a tar tape, fr'instance)and these will be different with each OS and then there are possible other concerns.. 3) You have booted (off the installation media, I guess) and are running system code...what happens when you overwrite code you're running. I know that, if I'm running a script in a normal environment AND I update and save that script during its run, funny and weird things happen. Wouldn't that be the case with OS system code as well? In all honesty, this is not so much an Amanda question (though anyone using A. must deal with it to do a system restore) as it is a OS-peculiarities question. Unfortunately, someone has absconded with my O'Reilly 'Unix Backup and Recovery Book', which should answer some of those questions. Does anyone suggestions for other books on the same topic (the problems #2 & #3) or have a good chapter on it for Solairs and LInux? I have the Running Linux book but it only talks about file restoration, not system restoration. There are all sorts of magical possibilities inherent in a Logical Volume Manager...which IBM has and gave to Linux...I am waiting/hoping for a Linux mksysb equivalent. FWIW, Sysback will work with mulitple tapes and supports tape streamingif any AIXers would like more info on Sysback, feel free to drop me a line. Again thanks for thoughtful help! S. -- Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 [EMAIL PROTECTED] voice: 845-758-7475, fax: 845-758-7035
Easy question
I'm getting this on several of my Win2K clients: mordor //bali/personal$ lev 0 FAILED [missing result for //bali/personal$ in mordor response] This hasn't always happened with them. This is Amanda 2.4.1p1 running on Debian Linux: Linux mordor 2.1.126 #1 SMP Mon Nov 2 16:09:40 MST 1998 i686 unknown Any ideas? -- Terri Eads Systems Administrator [EMAIL PROTECTED] Research Applications Program (303) 497-8425 National Center for Atmospheric Research
Speed of backups under amanda with gpg and gzip wrapper?
Hello, I'm currently in the testing phase for switching our amanda backups over to Judith Freeman's secure scheme, using gpg and a gzip wrapper (http://security.uchicago.edu/tools/gpg-amanda.) Everything's working great with our test computers, and, so far, I'm pretty psyched about it. However, I would like to ask anybody who's actually done a full scale change over from regular amanda to this secure amanda whether or not they experienced significant slow downs as a result. The small scale testing that I'm doing seems to be taking quite a long time. It's not a huge deal if our backups take longer as a result of this added security, but it's going to take double or triple time, then we might need to add another amanda server into the mix. If I missed this aspect of the secure amanda discussion in the archives, then please point me to them. Thanks for your insight. Jenn
Re: Who uses Amanda?
Paul Bijnens <[EMAIL PROTECTED]> wrote: > > Even more important than who uses it, is how good is it. > And I can tell you from personal experience this last month that it > works very good. I had 4 disk crashes over a period of 5 weeks now > (yes, that's more than the 15 years before), all on critical systems. Interesting.. We've had two hard disks fail recently, along with our Amanda tape drive (the holding disk allowed us to do 4 backups before a new drive showed up). I've also heard of other people having unusual problems in the last few weeks.. Makes me wonder if there was some excess solar radiation or something recently. > I've restored everything from amanda tapes, up to the last byte. > Among the crashed disks was: one with home directories for a complete > department (on Solaris), one with the second drive on a PC running > W2000 (containing only data), one with the only disk in Linux computer > (boot from cd, and restore over the network), and another one containing > the root filesystem of a Linux machine, located outside the firewall (boot > from cd, while computer is moved inside firewall, and restore over network). > Between crash and final reboot was no more then 3 hours for each of the > systems. I'm curious, do people have a preferred recovery CD? I got stuck with an old Linuxcare bootable business card (burned onto a regular-sized CD) the other day that had some pretty aincent stuff on it. That restore is still in progress, unfortunately.. I'm hoping to have better luck using a more recent LNX-BBC 1.618. Since our tape drive had failed recently, I just copied the relevant dumps onto my laptop's hard drive and I've been using netcat (nc) to send the dumps to the system I'm restoring on.. -- Mike Hicks [mailto:[EMAIL PROTECTED]] Unix Support Assistant| Carlson School of Management Office: 1-160 Phone: 6-7909 | University of Minnesota msg09586/pgp0.pgp Description: PGP signature
Re: Couldn't resolve hostname
>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.
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".
Looking at the code, and making a guess at where this message is coming
from, it looks like these are the things that might trigger it:
* The server called gethostbyname("host.comp.bogus") and did not get
a valid response. Are you sure that host name is valid? You
might test it out with:
ftp://gandalf.cc.purdue.edu/pub/amanda/gethostby*.c
* The call to krb_mk_req() failed for some reason.
Are you using Kerberos successfully with other clients?
Other than the above, I'd have to start adding debugging print statements
to make any further guesses as to where it's going wrong.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Reg:Overwriting of tapes
Hi everyone I have a HP-DAT24*6 tape drive connected to my backup server running on linux. It works fine for a cycle of 6 tapes. I want to reuse the tapes but after one cycle I am not able to do so. The tape changer acts weirdly skipping tapes and doing any backups. This is my changer file. do I have to make any changes to it. Any suggestions regarding this. #Changer file for chg-mtx firstslot=1 1st tape slot lastslot=6 Last tape slot cleanslot=6 Slot with cleaner tape # # # Do you want to clean the drive after a certain number of accesses? # # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we # #have no reliable way to count this. A single amcheck could # #generate as many accesses as slots you have, plus 1. # # ALSO NOTE - many modern tape loaders handle this automatically. # AUTOCLEAN=0 Set to '1' or greater to enable # autocleancount=99 Number of access before a clean. # havereader=0 If you have a barcode reader, set to 1. # offlinestatus=1 Set to 0 if 'mt status' gives an # "offline" when drive is offline. # Set to 1 or greater if 'mt status' # doesn't give and offline, rather an # "ONLINE" when drive is online. # OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a # 'mt offline' before mtx unload? ### _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Newbie first questions
>So the core of my worry is basically, 'Surely you can't just boot off the dist >ribution media, get a barebones TTY window and then Amanda will restore >everything with an under-the-covers tar -xvf rmt0 /' It depends on the OS, but you're right, there is usually some other work you will have to do before turning Amanda loose on the bulk of the data. >There are two problems, right away >1) I guess you have to reconstruct the partitions first (in Linux too?) If you're starting from a brand new disk, then yes. >2) What do you do about boot records, hidden system files ... You figure out what you need to do ahead of time (as I said, installboot for Solaris, and Bernhard gave the basics for Linux) and write it down on paper in your procedures book. :-) Some OS's (I think Linux falls in this category) have packages that let you create a boot-able medium that can do a lot of this for you, ala mksysb. But that's a Linux question, not an Amanda one (although there is probably plenty of expertise on this list). FYI, there has been some discussion in the past about adding special files to the Amanda tapes to help with disaster recovery. For instance, it could be a tar of various config files to make putting things back together easier. Or it could be a script that actually did the work (writing the script would be an exercise left to you :-). >... and sparsely-written > data (you *don't* restore Oracle from a tar tape, fr'instance)... Now you've gone "below" Amanda. Amanda is a manager of other backup programs. It does not actually do backups itself (it doesn't read the disk, etc). However, all dump style programs (backup, ufsdump, dump, etc) handle sparse files. What comes back will be what was there to start with. GNU tar can also do sparse files, and Amanda runs it with the flags needed to do so. Databases (e.g. Oracle), though, are another matter. Those are not just sparse files. They are also "live" and you can't just back them up while the engine is running. There are numerous ways around this (check the mailing list archives). We run Oracle here and do it by having a large "backup" area that we tell Oracle to write its own backups into, then we use Amanda to dump that. See: ftp://gandalf.cc.purdue.edu/pub/amanda/dbbackup.* It's a little out of date, but should still work. And yes, I've even had to restore from them. >... and these will be different with each OS >and then there are possible other concerns.. Yup. In general, you need to know what you're doing. That's why us backup folks rake in the huge bucks :-). >3) You have booted (off the installation media, I guess) and are running syste >m code...what happens when you overwrite code you're running. ... Ummm, if you booted off installation media, such as a CD-ROM, you *can't* overwrite the code being run :-). It's called "Read-Only" for a reason. Taking Solaris as an example, I would boot off the CD and at that point (well, after answering a lot of annoying questions), I'd have a normal TTY window, but it's all associated with the CD. Next I'd re-partition the disk drive (if needed), newfs the partitions, and finally mount and restore into them. FYI, I've done this lots of times. I don't even bother waking up any more :-). Note that you don't need Amanda laying around to do this. Amanda tape images can be processed with normal Unix tools (mt, dd and whatever restore program matches the dump format). The one thing you might want to be careful about is compression. Just to be safe, I would probably *never* software compress my OS file systems on the off chance I didn't have the uncompress program during such a disaster recovery. >S. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda was getting confused, but apparently no more :-)
>I wonder how hard it would be to train amanda to rotate holding >areas (partitions) on a raid instead of tapes? ... That's already part of 2.4.3 (or the amanda-242-tapeio CVS branch). >Gene John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Easy question
>I'm getting this on several of my Win2K clients: Ummm, how is it you can put "Easy question" and "Win2K" in the same letter? :-) >mordor //bali/personal$ lev 0 FAILED [missing result for //bali/personal$ >in mordor response] > >This hasn't always happened with them. ... Does it happen for a given PC some of the time but not others? Or once it starts happening with a particular host does it keep doing it? >This is Amanda 2.4.1p1 ... The first thing I'd suggest is upgrading mordor to 2.4.2p2 or later. Among other things, the logging is much better for tracking problems. Whether you do that or not, you need to catch one of the smbclient commands in action (/tmp/amanda/sendsize*debug) to see what it tried to do. Building with --with-pid-debug-files makes this much easier, although you have to clean out /tmp/amanda by hand once in a while (all of this is better in 2.4.2p2 and later). This message comes from planner when it does not get an estimate back from a client. It could just be that the client is taking a long time (that's another thing that's better with 2.4.2 -- smbclient is run with "du" instead of "dir" and is much faster), in which case cranking up etimeout in amanda.conf might help. If more than one machine has Samba installed (i.e. something other than "mordor"), you might try spreading the load by changing disklist. Note that those PC's will then look "new" to Amanda and so full dumps will be required to get started unless you mess around with the database. >Terri Eads John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Overwriting of tapes
The problem is possibly in the number of tapes that AMANDA expects to use before cycling back to the first one. If all you're ever going to use is those six tapes, then that needs to be set up correctly in your amanda.conf file. (see the comments next to the 'tapecycle' parameter.) I suspect that if you run amcheck, it is expecting a new tape, instead of one of the six already-used tapes. > -Original Message- > From: chandrasekar [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 30, 2002 12:01 PM > To: [EMAIL PROTECTED] > Subject: Reg:Overwriting of tapes > > > Hi everyone > I have a HP-DAT24*6 tape drive connected to my backup > server running > on linux. It works fine for a cycle of 6 tapes. I want to > reuse the tapes but > after one cycle I am not able to do so. The tape changer acts weirdly > skipping tapes and doing any backups. > This is my changer file. do I have to make any changes to it. > Any suggestions > regarding this. > #Changer file for chg-mtx > > >firstslot=1 1st tape slot >lastslot=6 Last tape slot >cleanslot=6 Slot with cleaner tape > # > # # Do you want to clean the drive after a certain number > of accesses? > # # NOTE - This is unreliable, since 'accesses' aren't > 'uses', and we > # #have no reliable way to count this. A single > amcheck could > # #generate as many accesses as slots you have, plus 1. > # # ALSO NOTE - many modern tape loaders handle this automatically. > # > AUTOCLEAN=0 Set to '1' or greater to enable > # > autocleancount=99 Number of access before a clean. > # > havereader=0 If you have a barcode reader, set to 1. > # > offlinestatus=1 Set to 0 if 'mt status' gives an > # "offline" when drive is offline. > # Set to 1 or greater if 'mt status' > # doesn't give and offline, rather an > # "ONLINE" when drive is online. > # > OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a > # 'mt offline' before mtx unload? > ### > > _ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com >
Re: Reg:Overwriting of tapes
>... It works fine for a cycle of 6 tapes. I want to reuse the tapes but >after one cycle I am not able to do so. The tape changer acts weirdly >skipping tapes and doing any backups. >... > firstslot=1 1st tape slot > lastslot=6 Last tape slot > cleanslot=6 Slot with cleaner tape Ummm, what's in slot 6 of your changer? Is it a real tape or a cleaning tape? If it's a real tape, you should not set cleanslot to 6. You should set cleanslot to the tape slot that has a cleaning tape. If you don't have a cleaning tape, set it to something outside the first .. last bounds (e.g. "cleanslot=99"). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: su - amanda -c "/usr/local/libexec/amandad"
On Wed, 30 Jan 2002 at 12:07pm, Steve wrote > On Wednesday 30 January 2002 09:05 am, you wrote: > > On Wed, 30 Jan 2002 at 8:49am, Steve wrote > > > > > Hi, > > > > > > I had backup working on both the host and the guest. > > > Then I got an email saying: > > > > > > FAILURE AND STRANGE DUMP SUMMARY: > > >pc16 hda6 lev 0 FAILED [Request to vg16 timed out.] > > >pc21 hda6 lev 0 FAILED [Request to vg21 timed out.] > > > > So you're saying that it *was* working, and now it isn't. And, let me > > guess, you didn't touch anything, right? ;) > > Never said that.. It's not been a perfect working setup yet. I did discover > that I have made amanda run as root, so I changed that to amanda today. I gathered from "I had backup working" that amanda was working, then stopped. I see now that isn't the case. > > The question is what's in the amandad*debug (it if exists) from the time > > at which the backup failed (find it via the timestamps). Do these hosts > > still pass amcheck? > > No it doesn't. > log.20020130.0 says that the planner failed on the two due to timeout. > Well, that's dandy. I know to only change one thing at a time but I don't > recall having changed anything. Scary. What is the exact output of amcheck (run from the AMANDA server)? When you run amcheck, do any files get created in /tmp/amanda on the clients? What are they, and what are their contents? If no files are created, are there any messages in /var/log/messages on the clients? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amcheck ...again (but on a different machine)
I'm not as slow as my questions indicate Scenario: Starting up the production tape server have installed 2.4.2. Disklist has partitions on the tape server only (initial population). Ran amcheck and it fails saying that the host is down. The client and the tape server are one in the same. 1. ) netstat -a shows that the port is being listened 2.) parameters in /etc/inetd.conf and /etc/services are the settings that patch-system appends (index, tape, and amanda daemon) 3. ) ls -lu shows that the access time on the amandad doesn't change since install time (which means that the daemons aren't talkin' to each other) 4.) debug is created in the tmp space and indicates that it was local and an attempt was made (see pasted) amcheck: debug 1 pid 16456 ruid 9732 euid 0 start time Wed Jan 30 14:55:13 2002 amcheck: dgram_bind: socket bound to 0.0.0.0.1001 amcheck: pid 16456 finish time Wed Jan 30 14:55:43 2002 I would understand if it was a external box, but this is the same box. Any ideas Don Potter
Re: amcheck ...again (but on a different machine)
On Wed, 30 Jan 2002 at 3:05pm, Don Potter wrote > I'm not as slow as my questions indicate Amanda is a rather nice system that can take a fair bit of elbow grease to get going. It also tweaks all sorts of things in the underlying OS setup and can often indicate problems there. In short, don't sweat it. > Scenario: > Starting up the production tape server have installed 2.4.2. Disklist > has partitions on the tape server only (initial population). Ran > amcheck and it fails saying that the host is down. The client > and the tape server are one in the same. > > 1. ) netstat -a shows that the port is being listened > 2.) parameters in /etc/inetd.conf and /etc/services are the settings > that patch-system appends (index, tape, and amanda daemon) > 3. ) ls -lu shows that the access time on the amandad doesn't change > since install time (which means that the daemons aren't talkin' to each > other) > 4.) debug is created in the tmp space and indicates that it was local > and an attempt was made (see pasted) > > amcheck: debug 1 pid 16456 ruid 9732 euid 0 start time Wed Jan 30 > 14:55:13 2002 > amcheck: dgram_bind: socket bound to 0.0.0.0.1001 > amcheck: pid 16456 finish time Wed Jan 30 14:55:43 2002 amcheck*debug is from the amcheck process, i.e. its a server side program. What you really need to check for is the client side stuff. Is an amandad*debug file is getting created when you run amcheck. If so, what are its conents? Any messages in the system logs? > I would understand if it was a external box, but this is the same box. Amanda treats all clients the same, so it really doesn't matter that the client is the server (or vice versa). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amcheck ...again (but on a different machine)
That's a relief...I was feeling rather inadequate I digress. No amandad debug file (since the access time hasn't changed that would be expectedright???) and nothing in /var/adm/messages as well I was concerened with the issue of access problems (from a previoous thread) and tried running amandad as root...same outcome.. I can invoke the amandad by hand it timesout after 30 seconds (as expected) and it creates the debug file with the expected contents of a happy daemon. Joshua Baker-LePain wrote: >On Wed, 30 Jan 2002 at 3:05pm, Don Potter wrote > >>I'm not as slow as my questions indicate >> > >Amanda is a rather nice system that can take a fair bit of elbow grease to >get going. It also tweaks all sorts of things in the underlying OS setup >and can often indicate problems there. In short, don't sweat it. > >>Scenario: >>Starting up the production tape server have installed 2.4.2. Disklist >>has partitions on the tape server only (initial population). Ran >>amcheck and it fails saying that the host is down. The client >>and the tape server are one in the same. >> >>1. ) netstat -a shows that the port is being listened >>2.) parameters in /etc/inetd.conf and /etc/services are the settings >>that patch-system appends (index, tape, and amanda daemon) >>3. ) ls -lu shows that the access time on the amandad doesn't change >>since install time (which means that the daemons aren't talkin' to each >>other) >>4.) debug is created in the tmp space and indicates that it was local >> and an attempt was made (see pasted) >> >>amcheck: debug 1 pid 16456 ruid 9732 euid 0 start time Wed Jan 30 >>14:55:13 2002 >>amcheck: dgram_bind: socket bound to 0.0.0.0.1001 >>amcheck: pid 16456 finish time Wed Jan 30 14:55:43 2002 >> > >amcheck*debug is from the amcheck process, i.e. its a server side program. >What you really need to check for is the client side stuff. Is an >amandad*debug file is getting created when you run amcheck. If so, what >are its conents? Any messages in the system logs? > >>I would understand if it was a external box, but this is the same box. >> > >Amanda treats all clients the same, so it really doesn't matter that the >client is the server (or vice versa). >
Re: amcheck ...again (but on a different machine)
>I'm not as slow as my questions indicate :-) :-) The things you're running into are among the most common initial problems. Don't despair. Since they are so common, they are even documented in the FAQ :-). Have you read and tried all the steps documented here: http://amanda.sourceforge.net/fom-serve/cache/16.html http://amanda.sourceforge.net/fom-serve/cache/140.html In addition to the above, have you tried all the tricks we talked about yesterday (the shell script and truss)? >I would understand if it was a external box, but this is the same box. There is no difference as far as Amanda is concerned. It still makes a network connection (even though it's through the local host interface). In particular this means inetd has to be set up right, which is the most common source of trouble. >Don Potter John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Easy question
Thanks for the quick response John. I used that title to get attention, did it work? :-) This has been a real pain to get working, seems like it was fine with 98 and NT, but 2000 has thrown a wrench in the works. To answer some of your questions: It doesn't happen on all W2K hosts, but when it starts it keeps doing it. I swapped some W2K hosts from a different config and neither worked on each others configs, where the ones on the other config *were* working. I am waiting to upgrade when my new server arrives, so maybe the problem will not follow. I will also try your suggestion about catching the processes in the act, that could prove interesting. I will also up the timeout to see what effect that has. Thanks for the advice! Terri John R. Jackson wrote: > > >I'm getting this on several of my Win2K clients: > > Ummm, how is it you can put "Easy question" and "Win2K" in the same > letter? :-) > > >mordor //bali/personal$ lev 0 FAILED [missing result for //bali/personal$ > >in mordor response] > > > >This hasn't always happened with them. ... > > Does it happen for a given PC some of the time but not others? Or once > it starts happening with a particular host does it keep doing it? > > >This is Amanda 2.4.1p1 ... > > The first thing I'd suggest is upgrading mordor to 2.4.2p2 or later. > Among other things, the logging is much better for tracking problems. > > Whether you do that or not, you need to catch one of the smbclient > commands in action (/tmp/amanda/sendsize*debug) to see what it tried > to do. Building with --with-pid-debug-files makes this much easier, > although you have to clean out /tmp/amanda by hand once in a while > (all of this is better in 2.4.2p2 and later). > > This message comes from planner when it does not get an estimate back > from a client. It could just be that the client is taking a long time > (that's another thing that's better with 2.4.2 -- smbclient is run with > "du" instead of "dir" and is much faster), in which case cranking up > etimeout in amanda.conf might help. > > If more than one machine has Samba installed (i.e. something other > than "mordor"), you might try spreading the load by changing disklist. > Note that those PC's will then look "new" to Amanda and so full dumps > will be required to get started unless you mess around with the database. > > >Terri Eads > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Paralellism possible for offsite storage?
Even though the Amanda docs' recommendation for off-site storage is a separate config (always full, no record), I'm trying to minimize the client load and bandwidth while making a separate set of tapes for off-site storage. Is there a way to do either of the following: Write the same data to two drives simultaneously? Filling the tape might be an issue, but I guess if you hit EOM on either drive you could restart the current image on both. Leaving level 0s on the holding disk after a write so that something like amflush could make another tape of it? Some of my backups are across a WAN and take several hours, dragging the data across twice seems like a gross inefficiency. I could just make direct copies of the tapes, but two separate writes has better odds of having at least one good one. Thanks, Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
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: Simultaneous Multi-Tape Multi-Host Backups
Okay, so if I go with the 4-Client-4-FileSys and 1-Host-4-TapeDrive situation. Can Amanda backup the 4 filesystems to the 4 tape-drives simultaneously from one config file? From what I've configured so far (with the chg-multi.conf), it can only treat drives as a disk-changer writing to them serially (even though they are 4 separate drives that could be written to simultaniously). "Brandon D. Valentine" wrote: > > On Tue, 29 Jan 2002, Aaron Rainwater - TXDC SysAdmin wrote: > > >Has anyone out there configured Amanda to make backups > >to multiple hosts and tape-drives simultaneously without > >having to create copious amounts of config files. > > > >The full realization of this concept would be to be able > >to backup data from, say, 4 filesystems on 4 machines > >to 4 tape-drives on 4 machines, simultaneously. > > Well, here's a theory. I have no idea if this would work, so YMMV. > > Setup Amanda in the usual fashion, i.e. choose a machine to run the > Amanda server and install the client on all 4 machines. Configure the > Amanda server with 4 seperate configs, one for each machine you want to > backup. In each config find a way to make amanda use the remote tape > drives via rmt (I don't know if this is possible, I'm sure one of the > Amanda hackers could answer it). That might work. > > I however strongly question your motivations for wanting to setup > something like this. I assume you want to do it because you already own > 4 tape drives and want to make use of all of them? Here's a better > suggestion: > > Find an obsolete machine you can devote to running Amanda and move all 4 > tape drives into it. I have seen a 486 DX/2 66 w/ an Adaptec 1542 ISA > SCSI card in it do DAE across 6 SCSI CDROM drives and not saturate the > bus. You'll have no problem using an old 486 or Pentium class machine > with any supported SCSI or IDE (depending on what kind of drives you > have) controller card. 4 tape drives definitely won't stream fast > enough to saturate the bus. I'd use something like NetBSD to keep the > machine lean. Obviously the slower your tape server the more inclined > you should be to use client compression, but the devil's in the details. > You might even be able to write a changer script that would allow you to > treat all 4 drives like a 4-tape changer and use just one amanda config. > You'd be able to go a whole week without going into your closet to > change a tape. I actually have considered doing this at the house with > a stack of old Travan drives I have, for my personal backups. Load them > up at the beginning of the week and forget about them. > > -- > Brandon D. Valentine <[EMAIL PROTECTED]> > Computer Geek, Center for Structural Biology > > "This isn't rocket science -- but it _is_ computer science." > - Terry Lambert on [EMAIL PROTECTED] -- Aaron Rainwater TXDC System Administrator Fantastico ;>
Suggestion for next amanda: put tcpportrange in amadminversion output
One of the things which was disquieting to me while trying to troubleshoot my problems with TCP and UDP ports was the inability to check what options I had compiled with using "amadmin version". I've pasted in the results of my system at the end of this message. It seemed like many other compile time definitions were listed in the "defs" section. I initially doubted whether I had compiled it right, because "--with-udpportrange=932,948" and "--with-tcpportrange=10080,10100" didn't appear. I believe that this section is output in some of the routine logging files, also. Just my suggestion. Wasn't sure if I could or should submit this to the amanda-dev list, since I don't subscribe to it. -Kevin Zembower amanda@admin:~ > amadmin DailySet1 version build: VERSION="Amanda-2.4.3b1" BUILT_DATE="Fri Jan 4 11:18:53 EST 2002" BUILT_MACH="Linux admin 2.4.4-64GB-SMP #1 SMP Fri May 18 14:54:08 GMT 2001 i686 unknown" CC="gcc" paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" libexecdir="/usr/local/libexec" mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/" DUMP="/sbin/dump" RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip" UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" listed_incr_dir="/usr/local/var/amanda/gnutar-lists" defs: DEFAULT_SERVER="admin" DEFAULT_CONFIG="DailySet1" DEFAULT_TAPE_SERVER="admin" DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amanda@admin:~ > - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Simultaneous Multi-Tape Multi-Host Backups
>... Can Amanda backup the 4 filesystems to the 4 tape-drives >simultaneously from one config file? ... No. That will take a major overhaul (although it's definitely needed). >Aaron Rainwater John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Error building changer-src
>I am getting the following error when building Amanda 2.4.1p1 ... Help with such an old release is going to be difficult, however ... >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. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Simultaneous Multi-Tape Multi-Host Backups
On Wed, 30 Jan 2002, Aaron Rainwater - TXDC SysAdmin wrote: >Okay, so if I go with the 4-Client-4-FileSys and 1-Host-4-TapeDrive >situation. Can Amanda backup the 4 filesystems to the 4 tape-drives >simultaneously from one config file? From what I've configured so >far (with the chg-multi.conf), it can only treat drives as a >disk-changer writing to them serially (even though they are 4 >separate drives that could be written to simultaniously). I don't believe it can do it simulataneously, no. It can do it serially, yes. One possible way to get it going in parallel is to define 4 seperate config files, one for each client. Then if your cron job runs 4 copies of amdump, each with a different config specified, it should run in parallel. Each config just has a disklist which knows about the disks on its assigned machine. This might even have nice administrative side effects, making it easier to keep each machine on a specific set of tapes and being able to modify the configs on a per machine basis. Let the list know if you get it setup and running. I think we'd be interested to hear your success story. -- Brandon D. Valentine <[EMAIL PROTECTED]> Computer Geek, Center for Structural Biology "This isn't rocket science -- but it _is_ computer science." - Terry Lambert on [EMAIL PROTECTED]
Re: Paralellism possible for offsite storage?
>Write the same data to two drives simultaneously? ... It wasn't the intent :-), but you can do this with amanda-2.4.3 (now in beta) or amanda-242-tapeio (from CVS) by using the "rait" output driver and defining two drives. The "first" drive will contain the real data and the "last" (second) drive contains the checksum (exclusive or). But since there is only one drive, the checksum is identical to the data. I think. You should test it. >Filling the tape might be >an issue, but I guess if you hit EOM on either drive you could restart the >current image on both. That's what will happen with the above code. >Leaving level 0s on the holding disk after a write so that something like >amflush could make another tape of it? I re-posted some changes recently that hook the unlinking of images from the holding disk. It was meant to do all images, but could be changed to do only level 0's. >Some of my backups are across a WAN and take several hours, dragging the data >across twice seems like a gross inefficiency. ... If you have enough holding disk space, you could set "reserve" to allow full dumps and set tapedev to "/no/such/device" to force amdump to run but leave everything in the holding disk. Then some clever hard linking (to prevent removal) and multiple amflush runs should be able to accomplish what you want. >Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda in aix
>ok, i think a solved my problem, i set the LIBPATH variable to the gnu >library directory. I think you have some serious problems with your compiler installation, and you should probably find some help with the (e.g. from the documentation about your gcc install, or maybe an AIX or gcc FAQ someplace), but be that as it may ... >Now i have another problem, when i make the source i get the next error: > >collect2: ../common-src/libamanda.a:not a COFF file Here's what I would try: make distclean ./configure --disable-libtool ... make John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
upgrading from amanda-2.4.1p1
I'm going to upgrade my Amanda installation from 2.4.1p1 to 2.4.3b2 in the next couple days. Will I be able to use my old config files, or will they all need to be rewritten? Are there any other gotchas I should be aware of? --david -- David Hayes - [EMAIL PROTECTED] Black Diamond Equipment - 2084 East 3900 South, SLC, UT, USA 84124 phone: 801-365-5520 fax: 801-278-5544
Re: Suggestion for next amanda: put tcpportrange in amadmin version output
KEVIN ZEMBOWER ([EMAIL PROTECTED]): > One of the things which was disquieting to me while trying to > troubleshoot my problems with TCP and UDP ports was the inability to > check what options I had compiled with using "amadmin version". > I've pasted in the results of my system at the end of this message. It > seemed like many other compile time definitions were listed in the > "defs" section. I initially doubted whether I had compiled it right, > because "--with-udpportrange=932,948" and > "--with-tcpportrange=10080,10100" didn't appear. I believe that this > section is output in some of the routine logging files, also. > Just my suggestion. Wasn't sure if I could or should submit this to the > amanda-dev list, since I don't subscribe to it. > -Kevin Zembower > amanda@admin:~ > amadmin DailySet1 version > build: VERSION="Amanda-2.4.3b1" >BUILT_DATE="Fri Jan 4 11:18:53 EST 2002" >BUILT_MACH="Linux admin 2.4.4-64GB-SMP #1 SMP Fri May 18 > 14:54:08 GMT 2001 i686 unknown" >CC="gcc" > paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" >libexecdir="/usr/local/libexec" mandir="/usr/local/man" >AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" >CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" >RDEV_PREFIX="/dev/" DUMP="/sbin/dump" >RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" >GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip" >UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" >listed_incr_dir="/usr/local/var/amanda/gnutar-lists" > defs: DEFAULT_SERVER="admin" DEFAULT_CONFIG="DailySet1" >DEFAULT_TAPE_SERVER="admin" >DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM >LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE >AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS >CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP >COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" >COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" How about an amadmin command like 'configure-options' that allows you to do something like this when upgrading: ./configure `amadmin configure-options` -- Jeremy Wadsack Wadsack-Allen Digital Group
Re: Amanda won't dump one particular partition
>> /sbin/dump 0sf 1048576 - /dev/sda5 | /bin/gzip -dc | cat > /dev/null > >That command fails with > >gzip: stdin: not in gzip format Sorry. You're right that the 'd' should not have been there. >... At least I can run backups with compression once again. So, where are you at? Do you still have a problem or not? If you do, I think the next thing I'd try (and it's icky) is put the appended script (after you test it -- I did some but not enough) someplace. Then rebuild, but set the GZIP environment variable before running ./configure so Amanda uses the script: make distclean GZIP=/path/to/the/test/script ./configure ... # Make sure ./configure found the "right" gzip make su -c "make install" Then after a failed run, see if any of the /tmp/gzip.log.* files show anything interesting. > [EMAIL PROTECTED] John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] #!/bin/bash exec 8>&2 2> /tmp/gzip.test.$$ # dup 2 -> 8 and re-open 2 echo === $(/bin/date): start $$: $0 "$@" >> /tmp/gzip.log.$$ ps -fp $$,$PPID >> /tmp/gzip.log.$$ /bin/gzip "$@" status=$? cat /tmp/gzip.test.$$ >> /tmp/gzip.log.$$ cat /tmp/gzip.test.$$ 1>&8 echo === $(/bin/date): done: status = $status >> /tmp/gzip.log.$$ exit $status
Re: Dump disk size and backup failure
Wayne Richards wrote:
>
> We have been experiencing a lot of failures on full backup with a large dump
> disk.
>
> Our dump disk devices are:
>
> /dev/dsk/c0t13d0s0 83143932708 8145398 1%/usr13
> /dev/dsk/c2t1d0s317413250 10 17239108 1%/usr14
>
> The holdingdisk definitions are:
>
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/usr13/amanda_holding_disk" # where the holding disk is
> use -2500 mb# how much space can we use on it
> chunksize 0 mb
> }
>
> holdingdisk hd2 {
> comment "main holding disk"
> directory "/usr14/amanda_holding_disk" # where the holding disk is
> use -2500 mb# how much space can we use on it
> chunksize 0 mb
> }
>
> All backups work fine using hd1, but when using hd2, the disk fills; backups
> go into degraded mode and several fail. Is there some limit on the size of
> holding disk that amanda can manage?
Not that I've encountered. I'm using a 75Gb drive as my holding disk.
Backing up 50Gb a night to AIT-II tape from about 200Gb across 80 disks.
Try setting chunksize to 2000Mb (not 2Gb) and see if that fixes things.
--
[EMAIL PROTECTED] - HMC UNIX Systems Manager
My opinions are my own and probably don't represent anything anyway.
Re: upgrading from amanda-2.4.1p1
>I'm going to upgrade my Amanda installation from 2.4.1p1 to 2.4.3b2 in >the next couple days. Will I be able to use my old config files, or >will they all need to be rewritten? ... They should work pretty much as written. As far as I know, everything is upward compatible. The first thing I'd do after the upgrade is something like: amadmin tape The output is not what's interesting. The interesting thing is if it throws any errors, since it fully parses your config files. >Are there any other gotchas I should be aware of? You do understand the 'b' in the name means "Beta", right? As in, we're still coding (and documenting), and if you run into trouble, we sort of expect you to be able to do some debugging. If you want a more stable release, I'd recommend 2.4.2p2. >--david John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: upgrading from amanda-2.4.1p1
On Wed, 30 Jan 2002, John R. Jackson wrote: >They should work pretty much as written. As far as I know, everything >is upward compatible. > >The first thing I'd do after the upgrade is something like: > > amadmin tape > >The output is not what's interesting. The interesting thing is if it >throws any errors, since it fully parses your config files. Thanks. This is good to know. >You do understand the 'b' in the name means "Beta", right? As in, >we're still coding (and documenting), and if you run into trouble, >we sort of expect you to be able to do some debugging. > >If you want a more stable release, I'd recommend 2.4.2p2. Oops- that was a typo on my part. I'd downloaded both, but planned to stick with the stable version. --david
Re: Suggestion for next amanda: put tcpportrange in amadmin version output
>How about an amadmin command like 'configure-options' that allows you >to do something like this when upgrading: > > ./configure `amadmin configure-options` That would be almost impossible. Amanda does not have that much control over ./configure. You would need to know all the args that went in to ./configure so they could be saved away, but that would require changes to autoconf (not Amanda). An alternative is to create a file named config.local. If that exists, it is sourced into ./configure (that's standard autoconf behavior). So you can do things like this: with_user=amanda with_group=amanda with_tcpportrange=2000,2040 Just keep this file around and you'll know what you used the last time. >Jeremy Wadsack John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: "No working file locking" and ruserok compile error
> >Take a look at config.log and see why the test programs are failing. >It might even be the ruserok() problem. > >>B) When I compile on OSF/1 v5.1 (or DEC ALPHA, or Tru64), I get an >> error about ruserok being declared twice... >> I am using a gnu make 3.79 and gcc 3.0.3. >> Can I comment out the ruserok declaration in amanda.h with no >> adverse effects? > >In theory, the declaration in amanda.h is only enabled if ./configure >did **not** find a declaration in a certain set of system header files. >Where is the second (system) declaration on your system? This may >just be a matter of adding another header file to the list or fixing a >test program. Again, look for what happened in config.log. > I have searched the config.log file and I see no references to the string 'ruserok' with regard to the "multiply declared ruserok" issue What other information could I provide about the ruserok issue? What can I do to debug it, other than the config.log file? and... I see no reference to the flock tests or any lock tests for that matter... The only occurrence of the string 'lock' in the config.log file was inside the word 'block' Where else can I look to see why the configure script is not finding evidence of file locking on a OSF/1 v5.1 Unix system? ## Since this is a proprietary vendor supplied distribution -- unlike the GNU distribution -- readline was also missing. So, since I thought this to be an easy fix, I built and installed readline, however subsequent runs of the AMANDA configure script did not pick it up... Maybe someone can make a suggestion to make it work? Here is what I am doing to set the environment in which configure runs: CFLAGS="-I/usr/local/include" \ LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH" \ ./configure \ --prefix=/usr/local/amanda-2.4.2p2 \ --without-amandahosts \ --with-user=amanda \ --with-group=operator \ --with-configdir=/usr/local/etc/amanda \ --with-tmpdir=/tmp/amanda \ --with-debugging\ --with-debug-days=1 \ previous to the above invocation: CFLAGS was undefined LD_LIBRARY_PATH=/usr/local/gcc-3.0.3/lib The readline hdr files and lib were/are here: /usr/local/include/readline/*.h /usr/local/lib/libreadline.a Thanks to all in this wonderful community May all your backups be bit-perfect.
Re: Suggestion for next amanda: put tcpportrange in amadmin version output
John R. Jackson ([EMAIL PROTECTED]): >>How about an amadmin command like 'configure-options' that allows you >>to do something like this when upgrading: >> >> ./configure `amadmin configure-options` > That would be almost impossible. Amanda does not have that much control > over ./configure. You would need to know all the args that went in to > ./configure so they could be saved away, but that would require changes > to autoconf (not Amanda). Well, each args that went into ./configure has some effect on the code. So the code that it affects can add the appropriate arg to a common string. I honestly know nothing about autoconf, but I do know that the PHP installation does this. Look at any page with phpinfo() on it and right at the top is the configure string. It's *very* helpful when upgrading a server. > An alternative is to create a file named config.local. If that exists, > it is sourced into ./configure (that's standard autoconf behavior). > So you can do things like this: > with_user=amanda > with_group=amanda > with_tcpportrange=2000,2040 > Just keep this file around and you'll know what you used the last time. Right, but that's an extra step in the install process. Maybe 'make install' should but config.local somewhere helpful (like /var/amanda?) and the docs can mention this technique for upgrading. But it's still not as clean as the previous suggestion. I'm just thinking usability here. Computers are capable of being smart so they should be. :-) -- Jeremy Wadsack Wadsack-Allen Digital Group
Re: amanda was getting confused, but apparently no more :-)
On Wednesday 30 January 2002 01:27 pm, John R. Jackson wrote: >>I wonder how hard it would be to train amanda to rotate holding >>areas (partitions) on a raid instead of tapes? ... > >That's already part of 2.4.3 (or the amanda-242-tapeio CVS branch). Humm, might be a good thing to know. How-to Docs location? Back on the trail of this miss-behaving drive, I was right, in an afternoons worth of messing with this thing, both by hand where it works nominally with dd, mt and mtx, and mt reports no softerrors ever, but let this same amanda-2.4.3b2-20020129 or one of the earlier ones too have a whack at it and it spends half the day running to the cleaning tape in slot 4! Useage count just for today is about 52 since it will normally increment it by 4 for each full run of amcheck or similar scanning the slots util. Immediately after amanda has errored out, an mt -f /dev/nst0 status will return a BOT ONLINE IM_REP_EN with a 4101 status, and if BOT isn't valid, its 8101. Two things enter into this that might be contributors to the problem, first being the revision number of this particular Python 28849-XXX drive, which is 4.CM according to dmesg. The second is that originally the dc dipswitch was on when I labeled the tapes, and I've been fighting with that ever since. I did succeed in getting a title header written to one out of 6 tapes that doesn't turn the compression led back on when a "mt -f /dev/nst0 rewind && dd if=dev/nst0" is done. BTW, I can do that without error 50 times in a row, and even wrote one nearly 20 meg file with tar and recovered it, again using tar. dd also works if the file is some even multiple of 512 bytes long. If amanda wasn't so concerned with the cleaning tape, I think I'd have a working system, but when amanda sends it to slot 4 and then seems to forget it has to reload the correct 'next' slot when doing a show or such, so it says theres an io error for every slot, usually accompanied by a 'while rewinding' when there isn't even a loaded tape! I haven't tried taking the cleaning tape out of the configuration yet. This same code, compiled on my machine at home, using the same model of drive but possibly a newer rev version, runs quite nicely now. Cheers John & Thomas, Gene
Re: "No working file locking" and ruserok compile error
>I have searched the config.log file and I see no references to the
>string 'ruserok' with regard to the "multiply declared ruserok"
>issue...
That doesn't make any sense. Here's what I see:
configure:14463: checking for ruserok
configure:14491: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
1>&5
configure:14517: checking for ruserok declaration in netdb.h sys/socket.h libc.h
and so on. In other words, every place ./configure does a test
there should be the same thing in the log along with the actual test
and results. Here's a failure, for instance (Solaris does not have
setmntent):
configure:15096: checking for setmntent
configure:15124: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
1>&5
Undefined first referenced
symbol in file
setmntent /var/tmp/cccfHbIc.o
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 15101 "configure"
#include "confdefs.h"
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char setmntent(); below. */
#include
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char setmntent();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_setmntent) || defined (__stub___setmntent)
choke me
#else
setmntent();
#endif
; return 0; }
You have to do a "make distclean" first or else the stuff will come from
the cache and you won't see the test results.
>I see no reference to the flock tests or any lock tests for that
>matter... The only occurrence of the string 'lock' in the config.log
>file was inside the word 'block'
Again, this make no sense. Here's the very end of my log:
configure:19342: checking whether posix fcntl locking works
configure:19362: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include-L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
1>&5
In file included from configure:19358:
/home/fortress/a/jrj/work/amanda/amanda-242/common-src/amflock.c:412: warning:
return-type defaults to `int'
If you're not seeing output like this (and you've done a distclean),
I'm not sure what's going on.
>CFLAGS="-I/usr/local/include" \
>LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH" \
>./configure \
>...
Setting LD_LIBRARY_PATH should be a last resort. I think you should be
able to accomplish the same thing setting LIBS, e.g.:
CFLAGS="-I/usr/local/include" \
LIBS="-L/usr/local/lib" \
./configure \
...
Then you need to look at the configure output to see what it says about
finding readline, e.g. from my system:
checking for readline.h... no
checking for readline/history.h... yes
checking for readline/readline.h... yes
checking for readline in -lreadline... yes
If that doesn't work, you're back to looking at config.log to find out
why the test programs failed.
>--with-debug-days=1
Any particular reason you're lowering this value? I'd think you'd want
at least a weekend worth of logs left around.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Suggestion for next amanda: put tcpportrange in amadmin version output
>Well, each args that went into ./configure has some effect on the >code. So the code that it affects can add the appropriate arg to a >common string. That's hundreds of entries and a maintenance nightmare. No thanks :-). >I honestly know nothing about autoconf, but I do know that the PHP >installation does this. ... OK, I see what they've done and will try to get something similar into Amanda. >... Computers are capable of being smart so they should be. :-) Computers are not capable of being smart, just fast. The programmers who work on them are the only ones with any intelligence. In other words, "neat" things like this take effort, sometimes magnitudes more than you might think just from the basic idea. That's not a gripe or anything. I've certainly made my fair share of "little suggestions" to others, even to myself :-). >Jeremy Wadsack John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: [Amanda-users] Re: Suggestion for next amanda: put tcpportrange in amadmin version output
On Wed, Jan 30, 2002 at 03:37:58PM -0700, Jeremy Wadsack wrote:
>
> KEVIN ZEMBOWER ([EMAIL PROTECTED]):
>
> > One of the things which was disquieting to me while trying to
> > troubleshoot my problems with TCP and UDP ports was the inability to
> > check what options I had compiled with using "amadmin version".
> > I've pasted in the results of my system at the end of this message. It
> > seemed like many other compile time definitions were listed in the
> > "defs" section. I initially doubted whether I had compiled it right,
> > because "--with-udpportrange=932,948" and
> > "--with-tcpportrange=10080,10100" didn't appear. I believe that this
> > section is output in some of the routine logging files, also.
>
> > Just my suggestion. Wasn't sure if I could or should submit this to the
> > amanda-dev list, since I don't subscribe to it.
>
> > -Kevin Zembower
>
> > amanda@admin:~ > amadmin DailySet1 version
> > build: VERSION="Amanda-2.4.3b1"
> >BUILT_DATE="Fri Jan 4 11:18:53 EST 2002"
> >BUILT_MACH="Linux admin 2.4.4-64GB-SMP #1 SMP Fri May 18
> > 14:54:08 GMT 2001 i686 unknown"
> >CC="gcc"
> > paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
> >libexecdir="/usr/local/libexec" mandir="/usr/local/man"
> >AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
> >CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/"
> >RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
> >RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
> >GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip"
> >UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail"
> >listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
> > defs: DEFAULT_SERVER="admin" DEFAULT_CONFIG="DailySet1"
> >DEFAULT_TAPE_SERVER="admin"
> >DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
> >LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
> >AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
> >CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
> >COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
> >COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
does this help. or is this exactly what is not nead, how far do we go? this could end
up being a big mess.
diff -u -r1.28 genversion.c
--- common-src/genversion.c 2001/03/20 00:27:18 1.28
+++ common-src/genversion.c 2002/01/31 00:10:13
@@ -116,6 +116,13 @@
const char *v;
char *verstr;
int v_len;
+#ifdef TCPPORTRANGE
+char tcp_port_range[12];
+#endif
+
+#ifdef UDPPORTRANGE
+char udp_port_range[12];
+#endif
printf("/* version.c - generated by genversion.c - DO NOT EDIT! */\n");
printf("const char * const version_info[] = {\n");
@@ -340,6 +347,16 @@
#ifdef UNCOMPRESS_OPT
prvar("UNCOMPRESS_OPT", UNCOMPRESS_OPT);
+#endif
+
+#ifdef TCPPORTRANGE
+snprintf(tcp_port_range, 12, "%d,%d", TCPPORTRANGE);
+prvar("TCPPORTRANGE", tcp_port_range);
+#endif
+
+#ifdef UDPPORTRANGE
+snprintf(udp_port_range, 12, "%d,%d", UDPPORTRANGE);
+prvar("UDPPORTRANGE", udp_port_range);
#endif
endline();
pics
http://www.humanfactors.uq.edu.au/internal/tim/ -- Sarah Hollings Ph +61 7 33656080 Information Technology Manager Fx +61 7 33656171 Key Cntr for Humanfactors & Applied Cognitive Psychology at the University of Queensland, Saint Lucia
Re: Suggestion for next amanda: put tcpportrange in amadmin version output
On Wed, Jan 30, 2002 at 03:37:58PM -0700, Jeremy Wadsack wrote: > > KEVIN ZEMBOWER ([EMAIL PROTECTED]): > > > One of the things which was disquieting to me while trying to > > troubleshoot my problems with TCP and UDP ports was the inability to > > check what options I had compiled with using "amadmin version". > > I've pasted in the results of my system at the end of this message. It > > seemed like many other compile time definitions were listed in the > > "defs" section. I initially doubted whether I had compiled it right, > > because "--with-udpportrange=932,948" and > > "--with-tcpportrange=10080,10100" didn't appear. I believe that this > > section is output in some of the routine logging files, also. > > > Just my suggestion. Wasn't sure if I could or should submit this to the > > amanda-dev list, since I don't subscribe to it. > > > -Kevin Zembower > > > amanda@admin:~ > amadmin DailySet1 version > > build: VERSION="Amanda-2.4.3b1" > >BUILT_DATE="Fri Jan 4 11:18:53 EST 2002" > >BUILT_MACH="Linux admin 2.4.4-64GB-SMP #1 SMP Fri May 18 > > 14:54:08 GMT 2001 i686 unknown" > >CC="gcc" > > paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" > >libexecdir="/usr/local/libexec" mandir="/usr/local/man" > >AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" > >CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" > >RDEV_PREFIX="/dev/" DUMP="/sbin/dump" > >RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" > >GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip" > >UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" > >listed_incr_dir="/usr/local/var/amanda/gnutar-lists" > > defs: DEFAULT_SERVER="admin" DEFAULT_CONFIG="DailySet1" > >DEFAULT_TAPE_SERVER="admin" > >DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM > >LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE > >AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS > >CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP > >COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" > >COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" > > How about an amadmin command like 'configure-options' that allows you > to do something like this when upgrading: > >./configure `amadmin configure-options` > What about config.status? This can be used to rebuild the configuration. Can it be re-used on a newer version of the package? -- Steve Feehan
apologies for previous post in error
Apologies for my previous post - my mail client automatically included amanda-users in a subject list. -- Sarah Hollings Ph +61 7 33656080 Information Technology Manager Fx +61 7 33656171 Key Cntr for Humanfactors & Applied Cognitive Psychology at the University of Queensland, Saint Lucia
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
config/build assumptions (and how to fix)
Is it a bad assumption to think that amanda's build process will "bail" if there is something that it needs which is not found by the configure/autoconf programs? Here are some samples of the more prominent complaints: [ from ALPHA running OSF1 v5.1 ] creating cache ./config.cache checking host system type... alphaev6-dec-osf5.1 checking target system type... alphaev6-dec-osf5.1 checking build system type... alphaev6-dec-osf5.1 . . checking for working aclocal... missing checking for working autoconf... missing checking for working automake... missing checking for working autoheader... missing checking for working makeinfo... missing . checking for bison... no checking for byacc... no . checking for perl5... no [Note perl 5.005 is at /usr/bin/perl... whereis finds it no problem... /usr/bin is in my path checking for yywrap in -lfl... no [Note: I have installed the GNU flex-2.5.4 thinking the yywrap would be included... The fl library file is where I expect. checking for history.h... no checking for readline.h... no checking for readline/history.h... no checking for readline/readline.h... no [Note: These are installed and accessible. Why not found ?? . . checking whether posix fcntl locking works... no checking whether flock locking works... no checking whether lockf locking works... no checking whether lnlock locking works... no configure: warning: *** No working file locking capability found! configure: warning: *** Be VERY VERY careful. # What can safely be ignored... aclocal? autoconf? automake? makeinfo? bison? byacc? yywrap? I understand the file locking is required. I just got to get the configure script to see it... ### My attempts to tell the configure program where the includes and libraries are, look like this: > cd amanda-2.4.2p2 > CFLAGS="-I/usr/local/include -I/usr/local/include/readline" \ LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH" \ ./configure \ --prefix=/usr/local/amanda-2.4.2p2 \ --without-amandahosts \ --with-user=amanda \ --with-group=operator \ --with-configdir=/usr/local/etc/amanda \ --with-tmpdir=/tmp/amanda \ --with-debugging\ --with-debug-days=4 ### Thanks everyone -J
'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
