-
Notifications
You must be signed in to change notification settings - Fork 172
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
Unable to run the pipeline. invalid jar file error #420
Comments
Please add the following line to your module load singularity Also check if Cromwell JAR file is corrupted. java -jar /usr/users/shashank.tiwari/.caper/womtool_jar/womtool-82.jar --version |
Thank you for your reply. I fixed the issue with womtool.jar by using changing the java version from:
I have also attached the output cromwell file in this message. Please let me know what you think about the problem and if I should raise this in a new issue. Thank you for your help |
To further add to the above issue, the cromwell log file indicated an issue with the
With the stderr file indicating:
However on checking the directory I can see that the samstats file is present in the specified location:
|
Describe the bug
A clear and concise description of what the problem is.
Thank you for the pipeline,however I am having issues with running the pipeline on an HPC with slurm and singularity. The run fails with the error:
STDERR=Error: Invalid or corrupt jarfile /usr/users/shashank.tiwari/.caper/womtool_jar/womtool-82.jar
These are the input commands used:
OS/Platform
Caper configuration file
Paste contents of
~/.caper/default.conf
.Input JSON file
Paste contents of your input JSON file.
Troubleshooting result
If you ran
caper run
without Caper server then Caper automatically runs a troubleshooter for failed workflows. Find troubleshooting result in the bottom of Caper's screen log.If you ran
caper submit
with a running Caper server then first find your workflow ID (1st column) withcaper list
and runcaper debug [WORKFLOW_ID]
.Paste troubleshooting result.
The text was updated successfully, but these errors were encountered: