That's not for the MPI communications but for the process management part
(PRRTE/PMIX). If forcing the PTL to `lo` worked it mostly indicates that
the shared memory in OMPI was able to be set up correctly.
George.
On Mon, Feb 5, 2024 at 3:47 PM John Hearns wrote:
> Stupid question... Why is
Stupid question... Why is it going 'out' to the loopback address? Is shared
memory not being used these days?
On Mon, Feb 5, 2024, 8:31 PM John Haiducek via users <
users@lists.open-mpi.org> wrote:
> Adding '--pmixmca ptl_tcp_if_include lo0' to the mpirun argument list
> seems to fix (or at least
That would be something @Ralph Castain needs to be
looking at as he declared in a previous discussion that `lo` was the
default for PMIX and we now have 2 reports stating otherwise.
George.
On Mon, Feb 5, 2024 at 3:15 PM John Haiducek wrote:
> Adding '--pmixmca ptl_tcp_if_include lo0' to the
Adding '--pmixmca ptl_tcp_if_include lo0' to the mpirun argument list seems
to fix (or at least work around) the problem.
On Mon, Feb 5, 2024 at 1:49 PM John Haiducek wrote:
> Thanks, George, that issue you linked certainly looks potentially related.
>
> Output from ompi_info:
>
>
Thanks, George, that issue you linked certainly looks potentially related.
Output from ompi_info:
Package: Open MPI brew@Monterey-arm64.local Distribution
Open MPI: 5.0.1
Open MPI repo revision: v5.0.1
Open MPI release date: Dec 20, 2023
MPI
OMPI seems unable to create a communication medium between your processes.
There are few known issues on OSX, please read
https://github.com/open-mpi/ompi/issues/12273 for more info.
Can you provide the header of the ompi_info command. What I'm interested on
is the part about `Configure command li
