<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18812"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=359202023-27092009><FONT color=#0000ff
size=2 face=Arial>You may want to test the MPICH2 installation independent of
Rmpi first. You can run make testing in the top level mpich2 directory, which
will run through the entire test suite (>500 tests). If that works, you may
need to contact the Rmpi developers about this specific
problem.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359202023-27092009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=359202023-27092009><FONT color=#0000ff
size=2 face=Arial>Rajeev</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=359202023-27092009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> mpich-discuss-bounces@mcs.anl.gov
[mailto:mpich-discuss-bounces@mcs.anl.gov] <B>On Behalf Of </B>Cye
Stoner<BR><B>Sent:</B> Sunday, September 27, 2009 2:07 AM<BR><B>To:</B>
mpich-discuss@mcs.anl.gov<BR><B>Subject:</B> [mpich-discuss] Rmpi technical
problem/question with MPICH2<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=gmail_quote>I'm sorry if this is the wrong channel of communication
for these types of problems. If that is the case, I would appreciate knowing
where to go.<BR><BR>I am aware that Rmpi was mostly developed under LAM-MPI,
but I am attempting to deploy it under MPICH2.<BR>MPICH2 has been set up using
the "./configure --with-device=ch3:sock" command in order to avoid a bug I was
encountering with some of the nodes. Everything else under MPICH2 now works,
and I can compile and run the examples without problem. MPICH2 is deployed
across the cluster under the /mirror/mpich2 directory. If it's relevant, they
also have their home directories for the mpiu user mirrored over I am running
into problems with Rmpi.<BR><BR>To install Rmpi, I used my generic mpiu
account, and executed the following commands:<BR>> install.packages("Rmpi",
configure.args="--with-mpi=/mirror/mpich2")<BR><BR>This installation completes
without error, and I am able to load the Rmpi library with the ">
library(Rmpi)" command from the R prompt.<BR><BR>This is where my problems
occur, and where I could use your advice.<BR><BR>If I start the mpd daemon
with 1 node using the following command:<BR>$ mpdboot -n 1 -v<BR>then I can
successfully start use<BR>> mpi.spawn.Rslaves()<BR>command to start the
Rslaves with the following output<BR clear=all> 1 slaves are
spawned successfully. 0 failed.<BR>master (rank 0, comm 1) of size 2 is
running on: hal <BR>slave1 (rank 1, comm 1) of size 2 is running on:
hal<BR>> mpi.remote.exec(paste("I
am",mpi.comm.rank(),"of",mpi.comm.size()))<BR>$slave1<BR>[1] "I am 1 of
2"<BR>> mpmpi.close.Rslaves()<BR>mpi.close.Rslaves()<BR>[1] 1<BR>>
mpi.quit()<BR>> Error: unexpected '>' in ">"<BR>>
mpi.quit()<BR>mpi.quit() <BR>mpi.quit()<BR><BR>There seems to be some error
(possibly permissions?) and after getting back to the $ prompt, I get a lot of
errors in the following form:<BR>mpiexec_hal (handle_stdin_input 1089): stdin
problem; if pgm is run in background, redirect from /dev/null<BR>mpiexec_hal
(handle_stdin_input 1090): e.g.: mpiexec -n 4 a.out
< /dev/null<BR><BR><BR>After doing this, I can <BR>However, if I start the
mpd daemon with 2 (or more) nodes, using the following commands from the R
prompt:<BR>> library("Rmpi")<BR>> mpi.spawn.Rslaves()<BR>I immediately
get the following error:<BR><BR>Error in mpi.comm.spawn(slave =
system.file("Rslaves.sh", package = "Rmpi"), : <BR> Other MPI
error, error stack:<BR>MPI_Comm_spawn(144)...........:
MPI_Comm_spawn(cmd="/home/mpiu/R/i486-pc-linux-gnu-library/2.6/Rmpi/Rslaves.sh",
argv=0x8b8ce20, maxprocs=1, MPI_INFO_NULL, root=0, MPI_COMM_SELF,
intercomm=0x88cd0e0, errors=0x80ff870)
failed<BR>MPIDI_Comm_spawn_multiple(233): PMI_Spawn_multiple failed<BR><BR>For
this particular error, the output of "mpdtrace -l" is:<BR>hal_43272
(192.168.100.1)<BR>n01_55355 (192.168.100.101)<BR><BR>Where hal is the name of
the master node with mpd listening on port 43272, and n01 is the slave node
listening on port 55355.<BR><BR>I have tried several different versions of
Rmpi (0.5-7 and 0.5-8), but get the same error regardless.<BR><BR>This error
seems to be caused within the mpi_comm_spawn(...) call under the ./src/Rmpi.c
file of the Rmpi package.<BR><BR>I am completely baffled by this, and any help
(or a good mailing list from which to ask for help) would be very much
appreciated.<BR><BR>Thank you for your time,<BR>Cye Stoner<BR><FONT
color=#888888><BR><BR>-- <BR>"If you already know what recursion is, just
remember the answer. Otherwise, find someone who is standing closer
to<BR>Douglas Hofstadter than you are; then ask him or her what recursion is."
- Andrew Plotkin<BR></FONT></DIV><BR><BR clear=all><BR>-- <BR>"If you already
know what recursion is, just remember the answer. Otherwise, find someone who
is standing closer to<BR>Douglas Hofstadter than you are; then ask him or her
what recursion is." - Andrew Plotkin<BR></BLOCKQUOTE></BODY></HTML>