Problems with archiving

I am running a version of UKESM on monsoon archiving to mass.
After running successfully for many model years the model has stopped due to a problem with the archive_integrity process.
I think I’ve tracked the problem down to the command:
moo ls -l moose:/crum/u-ck613/
Which brings up a long error message, starting:
aschurer@xcslc0:~> moo ls -l moose:/crum/u-ck613/

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00002aaaabefb7d2, pid=109339, tid=46912910698240

So I’m now wondering if the data has been corrupted. Any help would be gratefully appreciated.

Many thanks

Does anyone have any thoughts about this?
Should I contact the monsoon support team instead?

Hi Andrew

Sorry for the lack of response - we didn’t make progress understanding this. Monsoon may have some ideas.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.