Overview

Customers may experience an issue where the Solr service does not create an index after a database conversion and ingestion.

This problem typically manifests as an CExportAsJSON::ExportToSolr failed with code -1 -  'HTTP ERROR 503 Service Unavailable' message when running the SOLR command line utlity solrutil, indicating that the Solr service is not running or is not accessible at the time of initialization.

This issue may occur even after successful database conversion and ingestion processes, and despite various troubleshooting steps such as checking the Solr service status, reviewing Solr logs, validating file permissions, reviewing Solr configuration, updating the Solr schema, adjusting Java memory settings, and reinstalling Solr.

Solution

To resolve this issue, follow these steps:

1. Check all the files in the rh9 folder and ensure they are executable.
2. If not, you may change the permissions of all files in the rh9 folder to be executable by running the command `chmod 777` on all files in the rh9 folder.
3. Run the preinstall script again.

After these steps, the Solr service should start correctly.

Summary

In cases where the Solr service does not create an index after a database conversion and ingestion, the issue may be due to non-executable files in the rh9 folder. Changing the permissions of these files to be executable and running the preinstall again should resolve the issue.

FAQ

1. What does the 'HTTP ERROR 503 Service Unavailable' message mean?
   This message indicates that the Solr service is not running or is not accessible at the time of initialization.
2. What does the `chmod 777` command do?
   This command changes the permissions of files, making them executable.
3. What should I do if the issue persists after following these steps?
   If the issue persists, it is recommended to contact technical support for further assistance.