koopa-admin-log/2026/2026-09-19--goa-regio-ng-login-health+monitoring.md

2026-09-19 — GOA single-CTR: login-health + monitoring

Why

koopa-login-health FAIL×3 on dead taler-hacktivism* + WARN koopa-tor-relay. Live stack is goa-regio-ng (pasta 9010–9015) + host tor.service (ORPort 8080).

Live SoT (hernani@koopa)

Piece	Detail
GOA CTR	goa-regio-ng — image localhost/goa-regio-ng:empty-current
Scripts	~/scripts/taler-shared/goa-regio-ng/ · goa-all-in-one.sh
Bak	~/backups/goa/current
Landings	host /var/www/*-landing/ + ~/goa-landing-deploy · Caddy outside CTR
Tor	host tor.service — not container koopa-tor-relay
Forgejo	:9024/:9200 · edge Caddy :9000/:9001

Repo changes (magikoopa, no push yet)

koopa-admin-log

• scripts/login-health/: CRITICAL/EXPECT → goa-regio-ng (+ forgejo); drop legacy + tor-relay; host tor.service check; probes 9010–9012
• delete host/overview/{LIVE,services}.* · delete configs/tor/*
• rewrite host/tor/README.md · shorten README / ports / koopa-setup / login-health README
• ISSUES I-07 → host Tor SoT

elelmon + taler-monitoring (EQ scripts mirrored)

• BANK=EX=MER=goa-regio-ng; drop nginx-in-bank; host stats.json fallback
• check_{server,inside,urls,versions,e2e,sanity}.sh · metrics.sh · lib.sh · docs

Verify (after deploy on koopa — Freigabe)

koopa-login-health show -v
# expect: goa-regio-ng OK · no taler-hacktivism* · tor.service OK|WARN

STATE dir name taler-hacktivism-monitoring kept (host-agent path, not CTR).