runtime error

[junoh@uci_edu]

Can anybody tell me the nature of the message below from the runtime error of running cesm1_0_rel04?


CCSM PRESTAGE SCRIPT HAS FINISHED SUCCESSFULLY
******** Mon Mar 19 14:10:50 PDT 2012 -- CSM EXECUTION BEGINS HERE
******** Mon Mar 19 14:10:50 PDT 2012 -- CSM EXECUTION HAS FINISHED
Model did not complete - see /data/junoh/test1/run/cpl.log.120319-142641

Below is the text at the end of cpl.log.120319-142641:

(seq_timemgr_clockPrint) Intervl yms = 0 0 432000
(seq_timemgr_clockPrint) Alarm = 5 seq_timemgr_alarm_history
(seq_timemgr_clockPrint) Prev Time = 00001201 00000
(seq_timemgr_clockPrint) Next Time = 99991201 00000
(seq_timemgr_clockPrint) Intervl yms = 9999 0 0
(seq_timemgr_clockPrint) Alarm = 6 seq_timemgr_alarm_histavg
(seq_timemgr_clockPrint) Prev Time = 00001201 00000
(seq_timemgr_clockPrint) Next Time = 99991201 00000
(seq_timemgr_clockPrint) Intervl yms = 9999 0 0
(seq_timemgr_clockPrint) Alarm = 7 seq_timemgr_alarm_tprof
(seq_timemgr_clockPrint) Prev Time = 00001201 00000
(seq_timemgr_clockPrint) Next Time = 99991201 00000
(seq_timemgr_clockPrint) Intervl yms = 9999 0 0


(seq_mct_drv) : Initialize each component: atm, lnd, ocn, and ice


Below is the text at the end of ccsm.log.120319-142641:

1 pes participating in computation for CLM

-----------------------------------

NODE# NAME
( 0) compute-4-26.local

ccsm.exe:5111 terminated with signal 11 at PC=a6f3a8 SP=7fff19f0b560. Backtrace:
./ccsm.exe(decompinitmod_decompinit_glcp_+0x12b8)[0xa6f3a8]
--------------------------------------------------------------------------
mpirun has exited due to process rank 3 with PID 5111 on
node compute-4-26.local exiting improperly. There are two 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"

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


Thanks, Juno