-
Notifications
You must be signed in to change notification settings - Fork 0
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
Clean install of hydra-jetty results in broken solr deployment #138
Comments
@StudioZut did you the following again:
|
@kilahimm I know I did those on my clean instance, and tried a few times with @StudioZut on his instance. I believe there is a problem with the version of hydra-jetty; I would recommend trying to see if you can get it to pin the version back (the solution in samvera-deprecated/sufia#1300 might be worth another try ) |
This may have been resolved in Sufia 6.4.0 by samvera-deprecated/sufia@cf4de2a / samvera-deprecated/sufia#1330 - test and close if this works now. |
@StudioZut encountered this problem and I was able to reproduce it in a brand new instance. I installed just sufia (no DB), java 8, and ran the hydra-jetty install steps (rake sufia:jetty:config). Jetty runs, with fedora, but solr doesn't run correctly. Error 500 with stack trace:
I am fairly confident that this has something to do with it. https://github.com/projecthydra/sufia/pull/1300/files
I tried overriding sufia-dev.rake with the version there that adds pinning the version of hydra-jetty but haven't gotten this to work yet (this part may be worth another try).
@kilahimm sending this to you as I'm hoping you might have some bandwidth at the moment. I am severely crunched for time at the moment, and would like to get @StudioZut up and running. An alternative would be to have him set up the separate deployment of solr and fedora, but on the same server, as per the production install section of the readme.
The text was updated successfully, but these errors were encountered: