|
Re: running amdump manually at the moment with extra debugging enabled
2007-09-28 10:08:42
Jean-Louis Martineau wrote:
Craig Dewick wrote:
6 root@jedi #----> more dumper.20070928130458000.debug
dumper: debug 1 pid 15243 ruid 982 euid 0: start at Fri Sep 28
13:04:58 2007
dumper: debug 1 pid 15243 ruid 982 euid 0: rename at Fri Sep 28
13:04:58 2007
dumper: time 173.205: connect_port: Try port 0: Available -
dumper: time 173.212: connect_portrange: connect from ::.35127
failed: Network is unreachable
dumper: time 173.213: connect_portrange: connect to ::1.35126 failed:
Network is unreachable
dumper: time 173.213: stream_client: Could not bind to port in range
0-0.
localhost resolv to '::1', which is an IPv6 address, but you doesn't
have IPv6 configured.
Why localhost resolv to '::1' instead of 127.0.0.1?
Check your host table configuration, starting from /etc/nsswitch.conf
amanda use the getaddrinfo function to get the address of localhost.
Also, on Solaris, I found /etc/inet/ipnodes as having a reference to
'::1', and commented it out.
However, in my case when those addresses turned up, it was because the
IPv4 addresses had failed and it was doing some sort of fallback check
on IPv6. I've had trouble totally getting rid of the references to IPv6.
But usually the reason it shows up is because of some other failure. So
the error messages I see with it are misdirections or obfuscations.
So, Craig, DO you have IPv6 set up? Or is this a misleading error
subsequent to some other failure?
---------------
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
|
|
|
