#2616 closed help (fixed)

Suite on Archer continually queueing

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

Description

Hi,

Sorry to bother you again, but one of my suites (u-ba469) running on Archer has been just hanging for the last few days - it's been running perfectly well so far, but got to 2319 and just says "submitted" since the middle of last week. I thought at first it might be because of a particularly busy period in the queue, but surely it shouldn't take this long? All of my other cycles have been in the queue for a maximum of a few hours.

Charlie

Change History (4)

comment:1 Changed 11 months ago by ros

Hi Charlie,

If you look on ARCHER (qstat -u cjrw09) you will see that you have no jobs in the queue and looking in the job.out file for the 2319 cycle it has run successfully.

Cylc sometimes loses contact with the suite, so if there seems to be a very long delay in a task running it is always wise to check on ARCHER. If you still have the cylc GUI up try manually polling the coupled task. If that doesn't work. Shut the suite down, if it isn't already and restart it.

Cheers,
Ros.

Last edited 11 months ago by ros (previous) (diff)

comment:2 Changed 11 months ago by ros

Hi Charlie,

There are permission denied errors connecting to ARCHER (see the <suite>/log/suite/err file. Please make sure you can login from PUMA to ARCHER with no prompt for password or passphrase.

Cheers,
Ros.

comment:3 Changed 11 months ago by charlie

Thanks Ros, I have now restarted the suite. As you suggested, when I shut everything down and tried to log back onto Archer, it asked for a password - so my ssh agent must have died at some point last week, meaning the next cycle couldn't be submitted. I didn't know that could happen mid simulation. I have now restarted my agent the usual way, and have restarted the suite - it's now running.

Charlie

comment:4 Changed 11 months ago by charlie

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