After puma2 and ARCHER2 both came back online I set everything back up and tried to run cylc play as in Restarting after puma2 reboot
Unfortunately the suite had submit-failed 10 times for many tasks in the UM building stage so did not keep running; I retriggered all the failed tasks with trigger “*//*/*:failed” from Interventions — Cylc 8.6.5 documentation but this didn’t fix the issue. Finally I ran cylc clean u-ea310 and cylc vip u-ea310 to try running the suite again from scratch.
However, I still get submit-failed for multiple tasks, with error messages saying certain files can’t be found; these look similar to the error logs in Submit-failed: puma2 to ARCHER2? - #8 by racheldiamond . Could this be some ongoing issue with the setup of my account on puma2 or ARCHER2? I think I now should have the correct versions of rose and cylc everywhere.
No joy I’m afraid, It looks like you’re whole work space is locked down.
cd /work/n02/n02/radiam24/
-bash: cd: /work/n02/n02/radiam24/: Permission denied
Just to note in case you’re not aware, the ~/cylc-run/u-ea310 folder sits in $HOME and the run1 (e.g.) directory is actually a symbolic link to the work area.
Re viewing files/folders, user needed to update their /work/n02/n02/$USER permissions from drwxr-S--- (upper case S!) to drwxr-s--- (lower case s) using chmod g+x ... See here Wikipedia.
Re submit-failed status messages, advised that ARCHER2 username was (I think) incorrect.
