Gateway server: Difference between revisions
No edit summary |
|||
| Line 24: | Line 24: | ||
To access top, start an ssh session and at the prompt: <code>jmoss2@prod_tms_server:~$ top</code>. | To access top, start an ssh session and at the prompt: <code>jmoss2@prod_tms_server:~$ top</code>. | ||
= System Logs = | |||
The Gateway Server provides [http://77.68.28.115/logs/ comprehensive logs] for all running services. The logging level is set to provide debug and error information and administrators therefore can expect that in some cases, the logs are quite large despite log rotation in operation. | |||
Revision as of 15:33, 6 July 2020
This page provides details on the tools and interfaces provided to monitor and diagnose issues with the Gateway Server
Glances / top
These tools are provided to visually display the performance and load of the operating system and to view running services. Administrators should be cognisant of:
- High CPU load and any associated warnings;
- High memory usage and any associated warnings - including swap file usage;
- High file system usage;
- Running processes, or processes not running that should be (note: a script is provided for this purpose).
Glances
Click here to learn more about Glances.
There are 2 ways to access Glances on the Gateway Server
- Method 1: Access via the Web Interface, or
- Method 2: Start an ssh session and at the prompt:
jmoss2@prod_tms_server:~$ glances.
top
Click here to learn more about top.
To access top, start an ssh session and at the prompt: jmoss2@prod_tms_server:~$ top.
System Logs
The Gateway Server provides comprehensive logs for all running services. The logging level is set to provide debug and error information and administrators therefore can expect that in some cases, the logs are quite large despite log rotation in operation.