Post-Mortem
guest@6admin.io:~$ ls ~/tags/post-mortem
Jenkins on Windows Server: what not to do
A Jenkins controller on a domain-joined Windows host, the built-in node on the controller, the 8080 in the open, AD credentials in cleartext: the anatomy of a compromise chain and how to take it apart.
The cloned hostgroup that refused to save
A cloned Foreman hostgroup throws a 500 on every edit. The trail leads to a field that gains a base64 layer with each clone and in passing to a Windows administrator password stored reversibly in the database and copied into the audit logs.
A persistent volume is not durable data
After a hard power loss, PowerDNS's MySQL comes back empty. The host records are gone, nobody noticed and the only reason the story ends well is that the source of truth had survived.
The log driver that stopped the container from starting
A dirty power loss, a corrupted Swarm overlay, an internal DNS that no longer resolves and containers that refuse to start because their log driver cannot resolve a name. The anatomy of a cascade and why the real fault was elsewhere.
A segfault in the JVM and an EDR at the bottom of the stack
A Jenkins controller crash-looping on EXCEPTION_ACCESS_VIOLATION, a JDK migration done with no post-mortem and an EDR DLL showing up at the bottom of every crash dump. How to read a stack honestly and confirm a cause by elimination rather than conviction.
Chaos engineering: breaking things for real, but not just any way
Chaos engineering is not sabotage: it is a controlled experiment, with a measured steady state, a hypothesis, real faults injected and a bounded blast radius. History, principles, tools and an honest fit for modest infrastructure.