Product: ProfileUnity
Product Version: 6.8.5 +
Expires on: 365 days from publish date
Updated: April 19, 2024
Problem:
CPU is at or near maximum usage on a clustered Management Console server.
Symptoms:
Task Manager will show that processes related to LSASS will be utilizing a high percentage of the CPU.
Possible Resolution:
Open the computer certificate store on the affected server. There should be a ProfileUnity-Mongo@YourMemeberServer certificate from each of your clustered servers in the Personal and Trusted Root Certification Authorities certificate stores.
If you are missing a ProfileUnity-Mongo certificate from one of your clustered servers:
- Stop all Liquidware ProfileUnity/FlexApp services and the MongoDB service on the server with 100% CPU utilization.
- Take note of which server's ProfileUnity-Mongo certificate is missing.
There should be a ProfileUnity-Mongo cert from each of the servers on every clustered server. - From the server where the certificate is missing from, export the ProfileUnity-Mongo certificate with its private key.
Example: If ProU3.x's ProfileUnity-Mongo cert is missing, export the ProfileUnity-Mongo cert from ProU3.x - Import the ProfileUnity-Mongo certificate into the Personal and Trusted Root Certification Authorities certificate stores on the server with 100% CPU utilization.
- In this order, start:
- MongoDB service
- Liquidware Labs ProfileUnity Service
- Liquidware Labs ProfileUnity License Service
- Liquidware Labs FlexDisk Service
If there were member servers removed from the cluster, ensure those servers are no longer trying to communicate with the cluster by stopping the MongoDB service.
If you continue to see this issue:
- Stop all the Liquidware ProfileUnity/FlexApp services and then stop the MongoDB service.
- Clear the logs in:
- C:\Program Files (x86)\Liquidware Labs\ProfileUnity\logs
- C:\Program Files\MongoDB\log\mongo.log
- C:\Program Files (x86)\Liquidware Labs\ProfileUnity\FlexDisk\flexdisk.log
- C:\Program Files (x86)\Liquidware Labs\ProfileUnity\License Server\Logs
- Start the MongoDB service and then the Liquidware services.
- Contact support (support@liquidware.com) and collect\zip\attach the following updated logs:
- C:\Program Files\MongoDB\log\mongo.log
- C:\Program Files (x86)\Liquidware Labs\ProfileUnity\logs
- C:\Program Files (x86)\Liquidware Labs\ProfileUnity\FlexDisk\flexdisk.log
- C:\Program Files (x86)\Liquidware Labs\ProfileUnity\License Server\Logs