ERROR: 192.168.0.73: [host u03: port 57341 not secure]
bash-2.00$ ll /Disk2/usr-local/sbin/amcheck -rwsr-x---1 amanda backup 129412 Dec 23 12:53 /Disk2/usr-local/sbin/amcheck bash-2.00$ whoami amanda bash-2.00$ amcheck daily Amanda Tape Server Host Check - ERROR: program /usr/local/libexec/planner: not executable Holding disk /Disk2/AMANDA: 2692458 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet11 label ok NOTE: info dir /usr/adm/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/DailySet1/index/192.168.0.73: does not exist Server check took 0.115 seconds Amanda Backup Client Hosts Check ERROR: 192.168.0.73: [host u03: port 57349 not secure] Client check: 1 host checked in 0.115 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) Any ideas?
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
Andrea Dell'Amico wrote: Your amanda traffic to IP 192.168.0.73 is traversing a NAT device, or a udp proxy, that connects to the destination using an unprivileged port. Thanks, but that's highly unlikely. This is a standalone Solaris 7 machine (I didn't install it, though, so I cannot be completely sure), running both server and client, local intranet. amanda accepts traffic from privileged ports only. You can recompile the Would it help if I do a ./configure --with-user=root ? amanda sources after commenting out the checks, if you cannot fix your connection. Thanks again. I've been stuck on this for several days, so I really appreciate your help.
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
amanda-hackers cut from the CC list. On Thu, 8 Jan 2004 at 2:42pm, Eugen Leitl wrote > > amanda accepts traffic from privileged ports only. You can recompile the > > Would it help if I do a ./configure --with-user=root ? Don't Do That. Amanda won't (and shouldn't) run that way. But you do need to do 'make install' as root, as several binaries need to be setuid root. Did you do this? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
On Thursday 08 January 2004 08:16, Eugen Leitl wrote: >bash-2.00$ ll /Disk2/usr-local/sbin/amcheck >-rwsr-x---1 amanda backup 129412 Dec 23 12:53 >/Disk2/usr-local/sbin/amcheck > >bash-2.00$ whoami >amanda > >bash-2.00$ amcheck daily >Amanda Tape Server Host Check >- >ERROR: program /usr/local/libexec/planner: not executable Mine is: [EMAIL PROTECTED] i2c]$ ls -l /usr/local/libexec/planner -rwsr-x--- 1 root disk 92165 Jan 7 13:53 /usr/local/libexec/planner >Holding disk /Disk2/AMANDA: 2692458 KB disk space available, that's > plenty NOTE: skipping tape-writable test >Tape DailySet11 label ok >NOTE: info dir /usr/adm/amanda/DailySet1/curinfo: does not exist >NOTE: it will be created on the next run >NOTE: index dir /usr/adm/amanda/DailySet1/index/192.168.0.73: does > not exist Server check took 0.115 seconds > >Amanda Backup Client Hosts Check > >ERROR: 192.168.0.73: [host u03: port 57349 not secure] >Client check: 1 host checked in 0.115 seconds, 1 problem found > >(brought to you by Amanda 2.4.4p1) > >Any ideas? Are you sure you built amanda as the normal user? I actually have a user named amanda here which does the building. I do a chown on the archive, making it read amanda:disk, then su amanda to do the unpack, ./configure, and the make. And then did you su to root to do the install after the build was done? THis normally takes care of all permissions issues. I also use a script to do all this so that the configuration options passed are consistent from build to build. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
Joshua Baker-LePain wrote: Would it help if I do a ./configure --with-user=root ? Don't Do That. Amanda won't (and shouldn't) run that way. But you do I know. I was just getting desperate, and started tweaking random things. need to do 'make install' as root, as several binaries need to be setuid root. Did you do this? Originally, yes. make install as root. However, I'm getting a verboten: bash-2.00$ amcheck daily bash: /usr/local/sbin/amcheck: Permission denied # /usr/local/sbin/amcheck daily amcheck: running as user "root" instead of "amanda" # chown amanda /usr/local/sbin/amcheck # ls -la /usr/local/sbin/amcheck -rwsr-x--- 1 amanda backup129412 Jan 8 14:48 /usr/local/sbin/amcheck # /usr/local/sbin/amcheck daily amcheck: running as user "root" instead of "amanda" # exit # bash-2.00$ whoami amanda bash-2.00$ /usr/local/sbin/amcheck daily Amanda Tape Server Host Check - ERROR: program /usr/local/libexec/planner: not executable Holding disk /Disk2/AMANDA: 2692456 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet11 label ok NOTE: info dir /usr/adm/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/DailySet1/index/192.168.0.73: does not exist Server check took 0.164 seconds Amanda Backup Client Hosts Check ERROR: 192.168.0.73: [host u03: port 57421 not secure] Client check: 1 host checked in 0.130 seconds, 1 problem found (brought to you by Amanda 2.4.4p1)
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
Eugen Leitl wrote: Joshua Baker-LePain wrote: Would it help if I do a ./configure --with-user=root ? Don't Do That. Amanda won't (and shouldn't) run that way. But you do I know. I was just getting desperate, and started tweaking random things. need to do 'make install' as root, as several binaries need to be setuid root. Did you do this? Originally, yes. make install as root. However, I'm getting a verboten: bash-2.00$ amcheck daily bash: /usr/local/sbin/amcheck: Permission denied # /usr/local/sbin/amcheck daily # su amanda -c 'amcheck daily' amcheck: running as user "root" instead of "amanda" # chown amanda /usr/local/sbin/amcheck # ls -la /usr/local/sbin/amcheck -rwsr-x--- 1 amanda backup129412 Jan 8 14:48 The setuid bit only changes the effective user ID when you run a program, not the real user ID. Is "amanda" in the "backup" group? What does "id -Gn amanda" say? I would: # chown root /usr/local/sbin/amcheck # chmod 4750 /usr/local/sbin/amcheck (Just in case the chown turns off the setuid bit) # usermod -G backup amanda (adding any other groups you need) HTH, John /usr/local/sbin/amcheck # /usr/local/sbin/amcheck daily amcheck: running as user "root" instead of "amanda" # exit # bash-2.00$ whoami amanda bash-2.00$ /usr/local/sbin/amcheck daily Amanda Tape Server Host Check - ERROR: program /usr/local/libexec/planner: not executable Holding disk /Disk2/AMANDA: 2692456 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet11 label ok NOTE: info dir /usr/adm/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/DailySet1/index/192.168.0.73: does not exist Server check took 0.164 seconds Amanda Backup Client Hosts Check ERROR: 192.168.0.73: [host u03: port 57421 not secure] Client check: 1 host checked in 0.130 seconds, 1 problem found (brought to you by Amanda 2.4.4p1)
disk offline ?
Hi Group ! Maybe anyone has a hint for me ? We have about 30 Servers, all UNIX. They are all backed up with amanda, which worked very good, until some problems occured. I defined a TestSet an tried to put in a new host. But I don´t get it to work. I want to do a dump of the following partitions, which are really partitions on the target-host. - daisy / comp-hd-dump daisy /boot comp-hd-dump daisy /optcomp-hd-dump daisy /usrcomp-hd-dump - If I put comp-hd-tar in here, all works fine ... !? - FAILURE AND STRANGE DUMP SUMMARY: daisy /usr lev 0 FAILED [disk /usr offline on daisy?] daisy /opt lev 0 FAILED [disk /opt offline on daisy?] daisy /lev 0 FAILED [disk / offline on daisy?] ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - daisy / 0 FAILED --- daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 daisy /opt0 FAILED --- daisy /usr0 FAILED --- Why does /boot work ??? Ups, just saw it worked only the first time ... Now its the same message ... And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? Last Backup this night Were great anyone had a tip ! ...olli
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
Andrea Dell'Amico wrote: Don't do that, neither. Assign the group "backup" to the amanda user, chown root /usr/local/sbin/amcheck, and then rerun it as amanda. I've done what Gene Heskett said: # cat /etc/group ... backup::303:amanda ... # cat /etc/passwd ... amanda:x:400:303:Amanda Operator:/Disk2/amanda:/bin/bash ... As user amanda: bash-2.00$ tar zxvf amanda-2.4.4p1.tar.gz ... bash-2.00$ export LDFLAGS="-L/usr/local/lib -R/usr/local/lib" bash-2.00$ cd amanda-2.4.4p1 bash-2.00$ ./configure --with-user=amanda --with-group=backup ... bash-2.00$ make ... bash-2.00$ su # make install ... bash-2.00$ id amanda uid=400(amanda) gid=303(backup) bash-2.00$ amcheck daily bash: /usr/local/sbin/amcheck: Permission denied I've tried diverse suggestions from other posters (thanks!), but so far can't get anything other than a verboten, or the usual 'port not secure' shinola. Thanks, I'll keep trying.
Re: disk offline ?
--On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon <[EMAIL PROTECTED]> wrote: > Hi Group ! > > Maybe anyone has a hint for me ? > We have about 30 Servers, all UNIX. They are all backed up with amanda, > which worked very good, until some problems occured. > > I defined a TestSet an tried to put in a new host. But I don´t get it to > work. I want to do a dump of the following partitions, which are really > partitions on the target-host. > > - > daisy / comp-hd-dump > daisy /boot comp-hd-dump > daisy /optcomp-hd-dump > daisy /usrcomp-hd-dump > - > > If I put comp-hd-tar in here, all works fine ... !? > > - > FAILURE AND STRANGE DUMP SUMMARY: > daisy /usr lev 0 FAILED [disk /usr offline on daisy?] > daisy /opt lev 0 FAILED [disk /opt offline on daisy?] > daisy /lev 0 FAILED [disk / offline on daisy?] Disk offline messages are generally a result of permissions problems (if the disk were really offline you would have much bigger problems). Make sure your backup user is part of the correct group to have access to the disk. Try to 'su - backupuser' and check if you can see those disks. Tar works because Aamnda uses a suid runtar wrapper script that runs tar as root (although it isn't used by amcheck, so you would still get errors from amcheck even though amdump would work). Frank > > ... > > DUMP SUMMARY: DUMPER STATSTAPER STATS > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > daisy / 0 FAILED --- > daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 > daisy /opt0 FAILED --- > daisy /usr0 FAILED --- > > > > Why does /boot work ??? Ups, just saw it worked only the first time ... > Now its the same message ... > > And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? > Last Backup this night > > Were great anyone had a tip ! > > ...olli -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
Eugen Leitl wrote: Andrea Dell'Amico wrote: Don't do that, neither. Assign the group "backup" to the amanda user, chown root /usr/local/sbin/amcheck, and then rerun it as amanda. I've done what Gene Heskett said: # cat /etc/group ... backup::303:amanda ... # cat /etc/passwd ... amanda:x:400:303:Amanda Operator:/Disk2/amanda:/bin/bash ... As user amanda: bash-2.00$ tar zxvf amanda-2.4.4p1.tar.gz ... bash-2.00$ export LDFLAGS="-L/usr/local/lib -R/usr/local/lib" bash-2.00$ cd amanda-2.4.4p1 bash-2.00$ ./configure --with-user=amanda --with-group=backup ... bash-2.00$ make ... bash-2.00$ su # make install ... bash-2.00$ id amanda uid=400(amanda) gid=303(backup) bash-2.00$ amcheck daily bash: /usr/local/sbin/amcheck: Permission denied Try: ls -ld /usr/local/sbin ls -ld /usr/local Does amanda have permission to access those directories? I've tried diverse suggestions from other posters (thanks!), but so far can't get anything other than a verboten, or the usual 'port not secure' shinola. In older versions of Amanda, "port not secure" could be caused by --with-tcpports=... or --with-udpports=... on the configure command. Are you running the same Amanda version on the client and the server? John Thanks, I'll keep trying.
SUCESS: Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
To follow up on myself, the rights issues have been fixed. The key step was making the amanda user member of the backup group. Notice: it is necessary to logout an existing amanda session when rebuilding, as otherwise the original group membership will persist (and hence the original error message, see below bottom). Below procedure will make you happy on SPARC Solaris 7 (appropriately GNUified, of course): bash-2.00$ /usr/local/sbin/amcheck daily Amanda Tape Server Host Check - Holding disk /Disk2/AMANDA: 2667734 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet11 label ok NOTE: info dir /usr/adm/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/DailySet1/index/192.168.0.73: does not exist Server check took 0.061 seconds Amanda Backup Client Hosts Check ERROR: 192.168.0.73: [can not read/write /usr/local/var/amanda/gnutar-lists/.: No such file or directory] Client check: 1 host checked in 1.104 seconds, 1 problem found (brought to you by Amanda 2.4.4p1) There are only minor config issues left to be resolved. Thanks, everybody! Eugen Leitl wrote: Andrea Dell'Amico wrote: Don't do that, neither. Assign the group "backup" to the amanda user, chown root /usr/local/sbin/amcheck, and then rerun it as amanda. I've done what Gene Heskett said: # cat /etc/group ... backup::303:amanda ... # cat /etc/passwd ... amanda:x:400:303:Amanda Operator:/Disk2/amanda:/bin/bash ... As user amanda: bash-2.00$ tar zxvf amanda-2.4.4p1.tar.gz ... bash-2.00$ export LDFLAGS="-L/usr/local/lib -R/usr/local/lib" bash-2.00$ cd amanda-2.4.4p1 bash-2.00$ ./configure --with-user=amanda --with-group=backup ... bash-2.00$ make ... bash-2.00$ su # make install ... bash-2.00$ id amanda uid=400(amanda) gid=303(backup) bash-2.00$ amcheck daily bash: /usr/local/sbin/amcheck: Permission denied I've tried diverse suggestions from other posters (thanks!), but so far can't get anything other than a verboten, or the usual 'port not secure' shinola. Thanks, I'll keep trying.
Re: disk offline ?
I can su to amanda and chdir to usr and everything else thats failling ? Is it maybe because of the filesystem xfs on the target-machine ? I think amanda wants to do a xfsdump there, right ? I tried to run it as amanda and got it complaining to be root to run ... !? Thanks in advance ...olli Am Do, 2004-01-08 um 16.39 schrieb Frank Smith: > --On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon <[EMAIL PROTECTED]> > wrote: > > > Hi Group ! > > > > Maybe anyone has a hint for me ? > > We have about 30 Servers, all UNIX. They are all backed up with amanda, > > which worked very good, until some problems occured. > > > > I defined a TestSet an tried to put in a new host. But I don´t get it to > > work. I want to do a dump of the following partitions, which are really > > partitions on the target-host. > > > > - > > daisy / comp-hd-dump > > daisy /boot comp-hd-dump > > daisy /optcomp-hd-dump > > daisy /usrcomp-hd-dump > > - > > > > If I put comp-hd-tar in here, all works fine ... !? > > > > - > > FAILURE AND STRANGE DUMP SUMMARY: > > daisy /usr lev 0 FAILED [disk /usr offline on daisy?] > > daisy /opt lev 0 FAILED [disk /opt offline on daisy?] > > daisy /lev 0 FAILED [disk / offline on daisy?] > > Disk offline messages are generally a result of permissions > problems (if the disk were really offline you would have much > bigger problems). Make sure your backup user is part of the > correct group to have access to the disk. Try to 'su - backupuser' > and check if you can see those disks. >Tar works because Aamnda uses a suid runtar wrapper script that > runs tar as root (although it isn't used by amcheck, so you would > still get errors from amcheck even though amdump would work). > > Frank > > > > > ... > > > > DUMP SUMMARY: DUMPER STATSTAPER STATS > > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > > -- - > > daisy / 0 FAILED --- > > daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 > > daisy /opt0 FAILED --- > > daisy /usr0 FAILED --- > > > > > > > > Why does /boot work ??? Ups, just saw it worked only the first time ... > > Now its the same message ... > > > > And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? > > Last Backup this night > > > > Were great anyone had a tip ! > > > >...olli
Re: disk offline ?
--On Thursday, January 08, 2004 17:21:48 +0100 Oliver Simon <[EMAIL PROTECTED]> wrote: > I can su to amanda and chdir to usr and everything else thats failling ? > Is it maybe because of the filesystem xfs on the target-machine ? > I think amanda wants to do a xfsdump there, right ? I tried to run it as > amanda and got it complaining to be root to run ... !? You must use the right version of dump for the filesystem. Was Amanda built with support for xfsdump ? Are the disks on all your clients xfs or just on the one new client? If you have a mixture of filesystem types, I'm not sure how you configure multiple flavors of dump in one setup, hopefully someone else here has done it and will say how. Frank > > Thanks in advance > > ...olli > > Am Do, 2004-01-08 um 16.39 schrieb Frank Smith: >> --On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon <[EMAIL PROTECTED]> >> wrote: >> >> > Hi Group ! >> > >> > Maybe anyone has a hint for me ? >> > We have about 30 Servers, all UNIX. They are all backed up with amanda, >> > which worked very good, until some problems occured. >> > >> > I defined a TestSet an tried to put in a new host. But I don´t get it to >> > work. I want to do a dump of the following partitions, which are really >> > partitions on the target-host. >> > >> > - >> > daisy / comp-hd-dump >> > daisy /boot comp-hd-dump >> > daisy /optcomp-hd-dump >> > daisy /usrcomp-hd-dump >> > - >> > >> > If I put comp-hd-tar in here, all works fine ... !? >> > >> > - >> > FAILURE AND STRANGE DUMP SUMMARY: >> > daisy /usr lev 0 FAILED [disk /usr offline on daisy?] >> > daisy /opt lev 0 FAILED [disk /opt offline on daisy?] >> > daisy /lev 0 FAILED [disk / offline on daisy?] >> >> Disk offline messages are generally a result of permissions >> problems (if the disk were really offline you would have much >> bigger problems). Make sure your backup user is part of the >> correct group to have access to the disk. Try to 'su - backupuser' >> and check if you can see those disks. >>Tar works because Aamnda uses a suid runtar wrapper script that >> runs tar as root (although it isn't used by amcheck, so you would >> still get errors from amcheck even though amdump would work). >> >> Frank >> >> > >> > ... >> > >> > DUMP SUMMARY: DUMPER STATSTAPER STATS >> > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s >> > -- - >> > daisy / 0 FAILED --- >> > daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 >> > daisy /opt0 FAILED --- >> > daisy /usr0 FAILED --- >> > >> > >> > >> > Why does /boot work ??? Ups, just saw it worked only the first time ... >> > Now its the same message ... >> > >> > And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? >> > Last Backup this night >> > >> > Were great anyone had a tip ! >> > >> > ...olli -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
On Thursday 08 January 2004 10:00, Eugen Leitl wrote: >Andrea Dell'Amico wrote: >> Don't do that, neither. Assign the group "backup" to the amanda >> user, chown root /usr/local/sbin/amcheck, and then rerun it as >> amanda. > >I've done what Gene Heskett said: > ># cat /etc/group >... >backup::303:amanda >... ># cat /etc/passwd >... >amanda:x:400:303:Amanda Operator:/Disk2/amanda:/bin/bash >... > >As user amanda: >bash-2.00$ tar zxvf amanda-2.4.4p1.tar.gz >... >bash-2.00$ export LDFLAGS="-L/usr/local/lib -R/usr/local/lib" >bash-2.00$ cd amanda-2.4.4p1 >bash-2.00$ ./configure --with-user=amanda --with-group=backup >... >bash-2.00$ make >... >bash-2.00$ su ># make install >... >bash-2.00$ id amanda >uid=400(amanda) gid=303(backup) > >bash-2.00$ amcheck daily >bash: /usr/local/sbin/amcheck: Permission denied > >I've tried diverse suggestions from other posters (thanks!), >but so far can't get anything other than a verboten, or the usual >'port not secure' shinola. > >Thanks, I'll keep trying. I haven't posted this for a couple of weeks, so maybe the list will forgive me one more time. Here is the script I use to build amanda, executed as the user amanda (it will warn and exit if root runs it) after you've made amanda the owner of the tarball and unpacked it as the user amanda, copy this into the tarball generated directory, set the +x bit and run it. Here I call it gh.cf, but you can call it whatever. --- #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo " Warning " echo "Amanda needs to be configured and built by the user amanda," echo "but must be installed by user root." echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda make --- change the with-tape-server= to the FQDN of the host server, and take out the changer-device line if you don't have one. The FQDN must exist in your dns records, or in the /etc/hosts file. Also if amanda isn't a member of the group disk, change that to whatever has perms to have the run of the system. It was disk here on this formerly rh8.0 system. This script has been building amanda for me for well over a year now, including the 2.4.4p1-20040107 snapshot from yesterday which ran just fine last night. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: SUCESS: Re: ERROR: 192.168.0.73: [host u03: port 57341 not secure]
On Thursday 08 January 2004 11:17, Eugen Leitl wrote: >To follow up on myself, the rights issues have been fixed. >The key step was making the amanda user member of the backup group. >Notice: it is necessary to logout an existing amanda session when >rebuilding, as otherwise the original group membership will >persist (and hence the original error message, see below bottom). > >Below procedure will make you happy on SPARC Solaris 7 >(appropriately GNUified, of course): > >bash-2.00$ /usr/local/sbin/amcheck daily >Amanda Tape Server Host Check >- >Holding disk /Disk2/AMANDA: 2667734 KB disk space available, that's > plenty NOTE: skipping tape-writable test >Tape DailySet11 label ok >NOTE: info dir /usr/adm/amanda/DailySet1/curinfo: does not exist >NOTE: it will be created on the next run >NOTE: index dir /usr/adm/amanda/DailySet1/index/192.168.0.73: does > not exist Server check took 0.061 seconds > >Amanda Backup Client Hosts Check > >ERROR: 192.168.0.73: [can not read/write > /usr/local/var/amanda/gnutar-lists/.: No such file or directory] > Client check: 1 host checked in 1.104 seconds, 1 problem found > >(brought to you by Amanda 2.4.4p1) > >There are only minor config issues left to be resolved. > >Thanks, everybody! > >Eugen Leitl wrote: >> Andrea Dell'Amico wrote: >>> Don't do that, neither. Assign the group "backup" to the amanda >>> user, chown root /usr/local/sbin/amcheck, and then rerun it as >>> amanda. >> >> I've done what Gene Heskett said: >> >> # cat /etc/group >> ... >> backup::303:amanda >> ... >> # cat /etc/passwd >> ... >> amanda:x:400:303:Amanda Operator:/Disk2/amanda:/bin/bash >> ... >> >> As user amanda: >> bash-2.00$ tar zxvf amanda-2.4.4p1.tar.gz >> ... >> bash-2.00$ export LDFLAGS="-L/usr/local/lib -R/usr/local/lib" >> bash-2.00$ cd amanda-2.4.4p1 >> bash-2.00$ ./configure --with-user=amanda --with-group=backup >> ... >> bash-2.00$ make >> ... >> bash-2.00$ su >> # make install >> ... >> bash-2.00$ id amanda >> uid=400(amanda) gid=303(backup) >> >> bash-2.00$ amcheck daily >> bash: /usr/local/sbin/amcheck: Permission denied >> >> I've tried diverse suggestions from other posters (thanks!), >> but so far can't get anything other than a verboten, or the usual >> 'port not secure' shinola. >> >> Thanks, I'll keep trying. It sound like some of that tree is owned by root, so become root, cd to /usr/local/var, and chown -R amanda:backup amanda And then don't touch that stuff as root :) -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: disk offline ?
Hello again ... Am Do, 2004-01-08 um 17.37 schrieb Frank Smith: > --On Thursday, January 08, 2004 17:21:48 +0100 Oliver Simon <[EMAIL PROTECTED]> > wrote: > > > I can su to amanda and chdir to usr and everything else thats failling ? > > Is it maybe because of the filesystem xfs on the target-machine ? > > I think amanda wants to do a xfsdump there, right ? I tried to run it as > > amanda and got it complaining to be root to run ... !? > > You must use the right version of dump for the filesystem. Was Amanda > built with support for xfsdump ? Yes, we have about 15 (SuSI´s/SLES/SLOX) hosts running with xfs. No problem there. > Are the disks on all your clients xfs or just on the one new client? The rest is 10 Solaris (ufs) and some other linux´ (redhat ext3). > If you have a mixture of filesystem types, I'm not sure how you configure multiple > flavors of dump in one > setup, hopefully someone else here has done it and will say how. Thought, amanda examines it itself, and takes the correct version (dump/xfsdump) from the clients ?? > > Frank ...olli > > > > > Thanks in advance > > > > ...olli > > > > Am Do, 2004-01-08 um 16.39 schrieb Frank Smith: > >> --On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon <[EMAIL PROTECTED]> > >> wrote: > >> > >> > Hi Group ! > >> > > >> > Maybe anyone has a hint for me ? > >> > We have about 30 Servers, all UNIX. They are all backed up with amanda, > >> > which worked very good, until some problems occured. > >> > > >> > I defined a TestSet an tried to put in a new host. But I don´t get it to > >> > work. I want to do a dump of the following partitions, which are really > >> > partitions on the target-host. > >> > > >> > - > >> > daisy / comp-hd-dump > >> > daisy /boot comp-hd-dump > >> > daisy /optcomp-hd-dump > >> > daisy /usrcomp-hd-dump > >> > - > >> > > >> > If I put comp-hd-tar in here, all works fine ... !? > >> > > >> > - > >> > FAILURE AND STRANGE DUMP SUMMARY: > >> > daisy /usr lev 0 FAILED [disk /usr offline on daisy?] > >> > daisy /opt lev 0 FAILED [disk /opt offline on daisy?] > >> > daisy /lev 0 FAILED [disk / offline on daisy?] > >> > >> Disk offline messages are generally a result of permissions > >> problems (if the disk were really offline you would have much > >> bigger problems). Make sure your backup user is part of the > >> correct group to have access to the disk. Try to 'su - backupuser' > >> and check if you can see those disks. > >>Tar works because Aamnda uses a suid runtar wrapper script that > >> runs tar as root (although it isn't used by amcheck, so you would > >> still get errors from amcheck even though amdump would work). > >> > >> Frank > >> > >> > > >> > ... > >> > > >> > DUMP SUMMARY: DUMPER STATSTAPER STATS > >> > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > >> > -- - > >> > daisy / 0 FAILED --- > >> > daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 > >> > daisy /opt0 FAILED --- > >> > daisy /usr0 FAILED --- > >> > > >> > > >> > > >> > Why does /boot work ??? Ups, just saw it worked only the first time ... > >> > Now its the same message ... > >> > > >> > And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? > >> > Last Backup this night > >> > > >> > Were great anyone had a tip ! > >> > > >> > ...olli
Amanda .vs. Bacula
msg.pgp Description: PGP message
RE: Tapeless backup configuration
Paul, > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens > Sent: 07 January 2004 20:25 > To: chris > Cc: [EMAIL PROTECTED] > Subject: Re: Tapeless backup configuration > > > chris wrote: > > > I have set up the environment exactly as set out in > > http://amanda.sourceforge.net/fom-serve/cache/191.html and > have got to > > the part where I am trying to set the labels. When I run amlabel > > DailySet1 DailySet101 slot 1 I get the response: > > amlabel: could not load slot "1" : chg-multi: slot is empty. > > > > Can anyone give me a pointer as to what may be wrong with my > > configuration? > > Maybe forgot to create a "data" subdirectory in each "tape" directory? > See point 4 in above faq text. > > 4. Create the "tapes" on the tape server hard drive with > the associated > data directories: > > $mkdir /var2/amandadumps > $mkdir /var2/amandadumps/tape01 > $mkdir /var2/amandadumps/tape01/data > > I have checked the configuration and I now have the following structure in my "backup" area:- /home/spool/backup contains the following data -> /home/spool/backup/slot1 info slot1 slot1/data slot2 slot2/data slot3 slot3/data slot4 slot4/data .. When I run amcheck I get the following for each slot: amcheck-server: slot : chg-multi : slot is empty .. and after the listing of slots it reports: ERROR: new tape not found in rack (expecting a new tape) I still get the same error when I attempt to run amlabel: amlabel: could not load slot "1" : chg-multi : slot is empty I have followed the instructions for the RPM included with Fedora and still I am getting these errors. I appreciate your help, but I am still apparently missing a key element in the configuration. TIA -- From Chris Jones mailto:[EMAIL PROTECTED] web: http://www.stow-jones.co.uk/ My PGP Key:- RSA 2048/1024 Key ID: 0x99DD97E3 Fingerprint: 98B3 ED1D 9E45 A993 ECBE F94A DEC8 9A15 99DD 97E3
Amreport question
When I use amreport command the output contains page breaks. Is there any way to tell amreport not to put page breaks in its output? Thanks. -- Jack Cobb MIS Department Skyline Corporation [EMAIL PROTECTED]
RE: Tapeless backup configuration
--On Thursday, January 08, 2004 19:39:57 + Chris Jones <[EMAIL PROTECTED]> wrote: > Paul, > >> -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens >> Sent: 07 January 2004 20:25 >> To: chris >> Cc: [EMAIL PROTECTED] >> Subject: Re: Tapeless backup configuration >> >> >> chris wrote: >> >> > I have set up the environment exactly as set out in >> > http://amanda.sourceforge.net/fom-serve/cache/191.html and >> have got to >> > the part where I am trying to set the labels. When I run amlabel >> > DailySet1 DailySet101 slot 1 I get the response: >> > amlabel: could not load slot "1" : chg-multi: slot is empty. >> > >> > Can anyone give me a pointer as to what may be wrong with my >> > configuration? >> >> Maybe forgot to create a "data" subdirectory in each "tape" directory? >> See point 4 in above faq text. >> >> 4. Create the "tapes" on the tape server hard drive with >> the associated >> data directories: >> >> $mkdir /var2/amandadumps >> $mkdir /var2/amandadumps/tape01 >> $mkdir /var2/amandadumps/tape01/data >> >> > I have checked the configuration and I now have the following structure in > my "backup" area:- > /home/spool/backup contains the following > data -> /home/spool/backup/slot1 > info > slot1 > slot1/data > slot2 > slot2/data > slot3 > slot3/data > slot4 > slot4/data > .. > > When I run amcheck I get the following for each slot: > amcheck-server: slot : chg-multi : slot is empty > > .. and after the listing of slots it reports: > ERROR: new tape not found in rack >(expecting a new tape) > > I still get the same error when I attempt to run amlabel: > amlabel: could not load slot "1" : chg-multi : slot is empty What is in your changer.conf (or whatever you specified as changerfile in amanda.conf)? Also, make sure your 'tape' directories have the proper ownership/permissions so the amanda user can access them. Frank > > I have followed the instructions for the RPM included with Fedora and still > I am getting these errors. I appreciate your help, but I am still apparently > missing a key element in the configuration. > > TIA > -- > From > Chris Jones > mailto:[EMAIL PROTECTED] > web: http://www.stow-jones.co.uk/ > > My PGP Key:- > RSA 2048/1024 Key ID: 0x99DD97E3 > Fingerprint: 98B3 ED1D 9E45 A993 ECBE F94A DEC8 9A15 99DD 97E3 -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Anyone know how to do a planner-only run?
Just wondering if anyone knows how to kick off an amdump that doesn't actually write to tape (nor to holdingdisk nor even to /dev/null), but rather just stops after the planning stage, so one could see how much *would* have been written to tape/disk/whatever, which DLEs would have been bumped up to full dumps, and so forth? -- Mark
