-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix issue "returned non-zero exit status 52: b" on MCW data site #31
Comments
The tool annotated 193 notes then died during the submission From 9713419_fail.csv.zip:
Second submission that failed: From 9713424_fail.csv.zip:
|
Interestingly both submissions failed at/after the same request (193), which is before the end of the MCW dataset (424 notes). The tool logs don't show an error, just |
@thomasyu888 Given the above information, are there cases where event outside of the tool - for example from the controller - that could kill the tool? |
@tschaffter Not that I know of, unless the tool reached max memory allotted to it by the docker run command. |
Submissions:
The logs generated by the controller show:
Interestingly, I encountered this post that says that 52 is an error code if Apache Spark, which I use, associated to Out Of Memory.
However, the above logs is associated to a curl command. I found this comment online:
Did the tool crashed?
Other posts mention that this error is associated to "curl: (52) Empty reply from server".
Also:
@gkowalski I'm wondering whether the tool crashed, which may have led to curl receiving an empty response. This is way having a look at the MCW logs for the tool could help to identify if the tool crashed.
The text was updated successfully, but these errors were encountered: