When I execute the command: mpirun --allow-run-as-root -np 576 --bind-to core./wrf.exe, there is an abnormal printout at the end of the process: #13344
Description
Thank you for taking the time to submit an issue!
Background information
lscpu
Architecture: aarch64
CPU op-mode(s): 64-bit
Byte Order: Little Endian
CPU(s): 576
On-line CPU(s) list: 0-575
What version of Open MPI are you using? (e.g., v4.1.6, v5.0.1, git branch name and hash, etc.)
MPI Version: [email protected]
Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)
cat /etc/os-release
NAME="openEuler"
VERSION="22.03 (LTS-SP4)"
ID="openEuler"
VERSION_ID="22.03"
PRETTY_NAME="openEuler 22.03 (LTS-SP4)"
ANSI_COLOR="0;31"
If you are building/installing from a git clone, please copy-n-paste the output from git submodule status.
Please describe the system on which you are running
- Operating system/version:
- Computer hardware:
- Network type:
Details of the problem
When I execute the command: mpirun --allow-run-as-root -np 576 --bind-to core./wrf.exe, there is an abnormal printout at the end of the process:
starting wrf task 45 of 576
starting wrf task 53 of 576
starting wrf task 541 of 576
--------------------------------------------------------------------------
mpirun has exited due to process rank 23 with PID 0 on
node localhost 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 \"orte_abort\" and the mca parameter
orte_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 mpirun (as reported here).
You can avoid this message by specifying -quiet on the mpirun command line.
--------------------------------------------------------------------------but the content in the rsl.error.0000 file indicates that the operation was successful.
Timing for main: time 2015-04-28_00:04:55 on domain 1: 8.12602 elapsed seconds
Timing for main: time 2015-04-28_00:05:00 on domain 1: 9.83546 elapsed seconds
d01 2015-04-28_00:05:00 wrf: SUCCESS COMPLETE WRF
Please confirm if this is a bug.