Hello John R.! sorry for the late answer, I was very busy;) > -----Ursprüngliche Nachricht----- > Von: John R. Jackson [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 18. Juni 2001 21:31 > An: Michael Fritsch > Cc: [EMAIL PROTECTED]; Daniel Schwager > Betreff: Re: FreeBSD && amrecover: Port-Probs > > > >AMRECOVER Version 2.4.2p2. Contacting server on serv ... > >amrecover: did not get a reserved port: 50090 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > What's in /tmp/amanda/amrecover*debug? > serv>amanda# amrecover AMRECOVER Version 2.4.2p2. Contacting server on am-index ... amrecover: did not get a reserved port: 50065 serv>amanda# less amrecover.20010702165940.debug amrecover: debug 1 pid 726 ruid 0 euid 0 start time Mon Jul 2 16:59:40 2001 amrecover: stream_client: connected to 192.168.1.250.10082 amrecover: stream_client: our side is 0.0.0.0.50065 did not get a reserved port: 50065 amrecover: pid 726 finish time Mon Jul 2 16:59:41 2001 > >Also Telnet cannot connect. > > Does amindexd start on the server? If so, what's in > /tmp/amanda/amindexd*debug when you try this? serv>amanda# less amindexd.20010702165941.debug amindexd: debug 1 pid 727 ruid 80 euid 80 start time Mon Jul 2 16:59:41 2001 amindexd: version 2.4.2p2 < 220 serv AMANDA index server (2.4.2p2) ready. ? read error: Connection reset by peer amindexd: pid 727 finish time Mon Jul 2 16:59:42 2001 > If not, then you must have some other system configuration problem that's locking > out the connection (e.g. TCP wrappers). > Any hints more? Michael Fritsch infinis GmbH
