-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
SolrCore Initialization Failures #31
Comments
You're doing |
Thanks @rfay, but no, "adobe" is just my drush alias for the drupal site in the ddev project I am working on. Nothing is happening with a remote server. I have removed it from the error description in order to remove confusion, but I do wonder if this add on has been tested in multi-site setups. The old ddev-drupal9-solr add works fine in multi-site mode. One thing I appreciate about this add-on (ddev-solr) is that it doesn't force you to name your "core" (now collection) any one specific thing. But the cost of this seems to be that since nothing is pre-built/pre-configured on the server, that there are more problems in getting to a non-error state. When I ran into the error with the missing basic fields config, I wondered if it could be a change in the upstream docker container ... that this add on used to work but now is assuming certain defaults and configuration that no longer holds. |
I guess there's nothing wrong with using that one.
I have not heard of anyone using ddev-solr with multi-site, but don't know why that would actually be relevant.
There have been no non-trivial changes to this add-on in 10 months, see https://github.com/ddev/ddev-solr/commits/main/ Please try it in a limited test environment and see if you can sort out what's going on. (Create a trivial project using a quickstart, extend it to a multisite after you have the add-on working, etc.) |
Some interesting reading that might have some connection to the issues encountered here: |
Was https://www.drupal.org/project/search_api_solr/issues/3104189 actually the issue for you? |
Not sure. I am waiting for another time window where I can dig deeper and hopefully come up with some useful knowledge to help others. |
@apotek try to follow the README with a fresh installation of drupal. It seems that you messed up your Solr configs in Drupal. If that works we can take a closer look. |
no further feedback |
Sorry for the lack of feedback. I didn't have time budget to keep troubleshooting this add-on. We ended up having to use https://github.com/ddev/ddev-drupal-solr in order to get things working. If I ever get the budget to revisit this, I will add more info, but it looks doubtful. |
I am following the steps in the README.
ddev get ddev/ddev-solr
ddev restart
http://<projectname>.ddev.site:8983
"So, I go to
http://<my project>.ddev.site:8983
and log in and see the following:SolrCore Initialization Failures
So I check my logs:
Log4j2
Consequences
I also note that no cores or collections have been initialized on startup (according to the solr UI). I was expecting that one would be created in the docker compose build steps.
Sure enough, just as I feared, when I configure my connection to solr in Drupal with:
Server Name: solr
Backend: Solr
Solr Connector: Solr Cloud with Basic Auth
Solr node: solr
Solr port: 8983
Solr Path: /
Default solr collection: mycollection
http basic auth: (username and password as specified).
Save
I get the following message:
I check the solr admin page and I see that solr, as I feared, does not see my collection. I forge ahead...
Ok. I follow these instructions. Number of shards 1, etc, And I click the upload button.
I get the following error:
So it looks like the container is failing to be initialized with something essential pre-requisite setups.
When I ssh in to the container, I see indeed that no collection has been created on the file system:
Viewing the solr server I set up, I see that I can connect, but the collection is not available. "The Solr collection could not be accessed. Further data is therefore unavailable."
You can see also in the
search_api_solr
module output that the module is making a very odd request to solr:8983/solr/benz/admin/luke??? I have no idea why it would be requesting such a path.I have made no changes to anything other than the ones specified in the README. No customizations to the image, or to
.ddev/docker-compose.solr.yaml
Changing connection from auto detect to 8.x doesn't help.
Trying to make it work
Using the solr admin UI, I created a collection, using the same name as the failed attempt from the search_api_solr module.
That succeeded, and when I visited the server "view" page again, I get a message saying that the module can see the collection:
Ok Great! Time to upload the configset!
I click the Upload configset button and say yes to overwrite the _default config set for my collection.
And then I get this error in search_api_solr:
Looking in the logs on the solr server, I see:
I don't know how to interpret this but it sure seems like there is an incompatibility between the config set search_api_solr wants to generate and what solr-cloud is expecting.
Well, let's try with drush:
I'm stumped. I tore down and removed my ddev setup, purged my volumes and docker images and tried again. Same result.
The text was updated successfully, but these errors were encountered: