---
title: "Troubleshooting Acquia Search with Apache Solr Search module"
date: "2025-05-28T08:43:21+00:00"
summary: "Troubleshoot Acquia Search with Apache Solr: Step-by-step guide to resolve indexing issues and improve search results."
image:
type: "article"
url: "/acquia-cloud-platform/help/69461-troubleshooting-acquia-search-apache-solr-search-module"
id: "91ae98f3-d2bb-4155-ac86-365f4e7d26ef"
---

Note

Acquia Search may experience downtime when servers are rebooted for security reasons.

Use the following steps when you troubleshoot issues with Acquia Search with the Apache Solr Search module:

*   Attempt to connect from your local install using the subscription’s keys. You must disable and enable all the search modules to regenerate the salt variables. The step can determine if the issue is with the website or the search subscription.
*   Examine the version of the [Apache Solr Search](https://www.drupal.org/project/apachesolr) module.
*   If indexing appears to run fine but the results are sparse, examine `/admin/settings/apachesolr/query-fields` to ensure no major fields are configured to **Omit**. Also, scroll to the bottom of `/admin/settings/apachesolr/content-bias` and check which content types are excluded from indexing.
*   Find the last node indexed by completing the following steps:
    
    1.  Run the following command:
        
            drush -vd search-index
        
    2.  At some point, you’ll start seeing notices about what node IDs failed to index. Run the following command and note the limit:
        
            drush vget apachesolr_cron_limit
        
    3.  Divide the number returned by the previous command by `2`, and then use the resulting number with the following command:
        
            drush vset apachesolr_cron_limit [value]
        
        For example, if you have 100 results, run the following command:
        
            drush vset apachesolr_cron_limit 50
        
    4.  Repeat the process, halving the limit each time until you reach `1` as the returned number.
    
    When you reach `1`, you will know which node is causing problems.
    
    Another technique to find the last indexed node is to use the following command:
    
        drush vget apachesolr_index_last
    
    Use the following command for Drupal 7:
    
        drush php-eval 'module_load_include("inc", "apachesolr", "apachesolr.index"); $rows = apachesolr_index_get_entities_to_index(apachesolr_default_environment(), "node", 1); foreach ($rows as $row) { print_r($row); }'
    
    The reported node is probably where the indexing problem resides.