asets-gobizit/shutdown

Shutdown (all services)

Gracefully stop every service running on Danny's PC before a shutdown or restart. This is the single shutdown procedure — not just Hermes-specific.

When to Use

• User says "shutdown", "safe shutdown", "stop everything", "shutting down PC"
• User invokes /shutdown
• Before any planned PC restart or shutdown
• Before Windows Update forces a restart

Philosophy (MANDATORY for future installs)

Every new service Danny installs must be added to this skill. When installing anything that runs in the background (daemon, service, scheduled task, bot, database, LLM server, message queue, etc.), update this skill to include:

1. How to stop it gracefully
2. What state it needs to flush (DB WAL, session files, lock files)
3. The correct order relative to existing services
4. What .gitignore rules protect its data

Currently managed services (last verified 2026-04-25):

1. Paperclip (WSL, has embedded Postgres — most critical, stop FIRST)
2. n8n (WSL, systemd user service, port 5678 — stop before Hermes since workflows may depend on it)
3. Zenatta Fetch Server (Windows, port 8723 — feeds n8n newsletter IMAP workflow)
4. Claude Code Remote Control (Windows, supervisor + child)
5. Hermes gateway (WSL, systemd user service)
6. Guy's GMNR Telegram Bot (WSL, Python)
7. Ollama (WSL, port 11434)
8. PKA Caddy (Windows, port 8788 — file server for PKA Viewer)
9. PKA cloudflared (Windows, tunnel for pka.gobizit.ai + gmnr.gobizit.ai)
10. PKA API (Windows, Python Flask on port 8789 — kanban writes endpoint, behind Caddy /api/* proxy)
11. OpenClaw Telegram Bot (Windows, @DansksunBot — only if running)
12. NanoClaw (WSL, Node.js personal assistant — only if running)
13. WSL VM itself (optional, only for -FullShutdown)

Why This Is Needed

Abrupt shutdown causes:

• Postgres stale lock files (postmaster.pid) — next start fails until removed
• Orphaned Paperclip heartbeat runs — agents stuck in "running" state forever
• n8n execution queue corruption — in-flight workflows may leave partial state
• Hermes session ID corruption — garbage session IDs on next run
• Ollama model unload issues — next load may be slow
• Bot message state loss — queued messages may be dropped
• Possible DB corruption (low risk but real)

Shutdown Sequence (in order — DO NOT reorder)

1. Paperclip (FIRST — has embedded Postgres)

Stop-ScheduledTask -TaskName 'PaperclipAI' -ErrorAction SilentlyContinue

Wait 5 seconds for the restart loop to exit.

# Kill lingering Paperclip processes + embedded Postgres
wsl -d Ubuntu -- bash -lc "pkill -TERM -f 'paperclip' 2>/dev/null; sleep 3; pkill -KILL -f 'paperclip' 2>/dev/null; pkill -TERM -f 'postgres.*54329' 2>/dev/null"

Wait another 5 seconds for Postgres to flush WAL and release postmaster.pid.

2. n8n (workflow automation, port 5678)

wsl -d Ubuntu -- bash -lc "systemctl --user stop n8n 2>/dev/null; pkill -TERM -f 'n8n' 2>/dev/null"

Wait 3 seconds for in-flight executions to complete.

3. Telegram Bots

# Guy's GMNR Bot (if running)
wsl -d Ubuntu -- bash -lc "pkill -TERM -f 'guy_gmnr_bot.py' 2>/dev/null"

# OpenClaw @DansksunBot (Windows-side, if running)
powershell -Command "Get-CimInstance Win32_Process | Where-Object { \$_.CommandLine -match 'openclaw' } | ForEach-Object { Stop-Process -Id \$_.ProcessId -Force -ErrorAction SilentlyContinue }"

4. Hermes gateway

wsl -d Ubuntu -- bash -lc "source ~/.local/bin/env 2>/dev/null; hermes gateway stop"

(Uses systemctl --user stop hermes-gateway under the hood — NOT sudo systemctl which would fail.)

5. NanoClaw (if running)

wsl -d Ubuntu -- bash -lc "systemctl --user stop nanoclaw 2>/dev/null"

6. Ollama (if running)

wsl -d Ubuntu -- bash -lc "pkill -TERM -f 'ollama serve' 2>/dev/null"

Note: Ollama may auto-restart if installed as a Windows service. Check with powershell Get-Service Ollama if suspicious.

7. Verify everything is down

curl http://127.0.0.1:3100/api/health 2>&1     # should fail
curl http://127.0.0.1:5678/api/v1/workflows 2>&1  # should fail
powershell -Command "netstat -ano | findstr 54329"  # Postgres port - should be empty
wsl -d Ubuntu -- bash -lc "systemctl --user is-active hermes-gateway"  # should say 'inactive'
wsl -d Ubuntu -- bash -lc "systemctl --user is-active n8n"  # should say 'inactive'
wsl -d Ubuntu -- bash -lc "pgrep -f 'paperclip|guy_gmnr_bot|ollama|n8n'"  # should be empty

8. (Optional) Shut down WSL VM

Only use for full PC shutdown/reboot:

wsl --shutdown

Startup Sequence (after boot — mostly automatic)

1. WSL boots when Windows starts (may need first explicit wsl call)
2. Hermes gateway auto-starts via systemd linger (systemctl --user is-enabled hermes-gateway = enabled)
3. n8n — auto-starts via systemd linger (systemctl --user is-enabled n8n = enabled)
4. Paperclip auto-starts via Windows Task Scheduler PaperclipAI task
5. Ollama — depends on install; may be Windows service or manual
6. Guy's GMNR Bot — currently manual start if needed
7. OpenClaw — manual start (not currently running)

Manual start commands (if auto-start fails)

# Paperclip
Start-ScheduledTask -TaskName 'PaperclipAI'

# Hermes (correct — user service, not sudo)
wsl -d Ubuntu -- bash -lc "hermes gateway start"
# or: systemctl --user start hermes-gateway

# Guy's GMNR Bot
wsl -d Ubuntu -- bash -lc "cd /mnt/c/Users/dansk/Claude/Danny-Hermes-Projects/GMNR-Bot && source telegram_bot_env/bin/activate && python guy_gmnr_bot.py &"

# Ollama
wsl -d Ubuntu -- bash -lc "ollama serve &"

How to Invoke

/shutdown                       # stop all services, WSL keeps running
/shutdown --full                # also shutdown WSL (before reboot)

Or directly:

powershell -File "C:\Users\dansk\.claude\skills\shutdown\shutdown.ps1"
powershell -File "C:\Users\dansk\.claude\skills\shutdown\shutdown.ps1" -FullShutdown

Recovery from Unclean Shutdown

If shutdown was forced (power loss, BSOD, forgot to run this):

1. Stale Postgres lock: wsl -d Ubuntu -- bash -lc "rm /home/dansk/.paperclip-db/postmaster.pid"
2. Orphaned Paperclip runs: open UI → mark stuck runs as failed manually
3. Hermes session issues: run /hermes-restart skill
4. Guy's bot stuck: pkill -f guy_gmnr_bot.py then restart

Rule for Future Skills/Services

When you install ANY new service, tool, daemon, or bot on this PC, you MUST:

1. Add it to the "Shutdown Sequence" above (in correct order)
2. Add it to the "Startup Sequence" above
3. Document its data directories and lock files
4. Note any .gitignore protection needed
5. Commit the updated skill to the claude-skills repo

Related Skills

• /hermes-restart — diagnose and fix Hermes issues after bad startup
• /paperclip-update — update Paperclip safely (includes DB backup)
• Obsidian: [[Paperclip AI Agent]], [[Hermes Agent Local Installation]]