Log scaler
- Stop service
sudo systemctl stop InspireScaler30600.service
sudo systemctl stop InspireProductionServer-30354.service
sudo systemctl stop InspireContentManager-30353.service
- Move in the the logs folder (/data/Quadient/InspireScaler/logs)
- The files to check are
- If are necessary to empty the file, it's will possible with the following command:
echo "" > NameOfTheLog.log
- The most info is always in the server.log - in case of any issues with the app, check this log first.
- Cleaning IPS and ICM logs
- Now start the service in opposite order as were stopped.
sudo systemctl start InspireContentManager-30353.service
sudo systemctl start InspireProductionServer-30354.service
sudo systemctl start InspireScaler30600.service
- Verify that logs are getting filled correctly
Cache scaler
- Cleaning cache:
Scaler:
- cd /data/Quadient/InspireScaler/icm/internal/cache
- remove or rename file ─ _certificates_.txt
IPS:
- cd /data/Quadient/Inspire-Designer-data/working/InspireProductionServer-30354-cache
- remove or rename file ─ _certificates_.txt
Log Interactive:
- Stop service
sudo systemctl stop InspireInteractive.service
sudo systemctl stop InspireProductionServer-30354.service
sudo systemctl stop InspireContentManager-30353.service
- Clean logs nteractive:
cd /data/Quadient/InspireInteractive/
echo "" > Default.log
cd ./advanced/
echo "" > Detail.log
echo "" > Other.log
echo "" > Requests.log
echo "" > Saml2Spring.log
echo "" > Spring.log
cd ./icm/
echo "" > icm-library.log
- Cleaning IPS and ICM logs
- Now start the service in opposite order as were stopped.
sudo systemctl start InspireContentManager-30353.service
sudo systemctl start InspireProductionServer-30354.service
sudo systemctl start InspireInteractive.service
- Clean cache Interactive:
- cd /data/Quadient/Inspire-Designer-data/working/InspireProductionServer-30354-cache
- remove/rename _certificates_.txt
In the ICM - find vcs:\\Interactive\.config\configuration.json and edit the DB connection string to the correct DB.
