-
Notifications
You must be signed in to change notification settings - Fork 6
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
Many error messages on the Registry #230
Comments
504 Gateway error is from nginx timeout frontend, which is set to (30sec). However, It is not recommended increasing nginx timeout. Since, purging is a python job even after we get 504 error, when we reload the page for next time all datasets should be purged. However, there are some datasets which can't be purged using the UI due to a database error. However, these datasets can be deleted/purged by running a paster command in ckan -
There is a fix coming for this issue, please see the github issue, we will incorporate this fix once it is merged with upstream ckan. |
Is it ok to purge 7 datasets in below link manually? |
Purge functionality is implemented in staging |
Deployed in production. Please let me know if we are good to run purge command in production. Thanks |
Hi Swaroop, Purge is working in staging. I still get a 504 time out error in live. Yes please try it out. Do let us know if we can expect any down time. Thank you. |
The 504 error is the time out from nginx (which is the recommended setting)- not from the CKAN. So if you refresh the page after a couple of minutes, all dataset should be purged. This 504 time out error occurs when there is a lots of items to purge which takes more than 30 sec. If you visit the trash page now all datasets should be purged. Please let me know if this is not the case. Thanks |
Closing the issue - please reopen if you face any issues. |
Hi,
I tried to purge the Registry today but received a timeout error, and it didn't compete.
This data file is also showing a fair few error messages. Not sure if it's related to the purging or not? https://iatiregistry.org/dataset/ec-fpi-88
The text was updated successfully, but these errors were encountered: