Rebecca Pakish Crum wrote:


But the backups fail.  Checking the logs in /tmp/amanda (on the
clients), I see things like:

sendbackup: time 0.000: stream_server: waiting for connection:
0.0.0.0.33011
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.33012
sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.33013
sendbackup: time 0.001: waiting for connect on 33011, then


33012, then

33013
sendbackup: time 29.991: stream_accept: timeout after 30 seconds
sendbackup: time 29.991: timeout on data port 33011
sendbackup: time 59.991: stream_accept: timeout after 30 seconds
sendbackup: time 59.991: timeout on mesg port 33012
sendbackup: time 89.991: stream_accept: timeout after 30 seconds
sendbackup: time 89.991: timeout on index port 33013
sendbackup: time 89.991: pid 1873 finish time Thu Jan 8


01:05:15 2004


All hosts were configured with:

--with-tcpportrange=850,854 --with-udpportrange=850,854

So why am I getting connections on port 33011? I have

850-854 opened


on the firewall, but if it's trying to connect on 33xxx

then of course

it's not going to work.

On the server, my /etc/services has:

amanda 850/udp # amanda

backup services


amanda 850/tcp
kamanda 851/tcp # amanda backup services (Kerberos)
kamanda 851/udp # amanda backup services (Kerberos)
amandaidx 852/tcp # amanda


backup services


amidxtape 853/tcp # amanda

backup services


The clients have:

amanda 850/udp
amanda 850/tcp
kamanda 851/udp
amandaidx 852/tcp



All I can tell you is that for me to be able to back up my firewall, I had to create a rule that allowed my amanda server full access to all of my high ports (>1023). I had this problem and this is what Joshua from this listserv came back with. Worked like a charm. I would suggest trying this.




I suppose that could be the next option, but it still does not explain why amanda is connecting on port 33xxx when I compiled with restrictions to ports 850-854. I'm hoping someone can explain some of this to me.

Mike

Reply via email to