Opened 8 years ago

Closed 7 years ago

#1109 closed help (fixed)

CRUN problems

Reported by: emxin Owned by: um_support
Component: HECToR Keywords: CRUN
Cc: Platform: <select platform>
UM Version: 7.3



Recently my CRUN has problems. Some long run jobs crashed as the 'Elap Time' for one run was actually longer than 'required time' which is actually 12 hrs. Model seems can not stop properly (though it can make some CRUNs) and crashed before re-submitting another run. I had a same problem before and raised a ticket for it. The problem was gone after I copied a colleague's .bashrc and .profile (not sure about this solution). However, this time it does not work. It is a pain to re-submit jobs manually. Can you have a look and let me know what is wrong?

here are some job output files for check:


Change History (2)

comment:1 Changed 8 years ago by willie

Hi Xin,

The job xiizx has taken more than 12 hours and so has been terminated. You need to reduce the length of the run so that this and all the subsequent runs take less than 12hrs.


comment:2 Changed 7 years ago by willie

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.