On Jun 24, 2008, at 9:13 PM, Joshua Bernstein wrote:
Exactly, but for now, if I make sure the NODES envar is setup
correctly and make sure the OpenMPI is NFS mounted, and I actually
have to copy out the mca libraries (libcache doesn't seem to work),
I actually end up with something running!
On 6/24/08 7:13 PM, "Joshua Bernstein"
wrote:
>
>
> Ralph Castain wrote:
>> Hmmmwell, the problem is as I suspected. The system doesn't see any
>> allocation of nodes to your job, and so it aborts with a crummy error
>> message that doesn't really tell you the problem. We are working on
Ralph Castain wrote:
Hmmmwell, the problem is as I suspected. The system doesn't see any
allocation of nodes to your job, and so it aborts with a crummy error
message that doesn't really tell you the problem. We are working on
improving them.
How are you allocating nodes to the job? Does t
Hmmmwell, the problem is as I suspected. The system doesn't see any
allocation of nodes to your job, and so it aborts with a crummy error
message that doesn't really tell you the problem. We are working on
improving them.
How are you allocating nodes to the job? Does this BEOWULF_JOB_MAP conta
Ralph,
I really appreciate all of your help and guidance on this.
Ralph H Castain wrote:
Of more interest would be understanding why your build isn't working in
bproc. Could you send me the error you are getting? I'm betting that the
problem lies in determining the node allocation as th
Jeff Squyres wrote:
On Jun 23, 2008, at 2:52 PM, Joshua Bernstein wrote:
Excellent. I'll let Ralph chime in with the relevant technical
details. AFAIK, bproc works just fine in the v1.2 series (they use it
at LANL every day). But note that we changed a *LOT* in ORTE between
v1.2 and v1.3
I can guarantee bproc support isn't broken in 1.2 - we use it on several
production machines every day, and it works fine. I heard of only one
potential problem having to do with specifying multiple app_contexts on a
cmd line, but we are still trying to confirm that it wasn't operator error.
In th
Ralph Castain wrote:
Hi Joshua
Again, forwarded by the friendly elf - so include me directly in any reply.
I gather from Jeff that you are attempting to do something with bproc -
true? If so, I will echo what Jeff said: bproc support in OMPI is being
dropped with the 1.3 release due to lack o
On Jun 23, 2008, at 2:52 PM, Joshua Bernstein wrote:
Bummer! I would absolutely support, (along with Penguin) further
contributions and development of BProc support.
Note, though that BProc Scyld, and LANL BProc, have long ago forked.
We believe our BProc functionality has been developed be
Wow,
Seems like I've fallen behind in replying. I'll try to be sure to make
sure I answer everbody's questions about what I am trying to accomplish.
Jeff Squyres wrote:
On Jun 20, 2008, at 3:50 PM, Joshua Bernstein wrote:
No, we don't have an easy way to show which plugins were loaded and
Hi Joshua
Again, forwarded by the friendly elf - so include me directly in any reply.
I gather from Jeff that you are attempting to do something with bproc -
true? If so, I will echo what Jeff said: bproc support in OMPI is being
dropped with the 1.3 release due to lack of interest/support. Just
Hmmmthis email thread was forwarded to me by a friendly elf, so be sure
to include me directly in any reply. As the person who wrote a lot of the
bproc support, I'll try to catch up on it over the next couple of days.
One thing to correct right away, though. The --display-map function actually
On Jun 20, 2008, at 3:50 PM, Joshua Bernstein wrote:
No, we don't have an easy way to show which plugins were loaded and
may/will be used during the run. The modules you found below in --
display-map are only a few of the plugins (all dealing with the run-
time environment, and only used on
Thanks for the response Jeff,
Jeff Squyres wrote:
Greetings Josh.
No, we don't have an easy way to show which plugins were loaded and
may/will be used during the run. The modules you found below in
--display-map are only a few of the plugins (all dealing with the
run-time environment, and o
Greetings Josh.
No, we don't have an easy way to show which plugins were loaded and
may/will be used during the run. The modules you found below in --
display-map are only a few of the plugins (all dealing with the run-
time environment, and only used on the back-end nodes, so it may not
b
Well to answer my own question,
If I use the -display-map option, I get printed out a nice bit of
information that includes a list of the modules in use during the run as
shown below:
---SNIP---
Argv[0]: ./cpi
Env[0]: OMPI_MCA_pls=proxy
Env[1]:
Hi There,
I'm attempting to debug some configuration issue with the recent
version of OMPI, version 1.2.6. I'm able to build all of the MCA
modules, and I've figured out how to display the list of AVAILABLE
modules using ompi_info, but is there a way to display the list of
modules that was s
17 matches
Mail list logo
