×

Troubleshooting search error 425

 
When you use the advanced search feature in HTML files exported from Dr.Explain, you may encounter error messages with code 425 instead of search results.
 
A 425 error means the search index is being updated and is not yet ready. This is normal after you've made changes to your content.
 

Common causes

 
  • Indexing in progress: this is normal. Wait 5–10 minutes for large documentation sets.
  • Slow Solr service: increase CPU or memory limits for the Solr service.
  • Large index: allow more time for indexing to complete.
  • System overload: other processes might be using system resources.
 

Step 1: Wait a few minutes

 
Indexing takes time, especially for large document collections.
 
What to do:
 
  • Wait 5 minutes.
  • Try searching again.
 
If the error persists after 5 minutes: continue to Step 2.
 

Step 2: Check backend logs

 
This step requires access to your server via SSH and Docker.
 
Run this command:
 
docker compose logs drexplain-search-backend-controller
 

Look for these messages:

 
  • "Sending file xxx.htm to index" — the backend is currently indexing files. This is normal. Wait a few more minutes.
  • "Successfully sent file xxx.htm" — files are being sent to the index. If you see this repeatedly for a long time, the Solr service might be slow. Go to Step 3.
  • "Finished updating search index" — indexing is complete. Try searching again.
 
If indexing seems stuck: continue to Step 3.
 

Step 3: Check Solr resources

 
This step requires access to your server via SSH and Docker.
 

Check if Solr is using too much CPU or memory:

 
docker compose stats
 
Look for: the Solr container showing high CPU (near 100%) or memory usage.
 
If Solr is resource-constrained: your system might not have enough resources, or the CPU limit might be too low. Check your docker-compose.yaml file:
 
solr:
  deploy:
    resources:
      limits:
        cpus: '2.0'  # Should be at least 1.0 for reasonable performance
 
If the CPU limit is very low (e.g., 0.5): increase it to at least 1.0 or higher.
 

Step 4: Check for errors

 
This step requires access to your server via SSH and Docker.
 

Check for errors in the logs:

 
docker compose logs drexplain-search-backend-controller | grep -i error
docker compose logs solr | grep -i error
 
If you see errors: address the specific errors mentioned in the logs.
 
Made by Dr.Explain, software documentation tool