-
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
Sage data node returns 504 error #39
Comments
Will look at it when I'm back from vacation next Monday. |
I googled real quick and found this: https://easycloudsupport.zendesk.com/hc/en-us/articles/360002057472-How-to-Fix-504-Gateway-Timeout-using-Nginx Your submission went through which means that it is probably just another error code we have to potentially account for. |
Referencing the log file: https://www.synapse.org/#!Synapse:syn26477061
You shouldn't even have sent this message. But I will not complain too much. Thanks @thomasyu888 ! |
The potential issue described below is not related to this issue, however it shows that the controller was able to create an annotation store for a submission created via nginx and after Sijia shared his issue. Therefore it's possible that we are facing a random issue. I will look at the link Tom shared and further investigate. Note: I haven't seen the Incorrect annotation store name for Mayo Clinic dataset?The controller successfully created an annotation store for the submission I made after opening this ticket, for the i2b2 dataset. I confirmed this using its Swagger UI. I can't find a similar entry for the Mayo Clinic dataset. However, it seems that an annotation store for this dataset has been created after I made my submission:
Given how close the ID |
@ymnliu made a submission today to the date annotation task and received a workflow error file. Below is the main issue. The error seems to happen when the the controller tries to create an annotation store in the data node. This is a new issue that likely results from adding an
nginx
container in front of the data node API container.Additional information:
@thomasyu888 Do you have an idea what the issue may be?
Next:
The text was updated successfully, but these errors were encountered: