SSB search error: “No such file or directory” after interrupted archive job (4381132)

In certain cases, users may experience search errors or missing log results in SSB, accompanied by messages like:

Logspace indexer error: Error opening log store file: error='No such file or directory'

Investigation shows that this can occur if an archive job was interrupted before completion.
When this happens, some .store files are moved to the archive target, while others remain partially copied or missing.
The indexer (logindexd) process then attempts to rebuild its index based on an incomplete file structure and fails to locate the missing log store files.

In the archive directory, one or more folders with names like .conflict1, .conflict2, etc. may appear.
These indicate that the archive process retried the same day’s data transfer due to previous failed or incomplete attempts.
It is also worth noting that if a file has the .conflict${N} extension, it indicates that the system attempted the transfer N times before completing successfully.
This feature ensures that files are eventually saved even if temporary network issues occur during the archive process.

Typical causes include:

• Temporary network interruption between SSB and the NFS/Samba archive target.

• File system latency or mount timeout during the archive process.

• Insufficient permissions or space on the archive mount.

When the archive process successfully reruns the next day, it transfers all remaining files and corrects the file structure, restoring normal indexing and search functionality.

In most cases, no manual action is required.
After the next successful archive job, SSB automatically reindexes and the issue disappears.

To verify and prevent recurrence:

1. Check the stability of the connection to the archive target (NFS/Samba).

2. Ensure sufficient disk space and correct mount permissions.

3. Review /var/log/ssb/archive.log for “conflict” or “retry” messages.

4. If needed, collect the following outputs for Support:

    

   find /opt/ssb/var/logspace/id/<logspace_ID>/2025 -ls > /root/local.local.fslist.txt

   find /opt/ssb/var/archives/<logspace_ID>/2025 -ls > /root/local.archive.fslist.txt

If the issue persists after the next archive cycle, contact One Identity Support with the debug bundle and the above outputs.