[5781] | 1 | |
---|
| 2 | ####################################### |
---|
| 3 | EXECUTION of : time mpirun -hostfile hosts -rankfile rankfile -np 71 ./script_lmdz.x.ksh : -np 360 ./script_opa.xx.ksh : -np 12 ./script_xios.x.ksh |
---|
| 4 | |
---|
| 5 | -------------------------------------------------------------------------- |
---|
| 6 | MPI_ABORT was invoked on rank 442 in communicator MPI_COMM_WORLD |
---|
| 7 | with errorcode -1. |
---|
| 8 | |
---|
| 9 | NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes. |
---|
| 10 | You may or may not see output from other processes, depending on |
---|
| 11 | exactly when Open MPI kills them. |
---|
| 12 | -------------------------------------------------------------------------- |
---|
| 13 | -------------------------------------------------------------------------- |
---|
| 14 | mpirun has exited due to process rank 442 with PID 112172 on |
---|
| 15 | node curie3890 exiting improperly. There are two reasons this could occur: |
---|
| 16 | |
---|
| 17 | 1. this process did not call "init" before exiting, but others in |
---|
| 18 | the job did. This can cause a job to hang indefinitely while it waits |
---|
| 19 | for all processes to call "init". By rule, if one process calls "init", |
---|
| 20 | then ALL processes must call "init" prior to termination. |
---|
| 21 | |
---|
| 22 | 2. this process called "init", but exited without calling "finalize". |
---|
| 23 | By rule, all processes that call "init" MUST call "finalize" prior to |
---|
| 24 | exiting or it will be considered an "abnormal termination" |
---|
| 25 | |
---|
| 26 | This may have caused other processes in the application to be |
---|
| 27 | terminated by signals sent by mpirun (as reported here). |
---|
| 28 | -------------------------------------------------------------------------- |
---|
| 29 | 3.23user 10.68system 9:25.70elapsed 2%CPU (0avgtext+0avgdata 22304maxresident)k |
---|
| 30 | 7272inputs+8outputs (61major+9206minor)pagefaults 0swaps |
---|