-
Notifications
You must be signed in to change notification settings - Fork 243
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
fasterq-dump segfaults immediately #518
Comments
Update: Of the 5 files I tried this on, only one was successful. The one above (SRR1168069) failed with one error last time, and different error in subsequent tries with an older docker image. The other one I mentioned in that comment (SRR1168053) succeeded. using docker image
using docker image
|
Just did a new prefetch of |
By falling back to 2.10.9, and giving it more cores (4) and more memory (16g), I was able to push these through. using a command like: Even then, I've experienced issues where this command would segfault with
And then I could clear the temp directories, run the same command again, on the same machine, in the same directory, and it would succeed. Happy to provide more info if it's helpful for debugging, or for adding more informative error messages. |
Did you try the latest toolkit? |
Using 3.0.0 outside of docker seems to work fine, but I encounter the same issues from inside the official docker container. At this point, I think it might be some kind of strange environment issue in our HPC cluster's docker implementation that I can't nail down. I suppose this can be resolved, though I may come back and revisit it some day when I have more free time. Thanks |
It segfaults also inside docker? I would suggest the following:
|
I downloaded some data with
prefetch
and the status messages show that everything was pulled down successfully. All of the reference files, the sra file, and a vdbcache file are all present and seem of reasonable size:When I try to dump fastqs, though, I get an immediate segfault:
This is true whether I run it in
ncbi/sra-tools:latest
or use an older version likencbi/sra-tools:2.10.8
. To add to this, I was able to successfully convert one sra file (SRR1168053) to fastq using this command and the latest version, so I suspect a problem with the dataSuggestions for how to proceed or debug would be welcomed - thanks!
The text was updated successfully, but these errors were encountered: