On Tue, 30 Apr 2002 [EMAIL PROTECTED] wrote: > Hi :-) - I have installed amanda 2.4.2p2 on my SuSE 7.2, just like I have > read in the > docu. > I want it to run with my "onstream DI-30" tape-drive. > After installation I tried to run "./amcheck Daily", and it returned: > ----------------------------------------------------------------------- > linux:/usr/local/sbin # ./amcheck Daily > Amanda Tape Server Host Check > ----------------------------- > Holding disk /dumps/amanda: 16293988 KB disk space available, that's plenty > ERROR: cannot overwrite active tape DailySet100 > (expecting a new tape) > NOTE: skipping tape-writable test > 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: does not exist > Server check took 2.435 seconds > > Amanda Backup Client Hosts Check > -------------------------------- > ERROR: salty: could not resolve hostname > ERROR: slithy: could not resolve hostname > ERROR: master: could not resolve hostname > ERROR: slowsrv: could not resolve hostname > ERROR: bigwig: could not resolve hostname > ERROR: bozo: could not resolve hostname > ERROR: joespc: could not resolve hostname > ERROR: cleo: could not resolve hostname > ERROR: susie: could not resolve hostname > Client check: 9 hosts checked in 15.697 seconds, 9 problems found > > (brought to you by Amanda > 2.4.2) > > > ----------------------------------------------------------------------------- > > I am able to ping the computer by name, but I don't think that has something > to du > with my problem... > To me it looks that the directorys mentioned above (curinfo and indes) are > not being > created (they don't exist at start... > >
Those directories will be created when you actually run amdump. That is normal for amcheck to report when new hosts are added. You should be more concerned about the hostname resolution problem though. Casey
