wooo/awoooi
1
1
Fork 0
Code Issues 2 Pull Requests 1 Actions 2 Packages Projects Releases Wiki Activity

docs(ops): record runner guardrail follow-up

Browse Source
This commit is contained in:
Your Name
2026-05-05 15:28:31 +08:00
parent 1cc9de5722
commit 819734f655
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/LOGBOOK.md
View File

@@ -1611,10 +1611,12 @@ psql $DATABASE_URL -f apps/api/migrations/cleanup_duplicate_deprecated_playbooks
| `72d66e4` | stale job cleanup policy thresholds aligned with workflow/job timeout buffers |
| `d08d1e4` | `DockerContainerMissingResourceLimit` alert routing for Compose services missing CPU/memory guardrails |
| `209da7b` | deploy API image `docker-limit-alert-20260505-d08d1e4` |
| `96c1ba2` | CD host-runner helper containers 加固定名稱與 CPU/memory cap，避免 `funny_davinci` 類無名無上限容器 |
| `1cc9de5` | Systemd runner alert/runbook 指向 110 host script `/home/wooo/scripts/apply-runner-systemd-guardrails.sh` |
### 下一步
1. 在 110 以 sudo 執行 `bash scripts/ops/apply-runner-systemd-guardrails.sh --apply`。
1. 在 110 以 sudo 執行 `sudo /home/wooo/scripts/apply-runner-systemd-guardrails.sh --apply`。
2. 驗證 Prometheus 的 `SystemdRunnerWatchdogEnabled` / `SystemdRunnerMissingResourceQuota` 消失。
3. 部署 `/home/wooo/scripts/stop-stale-gitea-actions-jobs.sh`，讓 `DockerGiteaActionsJobStale` 先 dry-run、再人工/AI 審核後 `--apply`。
4. 觀察 110 load5/core 是否穩定低於 1.5，若仍高再調 Sentry ingestion/ClickHouse parts。