#2992 closed help (duplicate)

um-atmos recon threading levels and defensive checks

Reported by: Leighton_Regayre Owned by: um_support
Component: UM Model Keywords: reconfiguration recon threading levels defensive check
Cc: Platform: ARCHER
UM Version: 11.1

Description

Hello,

When submitting suite u-bk417 (set up to be nudged towards ECMWF wind fields and using offline oxidant ancillaries) I get a confusing error when the recon task fails.

The branch I am using is a copy of the UM vn11.1 trunk with some minor code changes. I had problems with the offline oxidants in this suite (ticket #2989) but this problem looks to be distinct. It is possibly related to ticket #2236 but these is no explanation on that ticket page about how the problem was resolved.

The errors in the job.out are:

[INFO] command: um-atmos
[WARN] UM version (VN=x.y) defined in the environment.
[INFO] Overriding $VN to 11.1
[WARN] Using default STASHmaster as none provided "/work/y07/y07/umshared/vn11.1/ctldata/STASHmaster".
[WARN] Using default STASH2CF as none provided "/work/y07/y07/umshared/vn11.1/ctldata/STASH2CF/STASH_to_CF.txt".
[INFO] Using executable: /work/n02/n02/lre/cylc-run/u-bk417/share/fcm_make_um/build-atmos/bin/um-atmos.exe
[INFO] Using script: /work/n02/n02/lre/cylc-run/u-bk417/share/fcm_make_um/build-atmos/bin/um-atmos
[INFO] exec /opt/cray/alps/5.2.5-2.0502.9955.44.1.ari/bin/aprun -ss -n 192 -N 24 -S 12 -d 1 -j 1 /work/n02/n02/lre/cylc-run/u-bk417/share/fcm_make_um/build-atmos/bin/um-atmos.exe

=====================================================
GCOM Version 6.6
XC30_MPI
Using precision : 64bit INTEGERs and 64bit REALs
Built at Mon Jun 4 17:10:37 BST 2018
=====================================================


WARNING - REQUESTED AND ACTUAL THREADING LEVEL DIFFERENT
THREAD LEVEL REQUESTED is MPL_THREAD_MULTIPLE
THREAD LEVEL SET is MPL_THREAD_SERIALIZED
gc_abort (Processor 0): um_abort called

Followed by an instance of "has failed to pass any defensive checks" for different routines, with error code 80. There are many more of these in the log.err file.

Thanks,

Leighton.

Change History (3)

comment:1 Changed 12 months ago by willie

Hi Leighton,

I notice you have several open tickets on the same suite u-bk417: #2989, #2982, #2981. It is not possible for us to track this. Let's try to focus on solving one issue at a time e.g 2989.

Be aware that ARCHER is having some problems today and is at risk - see http://www.archer.ac.uk/status/.

Willie

comment:2 Changed 12 months ago by Leighton_Regayre

Hi Willie,

This ticket was raised because I thought the issue was distinct from the one we were tracking in #2989. Following your suggestion, I've added the content of this ticket there instead.

Cheers,

Leighton.

comment:3 Changed 12 months ago by willie

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