This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
I agree so much that I just recently filed a bug about this same issue:
Thanks for the feedback, though -- this turns it from a hypothetical
issue into a "it has happened to at least one user" issue...
On Jun 20, 2008, at 8:00 PM, Scott Atchley wrote:
> Hi all,
> We had a customer using 1.2.6 with MX. We were running his jobs,
> some of which used the MX BTL and some used the MX MTL.
> He added a few more nodes to the cluster and installed the same
> OMPI. When we tried to run jobs that spanned the new nodes, the jobs
> failed. I did not keep the error messages, but it seems to be a
> standard message about a component such as "self" not found.
> The problem in fact was that he installed OMPI, but for some reason
> neither the MX BTL nor the MX MTL were installed. Thus, the failure.
> I do not believe the error message for the BTL runs ever
> specifically mentioned a missing MX component even though we were
> setting "--mca btl self,sm,mx" (we did not specify MX when using the
> MTL, we only used "--mca pml cm".
> It would be helpful in the case where a OMPI cannot run _and_ a
> module is specifically requested but not available to be mentioned
> in the error message.
> users mailing list