Skip to content
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

Problems with new cantaloupe.properties (1.0.0) #75

Open
patdunlavey opened this issue Sep 16, 2022 · 2 comments
Open

Problems with new cantaloupe.properties (1.0.0) #75

patdunlavey opened this issue Sep 16, 2022 · 2 comments

Comments

@patdunlavey
Copy link

I'm not sure if this is a bug report or a support request. It's not high-priority because we have a work-around that seems to be working.

When we upgraded our customized copy of archipelago-deployment-live by manually merging from esmero/archipelago-deployment-live/1.0.0, which includes the new esmero/cantaloupe-s3:6.0.0-multiarch image, I failed to notice that there were extensive changes to config_storage/iiifconfig/cantaloupe.properties. Remarkably, everything seemed to work fine! Well, except that we saw some errors for certain file formats, which lead us to notice our failure to pull in the new cantaloupe.properties file. So I copied in the 1.0.0 cantaloupe.properties file, and proceeded to add back in our S3Source settings (access_key_id, secret_key, and BasicLookupStrategy.bucket.name).

However, after restarting containers with these changes, all of our iiif file and info.json links are broken. I tried a few changes in the cantaloupe.properties file, including setting it to the stock 1.0.0 version (without our S3Source settings/credentials), and doing the opposite: adding in credentials/config for both S3Source and S3Cache, correcting the AWS region, and a few other things.

None of these changes helped. At the moment, I have reverted to the old cantaloupe.properties file, except I merged in the processor.ManualSelectionStrategy mappings from the new file, and now, as far as I can tell, everything is working fine.

As I think you know, @DiegoPino, we are using AWS S3 for both file storage and iiifcache. If you have any suggestions for settings I might look at in the new cantaloupe.properties file that might get it working for us, that would be great. But, as I said, we have it working, so no urgency.

@aksm
Copy link
Contributor

aksm commented Sep 16, 2022

Hi @patdunlavey, any chance it's permissions-related? I know I've accidentally skipped these lines from the docs once or twice in some upgrades I've done:

sudo chown 8183:8183 ../../config_storage/iiifconfig/cantaloupe.properties
sudo chown -R 8183:8183 ../../data_storage/iiifcache
sudo chown -R 8183:8183 ../../data_storage/iiiftmp

Can you share the original properties configs that you have?

@patdunlavey
Copy link
Author

Thanks @aksm . We're using S3 for our iiif caching. But I didn't think to check iiiftmp - I'm not sure if that uses S3 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants