User Tools
resolution_area:prometheus_resolutions:res-p1109
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| resolution_area:prometheus_resolutions:res-p1109 [2021/06/25 10:09] – external edit 127.0.0.1 | resolution_area:prometheus_resolutions:res-p1109 [2021/12/17 13:09] (current) – wflaherty | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| **Level:** Warning | **Level:** Warning | ||
| - | |||
| **Purpose: | **Purpose: | ||
| + | To ensure the services that are supposed to be running stay running | ||
| **Scenario: | **Scenario: | ||
| **Resolution: | **Resolution: | ||
| + | The service is running in a stable state | ||
| **Manual Action Steps:** | **Manual Action Steps:** | ||
| + | - ssh onto the affected server. | ||
| + | - Use `ps aux | grep < | ||
| + | - use `systemctl status < | ||
| + | - If the application is trying to restart over and over open / | ||
| + | - Edit the `Restart=` line to be off rather than on-failure or always. | ||
| + | - Use `sudo journalctl -ex` to see the logs of the server after attempting to restart the application. | ||
| + | - A problem for some things in the past that weren' | ||
| + | - ELK stack and MySQL all require an elasticsearch, | ||
| + | - Sometimes just fully shutting down the service with `sudo systemctl stop < | ||
| + | - If the bash prompt is behaving strangely, the server is likely running out of RAM for some reason. | ||
| + | - Another thing worth checking is the disk space. `df -h` | ||
| + | - If this is an Errigal app, you can check the logs at moros.err: | ||
| **Auto Clear:** | **Auto Clear:** | ||
| + | Its entirely possible the service will automatically recover | ||
resolution_area/prometheus_resolutions/res-p1109.1624612196.txt.gz · Last modified: 2021/06/25 10:09 by 127.0.0.1
Page Tools
