Yup, the 1.7.4rc2r30168 tarball appears to have resolved this.

-Paul


On Wed, Jan 8, 2014 at 4:08 PM, Ralph Castain <r...@open-mpi.org> wrote:

> Yeah - it only today was approved for move into 1.7.4 :-)
>
> Hopefully will make it into tonight's tarball
>
>
> On Jan 8, 2014, at 3:58 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>
> On Fri, Dec 20, 2013 at 4:16 PM, Ralph Castain <r...@open-mpi.org> wrote:
>
>> I'll silence it - thanks!
>>
>
> Ralph,
>
> As of the current tarball (1.7.4rc2r30148) this warning is still present.
> I have also now encountered the identical message on NetBSD-6/x86:
>
> -bash-4.2$ mpirun -np 1 --bind-to none examples/ring_c
> [pcp-j-17:02298] [[54421,1],0] ORTE_ERROR_LOG: Bad parameter in file
> /home/phargrov/OMPI/openmpi-1.7-latest-netbsd6-i386/openmpi-1.7-latest/orte/mca/oob/tcp/oob_tcp.c
> at line 291
> --------------------------------------------------------------------------
> WARNING: An invalid value was given for btl_tcp_if_exclude.  This
> value will be ignored.
>
>   Local host: pcp-j-17
>   Value:      127.0.0.1/8
>   Message:    Did not find interface matching this subnet
> --------------------------------------------------------------------------
>
> -Paul
>
>
>> On Dec 20, 2013, at 3:20 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>
>> On Fri, Dec 20, 2013 at 3:12 PM, Dave Goodell (dgoodell) <
>> dgood...@cisco.com> wrote:
>>
>>> On Dec 20, 2013, at 4:43 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>>>
>>> > The warning is correct that no such interface exists.
>>> > However 127.0.0.1/24 DOES exist:
>>> >
>>> > $ ifconfig lo0 inet
>>> > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>>> >        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
>>> >        inet 127.0.0.1 netmask 0xff000000
>>>
>>> Minor quibble, Paul: that looks like 127.0.0.1/8 to me, not /24...
>>>
>>> I have no specific help to offer for this issue though, sorry.
>>>
>>
>> Right, I think I put my IP hat on backwards.
>> Either way, the loopback interface exists and so the warning is a sign
>> that something is amiss.
>>
>> FWIW:
>> Trying "mpirun -mca btl self,sm -np 2 examples/ring_c" still hangs (w/o
>> this warning).
>> So, I doubt that issue is related to whatever is going on with respect IP
>> interfaces.
>>
>> -Paul
>>
>> --
>> Paul H. Hargrove                          phhargr...@lbl.gov
>> Future Technologies Group
>> Computer and Data Sciences Department     Tel: +1-510-495-2352
>> Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
>>
>>
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>
>
>
>
> --
> Paul H. Hargrove                          phhargr...@lbl.gov
> Future Technologies Group
> Computer and Data Sciences Department     Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
>
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>



-- 
Paul H. Hargrove                          phhargr...@lbl.gov
Future Technologies Group
Computer and Data Sciences Department     Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

Reply via email to