memory(MEM-20260819-C255FF): Desplegar Uptime Kuma como monitoreo central (health.mcps-epcm.org)

content/memorias/2026-08-19-mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org.md

@@ -0,0 +1,55 @@
++++
+title = "Desplegar Uptime Kuma como monitoreo central (health.mcps-epcm.org)"
+description = "Contenedor Uptime Kuma en mcps-hpc-01 con 22 monitores en 3 grupos; gotcha de systemd Type=notify que causaba reinicio en loop."
+date = 2026-08-19T18:55:56Z
+authors = ["gen"]
+slug = "mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org"
+template = "memory.html"
+
+[taxonomies]
+categories = ["memorias"]
+tags = ["monitoreo", "systemd", "uptime-kuma"]
+systems = ["mcps-hpc-01", "uptime-kuma"]
+
+[extra]
+id = "MEM-20260819-C255FF"
+kind = "memory"
+author_id = "gen"
+author_fingerprint = "SHA256:JhN1Tt4jYqWoJIznDJ6QkMAiOR6HFHr3xLz9aBJqmPg"
+risk = "low"
+ticket = ""
+review_required = true
+review_policy = "all-active"
+reviewer_snapshot = true
+reviewers = ["gen"]
+started_at = ""
+finished_at = ""
+duration_minutes = 0
+agent = "claude-code"
++++
+
+## Contexto
+
+Se desplegó Uptime Kuma como monitoreo centralizado de los servicios web de mcps-epcm.org y del clúster HPC, expuesto en https://health.mcps-epcm.org (VPN-only). Quedan pendientes sin resolver, encontrados por el propio monitoreo al arrancar: pgscat.mcps-epcm.org responde 502 (backend no responde) y encuestas.mcps-epcm.org responde 404 en / (posiblemente normal si esa app solo sirve rutas específicas).
+
+## Cambios realizados
+
+- Contenedor docker.io/louislam/uptime-kuma:1 desplegado en mcps-hpc-01, systemd unit container-uptime-kuma.service, IP fija 10.89.0.51 en mcps-net
+- Corregido Type=notify a Type=simple en el systemd unit: Uptime Kuma no manda la señal sd_notify y con Type=notify se quedaba en 'activating' y reiniciaba en loop
+- 22 monitores configurados en 3 grupos (servicios web mcps-epcm.org, infraestructura mcps-hpc-01, nodos del clúster HPC) mediante script Python con la librería no oficial uptime-kuma-api
+- Se quitaron del monitoreo pgscat y mta-sts a pedido explícito; los servicios detrás de Caddy siguen existiendo, solo se sacaron del monitor
+
+## Comandos relevantes (secretos redactados)
+
+```console
+pip install uptime-kuma-api
+```
+
+## Validación
+
+- Dashboard accesible en https://health.mcps-epcm.org con certificado real vía DNS-01
+- Página pública de estado sin login disponible en https://health.mcps-epcm.org/status/mcps
+
+## Riesgo y reversión
+
+Detener y deshabilitar container-uptime-kuma.service; no afecta a los servicios monitoreados, solo deja de haber monitoreo centralizado.

data/generated/site_state.json

@@ -1,15 +1,69 @@
 {
   "version": 2,
-  "generated_at": "2026-08-13T06:42:03Z",
+  "generated_at": "2026-08-19T18:55:56Z",
-  "source_sha256": "64a404e7ccb669ab6712d92141f5e2446eb3256723075a42bd7037380f285050",
+  "source_sha256": "3b9b369d32145a90a7fc4798bdc4ca538999d8619e1434747b2e83bcf761076a",
   "stats": {
     "active_admins": 1,
-    "pending_reviews": 0,
+    "pending_reviews": 1,
     "open_tasks": 1,
     "active_projects": 1
   },
-  "review_queue": [],
+  "review_queue": [
+    {
+      "entry_id": "MEM-20260819-C255FF",
+      "title": "Desplegar Uptime Kuma como monitoreo central (health.mcps-epcm.org)",
+      "description": "Contenedor Uptime Kuma en mcps-hpc-01 con 22 monitores en 3 grupos; gotcha de systemd Type=notify que causaba reinicio en loop.",
+      "date": "2026-08-19T18:55:56Z",
+      "author_id": "gen",
+      "risk": "low",
+      "tags": [
+        "monitoreo",
+        "systemd",
+        "uptime-kuma"
+      ],
+      "systems": [
+        "mcps-hpc-01",
+        "uptime-kuma"
+      ],
+      "permalink": "/memorias/mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org/",
+      "content_sha256": "a74e4f1493843970c55c3197fb2e5266c8b04cf631e7fd187890051a0f076686",
+      "reviewed_by": [],
+      "missing_reviewers": [
+        "gen"
+      ],
+      "required_count": 1,
+      "reviewed_count": 0
+    }
+  ],
   "recent_memories": [
+    {
+      "entry_id": "MEM-20260819-C255FF",
+      "title": "Desplegar Uptime Kuma como monitoreo central (health.mcps-epcm.org)",
+      "description": "Contenedor Uptime Kuma en mcps-hpc-01 con 22 monitores en 3 grupos; gotcha de systemd Type=notify que causaba reinicio en loop.",
+      "date": "2026-08-19T18:55:56Z",
+      "author_id": "gen",
+      "author_fingerprint": "SHA256:JhN1Tt4jYqWoJIznDJ6QkMAiOR6HFHr3xLz9aBJqmPg",
+      "risk": "low",
+      "review_required": true,
+      "review_policy": "all-active",
+      "reviewer_snapshot": true,
+      "reviewers": [
+        "gen"
+      ],
+      "tags": [
+        "monitoreo",
+        "systemd",
+        "uptime-kuma"
+      ],
+      "systems": [
+        "mcps-hpc-01",
+        "uptime-kuma"
+      ],
+      "slug": "mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org",
+      "permalink": "/memorias/mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org/",
+      "source_path": "content/memorias/2026-08-19-mem-20260819-c255ff-desplegar-uptime-kuma-como-monitoreo-central-health-mcps-epcm-org.md",
+      "content_sha256": "a74e4f1493843970c55c3197fb2e5266c8b04cf631e7fd187890051a0f076686"
+    },
     {
       "entry_id": "MEM-DEMO-001",
       "title": "Inicializar la estructura de la bitácora",