So, I have a number of machines I'm trying to set up with MPICH2, but I'm starting off with just 2. One is behind an NAT router and the other has a public ip, but is protected by an iptables firewall. <br><br>I can ssh back and forth between them, and I have them keyed so that you don't need a password to do so after starting an ssh-agent and giving the password to the RSA key. <br>
<br>I have MPICH_PORT_RANGE and MPIEXEC_PORT_RANGE set in /etc/profile on both systems to 10000:10100 and both firewalls allow traffic through on those ports (I've tested this with netcat). <br><br>mpdboot fails with the following output:<br>
mthiffau@foehammer ~ (255)% mpdboot -n 2 -v -f mpd.hosts<br>running mpdallexit on foehammer<br>LAUNCHED mpd on foehammer via <br>RUNNING: mpd on foehammer<br>LAUNCHED mpd on <a href="http://halo.mthiffau.ca">halo.mthiffau.ca</a> via foehammer<br>
mpdboot_foehammer (handle_mpd_output 415): failed to connect to mpd on <a href="http://halo.mthiffau.ca">halo.mthiffau.ca</a><br><br>So, mpd starts locally, and on the other machine, but afterwards comunication seems to break down. Does the ssh-ing back and forth have to be completely passwordless? Is there something else I have to do to ensure the correct port range gets used?<br>
<br>I suspect it might be the latter, as even with the environment variables set, mpdcheck -s starts listening on random ports that are outside the range specified.<br><br>Any help would be appreciated, thanks a bunch.<br>
<br>Matt Thiffault<br>