Hi,
Amrecover wants a reserved port (<=1024) for itself. Seems like you have
to rebuild it ;-). (Dunno *why*, but it does...)
Regards,
Arjan
Nate Burton wrote:
>
> I was able to run amdump and it appears that everything ran and backed up
> correctly, based on the logs and the Amanda report. Now I am trying to test
> and see if I can recover some files.
>
> When I run amrecover it is not connecting:
> admin2 is the client, admin1 is the server
>
> --------------------------------------------------------------------
> [root@admin2 amanda]# /usr/local/amanda/sbin/amrecover -C TestSet -s
> admin1.airscorp.com -t admin1.airscorp.com -d /dev/nst0
> AMRECOVER Version 2.5.0. Contacting server on admin1.airscorp.com ...
> amrecover: did not get a reserved port: 50012
> --------------------------------------------------------------------
> [root@admin2 amanda]# cat /tmp/amanda/amrecover.20010612111330.debug
> amrecover: debug 1 pid 8340 ruid 0 euid 0 start time Tue Jun 12 11:13:30 2001
> amrecover: stream_client: connected to 10.0.4.91.10082
> amrecover: stream_client: our side is 0.0.0.0.50012
> did not get a reserved port: 50012
> amrecover: pid 8340 finish time Tue Jun 12 11:13:30 2001
> --------------------------------------------------------------------
>
> I believe I have setup the .amandahosts file correctly, I added a line for
> admin2 with the user 'root' on the server admin1.
>
> Amanda was built with '--with-portrange=50000,50020' and it appeared to use
> those ports correctly when the backup was being performed, but why can it not
> get the reserved port now?
>
> The systems are admin1(Redhat 6.2), admin2(Redhat 7.1), Amanda cvs code from
> 6/04/01.
>
> Thanks
