-
Notifications
You must be signed in to change notification settings - Fork 596
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
GATK should warn the user when the temp dir is "noexec" #8453
Comments
I have also stumbled over this. I am adding a detailed error log.
|
To bump an old issue: I could take a look at this if you knew of a good Java library method to test whether a directory is Also, for anyone else who stumbles upon this in the meantime, the flag to pass to GATK is |
As reported recently by Eric Jones:
"Many newer Linux distributions will mount /tmp with the noexec mount option. If /tmp is noexec, then any JNA code (Java code that extracts native binary components into shareable libraries and then executes that code) will fail. There are a number of GATK methods that do this.
A typical error looks like:
java.lang.UnsatisfiedLinkError: /tmp/libbwa.2929202181066681888.jnilib: /tmp/libbwa.2929202181066681888.jnilib: failed to map segment from shared object
There's an easy fix for it: you can use --tmpdir or one of the typical java methods that reset java.io.tmpdir to name a directory that isn't noexec. But it's amazingly hard to find clues about that being necessary. I found no references to noexec on the forum nor in the help section of the gatk site"
We should address this by explicitly checking on GATK startup whether the selected temp dir is marked noexec, and warn the user in that case.
The text was updated successfully, but these errors were encountered: