If it is installed, libunuma should be in:
/usr/lib64/libnuma.so
as a softlink to the actual number-versioned library.
In general the loader is configured to search for shared libraries
in /usr/lib64 ("ldd <your_executable>" may shed some light here).
You can check if the numa packages are installed with:
yum list | grep numa (CentOS 7, RHEL 7)
dnf list | grep numa (CentOS 8, RHEL 8, RockyLinux 8, Fedora, etc)
apt list | grep numa (Debian, Ubuntu)
If not, you can install (or ask the system administrator to do it).
I hope this helps,
Gus Correa
On Wed, Jul 19, 2023 at 11:55 AM Jeff Squyres (jsquyres) via users <
users@lists.open-mpi.org> wrote:
> It's not clear if that message is being emitted by Open MPI.
>
> 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 <users-boun...@lists.open-mpi.org> on behalf of Luis
> Cebamanos via users <users@lists.open-mpi.org>
> *Sent:* Wednesday, July 19, 2023 10:09 AM
> *To:* users@lists.open-mpi.org <users@lists.open-mpi.org>
> *Cc:* Luis Cebamanos <luic...@gmail.com>
> *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 file
> or directory
> [LOG_CAT_SBGP] Failed to dlopen libnuma.so. Fallback to GROUP_BY_SOCKET
> manual.
> .....
>
> The funny thing is that the binary is executed despite the errors.
> What could be causing it?
>
> Regards,
> Lusi
>
