Dustin & Jean-Louis,
Dustin, thanks for the analysis and is seems to make sense because
indeed in the /etc/services only 703 and 708 are unassigned in between
700-710. However, my amanda is installed from rpm from the download
area of amanda (opensuse 10), and I really hesitate to do a compile
from source. In amanda.conf maxdumps was set to 3; I have set it now
to 2, would that not solve the problem because 2 ports are available?
Jean-Louis,
I did send my /etc/hosts to Dustin and it is:
"
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
127.0.0.2 fiume.localnet fiume
# my additions CSt
192.168.1.66 stremen.localnet stremen.xs4all.nl stremen
192.168.1.65 fiume.localnet fiume
192.168.1.250 corrente.localnet corrente
"
I have little knowledge about the meaning of all this and above the
line with CSt, it is generated (I think). Is it not simply that
localhost (== fiume, == fiume.localnet) can be addressed as 127.0.0.1
or 127.0.0.2?
Today there was no problem with amandabackup, tomorrow it will run with
maxdumps = 2.
Regards,
Charles
On Mon, 14 Apr 2008 16:15:52 -0400
Jean-Louis Martineau <martineau AT zmanda DOT com> wrote:
> Subject: Re: failures in 2.6.0 ("cannot read header ...")
> Charles, Dustin,
>
> I think the 127.0.0.2 is the source of the problem.
> Check the named configuration and host database, NIS, /etc/hosts.
> Why the hostname (fiume.localnet) resolve to 127.0.0.2?
> Do you have an interface configured for 127.0.0.2?
>
> Jean-Louis
>
> Dustin J. Mitchell wrote:
> > On Fri, Apr 11, 2008 at 4:05 PM, Charles Stroom
> > <charles AT stremen.xs4all DOT nl> wrote:
> >
> >> Many thanks for the offer. I will send you the last 3 days to your
> >> email address.
> >>
> >
> > OK, the 172.0.0.2 stuff is definitely weird, but doesn't seem to be
> > causing the problem. Here's what I found in the dumper debug logs:
> >
> > 1207905486.973842: dumper: security_getdriver(name=bsdtcp) returns
> > 0xb7e7b1e0
> > 1207905486.973863: dumper: security_handleinit(handle=0x805b110,
> > driver=0xb7e7b1e0 (BSDTCP))
> > 1207905486.973900: dumper: security_streaminit(stream=0x805b1d8,
> > driver=0xb7e7b1e0 (BSDTCP))
> > 1207905486.978126: dumper: connect_port: Skip port 700: owned by epp.
> > 1207905486.978613: dumper: connect_port: Skip port 701: owned by lmp.
> > 1207905486.979098: dumper: connect_port: Skip port 702: owned by iris-beep.
> > 1207905486.982921: dumper: connect_port: Try port 703: available - Success
> > 1207905486.982936: dumper: connect_portrange: Connect from 0.0.0.0.703
> > failed: Cannot assign requested address
> > 1207905486.982944: dumper: connect_portrange: connect to
> > 127.0.0.2.10080 failed: Cannot assign requested address
> > 1207905486.983435: dumper: connect_port: Skip port 704: owned by elcsd.
> > 1207905486.983921: dumper: connect_port: Skip port 705: owned by agentx.
> > 1207905486.984410: dumper: connect_port: Skip port 706: owned by silc.
> > 1207905486.984896: dumper: connect_port: Skip port 707: owned by
> > borland-dsj.
> > 1207905486.988626: dumper: connect_port: Try port 708: available - Success
> > 1207905486.988638: dumper: connect_portrange: Connect from 0.0.0.0.708
> > failed: Cannot assign requested address
> > 1207905486.988646: dumper: connect_portrange: connect to
> > 127.0.0.2.10080 failed: Cannot assign requested address
> > 1207905486.989138: dumper: connect_port: Skip port 709: owned by
> > entrust-kmsh.
> > 1207905486.989677: dumper: connect_port: Skip port 710: owned by
> > entrust-ash.
> > 1207905486.989685: dumper: connect_portrange: All ports between 700
> > and 710 are busy.
> > 1207905486.989691: dumper: stream_client: Could not bind to port in
> > range 700-710.
> > 1207905486.989702: dumper: security_seterror(handle=0x805b110,
> > driver=0xb7e7b1e0 (BSDTCP) error=Resource temporarily unavailable)
> > 1207905486.989710: dumper: security_close(handle=0x805b110,
> > driver=0xb7e7b1e0 (BSDTCP))
> > 1207905486.989720: dumper: security_stream_close(0x805b1d8)
> >
> > So Amanda was compiled with a port range of 700-710. Of those, only
> > 703 and 708 are not registered with a service name in /etc/services,
> > so Amanda tried both of those ports, and got "Cannot assign requested
> > address" (EADDRNOTAVAIL). Amanda then summed that up with the
> > (admittedly totally uninformative) error "Resource temporarily
> > unavailable" (EAGAIN).
> >
> > Amanda is probably failing on those two ports because another dumper
> > is already using them. On "good" days, Amanda manages to get each DLE
> > dumped via an open port, perhaps after retrying a few times. On bad
> > days, a dumper or two gets retried too many times, and Amanda gives
> > up.
> >
> > The solution is for you to rebuild Amanda with a bigger range of ports
> > or (if you're feeling hackish) to remove the other services in that
> > range from your /etc/services. I'll look into changing the error
> > message.
> >
> > HTH
> > Dustin
> >
> >
>
Charles Stroom
email: charles at stremen dot xs4all dot nl
|
