From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.9-12 i686)
Description of problem:
[ --with-portrange=low,high bind unreserved TCP server sockets to
ports within this range [unlimited]],
but common-src/stream.c stream_client() says
if (bind_portrange(client_socket, &claddr, PORTRANGE) == 0)
so that --with-portrange applies to client sockets too. This means that
amrecover doesn't work if the portrange is >1023.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Rebuild amanda with --with-portrange=<unreserved portrange>
Actual Results: amrecover: did not get a reserved port: <port #>
Expected Results: amrecover should work
--with-portrange is needed to do amanda backups with strong firewalls in
We don't build it that way, sounds like a local configuration issue. If you want
to change the ports the server is listening to, you can just change the ports in
the files in /etc/xinetd.d?
No, these are (usually high) ports that are used for streaming backup data. In your configuration amanda chooses any available port regardless of
the contents of /etc. But I'm not comfortable opening all ports between these machines, so I rebuilt amanda with the --with-portrange option. The
remarks in the configure script indicate that the --portrange option applies to servers only, but as delivered in your SRPM it applies to clients also. If
you feel this is not your problem, I can just upstream it.
Current amanda CVS takes a different (also effective) approach to my complaint. From the comments on the last revision:
Add stream_client_privileged() function to get a
privileged port and fail if one is not available.
The older stream_client() function gets a (non-privileged)
port in the configured portrange, if set and possible,
else anything available.
Use stream_client_privileged() in amrecover instead of
OK, we'll get that when amanda is updated next.
FWIW, the stream_client patch (from CVS) was recently posted to http://www.amanda.org/patches.html.
Today's the day for cleaning up old bugs. It looks like this has been
fixed for a long time now.