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
JES error causes cromwell to hang and spew useless (for a user) error messages #1631
Comments
This one is different from previous JES issues that were error 500. So this issue might be a dupe. |
Here is another one (only appeared once), but the workflow keeps going... I am not even sure if I need to quit...
|
Here is another error that a user will have trouble determining if the whole workflow failed:
|
@LeeTL1220 does this still happen? |
Yes. Not as bad, but still pretty hard to debug. A fair number of
transient errors when I use JES.
…On Tue, Apr 4, 2017 at 1:03 PM, Kate Voss ***@***.***> wrote:
@LeeTL1220 <https://github.com/LeeTL1220> does this still happen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1631 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACDXk-_InNBhbZ4MPXcOdseOkaYuW2N2ks5rsnf_gaJpZM4KiVST>
.
--
Lee Lichtenstein
Broad Institute
75 Ames Street, Room 7003EB
Cambridge, MA 02142
617 714 8632
|
@LeeTL1220 we have made number of improvements with transient errors in JES, Cromwell (in version 26) will now retry transient errors automatically. |
In order to fix this, I had to issue a few
kill -9 ...
The text was updated successfully, but these errors were encountered: