Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [OMPI devel] SCTP noisy failure
From: Brad Penoff (penoff_at_[hidden])
Date: 2007-12-12 22:24:31

On Dec 12, 2007 6:03 PM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> On Dec 12, 2007, at 8:58 PM, Brad Penoff wrote:
> >> That's not really the issue: I don't *want* SCTP support. :)
> >>
> >> I have a default RHEL4U4 install and now Open MPI is complaining on a
> >> default mpirun. Open MPI should work out of the box -- warning free
> >> -- on all supported operating systems.
> >
> > Haha, I caught that part as well (about the exclusivity "fix"). I was
> > just curious why the error is there in the first place because, after
> > all, everyone should want SCTP support, right ;-) ?
> ;-)
> > I didn't know
> > that any Linux distro had lksctp-tools installed by default, but the
> > module not loaded... learn something new every day though.
> Gotta love those screwy software authors!
> (I'm sure lots of people say that about us, too :-) )
> > So there's two issues (exclusivity not working as expected and then
> > the SCTP failure if you actually wanted SCTP support) and I'm
> > concerned about the one that most of you are not, I'm guessing ;-).
> I think exclusivity *is* working -- this is before that comes into
> play, IIRC. The _init function is querying your BTL to see if it
> wants to run.

OK, I've done a commit (r16951) to make it less noisy. Let me know
how it goes because I can't reproduce this at the moment.

I'm really curious about this release of Red Hat though....

On my Ubuntu system, if I try to create an SCTP socket and the kernel
module isn't loaded/modprobe'd, the system loads it automatically
based off the entry in the modules alias file which tells the system
where to find the appropriate .ko file.

These mappings seem to be messed up in the Red Hat out-of-the-box
RHEL4U4 release though, if I'm understanding things correctly... does
anyone know if this is is a known problem for this particular distro?
If not, I'll try to get to installing and playing with this release
eventually (working on Solaris support for the SCTP BTL (1-1) and a
few other non-OpenMPI things at the moment though...).


> --
> Jeff Squyres
> Cisco Systems
> _______________________________________________
> devel mailing list
> devel_at_[hidden]