*sigh* Thanks Ralph. I had another MPI implementation's CLI options wedged in my brain (where "--perhost" take's an argument).
Sorry for the noise, -Dave On Mar 31, 2014, at 12:05 PM, Ralph Castain <r...@open-mpi.org> wrote: > Well, that's why it is a "deprecated" option! :-) > > Looks like the command line parser then gets confused by the error in your > option - if you look more closely at the error, you'll see that it picked up > the "2" as the name of your executable. This is because "pernode" doesn't > take an argument - it is shorthand for "npernode 1". You probably meant to > use the "npernode" option, which would have worked. > > > On Mar 31, 2014, at 9:57 AM, Dave Goodell (dgoodell) <dgood...@cisco.com> > wrote: > >> Ralph, >> >> When I use the "--pernode" option (instead of "--map-by ppr:1:node") with >> v1.8@r31295, I get this: >> >> ----8<---- >> $ mpiexec --pernode 2 -n 4 --host dg1,dg2 ./ring_c >> -------------------------------------------------------------------------- >> The following command line options and corresponding MCA parameter have >> been deprecated and replaced as follows: >> >> Command line options: >> Deprecated: --pernode, -pernode >> Replacement: --map-by ppr:1:node >> >> Equivalent MCA parameter: >> Deprecated: rmaps_base_pernode, rmaps_ppr_pernode >> Replacement: rmaps_base_mapping_policy=ppr:1:node >> >> The deprecated forms *will* disappear in a future version of Open MPI. >> Please update to the new syntax. >> -------------------------------------------------------------------------- >> -------------------------------------------------------------------------- >> mpiexec was unable to find the specified executable file, and therefore >> did not launch the job. This error was first reported for process >> rank 0; it may have occurred for other processes as well. >> >> NOTE: A common cause for this error is misspelling a mpiexec command >> line parameter option (remember that mpiexec interprets the first >> unrecognized command line token as the executable). >> >> Node: savbu-usnic-a >> Executable: 2 >> -------------------------------------------------------------------------- >> ----8<---- >> >> That's a strange error for two reasons: >> >> * because mpiexec shouldn't be launching on the head node (I passed "--host >> dg1,dg2") >> * because the head node (savbu-usnic-a) actually does have a copy of this >> file in the exact same place as dg1/dg2 >> >> Everything works as expected if I pass the non-deprecated form of the option >> to mpiexec. I checked quickly at the tip of the v1.7 branch (v1.7@r31182) >> and it has the same behavior. I have not tried any other revisions yet. >> >> -Dave >> >
