Opened 5 years ago

Closed 5 years ago

#1395 closed help (fixed)

CRUN not re-submitting next month

Reported by: StevenTurnock Owned by: ros
Component: UKCA Keywords:
Cc: Platform: MONSooN
UM Version: 7.3

Description

I have recently set up a new job in HadGEM3-UKCA at UM Vn7.3 and when I submit the CRUN it runs for a single month and then finishes without re-submitting the next month even though I have specified the Job to run for 12 months. The NRUN seems to complete fine and so do the individual CRUNs but they are just not moving onto the next month as they should do. I have tried this a number of times now with the same result. Also I haven't changed too many details from the job that I copied from and the CRUNs for that job did not have this problem. The job id is xkngb if you want to look at the individual files. Thanks

Change History (5)

comment:1 Changed 5 years ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Steven,

I couldn't see anything wrong with your UMUI setup and so have taken a copy of your job and just changed the resubmit period to 1 day. The job is now resubmitting fine for me, but obviously isn't doing any archiving. I, therefore wonder if the archiving is causing a problem?? Did your working job archive ok and resubmit ok? What is the id of the working job?

Regards,
Ros.

comment:2 Changed 5 years ago by StevenTurnock

Hi Ros,

As far as I know this job and the other ones that I have used were set up just to archive to /nerc/ukca/username/ disk and they seemed to be fine with this. The id of the job that I copied to set this new one up was xjumg. The only other things that I can think are different is that I am a running from a local working copy at the moment and that the run length has been set to 12 months rather that a year. Will either of these cause a particular problem?

Thanks
Steven

comment:3 Changed 5 years ago by ros

Hi Steven,

Is this job still causing problems? Running from a working copy could potentially cause a problem depending on what you're doing, but I would think it unlikely. I'm currently trying to run your job in the same set up as you, but am having problems getting it to even do an NRUN at the moment.

Regards,
Ros

comment:4 Changed 5 years ago by StevenTurnock

Hi Ros,

Initially it was but it crashed one evening due to the ukca disk quota being exceeded and once I re-submitted an NRUN for the new month and then the corresponding CRUN it appeared to proceed as normal and did re-submit automatically for each following month. I have also set up another job based on the same original one (with slightly different ancillary files this time) and this job has worked as normal. So I am not quite sure why it was behaving like that in the first instance. Do you have any thoughts so I could try and avoid in the future?

Thanks
Steven

comment:5 Changed 5 years ago by ros

  • Resolution set to fixed
  • Status changed from accepted to closed

Hi Steven,

This was a bit of an unusual problem, I don't really have any ideas on what the problem was. Since the job worked with no modifications for me and has then run normally after another NRUN I can only assume there was something wonky with the running environment which got reset with the NRUN.

Regards,
Ros.

Note: See TracTickets for help on using tickets.