I am getting a 'Profiling Timer Alarm' signal after upgrading openmpi versions

[David12811]

Background information

What version of Open MPI are you using? (e.g., v4.1.6, v5.0.1, git branch name and hash, etc.)

I am upgrading from v4.1.6 to v5.0.5.

Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)

Installed from a tarball, openmpi-5.0.5.tar.bz2

Here are the configure flags I used:
--disabled-shared, --enable-static, --without-memory-manager, --disable-dlopen, --with-hwloc=internal, --with-libevent=internal, --with-pmix=internal, --with-prrte=internal, --disable-io-romio, --disable-hwloc-pci, --without-verbs, --disable-mpi-fortran

Please describe the system on which you are running

• Operating system/version:
  Linux x86_64 RedHat 8
• Computer hardware:
• Network type:

---

Details of the problem

I am upgrading from openmpi v4.1.6 to v5.0.5 and I am having some issues that I don't understand. I am relatively new to MPI, so please forgive my ignorance. I am able to configure, build, and install open mpi successfully but when I try to run my regular applications that utilize mpirun, I always get a profiling timer expired error that exits my program.

----------------------------------------------------------------------------------------
prterun noticed that process rank 0 with PID 2238574 on node 'hostname' exited on
signal 27 (Profiling timer expired).
----------------------------------------------------------------------------------------

Even when I run a simple mpirun --version command I see that same kind of message appear:

shell$ mpirun --version
mpirun (Open MPI) 5.0.5

Report bugs to https://www.open-mpi.org/community/help/
Profiling time alarm

I know there were some major changes structurally between the two versions but I just don't know what could be causing this, if I need to change my configuration in some way.

Any insight would be much appreciated.