You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
http://s3.amazonaws.com/ala-nameindexes/latest seems to be missing the following resources that are referenced by nameindexer tasks:
dwca-col.zip
dwca-col-mammals.zip
IRMNG_DWC_HOMONYMS.zip
col_vernacular.txt.zip
(also merge_namematching.tgz but this may not be in use anywhere)
The text was updated successfully, but these errors were encountered:
Those files may have been added to S3 since you created the issue and the person who fixed it may have forgotten to comment here to let you know. They seem to exist for me now, with modification dates of 14 December 2017, a week after you commented here, giving the impression someone silently fixed the issue.
There are some issues with consistency (both size and the paths inside of the tar files) between the files deployed to archives.ala.org.au/ala-starr.it.csiro.au and those on s3.amazonaws.com but the person who created the name indexes isn't working this week so I can't resolve those until next week at the earliest.
The aws_name_indexes_repo is set to http://s3.amazonaws.com/ala-nameindexes/latest in ansible/roles/common/tasks/setfacts.yml
Running the ala-demo.yml playbook fails on the following task:
TASK [nameindexer : Download Catalogue of Life 2012] ***********************************************************
fatal: [vagrant1]: FAILED! => {"changed": false, "dest": "/data/lucene/sources/dwca-col.zip", "msg": "Request failed", "response": "HTTP Error 404: Not Found", "state": "absent", "status_code": 404, "url": "http://s3.amazonaws.com/ala-nameindexes/latest/dwca-col.zip"}
http://s3.amazonaws.com/ala-nameindexes/latest seems to be missing the following resources that are referenced by nameindexer tasks:
dwca-col.zip
dwca-col-mammals.zip
IRMNG_DWC_HOMONYMS.zip
col_vernacular.txt.zip
(also merge_namematching.tgz but this may not be in use anywhere)
The text was updated successfully, but these errors were encountered: