Bug#1123047: openmpi-bin: prterun has exited due to process rank 1 with PID 4863 on node asus-tuf-gaming-a15 exiting improperly.

Kostiantyn Hermash kostiantyn.hermash at gmail.com
Tue Dec 16 12:20:22 GMT 2025


Package: openmpi-bin
Version: 5.0.7-1
Severity: normal
X-Debbugs-Cc: kostiantyn.hermash at gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

        I am running the siesta-5.4.1 computer program using OpenMPI-5.0.7-1
(trixie) like this:

        mpirun -np 8 siesta YAlO3.fdf | tee YAlO3_run_1.out


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

        This error with OpenMPI has been appearing since I upgraded from Debian
12 to Debian 13.

        I tried the old version Siesta-4.1.5 and the new version Siesta-5.4.1,
but this error takes place for both versions.

        I didn't have this error when I used Debian 12.

        I think that this is the following issue: https://github.com/open-
mpi/ompi/issues/12607


   * What was the outcome of this action?

        In the end of Siesta run I got the following error message from
OpenMPI:

>> End of run:  16-DEC-2025  10:33:38
Job completed
--------------------------------------------------------------------------
prterun has exited due to process rank 1 with PID 4863 on node asus-tuf-
gaming-a15 exiting
improperly. There are three reasons this could occur:

1. this process did not call "init" before exiting, but others in the
job did. This can cause a job to hang indefinitely while it waits for
all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

3. this process called "MPI_Abort" or "prte_abort" and the mca
parameter prte_create_session_dirs is set to false. In this case, the
run-time cannot detect that the abort call was an abnormal
termination. Hence, the only error message you will receive is this
one.

This may have caused other processes in the application to be
terminated by signals sent by prterun (as reported here).

You can avoid this message by specifying -quiet on the prterun command
line.
--------------------------------------------------------------------------
kostia at asus-tuf-gaming-a15:~/Дoкyмeнти/work/YAlO3_17$



        This error is shown not always, only sometimes.

        It seems that it doesn't actually influence on the siesta calculations.

        Siesta doesn't show any error messages.


   * What outcome did you expect instead?

        I did not expect the error message.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 13.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.57+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openmpi-bin depends on:
ii  libc6                        2.41-12
ii  libevent-core-2.1-7t64       2.1.12-stable-10+b1
ii  libhwloc15                   2.12.0-4
ii  libopenmpi40                 5.0.7-1
ii  libpmix2t64                  5.0.7-1
ii  openmpi-common               5.0.7-1
ii  openssh-client [ssh-client]  1:10.0p1-7

openmpi-bin recommends no packages.

Versions of packages openmpi-bin suggests:
ii  gfortran [fortran-compiler]  4:14.2.0-1

-- no debconf information


More information about the debian-science-maintainers mailing list