Opened 3 years ago

Closed 3 years ago

#2454 closed help (answered)

Archiving step 'fails'

Reported by: shakka Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: Monsoon2
UM Version: 10.4


Hello helpdesk,

Recently I've encountered a problem whereby the archiving of fieldsfiles following the completion of the forecast step shows up in the suite control GUI as 'retrying' and eventually 'failed', despite having succeeded.
There are no error files created and the data is successfully archived in MASS, but the fail error prevents the suite from continuing, which means I've been having to manually change the status of each archiving job to 'succeeded'. This isn't ideal, however, as I've been trying to run some 10-day cases, so having to check the run every few hours is quite a lot of effort.

Can you suggest anything to solve this?


Change History (3)

comment:1 Changed 3 years ago by ros

Hi Ella,

Is this u-aw620?

If so the cycles that I've just looked at for the Peninsula task archives, which are the only archives I can see which have restarted, failed because there were trying to archive zero-length files (see the log/job/...../job.err files).


comment:2 Changed 3 years ago by shakka

Hi Ros,

That makes sense - I've set the suite to ignore most of the output streams I usually use to minimise the amount of data that's getting re-written, so I'm guessing that's the origin of the 'zero length' error.

I'll see if there's a better way to do that.


comment:3 Changed 3 years ago by willie

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