I have 2 working instances of solr that i have been using on a couple Drupal sites using the std ApacheSolr module (not SearchAPI). I also have a site running using SearchAPI with the Search DB engine. It works fine. I am trying to see what is required to switch that SearchAPI based site over to use Solr.

My 2 solr instances are:

- local: Quickstart (Ubuntu) VM running Solr 1.4
- server: CentOS running Solr 3.5

I believe to use SearchAPI with either of these i need to copy over the schema.xml and solrconfig.xml from this module to the solr/conf folder. This fails for both instances when trying to access the solr admin page:

local: 

HTTP Status 500 - Severe errors in solr configuration. Check your log files for more detailed information on what may be wrong. If you want solr to continue after configuration errors, change: <abortOnConfigurationError>false</abortOnConfigurationError> in null ------------------------------------------------------------- org.apache.solr.common.SolrException: No system property or default value specified for confFiles at org.apache.solr.common.util.DOMUtil.substituteProperty(DOMUtil.java:311) at org.apache.solr.common.util.DOMUtil.substituteProperties(DOMUtil.java:264) at org.apache.solr.common.util.DOMUtil.substituteProperties(DOMUtil.java:272) at org.apache.solr.common.util.DOMUtil.substituteProperties(DOMUtil.java:272) at 
.
.
.

server:

HTTP ERROR 404
Problem accessing /solr/admin/index.jsp. Reason:
    missing core name in path

Comments

kenorb’s picture

kenorb commented
Priority: Normal » Major
kenorb’s picture

kenorb commented
Category: bug » support

Make sure that your solrcore.properties was properly copied into config dir.
I had the same error, but copying solrcore.properties solved the problem.

kenorb’s picture

kenorb commented
Status: Active » Postponed (maintainer needs more info)
liquidcms’s picture

liquidcms commented
Status: Postponed (maintainer needs more info) » Fixed

don't exactly recall what the issue was but i think getting latest -dev of Search API and the config files that came with it; and it works fine now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

rerooting’s picture

rerooting commented

This did not fix the issue for me, copying the config files didn't seem to help.

kenorb’s picture

kenorb commented

@rerooting:
Then you did something wrong.
E.g. you copied to the wrong dir, or you're using wrong version of solr, or something.
Make sure that you copied ALL the config files (including solrcore.properties) from the right dir to the right dir and look for the errors.
Please make sure that you're using 3.x version of Solr.
You can use the lastest Solr, but the config directories are different.
Once the solr is running, go to local admin page and check which version of schema you're loading. Also check the foreground for more details about the error.

Read more at:
https://drupal.org/node/1999280
As this is configuration issue, not the it-self module.

If you think it's a bug, then raise the separate issue describing more details.

rich_dawson’s picture

rich_dawson commented

Reporting the same issue. I deleted all duplicate entries listed by OP and found that solr now works (no longer encountering an error 500 page).

rerooting’s picture

rerooting commented

I'd suggest if you are running into this issue, to take a careful look at all your configuration files and double check the configuration in general as @kenorb reccomends. In my case, a puppet module that I was using was attempting to deploy instances with outdated config files. Sometimes providers such as Pantheon will provide their own solr config files, as will some modules where instances need specific configurations.

rich_dawson’s picture

rich_dawson commented

Thanks for your response rerooting. In my particular case, I am developing on xampp and installed solr into its own folder. I installed the Search API Solr Search module to integrate Solr into my Drupal site (so there should be no hosting provider issues here). The problem came when I copied the sorconfig.xml file from the 4.x branch over to my solr installation as instructed by the module's documentation. I came across this issue page and was able to resolve my problem by deleting the three duplicate entries listed in the discussion above. Opening the latest 7.x-1.3 branch of this module still shows the duplicate entries in the 4.x branch of the solrconfig.xml file. For example, there is both a <mergefactor>4</mergefactor> and a <mergefactor>10</mergefactor>.