FAQ & API Documentation

Select a category on the left, to get your answers quickly

Here are a few things to check if your Drupal won't connect to your Opensolr Index/Cluster.

1. Make sure you are using the latest Search API Opensolr module from the Drupal community, if you are using Druipal 8+ as this will make things much easier for you.

2. In your Drupal Solr Server settings, please select Solr with Basic AUTH OR Opensolr With Basic Auth

3. DO NOT forget to set the Opensolr Index AUTH Credentials, in your Drupal Solr Server Settings page, as it is described here

4. Try to set a shorter password for your Opensolr Index by going to your Index Security Tab in your Opensolr Index Control Panel (See image below). Replace INDEX_NAME with your own index name. (https://opensolr.com/admin/solr_manager/tools/INDEX_NAME#security)

Then try to use the new credentials in your Drupal Settings Page.

5. Make sure you upload the Solr configuration Files, provided by Drupal, in your Opensolr Index Control Panel, at: https://opensolr.com/admin/solr_manager/tools/INDEX_NAME#configuration (Replace INDEX_NAME with your own index name)

6. Make sure you use the correct connection parameters as indicated in the Opensolr Index Control Panel Dashboard: https://opensolr.com/admin/solr_manager/tools/INDEX_NAME#overview (Replace INDEX_NAME with your own index name)

I cannot index any content from my Drupal CMS to my Opensolr index.


Error is:

"2022-10-11 15:42:34 ERROR HttpSolrCall: - org.apache.solr.common.SolrException: java.io.FileNotFoundException: /usr/share/solr/example/multicore/INDEX_NAME/data/tlog/tlog.0000000000000002357 (No such file or directory)"



(replace INDEX_NAME with your own Opensolr INDEX NAME)


That's all because you are using updateLog in your solrconfig.xml

You can generally fix this by clicking Reload/Repair under the tools menu in your Opensolr index control panel.

Reload Repair Opensolr Index

There is also a Restart Solr Service that always fixes this issue, however that's only available if you have a Dedicated Opensolr Environment. 


The logic is that updateLog uses up a lot of system resources and causes the index to be corrupted until the tlog files are being removed, which is what that Reload/Repair button does among other things.
Another more permanent fix (only if you really must use updateLog in solrconfig.xml) is to move over to a larger dedicated OpenSolr Cloud server in which all server resources are not shared, and this issue will be mitigated.

Also, if you go here:

And you select solrconfig.xml form that select drop-down box, you then look for the updateLog snippet, and remove that tag entirely, for example:
    <str name="dir">${solr.ulog.dir:}</str>
Then this issue will not show up until you upload the config files from Drupal again. At which time you will have to do this again, or tell Drupal not to add that somehow.


You can use that, since that will try to reset the tlog (updateLog) of the Solr Index, which that's the thing that gets corrupted, and should sort this out.
Drupal - Search API Opensolr
Opensolr, is Drupal-Ready with, the Search API Opensolr Module.
Extends the main Search API Solr
 module and provides functionality for connecting and managing Solr using the Opensolr services.
Download NowRegister for a free 15 days trial


Drupal 6.x Known issue:

Looking at solrconfig_extra.xml you will find stuff like this:

<str name="accuracy">0.5</str>
<str name="maxEdits">2</str>
<str name="minPrefix">1</str>
<str name="maxInspections">5</str>
<str name="minQueryLength">4</str>
<str name="maxQueryFrequency">0.01</str>
<str name="thresholdTokenFrequency">.01</str>

You will have to change it to stuff like this:

<int name="maxEdits">2</int>
<int name="minPrefix">1</int>
<int name="maxInspections">5</int>
<int name="minQueryLength">4</int>
<float name="maxQueryFrequency">0.01</float>
<float name="thresholdTokenFrequency">.01</float>

I hope it's obvious why...
And please  try to find more occurrences of integers and floats being defined as strings, in the drupal config files... I'm sure there must be more erors like these, in other configs for other solr versions as well in drupal.

Just make sure that you have uploaded the solr config files that your drupal module has provided for you.
To upload your files, simply head on to your OpenSolr control panel, click on your index name, and then click on the Config Files Editor tab.

Once there, you should be able to see a dialog like this:

NOTE: Your files have to be inside of a valid ZIP archive.

After the upload, you will receive upload confirmation messages for each file inside your ZIp archive.
In case of an error, you wil receive the full java error stack-trace, so that you can easily identify the errors inside your configuration files.

We recommend you use a JSON Prettyfier extension for your browser. Preferably you could use one of chrome's extenstions for that.