Hi,

I've properly installed Solr 3.5.0 on Tomcat 7 in a CentOS 6 distribution, configuring Solr to run as a multisite server.
I've installed Drupal 7.12 and the module Apache Solr Search Integration (7.x-1.0-beta16) in two sites (site1 and site2), replacing the files schema.xml, solrconfig.xml and protwords.txt in the Solr directories with those that come with the module.

So, I've acces to:

http://localhost:8080/solr/

where appear the links to the administration pages of both sites:

http://localhost:8080/solr/site1/admin/
http://localhost:8080/solr/site2/admin/

And all works fine.

But when I try to configure the settings in the Drupal sites (admin/config/search/apachesolr/settings/solr/edit), I can't connect with the Solr server (the error message is "Your site was unable to contact the Apache Solr server.").

In the filed "Solr server URL" I've tried with:

http://localhost:8080/solr/site1/
http://localhost:8080/solr/site1
http://localhost:8080/solr/site1/admin/
http://localhost:8080/solr/site1/admin
http://localhost:8080/solr/
http://localhost:8080/solr

but I obtain the same error message with all of them.

I ignore if the module is conceived/ready to function in a multisite Solr configuration, and which URL should I use in that case.

Thanks!!

Comments

ecalcerrada’s picture

ecalcerrada commented
Assigned: ecalcerrada » Unassigned
ecalcerrada’s picture

ecalcerrada commented
Priority: Major » Critical
ecalcerrada’s picture

ecalcerrada commented
Priority: Critical » Major
nick_vh’s picture

nick_vh
he/him
Location Ghent
commented
Category: bug » support
Priority: Major » Minor
Status: Active » Closed (cannot reproduce)

It should be http://localhost:8080/solr/site1 and I'm not sure about the configuration but it will probably be a permission problem.
Keep investigating, but this is not a drupal problem unless proven otherwise

ecalcerrada’s picture

ecalcerrada commented

Ok, I've finally found the solution here (http://drupal.org/node/410896#comment-4113768).

The problem was SELinux preventing the http daemon from connecting to itself or the relay ports. SELinux denied the http daemon from connecting to itself or the relay ports. To allow httpd to connect to httpd/ftp ports you need to turn on the httpd_can_network_relay boolean:

# setsebool -P httpd_can_network_relay=1

webmaster-eddie’s picture

webmaster-eddie commented

I have the same problem - I am able to get solr admin page (solr 3.6 with tomcat 6.0.35 on debian 7.14 in an aegir platform) to show up in browser, but there is no connection - nothing sent from the site to the solr core instance. no path in solr config seems to work. COuld this be a problem because I am trying to use this inseide /var/aegir/platforms/platform-name ...

I have my CATALINA_BASE in /var/lib/tomcat6 and my CATALINA_HOME in /usr/share/tomcat6 (where there are no cataline files at all - tomcat6 and catalina look first to the BASE where the files are.

The point I am unclear about is - where exactly am I telling the tomcat6 solr instance what core I am referring to? Is it only in the Drupal module configuration settings (which won't take any path I give it)? I have followed the tutorials, and have checked my pemissions - all relevant files and directories are chown to tomcat6:tomcat6

ANy clues here? Thanks for input. The only guess I have is that I don't have iptables, I have ip6tables-multi and iptables-multi which I cannot seem to write to. I am looking into this, as I have set tomcat6 to use a different http port and have not added that port to iptables. WOuld this cause the drupal solr module configuration settings to fail?

Best

Eddie