Gateway server: Difference between revisions
| Line 42: | Line 42: | ||
Administrators should observe the following: | Administrators should observe the following: | ||
{{warning|1=Here is a long warning, which is sufficiently wordy to run onto a second line (unless you have a really large screen!), which would normally cause it to wrap round the icon, but because we passed it as a parameter it keeps its left alignment straight.}} | |||
[[File: Gateway_service_script.png|border|400px]] | [[File: Gateway_service_script.png|border|400px]] | ||
Revision as of 17:08, 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:
<user>@prod_tms_server:~$ glances.
top
Click here to learn more about top.
To access top, start an ssh session and at the prompt: <user>@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.
RabbitMQ Interface
Without doubt, the RabbitMQ broker is the main component of the Gateway Server.
Acumen Service Management Script
For convenience, a script is provided that guides administrators to the status of vital services on the Gateway Server. To access the script, start an ssh session and at the prompt:
<user>@prod_tms_server:~$ cd /var/www/server_tasks
<user>@prod_tms_server:/var/www/server_tasks$ ./service_script.sh
Administrators should observe the following:
Administrators should note that all referenced services are configured as system services and are setup to restart on failure therefore it would be unusual to observe any particular service down however, An administrator should attempt to start a service and consult the relevant logs if a service is observed to be down.
Also, selecting X against each service entry shows the systemd logs for the relevant service; this would be useful to diagnose any issues that the operating system has had in starting and running the service.