| Line | |
|---|
| 1 | |
|---|
| 2 | ####################################### |
|---|
| 3 | EXECUTION of : time mpirun -hostfile hosts -rankfile rankfile -np 71 ./script_lmdz.x.ksh : -np 12 ./script_xios.x.ksh |
|---|
| 4 | |
|---|
| 5 | -------------------------------------------------------------------------- |
|---|
| 6 | mpirun has exited due to process rank 72 with PID 96738 on |
|---|
| 7 | node curie2935 exiting improperly. There are two reasons this could occur: |
|---|
| 8 | |
|---|
| 9 | 1. this process did not call "init" before exiting, but others in |
|---|
| 10 | the job did. This can cause a job to hang indefinitely while it waits |
|---|
| 11 | for all processes to call "init". By rule, if one process calls "init", |
|---|
| 12 | then ALL processes must call "init" prior to termination. |
|---|
| 13 | |
|---|
| 14 | 2. this process called "init", but exited without calling "finalize". |
|---|
| 15 | By rule, all processes that call "init" MUST call "finalize" prior to |
|---|
| 16 | exiting or it will be considered an "abnormal termination" |
|---|
| 17 | |
|---|
| 18 | This may have caused other processes in the application to be |
|---|
| 19 | terminated by signals sent by mpirun (as reported here). |
|---|
| 20 | -------------------------------------------------------------------------- |
|---|
| 21 | 7.54user 48.02system 1:06:36elapsed 1%CPU (0avgtext+0avgdata 3716maxresident)k |
|---|
| 22 | 32inputs+8outputs (0major+4009minor)pagefaults 0swaps |
|---|
Note: See
TracBrowser
for help on using the repository browser.
