-
Notifications
You must be signed in to change notification settings - Fork 14
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
CKAN Harvest troubleshooting: ERDDAP WAF harvests failures/outdated datasets #238
Comments
The GCOOS Oceanographic WAF (https://data.ioos.us/harvest/gcoos-erddap-oceanographic/job/last) was deleted from CKAN at some point, need to restore it. URLs: https://erddap.gcoos.org/erddap/ |
Looks like ERDDAP WAF harvests are working better as of June/July, closing this issue. |
Reopening and renaming this issue as there is still an issue where some harvest jobs get stuck in a frozen state and the cleanup script does not properly identify them and restart the jobs. This resulted in significantly outdated datasets or WAFs where no datasets were present due to a failed harvest. During today's meeting @benjwadams updated the script to use the Let's keep this issue open until the CKAN harvesting is functioning properly and consistently for most harvests (CS-W excepted). |
GCOOS WAF Historical WAF - https://data.ioos.us/harvest/gcoos-waf-historical/job Looks OK These all look OK, with CARICOOS having possibly changed ERDDAP location. |
Spot check today of harvest sources shows many jobs not finished properly (no finish date in job metadata) since ~ Feb 20 - cleared by cleanup script instead? Harvester configuration (Docker containers):
|
Further investigation shows that after the fixes for automatic job starts for stuck harvests were removed, non-daily jobs appear to be running on the appropriate schedule. Here is "GCOOS Oceanographic WAF", which is
|
Related to #247 |
During today's Catalog meeting, we changed the GCOOS ERDDAP Biological WAF harvest to manual to test whether CKAN honors these settings properly or not. Follow up to confirm in the next few days. |
GCOOS ERDDAP Biological WAF has not run a harvest since June 4, so it looks like the harvest settings are being honored. ERDDAP harvests in general appear to be working more reliably, so closing this issue again as resolved. |
This may be a one-off, but the AOOS ERDDAP WAF harvest job appears to be 'stuck'. It hasn't run since July 30: https://data.ioos.us/harvest/aoos-erddap/job Also:
Reopening this issue to address this and in case there are other problems with harvest jobs not being run on an ongoing (weekly) basis. |
With changes made to harvest sources to weekly frequency per ioos/catalog#91, the harvests appear to be running more reliably now. Closing this issue again. |
Note:
This issue is more about restoring overall harvesting functionality than troubleshooting individual harvest sources. We'll work off of a separate, newly created issue: ioos/catalog#87 to restore all of the RA/data provider harvest sources once CKAN harvesting is functioning more consistently/reliably.
Example harvests:
Example list of some harvest sources that have had issues in the past for reference
GCOOS Oceanographic: https://data.ioos.us/harvest/gcoos-erddap-oceanographic/job/last - no datasets
GCOOS Biological: https://data.ioos.us/harvest/gcoos-erddap-biological/job/last - no datasets
GCOOS Historical: https://data.ioos.us/harvest/gcoos-waf-historical/job/last - no datasets
CARICOOS: https://data.ioos.us/harvest/caricoos-erddap-server-iso-waf/job/last - no datasets
The text was updated successfully, but these errors were encountered: