Travan TR5, 500SC, Linux 7.1 amanda...
Yay!!! I'm reading and writing!!! Many thanks to (in no particular order): Seth Mos, Robert Wideman, Matt Domsch and Ashley from the amanda lists... I got it working by using ide-scsi, and the following lilo.conf entry: append=/dev/ht0=ide-scsi and... Then put this in /etc/rc.d/rc.local: rmmod ide-tape modprobe ide-scsi hdparm -d0 /dev/hdd mt -f /dev/st0 stoptions no-blklimits Ok... Now the reason I was having trouble getting it to automagically detect the ide-cum-scsi drive was because the ide-tape stuff was compiled into the kernel, rather than being a module. this meant that it couldn't rmmod ide-tape :o( . recompiled the kernel with ide-tape as a module, and it's all happy now. Cheers! Chris Herrmann Far Edge Technology p. 02 99553640 f. 02 99547994 m. 0403 393309 http://www.faredge.com.au
oops
and phil cooper! sorry! Chris Herrmann Far Edge Technology p. 02 99553640 f. 02 99547994 m. 0403 393309 http://www.faredge.com.au
Re: Holding disk
Before running amcleanup I checked the content of my holding disk. It contained a subfolder with the date of the normal run, but the folder was empty. There's not enough information yet to know what's going on with your setup. You need to get through a complete amdump without it aborting before we deal with the holding disk situation. The datestamp directory is normal in the sense that that's created early in the amdump run to hold the images. But my guess is something else happened to cause the run to abort, hence the empty holding disk and amcheck whining about amdump still running. Check to see if amdump is still running (ps -u amanda-user). Assuming it isn't, run amcleanup. Run amcheck and make sure it's happy. Then run amdump and if it fails, report everything it had to say. If it does not fail, look in your holding disk area again. I'm running Amanda version 2.4.2p2 Thanks for that info. At least we'll know what set of code to be looking at. Hi, I'm having the same problem here, also running Amanda 2.4.2p2. I run # su amanda -c "amdump daily", which finishes with no errors. I get an email report saying: *** A TAPE ERROR OCCURRED: [rewinding tape: Inappropriate ioctl for device]. I do a ps to make sure amdump is not running, then # su amanda -c "amcleanup daily", which gives me: amcleanup: no unprocessed logfile to clean up. Scanning /export/dumps/amanda... # I then run # su amanda -c "amcheck daily", and get: Amanda Tape Server Host Check - Holding disk /export/dumps/amanda: 4784640 KB disk space available, using 4774400 KB ERROR: /export/dumps/amanda: rewinding tape: Inappropriate ioctl for device (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/local/etc/amanda/daily/index: does not exist Server check took 30.118 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.112 seconds, 0 problems found I had set tapedev "/export/dumps/amanda" in amanda.conf with the (obviously mistaken) understanding that Amanda would just dump to that dir. Should I be setting this differently or commenting out something else in amanda.conf to prevent it from mistaking this for a tape? Any help appreciated. Thanks, Shawn
amrecover and /etc/hosts.allow
Hello All, After adding ALL: ALL to my /etc/hosts.deny file, amrecover stopped working. Before I go on, let me explain how I use amrecover; I never use it from the client, only from the server. I recover files and folders to a web directory on the amanda server and the clients pick them up thru the web or ftp. Each client has their own recovery directory on the server, and the server runs SSL to encrypt the data transfer. It's simple, and it works good in my situation. Anyway, amrecover stopped working after I added ALL: ALL to /etc/hosts.deny, even though the server's IP was included in /etc/hosts.allow. When I added ALL: 127.0.0.1 to /etc/hosts.allow everything worked fine again. Thought this might help others who have had this problem. Brad
Re: amandahostsauth failed
OK, it turned out to be the fully qualified (vs not) name in
.amandahosts.
I changed to just use the short name (which is what was used in the
amanda error message and amcheck doesn't give any errors now.
I found this in the faq-o-matic.
gene
On Mon, 2002-02-04 at 10:18, gene wrote:
On Friday, I finally succeeded in getting Amanda to complete a
successful backup run on the tape server. Today I'm trying to add a
Linux (RH 7.2) client. I can't seem to get past the 'amanadahostauth
failed' when running an amcheck.
I have a .amandahosts file on the client (lincvs):
datadev.mydomain.com amanda
datadev is the tape server (Solaris 8). I do have ipchains running on
lincvs and I have put in rules to allow ports 10080, 10082, and 10883
thru. I have also stopped ipchains completely and run the amcheck from
the tapeserver with the same results.
Both datadev (tapeserver) and lincvs (client) are runing 2.4.2p2. The
RedHat box (lincvs) is running with the amanda rpm's that came with 7.2.
lincvs is
I have run the C pgm from the O'Reilly B/U book that checks that the
services are called correctly and that is ok (on both client and
tapeserver).
I'm sure I'm overlooking something, and I'm still digging through the
faq-o-matic and any newsgroup searches, as well as looking at Chapter 4
in the O'Reilly Backup and Recovery book. Any/all help is appreciated.
The amcheck output from the tapeserver is below. I know I need to do a
amrmtape to re-use the DailySet101 tape below while I'm testing):
{datadev:amanda}$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /backup/amanda: 11432812 KB disk space available, that's
plenty
ERROR: cannot overwrite active tape DailySet101
(expecting tape DailySet102 or a new tape)
NOTE: skipping tape-writable test
NOTE: info dir /var/amanda/DailySet1/curinfo/lincvs.mydomain.com: does
not exist
Server check took 3.784 seconds
Amanda Backup Client Hosts Check
ERROR: lincvs.mydomain.com: [access as amanda not allowed from
amanda@datadev] amandahostsauth failed
Client check: 2 hosts checked in 0.098 seconds, 1 problem found
(brought to you by Amanda 2.4.2p2)
Thanks for your help!
Gene
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
GNUTAR program not available
Amanda Backup Client Hosts Check ERROR: db-test.ems.sat: [GNUTAR program not available] GNU tar exists on the client machine, I can log in as amanda, and gnu tar is in amanda's path. I can also execute gnu tar as the amanda user. Owners for tar are: -r-xr-xr-x 1 root other 901120 Feb 4 10:15 tar amanda runs as user amanda: group operator. What am I not doing correctly here? Thanks, Brian Davidson DynCorp Treasury Integration Group 11710 Plaza America Dr. Reston, VA 20190 703-261-4694 [EMAIL PROTECTED]
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
John, No and Yes. /usr/local/sbin and /usr/local/libexec are on bali:/usr/local which is of course local to bali but remote to all (other) amanda clients. Also amanda server laksha (with clients laksha and andaman) mounts /usr/local from bali. The critical programs (the ones that are owned by root:sys and have suid) are rx by group (sys). I thought that would allow read by members of the group and then suid which is really only an issue once the program is in memory on the remote system ?? Unless, IRIX, unlike Solaris, is stripping the suid bit across the NFS network mount. I mean, this works fine on the Solaris config but is a problem on IRIX. I wonder how the other managers would feel if I wanted to allow Root=read on the /usr/local nfs mounted partition (I wonder if its an option vs root=rw). Or did you mean something else ? IRIX, like unix only different. thanks, Brian Amcheck now runs correctly with only one remaining error message. ... ERROR: running as user amanda instead of root This says you have dumpuser in amanda.conf set to root, but you are trying to run amcheck as amanda. It's even in the amcheck(8) man page :-). Oddly enough I have another server (with two clients, including itself) of the same architecture and running the programs from the crossmounted disks on the server we have been talking about. ... ERROR: laksha: [host laksha: port 1145 not secure] ERROR: andaman: [host laksha: port 1145 not secure] Either amcheck is not running setuid-root or you have something between the server and clients (e.g. a firewall) that is doing port remapping. Do I understand you correctly that amcheck itself is NFS mounted on the server? If so, are the NFS export and mount options set up so root stays root across the mount and setuid programs are allowed? Brian John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: GNUTAR program not available
On Mon, 4 Feb 2002 at 10:55am, Davidson, Brian wrote Amanda Backup Client Hosts Check ERROR: db-test.ems.sat: [GNUTAR program not available] GNU tar exists on the client machine, I can log in as amanda, and gnu tar is in amanda's path. I can also execute gnu tar as the amanda user. Owners for tar are: -r-xr-xr-x 1 root other 901120 Feb 4 10:15 tar amanda runs as user amanda: group operator. What am I not doing correctly here? Was tar in the same location when you ./configured amanda on db-test? amanda stores the locations of such things at configure time. You can look at what configure found in /tmp/amanda/amandad*debug on db-test. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
How do I unsubscribe from the amanda list?
Re: How do I unsubscribe from the amanda list?
Send mail to listname[EMAIL PROTECTED] and when you want to unsubscribe, use the following line in the body: unsubscribe your-email-address
Re: Holding disk
Check to see if amdump is still running (ps -u amanda-user). Assuming it isn't, run amcleanup. Run amcheck and make sure it's happy. Then run amdump and if it fails, report everything it had to say. If it does not fail, look in your holding disk area again. Sorry if you're reciving the mail a second time, but it didn't pop up in the mail list, as far as I can see. I included the relevant log files of the run. everything worked, without the creation of the holding disk files. [root@milestone log]# ps -u operator PID TTY TIME CMD 1309 ?00:00:00 amflush 1310 ?00:00:00 taper 1311 ?00:00:00 taper 1325 ?00:00:00 chg-manual ?00:00:00 bash 2225 ?00:00:00 amcheck 2226 ?00:00:00 amcheck 2243 ?00:00:00 chg-manual [root@milestone log]# [operator@milestone amanda]$ amcheck daily Amanda Tape Server Host Check - Holding disk /big/amanda: 20220856 KB disk space available, that's plenty amcheck-server: slot 6: date 20020123 label System1-001 (exact label match) NOTE: skipping tape-writable test Tape System1-001 label ok Server check took 7.070 seconds Amanda Backup Client Hosts Check ERROR: daemon.system: [could not access /root (/root): Permission denied] Client check: 3 hosts checked in 5.113 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) [operator@milestone amanda]$ [root@milestone amanda]# ls -la /big/amanda insgesamt 12 drwx--3 operator disk 4096 Feb 4 11:00 . drwxrwxrwx9 root users4096 Jan 31 23:36 .. drwx--2 operator disk 4096 Feb 4 11:00 20020204 [root@milestone amanda]# ls -la /big/amanda/2* insgesamt 8 drwx--2 operator disk 4096 Feb 4 11:00 . drwx--3 operator disk 4096 Feb 4 11:00 .. [root@milestone amanda]# [operator@milestone log]$ amcleanup daily amcleanup: no unprocessed logfile to clean up. Scanning /big/amanda... [operator@milestone log]$ amanda.*.debug: amandad: debug 1 pid 3642 ruid 504 euid 504 start time Mon Feb 4 11:00:00 2002 amandad: version 2.4.2p2 amandad: build: VERSION=Amanda-2.4.2p2 amandad:BUILT_DATE=Fre Nov 30 18:43:15 CET 2001 amandad:BUILT_MACH=Linux milestone.system 2.4.4 #3 SMP Son Sep 23 13:29:35 CEST 2001 i686 unknown amandad:CC=gcc amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore GNUTAR=/bin/tar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=milestone.system DEFAULT_CONFIG=daily amandad:DEFAULT_TAPE_SERVER=milestone.system amandad:DEFAULT_TAPE_DEVICE=/dev/st0 HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=operator FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc got packet: Amanda 2.4 REQ HANDLE 001-D0A80708 SEQ 1012816801 SECURITY USER operator SERVICE sendsize OPTIONS maxdumps=1;hostname=milestone.system; GNUTAR /var 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /var 1 2002:2:2:4:22:14 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/adm 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/adm 1 2002:2:1:4:1:21 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/local 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/local 1 2002:2:1:4:19:52 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/src 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/src 1 2002:1:28:4:24:49 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /service 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /service 1 2002:1:31:4:1:10 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /root 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /root 2 2002:1:29:4:1:10 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /root 3 2002:2:3:21:38:24 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /home 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /home 2 2002:1:21:4:18:48 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /etc 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /etc 1 2002:1:31:4:2:40 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar
tar can't estimate
Hi everyone I've used amanda a while now using xfsdump on mostly SGI Irix machines. Recently I added a disklist entry that would use GNUtar though. But I get the following error and I'm not sure what to make of it. It seems tar is unable to accurately estimate the dump size. Here's all my outputs: From the report: ... FAILURE AND STRANGE DUMP SUMMARY: columbus.c /users lev 0 FAILED [disk /users offline on columbus.che.udel.edu?] ... From the log file: ... FAIL planner columbus.che.udel.edu /users 0 [disk /users offline on columbus.che.udel.edu?] ... From the amdump.1 file: planner: pid 60549 executable /usr/freeware/libexec/planner version 2.4.1p1 planner: build: VERSION=Amanda-2.4.1p1 planner:BUILT_DATE=Fri Mar 3 08:29:23 PST 2000 planner:BUILT_MACH=IRIX humu 6.2 01200533 IP22 planner: CC=/hosts/babylon.engr/usr/dist/new_toolroots/6.2/products/freeware/latest/ptoolroot/usr/bin/cc -nostdinc -I. -I/xlv1/freeware/2000.May/amanda/2.4.1p1-sgipl2-root/usr/freeware/include -I/xlv1/freeware/2000.May/amanda/2.4.1p1-sgipl2-root/usr/include -O3 -OPT:Olimit=0:space=ON -n32 -mips3 -nostdlib -L/xlv1/freeware/2000.May/amanda/2.4.1p1-sgipl2-root/usr/freeware/lib32 -L/xlv1/freeware/2000.May/amanda/2.4.1p1-sgipl2-root/usr/lib32 -woff 1009,1014,1048,1107,1110,1116,1164,1185,1188,1204,1230,1233 -Wl,-woff,85,-woff,84 -rpath /usr/freeware/lib32 planner: paths: bindir=/usr/freeware/bin sbindir=/usr/freeware/bin planner:libexecdir=/usr/freeware/libexec planner:mandir=/usr/freeware/man planner:CONFIG_DIR=/usr/freeware/etc/amanda planner:DEV_PREFIX=/dev/dsk/ RDEV_PREFIX=/dev/rdsk/ planner:DUMP=/sbin/dump RESTORE=/sbin/restore planner:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore planner:SAMBA_CLIENT=/usr/samba/bin/smbclient planner:GNUTAR=/usr/freeware/bin/tar planner:COMPRESS_PATH=/usr/sbin/gzip planner:UNCOMPRESS_PATH=/usr/sbin/gzip MAILER=/usr/sbin/Mail planner:listed_incr_dir=/var/amanda/gnutar-lists planner: defs: DEFAULT_SERVER=amanda-server DEFAULT_CONFIG=DailySet1 planner:DEFAULT_TAPE_SERVER=amanda-server planner:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY planner:USE_AMANDAHOSTS CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast planner:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc ... setting up estimates for columbus.che.udel.edu:/users driver: started dumper1 pid 65369 columbus.che.udel.edu:/users overdue 11720 days for level 0 setup_estimate: columbus.che.udel.edu:/users: command 0, options: last_level -1 next_level0 -11720 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) ... FAILED QUEUE: 0: columbus.che.udel.edu /users Oh yeah, and finally: /usr/freeware/bin/tar --version tar (GNU tar) 1.13 Does anyone have any ideas? Thanks! Jan Boshoff
Re: tar can't estimate
On Mon, 4 Feb 2002 at 12:13pm, Jan Boshoff wrote get the following error and I'm not sure what to make of it. It seems tar is unable to accurately estimate the dump size. Here's all my outputs: What's in /tmp/amanda/sendsize*debug on the client? Oh yeah, and finally: /usr/freeware/bin/tar --version tar (GNU tar) 1.13 Oops. That version is known not to work. Upgrade to 1.13.19 available from alpha.gnu.org (I'm not sure if there's a .dist for it on freeware or not). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
AMDUMP--newbie question
Hi fellows, finnally I've got amanda running I have made some
tests and I could see that amanda is what I was looking for, Now I
want to make amanda use a tape per day but I want it to make full
backups of my data each day I run it , How can I do this ??
Thanks in advance fo ryour answers
OK, it turned out to be the fully qualified (vs not) name in
.amandahosts.
I changed to just use the short name (which is what was used in the
amanda error message and amcheck doesn't give any errors now.
I found this in the faq-o-matic.
gene
On Mon, 2002-02-04 at 10:18, gene wrote:
On Friday, I finally succeeded in getting Amanda to complete a
successful backup run on the tape server. Today I'm trying to add a
Linux (RH 7.2) client. I can't seem to get past the 'amanadahostauth
failed' when running an amcheck.
I have a .amandahosts file on the client (lincvs):
datadev.mydomain.com amanda
datadev is the tape server (Solaris 8). I do have ipchains running on
lincvs and I have put in rules to allow ports 10080, 10082, and 10883
thru. I have also stopped ipchains completely and run the amcheck from
the tapeserver with the same results.
Both datadev (tapeserver) and lincvs (client) are runing 2.4.2p2. The
RedHat box (lincvs) is running with the amanda rpm's that came with 7.2.
lincvs is
I have run the C pgm from the O'Reilly B/U book that checks that the
services are called correctly and that is ok (on both client and
tapeserver).
I'm sure I'm overlooking something, and I'm still digging through the
faq-o-matic and any newsgroup searches, as well as looking at Chapter 4
in the O'Reilly Backup and Recovery book. Any/all help is appreciated.
The amcheck output from the tapeserver is below. I know I need to do a
amrmtape to re-use the DailySet101 tape below while I'm testing):
{datadev:amanda}$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /backup/amanda: 11432812 KB disk space available, that's
plenty
ERROR: cannot overwrite active tape DailySet101
(expecting tape DailySet102 or a new tape)
NOTE: skipping tape-writable test
NOTE: info dir /var/amanda/DailySet1/curinfo/lincvs.mydomain.com: does
not exist
Server check took 3.784 seconds
Amanda Backup Client Hosts Check
ERROR: lincvs.mydomain.com: [access as amanda not allowed from
amanda@datadev] amandahostsauth failed
Client check: 2 hosts checked in 0.098 seconds, 1 problem found
(brought to you by Amanda 2.4.2p2)
Thanks for your help!
Gene
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
--
Gene Matthews
Matthews Midrange Consulting, Inc.
(678) 923-8327
(877) 882-6291 (toll free)
http://mmc-inc.com
Alvaro A. Rosales Rojas. a.k.a. RAZA
Proud user of Pegasus Mail
Soporte Tecnico de Sistemas
Procacao S.A
3368113 ext 260
You'll never know how far you can go until you break the chains
that tie your soul
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
On Mon, 4 Feb 2002, Brian Cuttler wrote: Unless, IRIX, unlike Solaris, is stripping the suid bit across the NFS network mount. I mean, this works fine on the Solaris config but is a problem on IRIX. IRIX, like unix only different. Come on, be fair. IRIX, like _ANY_ unix will strip the suid bit if you specify that behavior, which sounds like the case here. Read fstab(4) under IRIX for information on the nosuid mount option. If you don't desire this security-enhancing behavior just remove the nosuid option from your NFS mount. -- 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]
Planner question
Is there a way to determine what planner determines as the compressed backup size of tthe various filesystems in your disklist while doing the initial estimate. I know when the completion report is sent you get the average compression rate. I was just wondering if that is compiled initially during planning and saved any a file. Is this data located in the amdump log file Thanks, Don
Re: tar can't estimate
Thanks for the help Josh I've upgraded to 1.13.19. Also, here's the output of /tmp/amanda/sendsize*debug: asking killpgrp to terminate calculating for amname '/users', dirname '/users' sendsize: getting size via gnutar for /users level 0 sendsize: running /usr/freeware/libexec/runtar --create --directory /users --listed-incremental /var/amanda/gnutar-lists/columbus.che.udel.edu_users_0.new --sparse --one-file-system --ignore-failed-read --totals --file /dev/null --exclude-from=/usr/freeware/etc/amanda/userfiles_amanda.exclude . runtar: error [must be invoked by root] . (no size line match in above gnutar output) . Thanks again!
Re: AMDUMP--newbie question
On Monday 04 February 2002 12:25, Alvaro Rosales R. wrote: Hi fellows, finnally I've got amanda running I have made some tests and I could see that amanda is what I was looking for, Now I want to make amanda use a tape per day but I want it to make full backups of my data each day I run it , How can I do this ?? Thanks in advance fo ryour answers in your amanda.conf file use these settings dumpcycle 0 runspercycle 1 tapecycle X (where X is the number of tape you have)
Obvious question
Ok, The answer to this is probably in front of my face. I am running Amanda-2.4.2p2 on Solaris 8. I back up WinNT and Win2k clients at this point, but would like to add in some RedHat clients. I set up the client on a RedHat 7.2 box, but it failed on me. How can I find out why it failed? Where do I find the debug or error log? Here is the report I got back: FAILURE AND STRANGE DUMP SUMMARY: host.locale. /export/home lev 0 FAILED [disk /export/home offline on mehrh.sac.unify.com?] host.locale. /usr lev 0 FAILED [disk /usr offline on mehrh.sac.unify.com?] Any help or pointers for this newbie would be much appreciated! Thanks, Brandon Moro Systems Administration, Unify Corporation [EMAIL PROTECTED] - From meanness first this Portsmouth Yankey rose, And still to meanness all his conduct flows.--Oppression, A poem by an American (Boston, 1765).
Re: Obvious question
On Mon, 4 Feb 2002 at 9:49am, Brandon Moro wrote The answer to this is probably in front of my face. I am running Amanda-2.4.2p2 on Solaris 8. I back up WinNT and Win2k clients at this point, but would like to add in some RedHat clients. I set up the client on a RedHat 7.2 box, but it failed on me. How can I find out why it failed? Where do I find the debug or error log? Debug files are in /tmp/amanda on the client -- you want to look at selfcheck*debug. Also, there's Faq-O-Matic, available through the amanda home page. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Planner question
On Mon, 4 Feb 2002 at 12:37pm, Don Potter wrote Is there a way to determine what planner determines as the compressed backup size of tthe various filesystems in your disklist while doing the initial estimate. I know when the completion report is sent you get the average compression rate. I was just wondering if that is compiled initially during planning and saved any a file. A history of compression ratios is saved in $logdir/curinfo/$HOST/$DISK. I think amanda assumes .5 to start, but I'm not sure. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: tar can't estimate
On Mon, 4 Feb 2002 at 12:42pm, Jan Boshoff wrote Also, here's the output of /tmp/amanda/sendsize*debug: asking killpgrp to terminate calculating for amname '/users', dirname '/users' sendsize: getting size via gnutar for /users level 0 sendsize: running /usr/freeware/libexec/runtar --create --directory /users --listed-incremental /var/amanda/gnutar-lists/columbus.che.udel.edu_users_0.new --sparse --one-file-system --ignore-failed-read --totals --file /dev/null --exclude-from=/usr/freeware/etc/amanda/userfiles_amanda.exclude . runtar: error [must be invoked by root] ^^^ There's the problem. Is the suid bit set on /usr/freeware/libexec/runtar? Hey, wait a minute... Err, you installed this from freeware, didn't you -- fess up! Amanda sets a lot of stuff at compile time -- compiling and installing from sources is *highly* recommended. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Backups can not be restored/recovered.
Well, last nights test, using not HW compression and software compression only was interesting. amverify failed miserably again on all the tape files, an example of the output. GDZN07 (agree-10._usr_local.20020204.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring agree-10._usr_local.20020204.1 gzip: stdin: invalid compressed data--format violated Error 32 (Broken pipe) offset 4390912+32768, wrote 0 amrestore: pipe reader has quit in middle of file. amrestore: skipping ahead to start of next file, please wait... /bin/gtar: Skipping to next header /bin/gtar: Error exit delayed from previous errors 64+0 records in 64+0 records out I don't understand this, I got the opposite result to what I expected. I had assummed that software compression would be OK and hardware wouldn't. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Glen and Rosanne Eustace, GodZone Internet Services, a division of AGRE Enterprises Ltd., P.O. Box 8020, Palmerston North, New Zealand 5301 Ph/Fax: +64 6 357 8168, Mob: +64 21 424 015
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
Brandon, Sorry - lack of sub-text in email. I wasn't really meaning to rag on IRIX, I've spent my whole tenure here working on it. I was contrasting it with Solaris because Solaris is doing what I want it to do and IRIX isn't. The truth is that one of the great joys of working on unix is that I can say this OS is like unix but different because its true of all of them. My fallback is to compare it (unix) to VMS... What I have is an amcheck error when running from amanda account. I _do not_ have the nosuid option set in /etc/fstab. Should I expect this error when running amcheck on the amanda server which also have /usr/local as a local XFS partition ? Does it make sense to see this error when the clients are mounting /usr/local via NFS from the server ? I'd expect different types of errors there, such as xfsdump failures. I'd thought at the least the server would run ok. This is a different issue from a second amanda server having a problem given that the second one NFS mounts /usr/local from the first on. One problem at a time though. thanks, Brian On Mon, 4 Feb 2002, Brian Cuttler wrote: Unless, IRIX, unlike Solaris, is stripping the suid bit across the NFS network mount. I mean, this works fine on the Solaris config but is a problem on IRIX. IRIX, like unix only different. Come on, be fair. IRIX, like _ANY_ unix will strip the suid bit if you specify that behavior, which sounds like the case here. Read fstab(4) under IRIX for information on the nosuid mount option. If you don't desire this security-enhancing behavior just remove the nosuid option from your NFS mount. -- 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]
Issue compiling amanda-2.4.2p2 under Solaris 8 on a Sun E4500
I've used amanda for several years and never had and issue compiling it under anything. However, I am having problems compiling it on a Sun E4500. I looked through the old list archives and there isn't a mention of this problem. Compilation hangs on uparse.c, without an error or warning of any sort: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../client-src -I../tape-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c uparse.c It was configured like this: ./configure --prefix=/usr/local --with-amandahosts --with-group=sys --with-user=amanda --without-server uname -a on the machine reports: SunOS newzeus 5.8 Generic_108528-12 sun4u sparc SUNW,Ultra-Enterprise Any help you could provide would be great. Thanks! -- Robert D. Haskins WorldNET Internet Services mailto:[EMAIL PROTECTED] http://www.ziplink.net/~rhaskins
Re: Two configurations questions
Beautiful. I was hoping it was something simple. Now to re-read the crontab manpage. Thanks again. On Fri, Feb 01, 2002 at 09:58:01AM -0500, Joshua Baker-LePain wrote: On Fri, 1 Feb 2002 at 1:33am, Ashley wrote I'm trying two configurations: Archive to run once a week. Dumps full backups to holding disk hd1. DailySet1 runs 6 days a week. Only does level 1 increments to hd2. How can I get DailySet1 to not run on the same day as Archive? Or rather, how can I get Archive to run on the day DailySet1 skips? How do I determine which day DailySet1 would skip? Err, you tell amanda when to run amdumps, and which config to run. So just make your crontab look like this (e.g.) 0 1 * * 1-6 amdump DailySet1 0 1 * * 7 amdump Archive -- Joshua Baker-LePain Department of Biomedical Engineering Duke University -- -ashley One of these days I'm going to completely organize my life.
Re: Issue compiling amanda-2.4.2p2 under Solaris 8 on a Sun E4500
I neglected to say what version of gcc I'm running: % gcc --version 2.95.3 Robert Haskins wrote: I've used amanda for several years and never had and issue compiling it under anything. However, I am having problems compiling it on a Sun E4500. I looked through the old list archives and there isn't a mention of this problem. Compilation hangs on uparse.c, without an error or warning of any sort: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../client-src -I../tape-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c uparse.c It was configured like this: ./configure --prefix=/usr/local --with-amandahosts --with-group=sys --with-user=amanda --without-server uname -a on the machine reports: SunOS newzeus 5.8 Generic_108528-12 sun4u sparc SUNW,Ultra-Enterprise Any help you could provide would be great. Thanks! -- Robert D. Haskins WorldNET Internet Services mailto:[EMAIL PROTECTED] http://www.ziplink.net/~rhaskins
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
I've modified the /etc/exports file to export my bali:/usr/local for root (though allowing root only from specific clients). I've made no changes to /etc/fstab since we already didn't have the nosuid option on the mount for the partition. I've confirmed that I can create files on /usr/local from the nfs clients (by creating a file there). This had no effect on the problems I've seen either from the NFS server/Amanda Server BALI ERROR: running as user amanda instead of root nor the error on the NFS client/Amanda server Laksha ERROR: andaman: [host laksha: port 1182 not secure] ERROR: laksha: [host laksha: port 1182 not secure] I'm a little afraid the error is higher up in the stack, something perhaps in the amanda config or compilation though there were no errors in compilation and the make install ran smoothly as well. Doing a fresh make install this morning I found that all suid programs where installed with the suid bit set, with owner root:sys -rwsr-x---1 root sys where the configure had been done with --with-user=amanda --with-group=sys and the amanda account (local in /etc/passwd on each server and client with identical/same UID) belonging to group sys.
LTO and changers
Hello, I have a few question about tape changers LTO. I know that amanda can not split a dump across multiple tapes, so if a dump was too large to fit on the tape, will amanda write the dump to the next available tape in the changer? Does amanda support more than one tape device, and if so can it write to more then one device at a time? Has anyone had success using amanda and an LTO changer? TIA! Andrew
Re: 2.4.2p2 on Irix 6.5.x, user=amanda, group=sys
On Mon, 4 Feb 2002, Brian Cuttler wrote: Should I expect this error when running amcheck on the amanda server which also have /usr/local as a local XFS partition ? I use NFS automounted amanda clients here with no problems. I have the partition with the amanda software installed exported like this(although I have genericized this some): --- /etc/exports /export/apps@ournetgroup(rw) --- --- auto.master /mnt auto.apps -intr --- --- auto.apps apps ourhost:/export/apps --- So that the amanda binaries would be in /mnt/apps/IRIX64/bin and /mnt/apps/Linux/bin respectively (so that the third level can be filled in by `uname -s`). Obviously the amanda UID/GID needs to be consistent across all clients whether it's maintained via NIS or by hand on each system. Otherwise the permissions on the binaries won't be right. I compile the clients on the NFS server hosting the apps directory with PREFIX set to /export/apps and then su to root in order to run the 'make install'. 'make install' takes care of all of the permissions including the various suid binaries. It works great for me. The Linux and IRIX clients have no problem using their binaries. The server is also a client and works great. I don't know what to tell you about the error you're seeing other than perhaps you missed a step somewhere in there. I can only hope reading this little writeup on how I've setup my NFS clients will remind you of something you forgot. -- 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: Obvious question
It would appear that there I am not getting a `selfcheck*debug.' Here is what I have: cd /tmp/amanda ls -ltr -rw---1 amanda disk 2081 Feb 1 16:47 amandad.20020201164738.debug -rw---1 amanda disk 1624 Feb 1 16:49 sendsize.20020201164910.debug -rw---1 amanda disk 2270 Feb 1 16:49 amandad.20020201164910.debug -rw---1 amanda disk 2081 Feb 1 16:51 amandad.20020201165136.debug -rw---1 amanda disk 2081 Feb 4 13:32 amandad.20020204133212.debug -rw---1 amanda disk 1624 Feb 4 13:33 sendsize.2002020413.debug -rw---1 amanda disk 2270 Feb 4 13:33 amandad.2002020413.debug In the sendsize*debug files, I see this: sendsize: debug 1 pid 25669 ruid 1471 euid 1471 start time Mon Feb 4 13:33:33 2002 /usr/local/libexec/sendsize: version 2.4.2p2 calculating for amname '/usr', dirname '/usr' calculating for amname '/export/home', dirname '/export/home' sendsize: getting size via gnutar for /export/home level 0 sendsize: getting size via gnutar for /usr level 0 sendsize: missing exclude list file /usr/local/lib/amanda/exclude.gtar discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /export/home --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/HOST.locale.corp.com_export_home_0.new --sparse --ignore-failed-read --totals . sendsize: missing exclude list file /usr/local/lib/amanda/exclude.gtar discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /usr --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/HOST.locale.corp.com_usr_0.new --sparse --ignore-failed-read --totals . error [exec /usr/local/libexec/runtar: Permission denied] sendsize: pid 25673 finish time Mon Feb 4 13:33:33 2002 sendsize: error [exec /usr/local/libexec/runtar: Permission denied] . (no size line match in above gnutar output) . error [exec /usr/local/libexec/runtar: Permission denied] sendsize: pid 25672 finish time Mon Feb 4 13:33:33 2002 sendsize: error [exec /usr/local/libexec/runtar: Permission denied] . (no size line match in above gnutar output) . sendsize: pid 25669 finish time Mon Feb 4 13:33:33 2002 As you can see, I seem to have a permissions problem on the /usr/local/libexec/runtar executable. cd /usr/local/libexec ls -ltr runtar -rwsr-x---1 rootsys99409 Feb 1 15:07 runtar The backup user ID is `amanda', and is a member of group `sys' as well as a member of group `disk'. I note also that the /tmp/amanda directory is created: ls -ltr /tmp drwx--S---2 amandadisk4096 Feb 4 14:16 amanda and the contents thereof, as seen above, are all created with owner `amanda' and group `disk'. So, it looks to me like `amanda' should have the permissions needed to execute runtar. And upon trying it, I see that, as user `amanda', I can run: /usr/local/libexec/runtar --version tar (GNU tar) 1.13.19 Copyright 20001 Free Software Foundtion, INC... blah blah blah Looking at the amandad*debug files seems to confirm that the backup is indeed connecting to the client as user `amanda'. Am I overlooking something? Also, since I do not have a selfcheck*debug, does this mean that I did not install something? Here is my ./configure: ./configure --with-user=amanda --with-group=sys --without-server --with-gnutar-listdir=$PATH/var/amanda/gnutar-lists --with-config=daily --with-gnutar=/bin/gtar Thank you for the pointer to the *debug files, and if you've time, thanks for reading this long-winded SOS! Brandon Moro Systems Administration, Unify Corporation [EMAIL PROTECTED] -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 10:15 AM To: Brandon Moro Cc: [EMAIL PROTECTED] Subject: Re: Obvious question On Mon, 4 Feb 2002 at 9:49am, Brandon Moro wrote The answer to this is probably in front of my face. I am running Amanda-2.4.2p2 on Solaris 8. I back up WinNT and Win2k clients at this point, but would like to add in some RedHat clients. I set up the client on a RedHat 7.2 box, but it failed on me. How can I find out why it failed? Where do I find the debug or error log? Debug files are in /tmp/amanda on the client -- you want to look at selfcheck*debug. Also, there's Faq-O-Matic, available through the amanda home page. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
specifying gnutar, trouble with OSF1 file system
Using AMANDA version 2.4.2p2 on OSF/Tru64 v5.1 On the client side, amanda is sending an inappropriate parameter to the /sbin/dump = sendsize: running /sbin/dump 0Esf 1048576 - /net/home1 running /usr/local/amanda-2.4.2p2/libexec/killpgrp dump: dump: Cannot open file-system file home1_dmn#home1_fs dump: Bad file system specification or bad file system. The raw device must dump: be entered when the file system's pathname has not been entered in the dump: fstab file. A bad file system is reported when the the magic number dump: is not found in the super block. = I think i should be using gnutar... As this would likely work-around this issue... At configure time, I have specified: --with-gnutar=/usr/local/gnu/bin/tar Only problem, I have not figured out how to force the use of gnutar instead of the distribution's dump program. The client in this case is still calling dump? And, btw, would this be the same way I get amanda to use the vdump program? vdump was found at compile-time. Though, when I get the configuration to work, will I again encounter amanda passing a bogus string which is likely obtained from the /etc/fstab file? I am specifying a file system location in the disklist: host /path-to/home1 no-record ### I believe it is OK to use no-record for testing right? I read about this somewhere... I think... Would it be weird to run the no-record config and see a file system get dumped to the holding disk and then written to tape? On another client -- which is working somewhat -- I saw this behavior... What does no-record mean exactly? thanks!!
Using Patch to apply advfs.diff
Hi Everyone I am trying to setup the amanda client on a TRU64 in particular OSF1 V4.0. (Note the amanda client is amanda-2.4.2p2) This means that I need to apply the advfs.diff patch. To do this I believed that I need ed to go into the client-src directory then type patch getfsent.h advfs.diff but when I do this I get a message saying Hmm... I can't seem to find a patch in there anywhere. Ive tried various combinations of switchs such as -l , p0 and p1 with no change. Can anyone give me an idea where Im going wrong ?? Thank You for your time Have a nice day :) __ The contents of this e-mail are privileged and/or confidential to the named recipient and are not to be used by any other person and/or organisation. If you have received this e-mail in error, please notify the sender and delete all material pertaining to this e-mail. __
Kernel 2.4.17 crashing
So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system, originally 7.1. I have the mt-st package version .5beta release 10. Occasionally when I attempt to run an amcheck, my system merely stops. No kernel panic, not segfaulting, it simply stops. Does anyone know of this problem? I'm going to try upgrading mt-st next, but I was hoping for a little confirmation. -Chris
Re: [Amanda-users] Kernel 2.4.17 crashing
every machine I've tried to run 2.4.17 upto 2.4.18-pre4 crashed. those kernels seem to be shit. although there are people who have had success. I'm running 2.4.18-pre7-ac1 now which seems to have fixed the problem. stick with 2.4.16 till 2.4.18 is released. On Mon, Feb 04, 2002 at 08:42:13PM -0500, Chris Dahn wrote: So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system, originally 7.1. I have the mt-st package version .5beta release 10. Occasionally when I attempt to run an amcheck, my system merely stops. No kernel panic, not segfaulting, it simply stops. Does anyone know of this problem? I'm going to try upgrading mt-st next, but I was hoping for a little confirmation.
Re: Kernel 2.4.17 crashing
On Mon, Feb 04, 2002 at 08:42:13PM -0500, Chris Dahn wrote: So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system, originally 7.1. I have the mt-st package version .5beta release 10. Occasionally when I attempt to run an amcheck, my system merely stops. No kernel panic, not segfaulting, it simply stops. Does anyone know of this problem? I'm going to try upgrading mt-st next, but I was hoping for a little confirmation. -Chris Is there a reason you need to run a 2.4 kernel? Sad to say, I've had _much_ better luck so far with the stability of 2.2.19 or 2.2.20. For a machine that must run 24/7, that's what I'll use, ten times out of ten. Is there any particular liklyhood the problem lies in mt-st hanging up? I'd think it much more plausible you're getting stuck someplace in a kernel driver. The mt-st is just a utility that lets you rewind tapes and the like. You didn't mention what tape drive and SCSI adaptor you're using. I've had kernel hangs due to (apparently) buggy SCSI firmware on tape drives, even in earlier kernels. Perhaps abetted by less than perfect kernel error recovery. -- - Dan Wilder [EMAIL PROTECTED] Technical Manager Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://www.linuxjournal.com/ -
Re: Kernel 2.4.17 crashing
Chris Dahn wrote: So, I upgraded my linux kernel to 2.4.17. I'm running a redhat system, originally 7.1. I have the mt-st package version .5beta release 10. Occasionally when I attempt to run an amcheck, my system merely stops. No kernel panic, not segfaulting, it simply stops. Does anyone know of this problem? I'm going to try upgrading mt-st next, but I was hoping for a little confirmation. Well, it's generally a really bad idea to run a kernel that hasn't been all that thoroughly beaten on by the masses. What's a worse idea is running a bleeding-edge kernel on the machine that does your backups! I would never even consider doing backups on a machine with anything but a stock release + vendor recommended updates! I would *very* strongly suggest you revert to the 7.1 or 7.2 kernel as shipped by Red Hat (or superceded by Red Hat recommended updates, of course). Marty -- Marty Shannon, RHCE, Independent Computing Consultant mailto:[EMAIL PROTECTED]
Re: Compression on Exb 8500
On Tue, 5 Feb 2002 at 5:51pm, Glen Eustace wrote It would seem that we have some kind of conflict with hardware and software compression. If both are on, the backups can not be restored. I have managed to turn off software compression and that seems to cure the problem but would prefer to do software and not hardware. I have tried turning off compression using 'mt -f tape setdensity 0x15', which seems to work but doesn't stick, the next time amanda writes to the drive it has gone back to 0x8c. This system is on RH6.2 on SPARC, is there anyway of permanently turning off compression on the Exb8500 ? Well, the drive should have some dipswitches -- check your hardware manual. Alternatively, from the mt man page: defdensity (SCSI tapes) Set the default density code. The value -1 disables the default density. The density set by setdensity overrides the default until a new tape is inserted. Allowed only for the superuser. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Compression on Exb 8500
Glen Eustace wrote: It would seem that we have some kind of conflict with hardware and software compression. If both are on, the backups can not be restored. I have managed to turn off software compression and that seems to cure the problem but would prefer to do software and not hardware. I have tried turning off compression using 'mt -f tape setdensity 0x15', which seems to work but doesn't stick, the next time amanda writes to the drive it has gone back to 0x8c. This system is on RH6.2 on SPARC, is there anyway of permanently turning off compression on the Exb8500 ? Try: man stinit and after you've created the proper device nodes (search the archive for an earlier post of mine), add post-install st /sbin/stinit to /etc/conf.modules. You already have the proper density codes, so it shouldn't take more than a few minutes to get it all set up. Marty -- Marty Shannon, RHCE, Independent Computing Consultant mailto:[EMAIL PROTECTED]
Re: GNUTAR program not available
I had a similar problem that meant amverify was not working. For some reason tar was not available. I had to delete configure.cache, make a symlink /usr/bin/gtar - /bin/tar, chown amanda:disk /usr/bin/gtar and then ./comfigure bla.bla. -with-gnutar=/usr/bin/gtar versions: amanda 2.4.p2, redhat7.1 patched. For what its worth, Kasper At 10:55 04-02-2002 -0500, Davidson, Brian wrote: Amanda Backup Client Hosts Check ERROR: db-test.ems.sat: [GNUTAR program not available] GNU tar exists on the client machine, I can log in as amanda, and gnu tar is in amanda's path. I can also execute gnu tar as the amanda user. Owners for tar are: -r-xr-xr-x 1 root other 901120 Feb 4 10:15 tar amanda runs as user amanda: group operator. What am I not doing correctly here? Thanks, Brian Davidson DynCorp Treasury Integration Group 11710 Plaza America Dr. Reston, VA 20190 703-261-4694 [EMAIL PROTECTED]
amanda+krb5 compile dies with libtool...
Hi, I have been compiling that latest stable CVS branch of Amanda (co amanda) plus the krb5 module in the amanda-krb-2 CVS tree, for an transition to a krb5 aware Amanda from a Krb4 install. Below is the result from a Tru64 v5.0 system (this src tree has already successfully compiled on BSDI). -=- gmake[1]: Entering directory `/tmp/Amanda-Krb5/amanda/common-src' /sbin/sh ../libtool --mode=link gcc -g -O2 -I/usr/local/krb5/include -L/usr/local/krb5/lib -o genversion genversion.o versuff.o -lm -ltermcap /usr/local/krb5/lib/libgssapi_krb5.a /usr/local/krb5/lib/libkrb5.a /usr/local/krb5/lib/libk5crypto.a /usr/local/krb5/lib/libcom_err.a ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: : Permission denied ../libtool: print: not found gmake[1]: *** [genversion] Error 1 gmake[1]: Leaving directory `/tmp/Amanda-Krb5/amanda/common-src' gmake: *** [all-recursive] Error 1 -=- And I expressly have '--disable-libtool' in the configure statement so it won't do it, yet it bitches about libtool... Any ideas? (Let me know if this is better served on amanda-hackers) I could install the latest version of GNU libtool, but I would hope it wouldn't come to that. Thanks - Peter Losher -- [EMAIL PROTECTED] - Internet Software Consortium - http://www.isc.org/
How do I unsubscribe from the amanda list?
Please, I want to unsubscribe me from this list. Tell me how.
