Documentation > Drupal

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

Drupal
Looking for a simpler approach? The new Opensolr Search module for Drupal 10/11 replaces Search API Solr entirely — AI-powered hybrid search with zero indexing load on Drupal. Get it on Drupal.org

The Error

Your Drupal site fails to index content to your Opensolr Index, and the Error Log shows:

org.apache.solr.common.SolrException: java.io.FileNotFoundException:
/usr/share/solr/example/multicore/INDEX_NAME/data/tlog/tlog.0000000000000002357
(No such file or directory)

This means the transaction log (tlog) on your Opensolr Index has become corrupted. The tlog is a write-ahead log that Solr uses to recover from crashes — but when tlog files get deleted or corrupted, Solr cannot process new updates.

What Is the Transaction Log?

WHAT HAPPENS WITH A CORRUPTED TLOGDrupal Updatesends documentWrite to tlogtransaction logtlog MISSING!FileNotFoundExceptionindexing stopsFix: Reload/Repair clears the corrupted tlog and resets itOr remove updateLog from solrconfig.xml to prevent it entirely

How to Fix It

Quick Fix: Click Reload/Repair

  1. Go to your Opensolr Index Control Panel
  2. Click Reload/Repair under the Tools menu
  3. This resets the tlog files and clears the corruption

Your index should start accepting updates again immediately.

Permanent Fix: Remove updateLog

If this keeps happening, you can remove the updateLog from your solrconfig.xml entirely:

  1. Open the Config Files Editor in your Opensolr control panel
  2. Select solrconfig.xml
  3. Find and remove the entire <updateLog> block:
<!-- Remove this entire block -->
<updateLog>
    <str name="dir">${solr.ulog.dir:}</str>
</updateLog>
  1. Save and Reload your Opensolr Index

Note: Without updateLog, Solr loses crash recovery for uncommitted documents. This is fine for most Drupal setups since Drupal can re-index any content. If you re-upload config files from Drupal later, check that Drupal has not added updateLog back.

For Dedicated Environments

If you have a Dedicated Opensolr Environment, the Restart Solr Service button is also available, which always resolves this issue completely.

Why Does This Happen?

The tlog corruption typically occurs on shared cloud infrastructure when:

  • The Solr process runs out of allocated resources during heavy indexing
  • Multiple concurrent write operations cause file contention
  • The shared storage layer has a momentary issue

On dedicated environments with full server resources, this issue is extremely rare.

Quick Checklist

  • Click Reload/Repair in your Opensolr control panel — this fixes it immediately
  • If it keeps recurring, remove <updateLog> from solrconfig.xml
  • On dedicated environments, use Restart Solr Service for a complete reset
  • After fixing, re-trigger indexing from Drupal

Keep seeing tlog errors? Reach out to us at support@opensolr.com — we can fix it and help you prevent it from recurring.