The problem is:
dumper: connect_portrange: connect from 0.0.0.0.585 failed: Operation
timed out
dumper: connect_portrange: connect to 209.123.46.114.10080 failed:
Operation timed out
dumper: stream_client: Could not bind to port in range 512-1023.
Could you try the attached patch?
Jean-Louis
Amanda try to use proviledged port in the range 512-1023.
It will not use port reserved for other services, as listed in
/etc/services.
There is less port available for tcp than udp.
Which amanda version are you using?
What is your OS?
Did it list all port from 512 to 1026 or it jump from 603
On Mon, 30 Apr 2007, Jean-Louis Martineau wrote:
Amanda try to use proviledged port in the range 512-1023.
It will not use port reserved for other services, as listed in /etc/services.
There appear to be very few ports available in that range.
There is less port available for tcp than udp.
Any ideas on this one? Should I just consider it a bug?
I'm not clear at all on why the server is picking a port over 1024, but
that does seem to be clearly happening, and then the client is rejecting
it (which does seem to be by design). FWIW, I *cannot* reproduce it when
firing off one
The dumper must be installed suid root.
What's in the dumper.timestamps.debug file?
Jean-Louis
Charles Sprickman wrote:
Any ideas on this one? Should I just consider it a bug?
I'm not clear at all on why the server is picking a port over 1024,
but that does seem to be clearly happening, and
On Sun, 29 Apr 2007, Jean-Louis Martineau wrote:
The dumper must be installed suid root.
[devel2]/tmp/amanda/server/DailySet1 # ls -l
/usr/local/libexec/amanda/dumper
-r-sr-x--- 1 root operator 30344 Mar 14 01:54
/usr/local/libexec/amanda/dumper
What's in the dumper.timestamps.debug
Hi all,
This is my last problem for the time being...
Server side reports this (amdump.1):
driver: result time 2126.498 from dumper2: TRY-AGAIN 02-9 NAK: host
h-74-0-x-28.phlapafg.covad.net: port 1026 not secure
The IP address there is the amanda server.
Client side reports this
