How to Configure Solr Content Search in a Multi-Tenant FileCloud Environment
Original Question or Issue:
The customer reported a Solr error affecting users in the EU. The FileCloud Admin Portal displayed an error when attempting to configure Content Search, indicating that the Solr server might not be running.
Environment:
- Product - FileCloud Server
- Version - 23.261.2
- Platform - Linux
Steps to Reproduce:
- Log in to the FileCloud Admin Portal.
- Navigate to the Content Search configuration.
- Attempt to configure Content Search.
- Observe the error message indicating that the Solr server may not be running.
Error or Log Message:
Error
Unable to create configuration. Please ensure Solr server is running.
Defect or Enhancement Number:
Cause:
The issue was related to the Content Search configuration in the multi-tenant FileCloud environment. The existing FC Core configuration required reconfiguration, including the correct tenant-specific folder name and data path.
Resolution or Workaround:
- Removed the old FC Core configuration and reconfigured Content Search from scratch.
- Accessed the database server and verified the database configuration using the MongoDB connection string.
- Identified the tenant site name as
customer_02. - Cleared the data location from the Solr FC data path.
- Reconfigured Content Search and initiated indexing.
- Verified the fix by logging in to a user account and successfully searching for files.
Configuration steps for future reference:
- On the Solr server, navigate to:
/var/www/html/thirdparty/overrides/solarium/Solarium - Copy the
fcskelfolder into:/opt/solrfcdata/var/solr/data - Rename the copied folder:
- Standard setup:
fccore - Multi-tenant setup:
fccore_<site_name>
customer_02tenant:fccore_customer_02 - Standard setup:
- Set the ownership of the folder and its contents to the
solruser.For thecustomer_02tenant, run:chown solr.solr -R /opt/solrfcdata/var/solr/data/fccore_customer_02 - Reconfigure Content Search and initiate indexing through the FileCloud Admin Portal.
- Log in to a user account and perform a search to verify that Content Search is working correctly.
Notes: