Opened 2 years ago

Closed 2 years ago

#2176 closed help (answered)

Postproc CYLC_SUITE_REG_NAME KeyError

Reported by: mattjbr123 Owned by: um_support
Component: UM Model Keywords: postproc, keyerror
Cc: Platform: Monsoon2
UM Version: 10.3

Description

Hello again (sorry, I seem to be bugging you a lot lately),

I suspect this problem is something to do with cylc versions, but problems at the Oxford end are still preventing me from accessing the yammer group to check anything there.

This is for suite u-ak617 again. The log files are currently in

/home/d04/mabro/cylc-run/u-ak617/log/job/20080902T0000Z/postproc_r050i1p00000/01

It seems that there is no item with the key 'CYLC_SUITE_REG_NAME' in the python os.environ dictionary which as far as I know contains all the set environment variables, indicating that this environment variable is either not being picked up or not being set. A quick grep for it in u-ak617/app/postproc and extracted code didn't bring up anything other than where it appears in unittests in the latter.

I last ran the postproc tasks successfully about a month ago, so not sure what's changed this time…

Ideas welcome…

Thanks,
Matt

Traceback (most recent call last):
  File "/home/d04/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/main_pp.py", line 89, in <module>
    main()
  File "/home/d04/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/main_pp.py", line 38, in main
    timer.initialise_timer()
  File "/projects/solar/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/timer.py", line 35, in initialise_timer
    from nlist import loadNamelist
  File "/projects/solar/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/nlist.py", line 23, in <module>
    import control
  File "/projects/solar/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/control.py", line 75, in <module>
    name = importlib.import_module(mod)
  File "/opt/python/gnu/2.7.9/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/projects/solar/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/moo.py", line 314, in <module>
    class MooseArch(object):
  File "/projects/solar/mabro/cylc-run/u-ak617/share/fcm_make_pp/build/bin/moo.py", line 316, in MooseArch
    archive_set = os.environ['CYLC_SUITE_REG_NAME']
  File "/opt/python/gnu/2.7.9/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'CYLC_SUITE_REG_NAME'
[FAIL] main_pp.py atmos # return-code=1
Received signal EXIT
2017-05-22T19:10:10Z CRITICAL - Task job script received signal EXIT
2017-05-22T19:10:10Z CRITICAL - failed

Change History (4)

comment:1 Changed 2 years ago by luke

Hi Matt,

Yes - this is to do with the Cylc versions. The following was posted on an internal Met Office newsgroup, and the commands have worked for me (twice!):

You should try the following to include the branch in your currently running
suite.

  1. Add branch to fcm_make_pp app by going to fcm_make_pp → Configuration and add this to the pp_sources box (you may need to press the + button): branches/dev/ericaneininger/postproc_2.0_retire_CYLC_SUITE_REG_NAME
  1. On the command-line do rose suite-run --reload in your ~/roses/[SUITE ID] directory (assuming you're still running, otherwise use --restart)
  1. In the Cylc GUI go to: control → insert tasks → fcm_make_pp.<any active cycle point>
    1. Make sure you ticket the box do not check if cyclepoint is valid
    2. Wait for that to run before continuing
  1. In the Cylc GUI go to: control → insert tasks → fcm_make2_pp.<any active cycle point>
    1. Make sure you ticket the box do not check if cyclepoint is valid
    2. Wait for that to run before continuing
  1. In the Cylc GUI re-trigger the failing postproc app by right-clicking on it and clicking Trigger (run now)

In the above, the <any active cycle point> will probably be something like 19880901T0000Z

I hope this helps.

Thanks,
Luke

Last edited 2 years ago by luke (previous) (diff)

comment:2 Changed 2 years ago by mattjbr123

Thanks Luke, will give it a spin…

Matt

comment:3 Changed 2 years ago by mattjbr123

Just to confirm this has fixed the problem, thanks :)

comment:4 Changed 2 years ago by luke

  • Resolution set to answered
  • Status changed from new to closed

Hi Matt,

That's great - I'll close this ticket now.

Thanks,
Luke

Note: See TracTickets for help on using tickets.