User Tools
resolution_area:watchdog_resolutions:res-w9801
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| resolution_area:watchdog_resolutions:res-w9801 [2021/06/25 10:09] – external edit 127.0.0.1 | resolution_area:watchdog_resolutions:res-w9801 [2022/02/14 16:38] (current) – 10.91.120.28 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| **Level:** __Critical__ | **Level:** __Critical__ | ||
| - | |||
| **Purpose: | **Purpose: | ||
| + | This alert is triggered by a log line in the displaying an error connecting to the MySQL database. | ||
| + | This will only appear for ATC, KLA and SCO. It is a common one if the AWS connection was denied. | ||
| **Scenario: | **Scenario: | ||
| **Resolution: | **Resolution: | ||
| + | Restart the application and then if the log line doesn' | ||
| **Manual Action Steps:** | **Manual Action Steps:** | ||
| + | If this is a new environment, | ||
| - | **Auto Clear:** | + | If this is a standard application then this is a bit more worrying. Please check over the env-configuration; |
| + | Of course, compare this application to other environments' | ||
| + | Perhaps the database was changed on another branch of the env-configuration and it wasn't merged. | ||
| + | |||
| + | **Auto Clear:** | ||
| + | No, this must be fixed manually. | ||
resolution_area/watchdog_resolutions/res-w9801.1624612196.txt.gz · Last modified: 2021/06/25 10:09 by 127.0.0.1