Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#1842 closed help (fixed)

HadGAM2 failing in FCM_MAIN

Reported by: jonny Owned by: ros
Component: UM Model Keywords:
Cc: Platform: ARCHER
UM Version: 6.6.3

Description

Hi,
I'm trying to submit a "compile and run" job on Archer (xmodb).

the FCM extract part seems to work OK, but I get the following message:

FCM_MAIN: Submitting umuisubmit_clr …

followed by:
qsub: script file:: No such file or directory
FCM_MAIN: Submit failed

I don't seem to have a umuisubmit_clr file in ~/umui_runs/xmodb-083161058/

I've seen a few tickets with this type of error. I've tried adjusting my environment and have tried submitting this a number of times to see if it was an intermittent network problem, but it fails each time. Any suggestions?

Cheers,
Jonny

Change History (12)

comment:1 Changed 3 years ago by ros

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

Hi Jonny,

I suspect at the end of the UMUI submission window (it might have disappeared off the end…) you will have something along the lines of:

You have selected a compilation step and  a continuation run CRUN.
This is not allowed. Please modify your UMUI settings.

You have a hand-edit ~umui/hadgem2/handedits/crun.ed that switches on CRUNs enabled. If you switch this off I think your job will then submit successfully.

Cheers,
Ros.

comment:2 Changed 3 years ago by jonny

Thanks Ros,
I tried that and it submitted fine. However the compilation failed, giving the following error:
ftn-2105 crayftn: ERROR in command line

"-i" is an invalid command-line option.

ftn-2191 crayftn: ERROR in command line

"8" is an invalid argument to the "-r" option.

ftn-2105 crayftn: ERROR in command line

"-t" is an invalid command-line option.

ftn-2105 crayftn: ERROR in command line

"-i" is an invalid command-line option.

ftn-2191 crayftn: ERROR in command line

"8" is an invalid argument to the "-r" option.

ftn-2105 crayftn: ERROR in command line

"-t" is an invalid command-line option.

ftn-2105 crayftn: ERROR in command line

"-i" is an invalid command-line option.

ftn-2191 crayftn: ERROR in command line

"8" is an invalid argument to the "-r" option.

ftn-2105 crayftn: ERROR in command line

"-t" is an invalid command-line option.

ftn-2105 crayftn: ERROR in command line

"-i" is an invalid command-line option.

ftn-2191 crayftn: ERROR in command line

"8" is an invalid argument to the "-r" option.

ftn-2105 crayftn: ERROR in command line

"-t" is an invalid command-line option.

fcm_internal compile failed (256)

do I need to set my compilation options differently?

Cheers,
Jonny

comment:3 Changed 3 years ago by ros

Hi Jonny,

I've just realised the job you've copied from Grenville is the intel compiler version he was using to do some testing. You need the cray compiler version which is UMUI job xjgcc.

Cheers,
Ros.

comment:4 Changed 3 years ago by ros

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

I'm now closing this ticket due to inactivity. Please re-open if you have further questions on this.

Regards,
Ros.

comment:5 Changed 3 years ago by jonny

HI Ros,
I've switched over to trying the job using the cce compiler, but still having problems getting it to run. It's failing to extract the code from FCM. Have I miss specified the path to the source code?

jonny@puma:/home/jonny> more /home/jonny/um/um_extracts/xmoda/umbase/ext.out
→Parse configuration: 0 second
→Setup destination: 0 second
Can't stat /home/jonny/um6.6.3/6.6.3_14918/HG6.6.3_hector_monsoon_archiving/src: No such file or directory

at /home/fcm/fcm-2016.02.0/bin/../lib/FCM1/ReposBranch.pm line 357.

ERROR: /home/jonny/um6.6.3/6.6.3_14918/HG6.6.3_hector_monsoon_archiving/src/include/declaration: declared source directory does not ex
ists
Extract failed on Thu Jul 7 10:43:16 2016.
→Extract: 5 seconds

Last edited 3 years ago by jonny (previous) (diff)

comment:6 Changed 3 years ago by grenville

Jonny

You should not need the working copy in the FCM Configuration Optional Modifications window - jusr switch it off - if you want archiving, please include

fcm:um_br/dev/jeff/HG6.6.3_hector_monsoon_archiving/src

in User Modifications.

Grenville

comment:7 Changed 2 years ago by jonny

HI Grenville,
I've made this modification and the job now starts to run, but appears to crash because of the archiving with:

"T qsserver failure at Wed Jan 4 17:17:04 GMT 2017
qscasedisp: return code after calling qshector_arch RCARC=2
qshector_arch: Failed to archive xmodaa.pjh8920 in 62.755 seconds."

in the .leave file.

I've checked that my ssh keys are ok and if I set the archive directory to be in 'work', rather than on the RDF and it seems to run fine then.

Any suggestions?

Jonny

comment:8 Changed 2 years ago by jonny

Hello,
The following hand edit is failing: ~jeff/umui_jobs/hand_edits/archiving_6.6.3 for this job?

jonny@puma:/home/jonny> more /home/jeff/umui_jobs/hand_edits/archiving_6.6.3
#!/bin/ksh

# Enable creation of qsmonsoon_nerc_arch and qshector_arch scripts
# for archiving on the monsoon nerc archive disk and on the hector archive.

ed FCM_UMUI_BASE_CFG <<\EOF
/inc $UM_SVN_URL∨src∨configs∨script_build∨script_targets.cfg/
c
inc fcm:um_br/dev/jeff/HG6.6.3_hector_monsoon_archiving/src/configs/script_build/script_targets.cfg
.
w
q
EOF

Do I need to run this this?

Cheers,
Jonny

comment:9 Changed 2 years ago by ros

  • Resolution answered deleted
  • Status changed from closed to reopened

comment:10 Changed 2 years ago by ros

Hi Jonny,

Please go to window "sub-model independent → compilation and modifications → UM Scripts Build" and switch on Enable build of UM scripts. Once you have succesfully rebuilt the UM scripts you can turn this option off again.

Cheers,
Ros.

comment:11 Changed 2 years ago by ros

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

comment:12 Changed 2 years ago by willie

Hi Jonny,

Regarding http://cms.ncas.ac.uk/ticket/1842#comment:7, I have now upgraded the archiving branch HG6.6.3_hector_monsoon_archiving to avoid this error. You just need to recompile your code, ensuring you use revision 21774 or later.

Regards,
Willie

Note: See TracTickets for help on using tickets.