https://blog.margrop.net/en/tag/ops/ Recent content in Ops on Margrop Blog Hugo -- gohugo.io en-US Mon, 13 Apr 2026 09:30:00 +0800 https://blog.margrop.net/en/post/openclaw-backup-failure-investigation-and-fix/ Mon, 13 Apr 2026 09:30:00 +0800 https://blog.margrop.net/en/post/openclaw-backup-failure-investigation-and-fix/ <p>This post is a full incident review, not because the failure was dramatic, but because it was a very typical automation problem.</p> <p>Two machines lost their automatic OpenClaw backups at the same time: a local macOS machine and a remote VPS. Manual runs worked on both sides, and the archives could still be synchronized to the NAS, but the scheduled jobs were unreliable. At first glance it looked like &ldquo;the scheduler did not fire.&rdquo; In reality, the root cause was spread across scheduling, permissions, locking, logging, and even the way I validated the schedule.</p> <p>That combination is what makes these incidents annoying: every individual piece looks almost fine, yet the full pipeline still fails.</p> https://blog.margrop.net/en/post/openclaw-upgrade-to-2026-3-23-compatibility-playbook/ Tue, 24 Mar 2026 21:20:00 +0800 https://blog.margrop.net/en/post/openclaw-upgrade-to-2026-3-23-compatibility-playbook/ <p>This post documents a real OpenClaw upgrade, not a laboratory demo. The goal was not simply to change a version string. The real goal was to move a small multi-node environment from <code>2026.3.8 / 2026.3.13</code> to <code>2026.3.23-2</code> while keeping message channels, external plugins, service startup behavior, and rollback paths under control.</p> <p>In practice, the most difficult part was not the OpenClaw core package. The hardest part was everything around it: plugin SDK compatibility, JIT cache reuse, mixed installation layouts, restricted outbound access on an edge node, and differences in bind mode that changed what health probes actually meant. If you do not identify those variables first, an upgrade can easily look successful while one or more production channels are already broken.</p>