User Tools
resolution_area:prometheus_resolutions:res-p1116
Differences
This shows you the differences between two versions of the page.
| resolution_area:prometheus_resolutions:res-p1116 [2021/12/20 14:44] – created wflaherty | resolution_area:prometheus_resolutions:res-p1116 [2021/12/20 16:06] (current) – wflaherty | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | CAS is out of memory | + | =====AppDown: |
| + | |||
| + | **Level: | ||
| + | * CASOutOfMemory - __Critical__ | ||
| + | |||
| + | **Purpose: | ||
| + | |||
| + | **Scenario: | ||
| + | |||
| + | **Resolution: | ||
| + | |||
| + | **Manual Action Steps:** | ||
| + | CAS is on the handlers and sometimes one. | ||
| + | Use [[https:// | ||
| + | to see where CAS is deployed for your investigation. | ||
| + | |||
| + | If there are two CAS's then you may be able to perform a restart of CAS for one handler without affecting the other. | ||
| + | |||
| + | - Open a terminal and cd into your local deployment-playbooks repo. | ||
| + | - Stop the CAS application: | ||
| + | - Do please note the --limit apps1 appended to the end of that command. You may want to change it for apps2 or remove it entirely. | ||
| + | - Once CAS has stopped, have a quick check on the server if its still running just in case. | ||
| + | - <code bash>ssh scotty@serverappsX.err "ps aux | grep cas"</ | ||
| + | - <code bash>ssh scotty@atcappsX.atc "ps aux | grep cas"</ | ||
| + | - <code bash>ssh scotty@extappsX.ext "ps aux | grep cas"</ | ||
| + | - <code bash>ssh scotty@scoapps1.err "ps aux | grep cas"</ | ||
| + | - <code bash>ssh scotty@scolb1.err "ps aux | grep cas"</ | ||
| + | - Start the CAS application: | ||
| + | - After the playbook has complete, ensure that the applicaiton is running. | ||
| + | |||
| + | |||
| + | |||
| + | **Auto Clear:** | ||
| + | Not sure, it might auto clear... | ||
| + | Restart just in case. | ||
resolution_area/prometheus_resolutions/res-p1116.1640011483.txt.gz · Last modified: 2021/12/20 14:44 by wflaherty
Page Tools
