This can happen for a number of different reasons. The key is to make sure the server has proper hardware specs along with checking the logs for errors. Sending us data points from the troubleshooting steps below will help tremendously. Below are steps to troubleshoot a GUI that is very slow or not initializing.
Step 1: Check the disk space and memory on the server itself to make sure you are not running out of storage space:
[support@demo ~]# df -h
Filesystem Size Used Avail Use% Mounted on
Step 2: Check the memory on your server directly and on any hypervisor you are currently running the server on. Lack of memory will cause performance issues:
[support@demo ~]# free
total used free shared buff/cache available
Mem: 65695452 4169860 804032 3277112 60721560 57712516
Swap: 67104752 15724 67089028
Step 3: Check the mysqld.log in real-time to see what errors you might be getting from the database
[support@demo ~]# tail -f /var/log/mysqld.log
Step 4: Run a web validation and check for any errors. If you see any errors, please email support (firstname.lastname@example.org) with this information:
[support@demo ~]# asl --web_validate -d
Step 5: Clear the cache on the browser and try logging back to into the GUI. While doing this, press ctrl + shift + i when logging into the GUI to check Network and Console performance. If you notices any errors, please send a screenshot in a ticket to support.
Step 6: Run the top command to see what processes are potentially bogging down your server:
[support@demo ~]# top