Solr 9 未加载但安装正确，配置集生成问题 - Drupal

Question

I have installed solr 9.0.0 on Apache2 Ubuntu 18.04 vagrant box. after the solr installation on my drupal site the solr page looks as below:

But when trying to open the solr url on browser - http://192.168.33.93:8983/solr/#/solr_core I see the below error:

Also tried http://localhost:8983/solr/#/solr_core produces the same error. Further, upon clicking the "Get condig.zip" button I see this error - Drupal\search_api_solr\SearchApiSolrException: No config-set template found for Solr branch 9.x in Drupal\search_api_solr\Controller\SolrConfigSetController->getConfigFiles() (line 285 of /vagrant/web/modules/contrib/search_api_solr/src/Controller/SolrConfigSetController.php) .

Any help on how the issue can be resolved?

Answer 1

...Step 5 – Allow Apache Solr Public Access The default Apache Solr runs on localhost only. To allow the Solr server publically accessible over networks, edit the /etc/default/solr.in.sh configuration file.

sudo vim /etc/default/solr.in.sh Search for the SOLR_JETTY_HOST variable. Uncomment it by removing the starting hash (#) symbol. Set the value to “0.0.0.0”.

read more in: https://tecadmin.net/how-to-install-apache-solr-on-ubuntu-22-04/

no meu caso eu configurei o firewall para liberar acesso a porta 8983 para a minha máquina, mas caso você esteja trabalhando em uma rede, você pode criar a regra que achar melhor!

Espero ter ajudado. Abraço

Answer 2

I've experienced a similar issue with Solr 9 service started but no webpage, seems by default it binds to IPV6. Disable ipv6 and edit the below adding the actual ip address.

"Solr now binds to localhost network interface by default for better out of the box security. Administrators that need Solr exposed more broadly can change the SOLR_JETTY_HOST property in their Solr include (solr.in.sh/solr.in.cmd) file."

if you installed as a service edit: /etc/default/solr.in.sh

standalone: solr-9.0.0/bin/solr.in.sh

Answer 3

I am able to figure out the problem. I was trying to install Solr 9 on Drupal 9.x which is not a possible thing. Drupal 9.x supported until solr 8. There was a config mismatch due to that. So I had to role back to solr 8 and re-upload correct configs, re-index my contents and everything worked correctly.