30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
---
|
|
id: a9d6f7a1-69d9-41ab-b28c-88f02d21a43b
|
|
type: decision
|
|
title: "LXC 300 was OpenClaw (migrated from LXC 224) - shut down intentionally"
|
|
tags: [proxmox, homelab, openclaw, infrastructure, cleanup]
|
|
importance: 0.6
|
|
confidence: 0.8
|
|
created: "2026-02-19T17:13:31.147499+00:00"
|
|
updated: "2026-02-19T17:16:52.507526+00:00"
|
|
---
|
|
|
|
## 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
|