Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem after going to ML4 on 5.1

Status
Not open for further replies.

Breslau

Technical User
Jul 14, 2003
278
US
I'm seeing the following error using a 3rd party file transfer program:

RPC: Unable to send; errno = Broken pipe

i can do a rpcinfo on the server side to the client (which had ml4 applied on it) and get a response back showing the desired port open on the client. another host, at ml3 does not show the same error and is able to connect to the particular server. i can also make my ml3 host a server and get the same error when the ml4 host tries to contact it.

my ml3 host will show a more detailed error:

RPC: 1832-006 Unable to send; errno = There is no proce
ss to read data written to a pipe.

i tried to look up this error code but did not find anything usefull, anyone have an idea?

thanks!
 
ok, i gave in and called ibm about this problem, i also sniffed the lan interface on the host with the problem and saw that the app was accepting an rpc request from another host but was then receiving a fin/ack immediately after that.

ibm suggested we update libc to 5.1.0.54, which corrected the issue. apparently the move to ml4 made rpc unhappy. i had also updated tcp.client to 55.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top