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 built 1.0.2 on Fedora 5 for x86_64 on a cluster setup as described
below and I witness the same behavior when I try to run a job. Any
ideas on the cause?
> Jeff Squyres wrote:
> > One additional question: are you using TCP as your communications
> > network, and if so, do either of the nodes that you are running on
> > have more than one TCP NIC? We recently fixed a bug for situations
> > where at least one node in on multiple TCP networks, not all of which
> > were shared by the nodes where the peer MPI processes were running.
> > If this situation describes your network setup (e.g., a cluster where
> > the head node has a public and a private network, and where the
> > cluster nodes only have a private network -- and your MPI process was
> > running on the head node and a compute node), can you try upgrading
> > to the latest 1.0.2 release candidate tarball:
> > http://www.open-mpi.org/software/ompi/v1.0/
> $ mpiexec -machinefile ../bhost -np 9 ./ng
> Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR)
> Failing at addr:0x6
>  func:/opt/openmpi/1.0.2a9/lib/libopal.so.0 [0x2aaaac062d0c]
>  func:/lib64/tls/libpthread.so.0 [0x3b8d60c320]
>  func:/opt/openmpi/1.0.2a9/lib/openmpi/mca_btl_tcp.so [0x2aaaae6e2b09]
>  func:/opt/openmpi/1.0.2a9/lib/libmpi.so.0(ompi_mpi_init+0x3af)
>  func:/opt/openmpi/1.0.2a9/lib/libmpi.so.0(MPI_Init+0x93)
>  func:/opt/openmpi/1.0.2a9/lib/libmpi.so.0(MPI_INIT+0x28)
>  func:./ng(MAIN__+0x38) [0x4022a8]
>  func:./ng(main+0xe) [0x4126ce]
>  func:/lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x3b8cb1c4bb]
>  func:./ng [0x4021da]
> *** End of error message ***