Opened 3 years ago

Last modified 3 years ago

#224 assigned

Long running cylc processes

Reported by: Scott Wales Owned by: Martin Dix
Priority: major Component: ACCESS model
Keywords: TIWG Cc:

Description

Martin says there are some long-running cylc jobs on accessdev - check why they aren't timing out

Change History (5)

comment:1 Changed 3 years ago by Martin Dix

% ps -ef | grep gui
...
rhw548   15609     1  6 Jul20 ?        3-23:49:51 python /usr/local/cylc/cylc-6.4.1/bin/cylc-gui --host=localhost au-aa356
...

4 days CPU time (and still increasing) yet the suite isn't currently running and was last active two months ago!

comment:2 Changed 3 years ago by Scott Wales

Timeout has been changed to 3 days in https://accessdev.nci.org.au/trac/browser/roses/a/a/3/5/6/trunk/suite.rc#L14, perhaps that isn't working?

comment:3 Changed 3 years ago by Martin Dix

I think that timeout just applies to the controlling cylc process and doesn't affect the gui.

Before the reboot we had some long running cylc-run processes (#196). At the moment it just seems to be the gui.

comment:4 Changed 3 years ago by Scott Wales

Owner: set to Martin Dix
Status: newassigned

comment:5 Changed 3 years ago by Scott Wales

Look into creating a script to notify users, or kill long running sessions

Note: See TracTickets for help on using tickets.