-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ln: failed to create symbolic link 'OPTIONAL_FILE': File exists #35
Comments
Hi, were you able to solve this issue? |
@jmcamza I'm rerunning it with exactly the same command-line. And in parallel I'm running a direct basecalling job with Dorado. Do you have any idea what could be the cause of the error? |
@weishwu I had the same issue and it was solved when I deleted the work folder that is automatically created to store temporary files. After that, the command was run successfully. However, I’m not sure about the root cause, hope this information helps. |
@jmcamza Thanks. My rerun worked out smoothly. I agree that it may be because I didn't delete the previous folder. The problematic run was the first time I ran two basecalling jobs simultaneously, so not sure if that could contribute to it ( I did separate them into two folders though). |
Sorry to reopen this. @jmcamza Is this what occurred to you also? |
Hi @weishwu, apologies for missing this. I've opened a ticket on our side to investigate this and will keep you updated. In the mean time, does using a separate work directory for each workflow instance solve your problem? You can specify a working directory to |
Hi @SamStudio8, I'm experiencing the same issue when I try to run the workflow, including when I set the working dir with my script:
my error output:
demo data w/o reference:
|
Operating System
Other Linux (please specify below)
Other Linux
RedHat 7.9 (Maipo)
Workflow Version
v2.9.0-gd9e8593
Workflow Execution
Command line
EPI2ME Version
No response
CLI command run
Workflow Execution - CLI Execution Profile
singularity
What happened?
The previous run with the same command-line (only with a different sample name) worked out without errors. This run failed after running for 6 days. I guess the main basecalling was completed but some final wrapping-up failed. Is there a way to retrieve the basecall results in one of the output folders?
The log file is attached. The main error message is:
basecall_aln_sup.10272-CV-1_A-WGS.log
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response
The text was updated successfully, but these errors were encountered: