-
Notifications
You must be signed in to change notification settings - Fork 112
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
Need help diagnosing issue: java.lang.AbstractMethodError on template #172
Comments
Hi @RussellMcOrmond,
This looks a lot like: #160 (comment) -- this was a bug introduced in 3.3.3 that is fixed now in the So, I guess I should release that soon. I don't know what's going on with the Docker inconsistencies, but sounds like it's related to the above. |
I'm still wondering if there are some external dependencies that I can look into. This morning I migrated a 4'th server to Cantaloupe, and this one isn't showing the error. So far that is: OK http://image.wellington.canadiana.ca/iiif/2 This deployment is also our first deployment to production using Docker. These types of inconsistencies are why I wanted to move to Docker, so I'm wanting to learn what type of external differences cause issues with our Canteloupe container so I can avoid them. |
Just from looking it over briefly, I don't see any evidence that there is anything wrong with your setup. One way to test (this would also help me as I've only been able to reproduce the AbstractMethodError in Tomcat 7) would be to build your own In any case, I'll try to get a release out soon knowing that this a bigger problem than it appeared in #160. |
Thanks for the suggestion. Our developer @SaschaAdler who I'd normally ask if he could build will be on vacation for a few days. I'm knee-deep in other deployment work (I'm mostly Ops in our currently 2-person DevOps team :-), and will hopefully have a chance to do a test build early next week. |
That's OK. 3.3.4 has just been released and includes the fix for these |
Yesterday was the day we moved Cantaloupe into production, after having tested for many months (including providing a public demonstration at Canada's ACCESS2017 conference).
We deployed with 3.3.2, but after noticing many 500 errors relating to creating cache directories (and remembering something about that in the 3.3.3 release), we moved to 3.3.3.
While the locking works and we don't get any errors on creating caches, and derivative images work, we are getting an odd error when looking at pages that have a template.
Example:
With 3.3.2 we get the splash page with the cantaloupe image indicating version, but a 500 error with 3.3.3.
There are further complications...
We are deploying Cantaloupe using Docker, with the configuration detailed at https://github.com/c7a/cihm-cantaloupe
If we deploy the identical 3.3.3 tagged image to 3 servers we have two that show the error, but for reasons we haven't been able to determine yet the third gives the expected message:
When I do a
docker image inspect docker.c7a.ca/cihm-cantaloupe:3.3.3
, I can confirm I'm using the same image with the same RepoDigests and the same Layers. I'm using the same Docker version and build, and I even tried upgrading to the same kernel version.We're using Puppet to deploy startup scripts for the containers, and the setup is the same other than the IP address that we are binding to which is different on each server.
I will continue to determine differences between these machines, but thought I would ask in case this looks familiar to anyone.
Note: We noticed these because we are getting 500 errors rather than 404 errors when browsers request /favicon.ico . http://image.ulloa.canadiana.ca/favicon.ico We'll be fixing this issue separately https://github.com/c7a/cihm-public-cos/issues/1
The text was updated successfully, but these errors were encountered: