ibacm is built with a default PID and socket path that will not exist: Example strace from ibacm startup: openat(AT_FDCWD, "/usr/var/run/ibacm.pid", O_RDWR|O_CREAT, 0640) = -1 ENOENT (No such file or directory) Example from ib_acme -e: /usr/var/run/ibacm-unix.sock,unable to contact service: No such file or directory Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=51c32bc73cde578ebf2e2fe367aed69290a1108c commit 51c32bc73cde578ebf2e2fe367aed69290a1108c Author: Daniel M. Weeks <dan@danweeks.net> AuthorDate: 2020-07-09 04:30:30 +0000 Commit: Mikle Kolyada <zlogene@gentoo.org> CommitDate: 2020-07-09 17:31:58 +0000 sys-cluster/rdma-core: Fix default RUNDIR Build system logic relies on user (ebuild) setting CMAKE_INSTALL_RUNDIR *not* CMAKE_INSTALL_FULL_RUNDIR. A default CMAKE_INSTALL_RUNDIR will always be appended to prefix. Closes: https://bugs.gentoo.org/731808 Package-Manager: Portage-2.3.103, Repoman-2.3.23 Signed-off-by: Daniel M. Weeks <dan@danweeks.net> Closes: https://github.com/gentoo/gentoo/pull/16643 Signed-off-by: Mikle Kolyada <zlogene@gentoo.org> .../rdma-core/{rdma-core-26.0-r1.ebuild => rdma-core-26.0-r2.ebuild} | 2 +- .../rdma-core/{rdma-core-26.1.ebuild => rdma-core-26.1-r1.ebuild} | 2 +- .../rdma-core/{rdma-core-27.0-r1.ebuild => rdma-core-27.0-r2.ebuild} | 2 +- .../rdma-core/{rdma-core-28.0.ebuild => rdma-core-28.0-r1.ebuild} | 2 +- .../rdma-core/{rdma-core-29.0.ebuild => rdma-core-29.0-r1.ebuild} | 2 +- .../rdma-core/{rdma-core-30.0.ebuild => rdma-core-30.0-r1.ebuild} | 2 +- sys-cluster/rdma-core/rdma-core-9999.ebuild | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-)