Use the procedure outlined in this SAS KB article to clear the standard middle-tier logs and rebuild the SAS Content Server search indexes. Rebuilding the indexes removes the existing index contents and creates new index contents when SAS Content Server starts.
Important
This procedure stops SAS services and removes existing log files and search-index contents. Schedule an outage before you begin. Delete only the contents of the listed directories, not the directories themselves.
Before you begin, do as follows:
- Confirm the SAS configuration directory and level for each server.
- Identify the primary and secondary middle-tier nodes. Skip secondary-node paths if the deployment contains one middle-tier node.
- Confirm that you can stop and start SAS services on the compute and middle tiers.
- Back up or archive the existing index contents if required by your site procedures.
Procedure
1. Stop the services.
- On every middle-tier server, stop SAS services using sas.servers stop.
- On every compute-tier server, stop SAS services using sas.servers stop,
- Confirm that the services have stopped before you continue.
2. Remove the existing log files.
Delete or archive the applicable log files from the following directories. Replace <SAS_CONFIG>, Lev#, SASServerX_Y, and the instance name with values from your deployment.
- <SAS_CONFIG>/Lev#/Web/WebAppServer/SASServerX_Y/logs/
- <SAS_CONFIG>/Lev#/Web/WebServer/logs/
- <SAS_CONFIG>/Lev#/Web/Logs/SASServerX_Y/
- <SAS_CONFIG>/Lev#/Web/activemq/data/
The distributed-cache directory name depends on the installed SAS® 9.4 revision. Use the directory that exists in your environment:
- <SAS_CONFIG>/Lev#/Web/gemfire/instances/ins_41415/*.log - earlier SAS 9.4 revisions
- <SAS_CONFIG>/Lev#/Web/geode/instances/ins_41415/*.log - later SAS® 9.4M8 (TS1M8) revisions and all SAS® 9.4M9 (TS1M9) revisions
Note: Only the folder name changes from gemfire to geode. The remainder of the path is the same. Do not create or rename either folder.
3. Remove the existing index contents
Delete or archive only the contents of the following applicable directories. Replace <SAS_CONFIG>, Lev1, and SASServer1_1 with values from your deployment.
Primary Node:
- <SAS_CONFIG>/Lev1/AppData/SASContentServer/Repository/repository/index/
- <SAS_CONFIG>/Lev1/AppData/SASContentServer/Repository/workspaces/default/
index/
Other Nodes:
- <SAS_CONFIG>/Lev1/AppData/SASContentServer/SASServer1_1/Repository/repository/
index/ - <SAS_CONFIG>/Lev1/AppData/SASContentServer/SASServer1_1/Repository/workspaces/
default/index/
Note: Delete the contents of each applicable index directory. Do not delete the index directory itself.
4. Start the services in order
- Start SAS services on the compute tier using sas.servers start.
- Start SAS services on the primary middle-tier server using ssas.servers start and wait until start-up completes.
- Start SAS services on each remaining middle-tier servers.
- Confirm that all required services are running.
Result
SAS services create new log files, and SAS Content Server rebuilds the search indexes after the services start.