t;
>> It does say it's falling back to a different behavior if libnuma.so is
>> not found, so it appears if it's treating it as a warning, not an error.
>> --
>> *From:* users on behalf of Luis
>> Cebamanos via users
>> *Sent:* Wednesday, July 19, 2
users@lists.open-mpi.org
*Cc:* Luis Cebamanos
*Subject:* [OMPI users] libnuma.so error
Hello,
I was wondering if anyone has ever seen the following runtime error:
mpirun -np 32 ./hello
.
[LOG_CAT_SBGP] libnuma.so: cannot open shared object file: No such
r.
> --
> *From:* users on behalf of Luis
> Cebamanos via users
> *Sent:* Wednesday, July 19, 2023 10:09 AM
> *To:* users@lists.open-mpi.org
> *Cc:* Luis Cebamanos
> *Subject:* [OMPI users] libnuma.so error
>
> Hello,
>
> I was wond
ia
users
Sent: Wednesday, July 19, 2023 10:09 AM
To: users@lists.open-mpi.org
Cc: Luis Cebamanos
Subject: [OMPI users] libnuma.so error
Hello,
I was wondering if anyone has ever seen the following runtime error:
mpirun -np 32 ./hello
.
[LOG_CAT_SBGP] libnuma.so: cannot open shared objec
Luis,
That can happen if a component is linked with libnuma.so:
Open MPI will fail to open it and try to fallback on an other one.
You can run ldd on the mca_*.so components in the /.../lib/openmpi directory
to figure out which is using libnuma.so and assess if it is needed or not.
Cheers,
Gil
Hello,
I was wondering if anyone has ever seen the following runtime error:
mpirun -np 32 ./hello
.
[LOG_CAT_SBGP] libnuma.so: cannot open shared object file: No such file
or directory
[LOG_CAT_SBGP] Failed to dlopen libnuma.so. Fallback to GROUP_BY_SOCKET
manual.
.
The funny thing i
