Skip to content

All-Might — Runbook

Routine Tasks

Check container status

ssh [email protected] "docker ps"

Restart a service

ssh [email protected] "docker restart <container>"

Logs

Log Contents Location Loki query Format
Shoko Server Anime indexing, AniDB sync, file matching Docker (LXC 116) stdout {job="allmight", container="shoko-server"} Plain text
Grimmory Book/manga library events Docker (LXC 116) stdout {job="allmight", container="grimmory"} Plain text
RomM ROM manager events, library scans Docker (LXC 116) stdout {job="allmight", container="romm"} Plain text
MariaDB Database queries, connections, startup, errors Docker (LXC 116) stdout {job="allmight", container="mariadb"} Plain text
OAuth2 Proxy (grimmory) Auth events Docker (LXC 119) stdout {job="infra-apps", container="oauth2-proxy-grimmory"} Plain text
OAuth2 Proxy (romm) Auth events Docker (LXC 119) stdout {job="infra-apps", container="oauth2-proxy-romm"} Plain text
OAuth2 Proxy (shoko) Auth events Docker (LXC 119) stdout {job="infra-apps", container="oauth2-proxy-shoko"} Plain text

Notes: - Main containers run on LXC 116 (job=allmight), OAuth2 proxies run on LXC 119 (job=infra-apps) - Shoko, Grimmory, and MariaDB produce very little stdout — empty Loki results are normal for these. Use docker logs via SSH to check startup output - SSH fallback: ssh [email protected] "docker logs shoko-server" (or other container names)


Troubleshooting

Shoko not syncing with AniDB

  1. Check Shoko logs: {job="allmight", container="shoko-server"} |= "error"
  2. Verify AniDB is reachable from the LXC
  3. Check if AniDB rate-limited the connection (common after mass imports)