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
I am running nextflow off AWS batch using -resume feature. The job did resume and the application completed its run, but at the last moment before it ends, it errors with
The user-provided path .command.log does not exist.
The files is not in the s3 output directory as well, but the other .command files are there. Anybody know anyway I can debug this? I tried Googling and looking at command.sh as well as the other output files, they do not provide any details.
This discussion was converted from issue #4986 on May 10, 2024 07:51.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am running nextflow off AWS batch using -resume feature. The job did resume and the application completed its run, but at the last moment before it ends, it errors with
The user-provided path .command.log does not exist.
The files is not in the s3 output directory as well, but the other .command files are there. Anybody know anyway I can debug this? I tried Googling and looking at command.sh as well as the other output files, they do not provide any details.
Beta Was this translation helpful? Give feedback.
All reactions