This document describes an issue where the User Interface (UI) runs slow and crashes intermittently.
There are no specific requirements for this document.
The information in this document is based on Cloud Center Versions up to 4.7.X.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Problem: UI Runs Slow and Crashes
There is a known issue affecting 4.6.3 - 4.7.x where the notifications seen on the dashboard (logins and logouts etc) do not get purged from the database, once the database runs out of memory to hold them all, the UI becomes unresponsive and eventually crashes
Step 1. Verify the CloudCenter build information using this command.
This particular Issue only affects in 4.6.3 - 4.7.X -- and was resolved in 4.8.0
Step 2. Login to Postgres using Cliqr user.
psql -U cliqr -d cliqrdb
Enter password for Cliqr
Step 3. Enter this command to check the count of notifications from Postgres database.
select count(*) from notification;
Step 4. Note the count of notifications, If number is in the hundred of thousands or millions then issue is present.
Step 5. Quit the Postgres database and list the /mnt and /bak directory. Ensure that the files are owned by the cliqruser in /bak directory. If do not, you hit a known bug.
ls -l /mnt
Step 1. You need to give cliqruser permissions to write to the file location.
chown cliqruser:cliqruser /mnt/
Step 2. Verify /mnt is owned by cliqruser.
Step 3. Edit cliqr-mgmt-scheduler-context.xml file as shown here.
Step 4. Searches for cronTrigger in the file and should bring you to the correct location, as shown in the image:
Step 5. Copy the property named cronExpression and put the original in comments, change the second value to 0/15 and the third to *, as shown in the image:
Step 6. This makes the purge notification run every 15 minutes to speed up the fix.
Step 7. Stop and start the tomcat service.