TruCluster
Showing results for 
Search instead for 
Do you mean 

rsh failed to cluster alias, rsh succeeded on each node

SOLVED
Go to Solution
Occasional Advisor

rsh failed to cluster alias, rsh succeeded on each node

Hi all,
I noticed a strange problem on my network these days :
I'm not able to rsh to my cluster aliases, but i'm able to rsh to each of the nodes.

$ rsh node1 id
uid=200(cros) gid=0(system) groups=200(nsgroup)
$ rsh node2 id
uid=200(cros) gid=0(system) groups=200(nsgroup)
$ rsh cluster-alias id
protocol failure in circuit setup

This happens on 3 clusters, whom configuration were not changed during last weeks.

I guess this is a network/firewall issue, but i'm searching an explanation.
Any ideas/tips welcome.
6 REPLIES
Honored Contributor

Re: rsh failed to cluster alias, rsh succeeded on each node

I see a couple of hits within ITRC (using 'Search')...see if it helps.
Honored Contributor

Re: rsh failed to cluster alias, rsh succeeded on each node

Ensure that you have the following configuration in the /etc/clua_services file:

exec 512/tcp in_multi,out_alias,static
login 513/tcp in_multi,out_alias,static

Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Occasional Advisor

Re: rsh failed to cluster alias, rsh succeeded on each node

No modifications done on the clusters, and we were able to rsh in the past.
Honored Contributor

Re: rsh failed to cluster alias, rsh succeeded on each node

Any changes to the DNS/hosts configuration or in the DNS server?

The firewall you are talking about is in front of the server and your client computer?

Can you rsh from the cluster nodes to the cluster alias?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Occasional Advisor

Re: rsh failed to cluster alias, rsh succeeded on each node

>Any changes to the DNS/hosts configuration or in the DNS server?
no, as far as i know :-)

> Can you rsh from the cluster nodes to the cluster alias?
Yes, i can.
Honored Contributor

Re: rsh failed to cluster alias, rsh succeeded on each node

From the Internet:


If you use rsh and get "protocol failure in circuit setup", this means that the reverse connection for the stderr channel is filtred somewhere in your network.

From the rshd man page:

The server checks the client's source port. If the port is not in the range 512 to 1023, the server aborts the connection.

You can use tcpdump to verify if the client is connecting from one of these ports. This may be a problem with the client.

See also:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=41854
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
//Add this to "OnDomLoad" event