Think about the configuration as having network -- it's just that the
machine you are connecting to is the local machine. You have to
configure your setup for that just like you would if it were across the
wire.
Also, in general, be sure to check your logs. Not only the amanda logs
in /tmp/amanda/, but the logs in /var/adm/. I've figured out some pretty
odd-ball stuff by looking through logs. For example, /var/adm/authlog
showed me that one client I had configured and addressed via one subnet
was coming back at me with a name based on it's presence in another
subnet that it was multihomed on. Changing my .amandahosts fixed that,
although I ought to go back and see why the client did what it did. I
also saw an instance where an error was reported with an IPv6 address,
but I had not installed or configured IPv6. I think when Solaris failed
on the connection, it was trying alternatives and reported the last
thing it tried, but that could just be my imagination running wild.
Anyway, it was another minor configuration error discovered by reading
log files.
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<hoogendyk AT bio.umass DOT edu>
---------------
Erdös 4
Jean-Louis Martineau wrote:
> Maybe localhost resolv to an IPv6 address and that network is not
> configured?
> >grep localhost /etc/hosts
> >netstat -nr
> Add 'debug_auth 1' to amanda.conf and retry.
> Post the taper.*.debug and dumper.*.debug files.
>
> Jean-Louis
>
> Paul Crittenden wrote:
>>
>> I have set up amanda-2.5.2p1 on Solaris 9, with it being the server
>> and client. I have run amcheck with no errors. I can label tapes but
>> when I run an amdump It fails. Here is the email I get.
>>
>> Date: Thu, 21 Jun 2007 12:54:16 -0500 (CDT)
>>
>> From: amanda AT simpson DOT edu
>>
>> Message-Id: <200706211754.l5LHsGB8010655 AT maple.simpson DOT edu>
>>
>> To: amanda AT maple.simpson DOT edu
>>
>> Subject: DailySet1 AMANDA MAIL REPORT FOR June 21, 2007
>>
>> Content-Length: 1971
>>
>> Hostname: maple
>>
>> Org : DailySet1
>>
>> Config : maple
>>
>> Date : June 21, 2007
>>
>> These dumps were to tape DailySet1-1.
>>
>> The next tape Amanda expects to use is: a new tape.
>>
>> FAILURE AND STRANGE DUMP SUMMARY:
>>
>> maple.simpson.edu /export/home/pdc lev 0 FAILED [port open: Network
>> is unreachable]
>>
>> maple.simpson.edu /export/home/pdc lev 0 FAILED [dump to tape failed]
>>
>> STATISTICS:
>>
>> Total Full Incr.
>>
>> -------- -------- --------
>>
>> Estimate Time (hrs:min) 0:00
>>
>> Run Time (hrs:min) 0:02
>>
>> Dump Time (hrs:min) 0:00 0:00 0:00
>>
>> Output Size (meg) 0.0 0.0 0.0
>>
>> Original Size (meg) 0.0 0.0 0.0
>>
>> Avg Compressed Size (%) -- -- --
>>
>> Filesystems Dumped 0 0 0
>>
>> Avg Dump Rate (k/s) -- -- --
>>
>> Tape Time (hrs:min) 0:00 0:00 0:00
>>
>> Tape Size (meg) 0.0 0.0 0.0
>>
>> Tape Used (%) 0.0 0.0 0.0
>>
>> Filesystems Taped 0 0 0
>>
>> Chunks Taped 0 0 0
>>
>> Avg Tp Write Rate (k/s) -- -- --
>>
>> USAGE BY TAPE:
>>
>> Label Time Size % Nb Nc
>>
>> DailySet1-1 0:00 0K 0.0 0 0
>>
>>
>> FAILED AND STRANGE DUMP DETAILS:
>>
>> /-- maple.simpson.edu /export/home/pdc lev 0 FAILED [port open:
>> Network is unreachable]
>>
>> \--------
>>
>>
>> NOTES:
>>
>> planner: Forcing full dump of maple.simpson.edu:/export/home/pdc as
>> directed.
>>
>> taper: tape DailySet1-1 kb 0 fm 0 [OK]
>>
>>
>> DUMP SUMMARY:
>>
>> DUMPER STATS TAPER STATS
>>
>> HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
>>
>> -------------------------- -------------------------------------
>> -------------
>>
>> maple.simpso -t/home/pdc 0 FAILED
>> --------------------------------------------
>>
>> (brought to you by Amanda version 2.5.2p1)
>>
>> Since this is the same machine why does it care about the network?
>> Obviously I don’t understand something.
>>
>> Paul Crittenden
>>
>> Computer Systems Manager
>>
>> Simpson College
>>
>> Phone: 515-961-1680
>>
>> Email: paul.crittenden AT simpson DOT edu
|
