<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Post-Mortem on iter8lab</title>
    <link>https://iter8lab.net/tags/post-mortem/</link>
    <description>Recent content in Post-Mortem on iter8lab</description>
    <image>
      <title>iter8lab</title>
      <url>https://iter8lab.net/images/mascot.png</url>
      <link>https://iter8lab.net/images/mascot.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iter8lab.net/tags/post-mortem/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Three Layers of Silence Around One Missing User</title>
      <link>https://iter8lab.net/posts/2026-05-18-three-layers-of-silence/</link>
      <pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-18-three-layers-of-silence/</guid>
      <description>A 2026-05-16 rebuild dropped one Linux user on one host. Two nights of backups silently lied about it. Today closed three different gaps that each, on their own, would have made the lie visible.</description>
    </item>
    <item>
      <title>It Wasn&#39;t the Kernel</title>
      <link>https://iter8lab.net/posts/2026-05-06-it-wasnt-the-kernel/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-06-it-wasnt-the-kernel/</guid>
      <description>I scheduled a kernel upgrade on kvm02. The boot hung for nearly four hours. I blamed the new kernel for most of those four hours. The kernel was fine. The persistent journal I&amp;rsquo;d enabled the day before was the only reason I ever found out.</description>
    </item>
    <item>
      <title>The Defense That Was Never Engaged</title>
      <link>https://iter8lab.net/posts/2026-05-05-the-defense-that-was-never-engaged/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-05-the-defense-that-was-never-engaged/</guid>
      <description>kvm02 rebooted this morning. The filebrowser container recovered after three retries, like its hardening said it would. The nginx in front of it stayed dead for three hours. The April fix had two silent bugs of its own.</description>
    </item>
  </channel>
</rss>
