RE: amcheck errors
-Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Friday, February 15, 2002 12:51 PM To: Davidson, Brian Cc: [EMAIL PROTECTED] Subject: Re: amcheck errors > >On Fri, 15 Feb 2002 at 12:10pm, Davidson, Brian wrote > >> ERROR: crypto-gw.irs.dev: [access as amanda not allowed from >> [EMAIL PROTECTED]] amandahostsauth failed >> ERROR: relay.irs.dev: [GNUTAR program not available] >> >> Question 1: Where does amcheck find this info from: >> ([EMAIL PROTECTED]) because that is a wrong host name and I can't find >> any config files that I made a typo in. (relay.irs.dev is the correct host >> name) >> >Are you sure? From a remote host, what does a DNS lookup give? crypto-gw >is seeing the amcheck request coming from relay-gw, not relay. > Here's my nslookup: it looks fine: crypto-gw% nslookup relay Server: relay.irs.dev Address: 10.10.40.33 Name:relay.irs.dev Address: 10.10.40.33 crypto-gw% >> Question 2: gnu tar is in the path, and is version 1.13, I deleted >> config.cache, and rebuilt amanda, but it's still not available. > >Are you sure configure found it when you built amanda? Also, plain 1.13 >is Bad. You want at least 1.13.19, which is available from alpha.gnu.org. Thanks for the info. I'll grab 1.13.19 and install. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amcheck errors
On Fri, 15 Feb 2002 at 12:10pm, Davidson, Brian wrote > ERROR: crypto-gw.irs.dev: [access as amanda not allowed from > [EMAIL PROTECTED]] amandahostsauth failed > ERROR: relay.irs.dev: [GNUTAR program not available] > > Question 1: Where does amcheck find this info from: > ([EMAIL PROTECTED]) because that is a wrong host name and I can't find > any config files that I made a typo in. (relay.irs.dev is the correct host > name) Are you sure? From a remote host, what does a DNS lookup give? crypto-gw is seeing the amcheck request coming from relay-gw, not relay. > Question 2: gnu tar is in the path, and is version 1.13, I deleted > config.cache, and rebuilt amanda, but it's still not available. Are you sure configure found it when you built amanda? Also, plain 1.13 is Bad. You want at least 1.13.19, which is available from alpha.gnu.org. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amcheck errors
>Question 1: Where does amcheck find this info from: >([EMAIL PROTECTED]) because that is a wrong host name ... Amanda (amandad on the client) took the IP number of the host connecting to it (the Amanda server) and did a gethostbyaddr on it. That returned "relay-gw.irs.dev". Whether it used DNS or not depends on how you set up your system. Use this little test program to do exactly what Amanda does: ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyaddr.c >Question 2: gnu tar is in the path, and is version 1.13, I deleted >config.cache, and rebuilt amanda, but it's still not available. As Joshua said, 1.13 is seriously evil, but that would not have caused Amanda to report it missing. What did ./configure say when it tried to find GNU tar? For instance, here's what mine says: checking for gtar... /opt/tar/bin/gtar If all else fails, you can use --with-gnutar=/path/to/gnu/tar to force ./configure to find it (rememeber to remove config.cache between each change). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck errors
On Fri, Sep 26, 2003 at 07:54:23AM +0200, Mats Blomstrand wrote:
> Hi all
> I have run into some silly permission problem that i cant figure out.
> What do i miss?
>
> As amanda-user i can run "mtx" just fine and change tapes back an forth,
> but "chg-zd-mtx" says:
>
> -bash-2.05b$ chg-zd-mtx -info
>no slots available
>
> And "amcheck normal" says:
>
> -bash-2.05b$ amcheck normal
> Amanda Tape Server Host Check
> -
> WARNING: program /usr/local/amanda/bin/planner: not setuid-root
> WARNING: program /usr/local/amanda/bin/dumper: not setuid-root
> WARNING: program /usr/local/amanda/bin/amcheck: not setuid-root
> Holding disk /amanda: 25678660 KB disk space available, using 25678660 KB
> amcheck-server: could not get changer info: no slots available
>
> Amanda Backup Client Hosts Check
>
> WARNING: hostname.deleted: selfcheck request timed out. Host down?
> Client check: 1 host checked in 29.999 seconds, 1 problem found
>
> (brought to you by Amanda 2.4.4)
>
> But i have set set the SUID bit:
>
> -bash-2.05b$ ls -l /usr/local/amanda/bin/{planner,dumper,amcheck}
> -rwsr-x---1 amanda amanda 93327 Sep 5 17:24
> /usr/local/amanda/bin/amcheck
> -rwsr-x---1 amanda amanda 89732 Sep 5 17:24
> /usr/local/amanda/bin/dumper
> -rwsr-x---1 amanda amanda 91540 Sep 5 17:24
> /usr/local/amanda/bin/planner
>
> And this is what the logfiles says after running "amcheck normal":
>
> -bash-2.05b$ cat /tmp/amanda/amcheck.20030926083742.debug
> amcheck: debug 1 pid 16062 ruid 501 euid 501: start at Fri Sep 26 08:37:42 2003
> amcheck: dgram_bind: socket bound to 0.0.0.0.32781
> changer: got exit: 2 str: no slots available
> amcheck-server: time 0.140: could not get changer info: no slots available
> amcheck-server: time 0.140: pid 16063 finish time Fri Sep 26 08:37:42 2003
> amcheck: pid 16062 finish time Fri Sep 26 08:38:12 2003
>
> chg-zd-mtx: debug 1 pid 16075 ruid 501 euid 501: start at Fri Sep 26 08:37:42
> 2003
> 08:37:42 Arg info:
>$# = 1
>$0 = "/usr/local/amanda/bin/chg-zd-mtx"
>$1 = "-info"
> 08:37:42 Running: mtx status
> 08:37:42 Exit code: 127
>Stderr:
> /usr/local/amanda/bin/chg-zd-mtx: line 387: mtx: command not found
> 08:37:42 Exit (2) -> no slots available
> chg-zd-mtx: pid 16154 finish time Fri Sep 26 08:37:42 2003
>
>
> I have also added these entries for xinetd and done a "kill -HUP":
>
> bash# cat /etc/xinetd.d/amanda-*
> #
> # amanda client tjänster
> #
> service amanda
> {
> disable = no
> socket_type = dgram
> protocol= udp
> wait= yes
> user= amanda
> server = /usr/local/amanda/bin/amandad
> log_type= SYSLOG
> }
> #
> # amanda server tjänster
> #
> service amandaidx
> {
> disable = no
> socket_type = stream
> protocol= tcp
> wait= no
> user= amanda
> server = /usr/local/amanda/bin/amindexd
> log_type= SYSLOG
> }
> #
> service amidxtape
> {
> disable = no
> socket_type = stream
> protocol= tcp
> wait= no
> user= amanda
> server = /usr/local/amanda/bin/amidxtaped
> log_type= SYSLOG
> }
>
>
> Any ideas about what im doing wrong?
Two items stand out.
The warning are:
> WARNING: program /usr/local/amanda/bin/amcheck: not setuid-root
Note the "root" part. Your programs are setuid-amanda. I.e. owned by...
I suspect that you did your install as the amanda user rather than as root.
Only the root user can do the proper change owner/permissions needed.
The second is this:
> amcheck-server: could not get changer info: no slots available
^^
Which suggests that you did not set up the changer.conf and/or amanda.conf
file(s) correctly. Instructions on doing this are in the comment section
of the chg-zd-mtx script. One gotcha, the file must have
a ".conf" extension but is listed in the amanda.conf file by just the
basename. So if you name the file "mats_mtx.conf" then in amand.conf
you just list "mats_mtx" as the changer file.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Prince
Re: amcheck errors
Joe Konecny wrote: Freebsd 5.2.1, amanda 2.4.4p2... compiled with user bin and group operator... I have no experience with freebsd. if I use this disklist... r4p17 amrd0s1f nocomp-root -1 local ...amcheck does nothing. I don't get a status report in mail. Amcheck always does something, when run on the command line. I suppose it says everyhing OK. When run as "amcheck -m" it only reports by mail if there are any errors. No news is good news in that case. Or do you mean that you don't get a report when running amdump either. if I use this disklist... r4p17 amrd0 nocomp-root -1 local ...amcheck gives me this error: ERROR: r4p17: [could not access amrd0 (amrd0): no such file or directory] As expected, I guess. I have no experience with freebsd. What are the names of the diskdevices in freebsd? It seems to me the normal block devices are /dev/amrd0s1f and not /dev/amrd0 (probably indicating the whole disk or raid array, and not a partition). Or did you expect something else? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amcheck errors
On Tuesday 18 May 2004 09:27, Joe Konecny wrote: >Freebsd 5.2.1, amanda 2.4.4p2... compiled with user bin >and group operator... I'd suspect that user=bin is too much. The normal is user=amanda, who is a member of the group disk or backup. Amanda being a totally unpriviledged, over 500 uid user. >if I use this disklist... >r4p17 amrd0s1f nocomp-root -1 local >...amcheck does nothing. I don't get a status >report in mail. > >if I use this disklist... >r4p17 amrd0 nocomp-root -1 local >...amcheck gives me this error: >ERROR: r4p17: [could not access amrd0 (amrd0): no >such file or directory] > >Any ideas? -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amcheck errors
On Tue, May 18, 2004 at 03:38:11PM +0200, Paul Bijnens wrote: > When run as "amcheck -m" it only reports by mail if there > are any errors. No news is good news in that case. That's my guess too. Try "amcheck -a". According to the man page: -a Like -m but the mail is always sent. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: amcheck errors
Olá Fábio, vc nao pode associar localhost no disklist, tambem passei por esse problema. Valeu - Original Message - From: "Fábio Mendonça Albuquerque Cunha" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 28, 2004 5:45 PM Subject: amcheck errors > Hello guys, > It's my first time trying to setup amanda and I am getting this output when I run amcheck : > > Amanda Tape Server Host Check > - > Holding disk /var/tmp: 194660 KB disk space available, that's plenty > NOTE: skipping tape-writable test > Tape DailySet101 label ok > Server check took 4.573 seconds > > Amanda Backup Client Hosts Check > > WARNING: localhost: selfcheck request timed out. Host down? > Client check: 1 host checked in 30.079 seconds, 1 problem found > > (brought to you by Amanda 2.4.2p2) > > My OS is Red Hat 8.0 > > Some could help me ? > > Regards, > > InfraNet Tecnologia > Fábio M. A. Cunha > (55 11) 5542-0941 ramal 22 > (55 11) 9603-6377 > www.infranetsp.com.br
Re: amcheck errors
On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: >Hello guys, >It's my first time trying to setup amanda and I am getting this > output when I run amcheck : > >Amanda Tape Server Host Check >- >Holding disk /var/tmp: 194660 KB disk space available, that's plenty >NOTE: skipping tape-writable test >Tape DailySet101 label ok >Server check took 4.573 seconds > >Amanda Backup Client Hosts Check > >WARNING: localhost: selfcheck request timed out. Host down? >Client check: 1 host checked in 30.079 seconds, 1 problem found > And we are back to the single, most covered in the docs, error. We don't mean to get short with newbies, but the use of localhost is a no-no. Please change your disklist entry to use the FQDN of the machine in question. Then, backup just a few days in the archives where I have posted the amanda file that goes in /etc/xinetd.d, and I'll mention that it may be you do not have the /home/(user)/.amandahosts file properly configured. Also, I suspect thats an rpm install, as 2.4.2p2 is getting pretty long in the tooth now. I'm running 2.4.5b1-20040510 snapshot here. While it is possible to beat the rpm versions around and make them work, generally speaking its a lot easier to build from the tarball, it takes me about 4 minutes to build each new snapshot and install it by use of the scripts I use here. >(brought to you by Amanda 2.4.2p2) > >My OS is Red Hat 8.0 > >Some could help me ? > >Regards, > >InfraNet Tecnologia >Fábio M. A. Cunha >(55 11) 5542-0941 ramal 22 >(55 11) 9603-6377 >www.infranetsp.com.br -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.23% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amcheck errors
Thanks Gene and Marcelo I run my backups and it's ok ! But now, when I try to recover this backup I get this output of amrecover: [EMAIL PROTECTED] DailySet1]# amrecover DailySet1 AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 asterix AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Why amanda is looking for a localhost, if I set up my .amandahosts like this : [EMAIL PROTECTED] amanda]# vi .amandahosts asterix amanda Someone could help me with this ? Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br On Fri, 28 May 2004 17:16:21 -0400, Gene Heskett escreveu: > De: Gene Heskett > Data: Fri, 28 May 2004 17:16:21 -0400 > Para: [EMAIL PROTECTED] > Assunto: Re: amcheck errors > > On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: > >Hello guys, > >It's my first time trying to setup amanda and I am getting this > > output when I run amcheck : > > > >Amanda Tape Server Host Check > >- > >Holding disk /var/tmp: 194660 KB disk space available, that's plenty > >NOTE: skipping tape-writable test > >Tape DailySet101 label ok > >Server check took 4.573 seconds > > > >Amanda Backup Client Hosts Check > > > >WARNING: localhost: selfcheck request timed out. Host down? > >Client check: 1 host checked in 30.079 seconds, 1 problem found > > > > And we are back to the single, most covered in the docs, error. We > don't mean to get short with newbies, but the use of localhost is a > no-no. Please change your disklist entry to use the FQDN of the > machine in question. > > Then, backup just a few days in the archives where I have posted the > amanda file that goes in /etc/xinetd.d, and I'll mention that it may > be you do not have the /home/(user)/.amandahosts file properly > configured. > > Also, I suspect thats an rpm install, as 2.4.2p2 is getting pretty > long in the tooth now. I'm running 2.4.5b1-20040510 snapshot here. > > While it is possible to beat the rpm versions around and make them > work, generally speaking its a lot easier to build from the tarball, > it takes me about 4 minutes to build each new snapshot and install it > by use of the scripts I use here. > > >(brought to you by Amanda 2.4.2p2) > > > >My OS is Red Hat 8.0 > > > >Some could help me ? > > > >Regards, > > > >InfraNet Tecnologia > >Fábio M. A. Cunha > >(55 11) 5542-0941 ramal 22 > >(55 11) 9603-6377 > >www.infranetsp.com.br > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.23% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com attorneys please note, additions to this message > by Gene Heskett are: > Copyright 2004 by Maurice Eugene Heskett, all rights reserved. > > >
Re: amcheck errors
On Friday 28 May 2004 18:34, Fábio Mendonça Albuquerque Cunha wrote: >Thanks Gene and Marcelo >I run my backups and it's ok ! >But now, when I try to recover this backup I get this output of > amrecover: > >[EMAIL PROTECTED] DailySet1]# amrecover DailySet1 >AMRECOVER Version 2.4.2p2. Contacting server on localhost ... >220 asterix AMANDA index server (2.4.2p2) ready. >500 Access not allowed: [access as amanda not allowed from > [EMAIL PROTECTED] amandahostsauth failed > >Why amanda is looking for a localhost, if I set up my .amandahosts > like this : > >[EMAIL PROTECTED] amanda]# vi .amandahosts >asterix amanda > >Someone could help me with this ? > Thats presuming that 'asterix' is an alias for the FQDN listed in your /etc/hosts file? And why is it using localhost? That doesn't work for amrecover as you've just found out. Also, perms on that file really should be 0600 although I recall a previous message that said it could be 0777 as far as amanda was concerned. Its just that its a security concern when made that freely accessable. And if you're running amrecover as root, I'd imagine that root also needs to be in that file too. However, if you have, as amanda, perms to write to some scratchpad dir for the recovery, then I'd imagine you could run amrecover as amanda. Personally, I've not done it. >Regards, > >InfraNet Tecnologia >Fábio M. A. Cunha >(55 11) 5542-0941 ramal 22 >(55 11) 9603-6377 >www.infranetsp.com.br > >On Fri, 28 May 2004 17:16:21 -0400, Gene Heskett escreveu: >> De: Gene Heskett >> Data: Fri, 28 May 2004 17:16:21 -0400 >> Para: [EMAIL PROTECTED] >> Assunto: Re: amcheck errors >> >> On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: >> >Hello guys, >> >It's my first time trying to setup amanda and I am getting this >> > output when I run amcheck : >> > >> >Amanda Tape Server Host Check >> >- >> >Holding disk /var/tmp: 194660 KB disk space available, that's >> > plenty NOTE: skipping tape-writable test >> >Tape DailySet101 label ok >> >Server check took 4.573 seconds >> > >> >Amanda Backup Client Hosts Check >> > >> >WARNING: localhost: selfcheck request timed out. Host down? >> >Client check: 1 host checked in 30.079 seconds, 1 problem found >> >> And we are back to the single, most covered in the docs, error. >> We don't mean to get short with newbies, but the use of localhost >> is a no-no. Please change your disklist entry to use the FQDN of >> the machine in question. >> >> Then, backup just a few days in the archives where I have posted >> the amanda file that goes in /etc/xinetd.d, and I'll mention that >> it may be you do not have the /home/(user)/.amandahosts file >> properly configured. >> >> Also, I suspect thats an rpm install, as 2.4.2p2 is getting pretty >> long in the tooth now. I'm running 2.4.5b1-20040510 snapshot >> here. >> >> While it is possible to beat the rpm versions around and make them >> work, generally speaking its a lot easier to build from the >> tarball, it takes me about 4 minutes to build each new snapshot >> and install it by use of the scripts I use here. >> >> >(brought to you by Amanda 2.4.2p2) >> > >> >My OS is Red Hat 8.0 >> > >> >Some could help me ? >> > >> >Regards, >> > >> >InfraNet Tecnologia >> >Fábio M. A. Cunha >> >(55 11) 5542-0941 ramal 22 >> >(55 11) 9603-6377 >> >www.infranetsp.com.br >> >> -- >> Cheers, Gene >> "There are four boxes to be used in defense of liberty: >> soap, ballot, jury, and ammo. Please use in that order." >> -Ed Howdershelt (Author) >> 99.23% setiathome rank, not too shabby for a WV hillbilly >> Yahoo.com attorneys please note, additions to this message >> by Gene Heskett are: >> Copyright 2004 by Maurice Eugene Heskett, all rights reserved. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.23% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amcheck errors
On Friday 28 May 2004 18:34, Fábio Mendonça Albuquerque Cunha wrote: >Thanks Gene and Marcelo My second reply to this post after I'd thought about it a bit. >I run my backups and it's ok ! >But now, when I try to recover this backup I get this output of > amrecover: > >[EMAIL PROTECTED] DailySet1]# amrecover DailySet1 >AMRECOVER Version 2.4.2p2. Contacting server on localhost ... >220 asterix AMANDA index server (2.4.2p2) ready. >500 Access not allowed: [access as amanda not allowed from > [EMAIL PROTECTED] amandahostsauth failed > >Why amanda is looking for a localhost, if I set up my .amandahosts > like this : > >[EMAIL PROTECTED] amanda]# vi .amandahosts >asterix amanda > >Someone could help me with this ? > Is this from an rpm install? The reason I ask is that the tape-servers FQDN (in your case localhost) is compiled into amanda when its built. Your initial invocation of amrecover should have looked like this: [EMAIL PROTECTED] root]# amrecover DailySet1 AMRECOVER Version 2.4.5b1-20040510. Contacting server on coyote.coyote.den ... 220 coyote AMANDA index server (2.4.5b1-20040510) ready. 200 Access OK Setting restore date to today (2004-05-28) 200 Working date set to 2004-05-28. Scanning /dumps... 200 Config set to DailySet1. 501 Host coyote.coyote.den is not in your disklist. Trying host coyote.coyote.den ... 501 Host coyote.coyote.den is not in your disklist. Trying host coyote ... 200 Dump host set to coyote. Trying disk /root ... $CWD '/root' is on disk '/root' mounted at '/root'. 200 Disk set to /root. /root amrecover> As you can see, it looked for the FQDN of the machine, then finally settled for its alias as listed in /etc/hosts. This is just one of the many reasons one should build amanda from scratch, those rpms are broken if 'localhost' is compiled in. One could even say they are drain bamaged. :-) If thats the case, rpm -e those broken rpms. Then get the latest tarball of the 2.4.5b1 series from a link near the bottom of the front page at amanda.org. Configuring and building amanda requires an unpriviledged user, such as amanda, who should be a member of some much higher group such as disk or backup. I've had to unpack amanda as root on a few occasions even though I'm sitting in the /home/amanda directory when I do the unpack. In that event, while still root, do a 'chown -R amanda:disk name-of-amanda-dir' to fix up the perms so amanda can build it. Here is the script I use, copied into the top level dir the tarball unpacks to, and then run as the user amanda here at this hillbillies house: -- #!/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 # the next 2 lines are in case you've changed something and are # rebuilding amanda again. 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 --- adjust the tape-server to your machines FQDN. Delete the changer-device= line if you don't have one. Set the exec bit on this script, and do a './whatever-name-you-gave-it', or use a child of sh and do 'sh ./whatever-etc' This will configure and make amanda, which takes about 3 minutes on this machine. Then become root, and do the 'make install', which takes another minute or so. That will get rid of the localhost stuff as long as you don't have any localhosts in your disklist. Then we can sort your next problems knowing we have a good install to work with. >Regards, > >InfraNet Tecnologia >Fábio M. A. Cunha >(55 11) 5542-0941 ramal 22 >(55 11) 9603-6377 >www.infranetsp.com.br > >On Fri, 28 May 2004 17:16:21 -0400, Gene Heskett escreveu: >> De: Gene Heskett >> Data: Fri, 28 May 2004 17:16:21 -0400 >> Para: [EMAIL PROTECTED] >> Assunto: Re: amcheck errors >> >> On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: >> >Hello guys, >> >It's my first time trying to setup amanda and I am getting this >> > output when I run amcheck : >> > >> >Amanda Tape Server Host Check >> >- >> >Holding disk /var/tm
Re: amcheck errors
>Here are the problems that I am currently having. ...
All the NOTE lines about things not existing may be ignored -- they are
for a new disk/client/whatever and will be created for you during the
normal run.
>ERROR: slowsrv: could not resolve hostname
This says Amanda could not look up host name "slowsrv", i.e. a call to
gethostbyname("slowsrv") reported an error, which must be some kind of
configuration problem with your machine.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck errors
> 104 holdingdisk /dev/dsk/c0t1d0s4 {
Well, that's a new one. :-)
The "name" (where you put "/dev/dsk/c0t1d0s4") of a holdingdisk is
just some text string. It's not even used anyplace else in Amanda.
So try something like this:
holdingdisk c0t1d0s4 {
directory "/export/home/dumps"
use 1700 Mb
chunksize 1Gb
}
Or this:
holdingdisk who_cares {
directory "/export/home/dumps"
use 1700 Mb
chunksize 1Gb
}
>Brandon Amundson
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amcheck errors with ADIC FastStor (dlt8000)
--On Friday, April 12, 2002 11:21:23 -0700 Joshua Hamor <[EMAIL PROTECTED]> wrote: > This is what i get everyday from my cron job of amcheck. Any ideas? > >> Amanda Tape Server Host Check >> - >> Holding disk /dumps/amanda: 14044688 KB disk space available, that's plenty >> amcheck-server: slot 2: date 20020318 label C5102 (active tape) >> amcheck-server: slot : no tape online >> amcheck-server: fatal slot mt:: /dev/nrst0: Input/output error >> ERROR: label C5103 or new tape not found in rack >> (expecting tape C5103 or a new tape) It looks like it checked the label on the tape in the drive, saw that it was the previous day's, tried to get the changer to get the right tape and then was unable to read the label for some reason (no tape, wrong tape, drive not ready, etc.) that the changer script couldn't handle. If you rerun amcheck again without touching anything and it is happy, I suspect that the changer script needs to wait longer after the tape change before trying to read the label to give the changer time to insert the next tape and for the drive to rewind. Otherwise try watching the library while you run amcheck and see what it is trying to do, and how far along it gets before it returns the error. Good luck, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amcheck errors with ADIC FastStor (dlt8000)
Joshua Hamor wrote: > > >Amanda Tape Server Host Check > >- > >Holding disk /dumps/amanda: 14044688 KB disk space available, that's plenty > >amcheck-server: slot 2: date 20020318 label C5102 (active tape) > >amcheck-server: slot : no tape online > >amcheck-server: fatal slot mt:: /dev/nrst0: Input/output error Do you actually have a changer or just a single tape drive? -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
