Opened 6 years ago

Closed 6 years ago

#1299 closed help (fixed)

Copy of job not compiling/building

Reported by: charlie Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: ARCHER
UM Version: 6.6.3

Description

Hi,

I'm trying to run a copy of one of my own jobs (which itself works fine). The only difference between the original and the new one in the start date (and start dump) and the fact that the original was set up for Hector whereas I'm now using Archer. I'm fairly sure, however, that I have changed the relevant parts, corresponding to the machine name etc.

However, when I try to compile my job (to build the executable, then stop), it runs for an hour but doesn't actually create the executable.

I don't think I've done anything silly, but clearly I have.

My compilation output is at /home/n02/n02/cjrw09/um/umui_out/xiogg000.xiogg.d14141.t154431.comp.leave

Would you mind taking a look?

Thanks,

Charlie

Change History (3)

comment:1 Changed 6 years ago by grenville

Charlie

There are problems with the serial queues - ARCHER are working on it as a matter of priority. I suggest running the compilation on the login node interactively. To do this, cd to the relevant umui_runs directory on ARCHER ( xiogj-141155532 maybe) and run the umuisubmit_compile script at the command line.

There may be an fcm lock file which will prevent compilation - simply delete the lock file if this is the case.

Grenville

comment:2 Changed 6 years ago by charlie

Thanks very much, Grenville. I have now done that (I had to delete the lock file as you said), and it seems to have compiled and built the executable correctly. So I have now submitted my job to run, and it is queueing normally - hopefully Archer have resolved the problems now…

Thanks a lot,

Charlie

comment:3 Changed 6 years ago by grenville

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

Charlie

This problem has been ongoing at ARCHER for some time - we too are hopeful of a solution but I don't think it's there yet.

Grenville

Note: See TracTickets for help on using tickets.