You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The internal readme does not describe how to cancel a run in progress, which is sometimes desirable. Doing so requires access to the workloads account, and a few unusual steps to login to the running EC2 instance.
The short version is:
From the workloads account, go to EC2 and locate the Nextflow-workload instance.
Click the "Connect" button, then choose the "Session Manager" tab and then click "Connect"
In the terminal that opens, enter teh following commands
sudo su ec2-user
tmux a
If there is an active run, you should then see the Nextflow run in progress (If there is not, you will get a "no sessions" message). To cancel the run, enter control-c.
If you wish to exit without canceling the run, you can simply close the tab, or press control-b followed by d to detach from the tmux session.
Other instructions to include might be where the active log file is for monitoring. I think it should be at /opt/nextflow/.nextflow.log
The text was updated successfully, but these errors were encountered:
It might make sense to bundle this with better instructions for local workflow testing. See #113 (review) for some thoughts (not quite tested) on that front.
The internal readme does not describe how to cancel a run in progress, which is sometimes desirable. Doing so requires access to the
workloads
account, and a few unusual steps to login to the running EC2 instance.The short version is:
workloads
account, go to EC2 and locate theNextflow-workload
instance.sudo su ec2-user
tmux a
If there is an active run, you should then see the Nextflow run in progress (If there is not, you will get a "no sessions" message). To cancel the run, enter
control-c
.If you wish to exit without canceling the run, you can simply close the tab, or press
control-b
followed byd
to detach from thetmux
session.Other instructions to include might be where the active log file is for monitoring. I think it should be at
/opt/nextflow/.nextflow.log
The text was updated successfully, but these errors were encountered: