**WARNING: THIS PAGE IS NOT APPROVED YET**

Checklist Guide

This checklist provides an approach to diagnosing and resolving common issues that might prevent the login page from displaying properly.

[Common] No Login Page

Check OS resources

Check available disk space: df -h

Check CPU Usage: top

Check RAM Usage: free -m

Look for available parameter.

It is ok to have very few free memory as long as available provides enough memory for the JAVA maximum allocated to grow fully.

Check Network

Confirm ports are not being used by another service: netstat -tulnp | grep [port_number]

Application ports are specified in setenv.sh

Default ports: 8888/8443 (collector) and 8080/8443/8444 (cockpit).

Check firewall rules: iptables -L or firewall-cmd --list-all

Firewall must not block incoming connections on application ports

Allow port : firewall-cmd --zone=public --add-port=[port_number]/tcp --permanent

Reload Firewall rule sudo firewall-cmd --reload

Check Application Service

Ensure the application services are running systemctl status promonitor / systemctl status promonitor-cockpit

Restart Service sometimes helps to recover: systemctl restart promonitor / systemctl restart promonitor-cockpit

Look for recent errors or messages in the application logs -> tail -f server.log

Dependencies

Dependency Issues:

Service Status Check: Verify the status of MySQL and VictoriaMetrics -> systemctl status mysqld.service, systemctl status victoriametrics.service

Reinstall Missing Dependencies: Reinstall missing dependencies -> apt-get install --reinstall mysqld or yum reinstall mysqld

Permission and Ownership Errors:

Verify File Permissions: Check for correct permissions -> ls -l /opt/Pro.Monitor

[Pro.Monitor] Can't create system

Basic Checks:

Verify Licenses expiration and the number of system allowed

[Pro.Monitor] Connector not working

Basic Checks:

Verify SAP JCO/SAP HANA driver installed