>Everything was running smoothly until about 30 days ago.
So the obvious question is, what did you change 30 days ago :-)?
>driver: dumping sv:da0s1f directly to tape
>driver: send-cmd time 3469.442 to taper: PORT-WRITE 00-00035 sv da0s1f 0 20001219
>driver: result time 3469.442 from taper: PORT 1596
This says driver told taper to get ready to do a direct to tape dump.
Taper created a local socket and reported back the port number, 1596.
All normal so far.
>driver: send-cmd time 3469.443 to dumper0: PORT-DUMP 01-00036 1596 sv da0s1f 0
>1970:1:1:0:0:0 DUMP |;bsd-auth;compress-best;index;
This is driver then telling dumper0 to start the direct to tape dump
and that taper is listening on port 1596. Still normal.
>driver: result time 3469.444 from dumper0: FAILED 01-00036 [taper port open:
>Connection refused]
This says dumper0 was not able to create the connection to taper due to
"Connection refused".
>driver: result time 3589.442 from taper: TAPE-ERROR 00-00035 [port connect timeout]
Finally, this says taper got tired of waiting on a dumper to connect.
So the real problem is why dumper could not connect to taper on localhost,
and I'm afraid I don't have any good ideas. It's possible for that error
to come out of stream_client in several places (although I strongly
suspect it's the connect() call). The following patch will log which
place threw the error (it's just for debugging, not a fix). You only
need to rebuild/install the server, not the clients.
Did you do anything "odd" with your network setup that would cause it
to be confused about what "localhost" means?
>Helio.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
stream.diff
