# Cannot kill a suite **URL:** \ **Category:** Unified Model\ **Tags:** help, cylc\ **Created:** [26 September 2024 06:35 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731 "2024-09-26T06:35:07Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sonyafiddes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/sonyafiddes/32/603_2.png) [@sonyafiddes](https://forum.access-hive.org.au/u/sonyafiddes)\ **Post date:** [26 September 2024 06:35 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/1 "2024-09-26T06:35:07Z")
Hi Team, I have a suite that has run successfully, but still seems to think it is running. `rose sgc` tells me ‘stopped with ‘succeeded’’ If I try `cylc stop 'u-di850'` I get: `Cannot connect: https://cylc.slf563.jk72.ps.gadi.nci.org.au:43092/set_stop_cleanly?kill_active_tasks=False: HTTPSConnectionPool(host='cylc.slf563.jk72.ps.gadi.nci.org.au', port=43092): Max retries exceeded with url: /set_stop_cleanly?kill_active_tasks=False (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',))` `cylc kill 'u-di850'` gives same response. Anyone know how I can stop this suite so I can re-run it!? Thanks, Sonya ---
**Author:** ![cbengel](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@cbengel](https://forum.access-hive.org.au/u/cbengel)\ **Post date:** [26 September 2024 06:54 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/2 "2024-09-26T06:54:24Z")
Hi Sonya, I am sure someone else will have a more thorough response, but it you want to run it again in the short-term, could you copy the roses/u-di850 directory to roses/u-di850.restart and then run from the new roses directory? It won’t solve the initial problem but might be a workaround … Best regards, Chermelle ---
**Author:** ![cbengel](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@cbengel](https://forum.access-hive.org.au/u/cbengel)\ **Post date:** [27 September 2024 03:29 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/3 "2024-09-27T03:29:26Z")
Hi Sonya, If you are still having any trouble with the job not stopping please email help@nci.org.au and hopefully they can point you in the right direction. Hopefully the problem resolved by itself. Best regards, Chermelle ---
**Author:** ![Paul.Gregory](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/paul.gregory/32/2566_2.png) [@Paul.Gregory](https://forum.access-hive.org.au/u/Paul.Gregory)\ **Post date:** [2 October 2024 01:27 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/4 "2024-10-02T01:27:50Z")
Hi Sonya I assume you’ve managed to fix this problem now, but in future, here are some commands I use to help kill errant rose suites and Cylc tasks. Some of these you may already know. From [Rose User Guide: Suite Control](https://metomi.github.io/rose/2018.02.0/html/rose-rug-suite-control.html) ```auto rose suite-stop rose suite-shutdown rose suite-clean ``` If there are still errant individual `cylc` processes I go after them with combinations of ```auto cylc scan cylc ping -v ROSE_ID ``` To find the Linux task/process ID of any `cylc` processes that remain you can use ```auto ps -fu $USER | grep cylc ps -ef | grep $USER ``` and then `kill `. See [Cylc scan and cylc kill - Cylc Support - Cylc Workflow Engine](https://cylc.discourse.group/t/cylc-scan-and-cylc-kill/281) for an example Although the error message you came up with looks more like a networking error b/w your persistent session and ARE/gadi and not a cylc issue per se. Cheers Paul ---
**Author:** ![sonyafiddes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/sonyafiddes/32/603_2.png) [@sonyafiddes](https://forum.access-hive.org.au/u/sonyafiddes)\ **Post date:** [2 October 2024 02:17 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/5 "2024-10-02T02:17:21Z")
Thanks Paul and Chermelle - actually the problem still persists. The rose commands all give me a similar error message as the original. The `cylc scan` command is telling me: `ERROR: [Errno -2] Name or service not known: cylc.slf563.jk72.ps.gadi.nci.org.au` I had also suspected this was because I’ve somehow stuffed up my persistent sessions - and possibly this confirms that to. I’ve not got a lot of time today to look at it, but I will try to take another look probably next week & let you know if I resolve it! I’ll email nci help as suggested too if I can’t figure it out then! Thanks for your help so far! ---
**Author:** ![cbengel](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@cbengel](https://forum.access-hive.org.au/u/cbengel)\ **Post date:** [2 October 2024 03:08 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/6 "2024-10-02T03:08:52Z")
Hi Sonya, The persistent sessions get killed after about 6 months or so. I usually just restart mine. You can check if your persistent session is still running with: persistent-sessions list See [Persistent Sessions... - NCI Help - Opus - NCI Confluence](https://opus.nci.org.au/pages/viewpage.action?pageId=241927941) I hope that helps. Best regards, Chermelle ---
**Author:** ![sonyafiddes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/sonyafiddes/32/603_2.png) [@sonyafiddes](https://forum.access-hive.org.au/u/sonyafiddes)\ **Post date:** [2 October 2024 23:05 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/7 "2024-10-02T23:05:33Z")
Thanks Chemelle + Paul - I’ve managed to fix it - was a persistent session problem. It had clearly been killed I guess with the maintenance they had to do a few weeks ago and I just didn’t even think of it… ---
**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\ **Post date:** [22 October 2024 21:42 UTC](https://forum.access-hive.org.au/t/cannot-kill-a-suite/3731/8 "2024-10-22T21:42:24Z")