cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
38d7d85339
claude-memory/graph/decisions/lxc-300-claude-code-shut-down-unused-container-a9d6f7.md
Cal Corum 34bb613c57 Add 20 retroactive edges and sync pending memory updates 
- 20 new high-quality edges across 8 project clusters
- Edge types: BUILDS_ON, RELATED_TO, ALTERNATIVE_TO, REQUIRES
- Updated relation metadata on connected memories
- New episode entries and memory files from recent sessions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-19 23:34:07 -06:00

1.3 KiB
Raw Blame History

id type title tags importance confidence created updated relations
a9d6f7a1-69d9-41ab-b28c-88f02d21a43b decision LXC 300 was OpenClaw (migrated from LXC 224) - shut down intentionally
proxmox
homelab
openclaw
infrastructure
cleanup
0.6 0.8 2026-02-19T17:13:31.147499+00:00 2026-02-20T04:32:38.480124+00:00
target type direction strength edge_id
76f14cf3-97d0-4962-8d26-bf375948b460 RELATED_TO incoming 0.8 dc2bea7d-5a66-44cf-b8a2-0725446d5bb5

LXC 300 Shut Down (2026-02-19) — Was Running OpenClaw

LXC 300 (hostname 'claude-code') was actually running OpenClaw, migrated from LXC 224 at some unknown point. This migration was never documented.

Evidence

  • LXC 224 (openclaw-lxc) had been shut down for ~10 minutes with no Uptime Kuma alert
  • As soon as LXC 300 was shut down, Uptime Kuma fired an OpenClaw Gateway down alert
  • The Uptime Kuma monitor was still pointed at 10.10.0.224:18789 (old LXC)
  • LXC 300 had hostname 'claude-code' which was misleading

Actions taken

  • LXC 300 shut down intentionally (OpenClaw no longer needed)
  • LXC 224 also shut down (was already empty after migration)
  • Uptime Kuma monitor for OpenClaw should be removed/disabled

Recovery if needed

  • Backup: /mnt/pve/home-truenas/pve7to8-backups/vzdump-lxc-300-2026_02_19-*.tar.zst
  • Start: pct start 300