System Health and Service Check
To identify an issue, you first need to check on system health and see which services and/or instances are running or has stopped. The Alarms & Monitoring module allows you to diagnose system health and check the status of services and instances.
To use the Monitoring feature, you must first configure the Monitoring screen. See the Configure Monitoring & Alarm guide to make the initial configurations.
To monitor system health:
- Log in with an admin user.
- Navigate to Alarms – Monitoring > Monitoring menu.
On the Monitoring screen, you can view the status of all instances in the environment, along with the CPU, memory, and disk utilization details.
Navigate to the Service Monitoring section on the Alarms – Monitoring > Monitoring screen to see if services are up and running. If the service status is Up, the service is running. If the status is Down, the service is inactive.
Click on the chart icon to see the service activity in detail. A different pop-up window opens for each service.
You can also check the status of Kron PAM components from Kron PAM Restricted CLI or Linux CLI. Execute the following commands to check the service status.
To restart or stop the services, execute the same command by replacing the status with restart or stop. (ex: systemctl restart netright-tomcat)
Kron PAM CLI | main ~$ service web-gui status |
Linux CLI | [root@sc~]# systemctl status netright-tomcat |
Kron PAM CLI | main ~$ service mobile-gui status |
Linux CLI | [root@sc~]# systemctl status mobilet |
Kron PAM CLI | main ~$ service ssh-proxy status |
Linux CLI | [root@sc~]# systemctl status nssoapp |
[root@sc~]# systemctl status guacd |
Kron PAM CLI | main ~$ service sftp-proxy status |
Linux CLI | [root@sc~]# systemctl status sftp_prox |
Kron PAM CLI | main ~$ service database-server status |
Linux CLI | [root@sc~]# systemctl status postgresql-11.service |
[root@sc~]# systemctl status symmetricds |