The Manager keeps on loading at startup

Problem/Symptom:The Manager keeps on loading and does not startup properly even after several minutes.

Potential Cause:

The Manager server (Java) tries to establish connections to the web server. If any of the server communication are not established, the Manager will not startup properly. The problem might be due to the following reasons:
- Java process not running on serverClient.
- The client cannot talk to server (blocked ports).
- Database is not running on the server.

The Manager server process is not running on the appliance or on the Manager software.

Remedy:

For Windows-based Manager, verify that the service is started and running properly.

From the Start Menu search bar, type cmd and open the command prompt with elevated privileges.
Run the command IMAGENAME eq java.exe to verify if Java is running on the server.
Check the output for java.exe on the server to ensure that the mem usage is above 500MB. If there is nothing listed, the Manager service is not running.
Run the following commands on a command prompt to verify that ports 8501 to 8505 are open and actively listening.
- netstat -an | find "LISTENING" | find "8501"
- netstat -an | find "LISTENING" | find "8502"
- netstat -an | find "LISTENING" | find "8503"
- netstat -an | find "LISTENING" | find "8504"
- netstat -an | find "LISTENING" | find "8505"
Verify if MariaDB is running by executing the command netstat -an | find "LISTENING" | find "3306"
Try to start the Manager manually by running tms.bat from <Manager_Install_Dir>\App\bin\. Look for error messages at the bottom of this output.
Check the bottom of the emsout.log file in <Manager_Install_Dir>\App\logs for errors.

Note
The default Manager installation directory is %programfiles%\Trellix\IPS Manager\App.

For Linux-based Manager, verify that the service is started and running properly.

Check if manager service is up by executing the manager status command.
Check if database service is up by executing the database status command.
Check the bottom of the emsout.log file for errors by executing the show log file emsout.log command.