[MPICH] HELP

[David Ashton]

Kevin,

You don't have an mpd running so you cannot start a job.  Please read the
user-guide and you'll be up and running in no time.

Also, the --localonly option you specified will only be visible to the user
application because you specified it after the executable name.  All
arguments to mpiexec must be passed before the application name.

But even if you place the argument in the correct place, --localonly is an
extended option provided by the smpd process manager not the default mpd
process manager.  -localonly works under Windows because smpd is the default
process manager under Windows MPICH2 but under Linux this option is not
available unless you specifically build with smpd.

-David Ashton

-----Original Message-----
From: owner-mpich-discuss at mcs.anl.gov
[mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of Kevin C.
Sent: Monday, June 20, 2005 11:11 AM
To: mpich-discuss at mcs.anl.gov
Subject: RE: [MPICH] HELP

Windows MPICH-1 seems to work now for running multiple processes on one 
machine. I haven't figured out how to setup MPICH-2 as it requires building 
opposed to MPICH-1 which was ready-built.

Linux MPICH-1 errors I still get are:

bash-3.00# /usr/lib/mpich-1.2.6/bin/mpirun -np 2 cpi --localonly
connect to address 127.0.0.1: Connection refused
Trying krb4 rsh...
connect to address 127.0.0.1: Connection refused
trying normal rsh (/usr/bin/rsh)
localhost.localdomain: Connection refused
p0_25434:  p4_error: Child process exited while making connection to remote 
process on localhost.localdomain: 0



Linux MPICH-2 errors I still get are:

bash-3.00# mpiexec -np 2 cpi --localonly
mpdrun_localhost.localdomain: cannot connect to local mpd 
(/tmp/mpd2.console_root); possible causes:
  1. no mpd is running on this host
  2. an mpd is running but was started without a "console" (-n option)