rsh - rcmd socket failure 1

[art15t]

Hi,

I have just encountered a problem with rsh where I had an overnight dispatch of files from one machine to another.

rsh returned:

rcmd: socket: Cannot assign requested address

Is there a tunable kernel parameter to increase nuber of sockets or is there some limitation with rsh. I killed of the overnight a few of the overnight dispatch processes and rsh was once again functioning.

Any ideas?

 

[J1mbo]

Have a look at this:

http://www.sunmanagers.org/pipermail/summaries/2002-February/002439.html

-jim

 

[art15t]

Many Thanks J1mbo!

That was just what i was looking for! Excellent mate!!

ART

 

[aramasw1]

Guys,
Could you please repost the solution to "rcmd: socket: Cannot assign requested address" problem again?
That website Jim referred to is no longer available and I would like to know the solution.
We are facing the same problem and tcp_time_wait_interval is set to 60 secs by default.
So I need a better solution.
Thanks

Anand

 

[art15t]

Well it's been a while since I had this problem and I think if I recall I upped the file handles in /etc/system and reduced the time wait to 30 seconds. Additonally, this was caused because I moved the app from a sparc20 to a V880 and the io was dramatically improved such that when I ran several batch in parallel it took just a matter of seconds to use up all the available port/sockets. The solution also involved checking for the error before establishing a connection. This together with reducing the number of parallel tasks solved the issue and I no longer came to work the next day to find the overnight batch had failed!

ART