Join us for an engaging webinar, as we unravel the potential of AI for revolutionizing document management.
Watch Now
Enable your employees to remain productive throughout the document management process.
Read More
Learn how SmartZone uses a regular expression engine integrated into the recognition engine to achieve the best possible accuracy on data that can be defined by a regular expression.
Docubee is an intelligent contact automation platform built to help your team success
After restarting the Prizm Services, you may notice that the http://localhost:18681/admin status page shows a status of “unhealthy” and in the Internal Services section, the mongo-manager-service is showing a clock, and the text-service is showing a red x.
http://localhost:18681/admin
How can this be fixed?
Reason:
This will typically occur when the mongo-manager-service detects an unclean shutdown and the cache gets corrupted.
How to Verify:
You can do a search in the C:\Prizm\logs\mongod.log file on Windows or the /usr/share/prizm/logs/mongod.log file on Linux for the word "unclean" and you may find the following error:
C:\Prizm\logs\mongod.log
/usr/share/prizm/logs/mongod.log
Detected unclean shutdown - C:\Prizm\cache\mongo-manager-service\data\mongod.lock is not empty.
Resolution:
Stop the Prizm Services. For PrizmDoc 13.3 and above, clear out all subfolders under prizm\cache (leave the prizm\cache folder). For PrizmDoc 13.2 and prior, clear out all files and subfolders under C:\Prizm\services\mongo-manager-service\bin\mongodb\data Start the Prizm Services.
Stop the Prizm Services.
For PrizmDoc 13.3 and above, clear out all subfolders under prizm\cache (leave the prizm\cache folder).
prizm\cache
For PrizmDoc 13.2 and prior, clear out all files and subfolders under C:\Prizm\services\mongo-manager-service\bin\mongodb\data
C:\Prizm\services\mongo-manager-service\bin\mongodb\data
Start the Prizm Services.