MPICH (p4mpd) trouble
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Rusty Lusk lusk at mcs.anl.govMon Nov 25 09:07:07 PST 2002
- Previous message: Top 500 trends
- Next message: Wireless Beowulf?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The usual reason for this is that the executable cannot be found on the remote machine. First make sure that it is there (either by copying it there or by having a shared file system), and then make sure that it can be found (either by supplying the full path name on the mpirun command or by putting the path to the executable in your environment). MPICH problems should in general be sent to mpi-bugs at mcs.anl.gov instead of to the beowulf list. Regards, Rusty Lusk | New to MPI, I'm setting up mpich 1.2.4 on my x86 linux box (Redhat 8.0 | ). Using the mpd daemon sounds like the cleanest way to accomplish | this, so I did the following as perscribed in the manual: | | ./configure --with-device=ch_p4mpd --prefix=/usr/local/mpich-1.2.4 | make | make install | | I created a .mpd.conf under /root and used chmod -o to make it | inaccessible to other users (as required by mpd ). | | I can manually start mpd without a problem, but I can't run the | examples. For example, if I do "mpirun -np 3 cpi" I immediately get | the error "job 1 aborted with code0 by process 2, unable to execute | program: cpi"
- Previous message: Top 500 trends
- Next message: Wireless Beowulf?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
