<div><br>Hi, I use mpich and freebsd for make a cluster, ,I Have 3 nodes and one master node</div>
<div>I think, that I configured the rsh and ssh, i can log in for all nodes with this, </div>
<div>in the file, inetd.conf i change to enable the rshd and rlogin, i have the file .rhosts, i configured the hosts.allow, hosts.equiv</div>
<div> </div>
<div>in the file sshd_config enabled the permitrootlogin yes</div>
<div> </div>
<div>i put my nodes in the file /...mpich/share/machines.freebsd whit the ip<br> </div>
<div>I use the tstmachines to test the nodes qith the master node, but i cant, this is the report,,.please help me, please</div>
<div><br><br>nodo1# ./tstmachines -v<br>Trying true on <a href="http://192.168.1.1">192.168.1.1</a> ...<br>Errors while trying to run rsh <a href="http://192.168.1.1">192.168.1.1</a> -n true<br>Unexpected response from <a href="http://192.168.1.1">
192.168.1.1</a>:<br>--> select: protocol failure in circuit setup<br>If your .cshrc, login, .bashrc, or other startup file<br>contains a command that generates any output when logging in,<br>such as fortune or hostname or even echo, you should modify
<br>that startup file to only print such a message when the<br>process is attached to a terminal. Examples of how to do<br>this are in the Users Manual. If you do not do this, MPICH<br>will still work, but this script and the test programs will
<br>report problems because they compare expected output from<br>what the programs produce.<br>Trying true on <a href="http://192.168.1.10">192.168.1.10</a> ...<br>Unexpected response from <a href="http://192.168.1.10">192.168.1.10
</a>:<br>--> rshd: Login incorrect.<br>If your .cshrc, login, .bashrc, or other startup file<br>contains a command that generates any output when logging in,<br>such as fortune or hostname or even echo, you should modify
<br>that startup file to only print such a message when the<br>process is attached to a terminal. Examples of how to do<br>this are in the Users Manual. If you do not do this, MPICH<br>will still work, but this script and the test programs will
<br>report problems because they compare expected output from<br>what the programs produce.<br>Trying true on <a href="http://192.168.1.11">192.168.1.11</a> ...<br>Unexpected response from <a href="http://192.168.1.11">192.168.1.11
</a>:<br>--> select: protocol failure in circuit setup<br>If your .cshrc, login, .bashrc, or other startup file<br>contains a command that generates any output when logging in,<br>such as fortune or hostname or even echo, you should modify
<br>that startup file to only print such a message when the<br>process is attached to a terminal. Examples of how to do<br>this are in the Users Manual. If you do not do this, MPICH<br>will still work, but this script and the test programs will
<br>report problems because they compare expected output from<br>what the programs produce.<br>Trying true on <a href="http://192.168.1.12">192.168.1.12</a> ...<br>Unexpected response from <a href="http://192.168.1.12">192.168.1.12
</a>:<br>--> rshd: Login incorrect.<br>If your .cshrc, login, .bashrc, or other startup file<br>contains a command that generates any output when logging in,<br>such as fortune or hostname or even echo, you should modify
<br>that startup file to only print such a message when the<br>process is attached to a terminal. Examples of how to do<br>this are in the Users Manual. If you do not do this, MPICH<br>will still work, but this script and the test programs will
<br>report problems because they compare expected output from<br>what the programs produce.<br> The test of rsh <machine> true failed on some machines.<br> This may be due to problems in your .login or .cshrc files;
<br> some common problems are described when detected. Look at the<br> output above to see what the problem is.<br><br> If the problem is something like 'permission denied', then the<br> remote shell command rsh does not allow you to run programs.
<br> See the documentation about remote shell and rhosts.<br><br>Trying ls on <a href="http://192.168.1.1">192.168.1.1</a> ...<br>Errors while trying to run rsh <a href="http://192.168.1.1">192.168.1.1</a> -n /bin/ls<br>
/usr/local/mpich-1.2.7/sbin/mpichfoo<br>Unexpected response from <a href="http://192.168.1.1">192.168.1.1</a>:<br>--> select: protocol failure in circuit setup<br>Trying ls on <a href="http://192.168.1.10">192.168.1.10
</a> ...<br>Unexpected response from <a href="http://192.168.1.10">192.168.1.10</a>:<br>--> rshd: Login incorrect.<br>Trying ls on <a href="http://192.168.1.11">192.168.1.11</a> ...<br>Unexpected response from <a href="http://192.168.1.11">
192.168.1.11</a>:<br>--> select: protocol failure in circuit setup<br>Trying ls on <a href="http://192.168.1.12">192.168.1.12</a> ...<br>Unexpected response from <a href="http://192.168.1.12">192.168.1.12</a>:<br>--> rshd: Login incorrect.
<br> The ls test failed on some machines.<br> This usually means that you do not have a common filesystem on<br> all of the machines in your machines list; MPICH requires this<br> for mpirun (it is possible to handle this in a procgroup file; see
<br> the documentation for more details).<br><br> Other possible problems include:<br> The remote shell command rsh does not allow you to run ls.<br> See the documentation about remote shell and rhosts.
<br> You have a common file system, but with inconsistent names.<br> See the documentation on the automounter fix.<br><br><br>4 errors were encountered while testing the machines list for freebsd<br>No machines seem to be available!
<br>nodo1#<br> </div>