-
Notifications
You must be signed in to change notification settings - Fork 38
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
Centrifuge error : (ERR): mkfifo(/tmp/72.inpipe1) failed. #422
Comments
This is not yet enough information to go on. The |
Something else that you can try is, when in that work directory, run echo $db_name to see if something went wrong there. |
Here is the contents of .command.log
The contents of .command.err look the same (to me) as .command.log
The .command.out file is empty
|
When I edited the .command.sh script to echo the $db_name variable, the result was Is this the correct value? |
I'm a bit at a loss as to the source of the error. @jfy133 do you have any ideas? |
Actually, there could be a problem with your harddrive where |
I get this sometimes too on my laptop during testing My suspicion is that somehow there is some conflict when there are multiple centrifuge jobs running at the same time. I think on my laptop I set maxForks to 1 and that helped reduce a lot those errors (IIRC). It's also been reported on the centrifuge repo I think but no response We have a slack thread with @erinyoung somewhere where I proposed it. |
I'm getting this issue too. So far setting the centrifuge process to maxForks = 1 has reduced it, less than ideal solution though. |
Spoke too soon. |
So I believe indeed it's something where two centrifuge runs on the same node send up trying to make the same pipe name, as per: https://stackoverflow.com/questions/13040021/mkfifo-error-error-creating-the-named-pipe-file-exists So I think if we can set a unique /tmp/ directory (as @LilyAnderssonLee tried before, but something went iffy), maybe we can get this to work |
My solution doesn't work currently because the --temp-directory option isn't exposed ot the suer for some reason... |
Perhaps centrifuge will honor the |
Nope, it's literally hardcoded in the software: https://github.com/DaehwanKimLab/centrifuge/blob/9e244583481cc273f74415f2a2418e8fd342ab17/centrifuge#L357 I've openned an issue to ask: DaehwanKimLab/centrifuge#268 |
Description of the bug
I downloaded the pre-built centrifuge database from https://benlangmead.github.io/aws-indexes/k2 (the full link is https://genome-idx.s3.amazonaws.com/centrifuge/nt_2018_3_3.tar.gz) to use with taxprofiler. It does not run as expected. I first brought this up in slack.
This is my database file (the listed kraken2 databases worked fine):
This is the error message:
Command used and terminal output
Relevant files
No response
System information
Nextflow version : 23.10.0 build 5889
Hardware : Local
Executor : local
Container engine: Singularity
OS : CentOS
Version of nf-core/taxprofiler : current
The text was updated successfully, but these errors were encountered: