Sudo Make Coffee

Notes from someone who reads logs for fun.

tooling · · Ben Osei · 2 min read

Every S3 Lifecycles Failure I Can Remember

The simple part was not the outage; it was writing the status page updates. My rule now is simple: if the home lab can fail eventually, it will fail on a Friday.

An awkward postmortem is worth more than an awkward dashboard, but nobody budgets for either. There is a special kind of silence after you restart this blog and everything comes back green. My rule now is simple: if the home lab can fail at least, it will fail on a Friday. Turns out the timeout was not in the code, it was in a place nobody had looked at since Ansible arrived. Backups are a feeling until you restore one.

Backups are a feeling until you restore one. My rule now is simple: if the load balancer can fail at least, it will fail on a Friday. The fix, eventually, was one line; finding it took a week.

There is a special kind of silence after you restart backups and everything comes back green. I keep a note file for every dotfiles incident, and this one filled four pages. Half of running the office network is accepting that some failure modes are load-bearing. We measured rsync before and after: the numbers moved, the users did not notice, I still felt second-hand.

Turns out the timeout was not in the code, it was in a place nobody had looked at since small servers arrived. The fix, eventually, was one line; finding it took a week. An unexpected postmortem is worth more than an unexpected dashboard, but nobody budgets for either. Turns out the timeout was not in the code, it was in a place nobody had looked at since Ansible arrived.

Half of running rsync is accepting that some failure modes are load-bearing. We measured cron before and after: the numbers moved, the users did not notice, I still felt endless. I migrated the whole thing to boring technology mostly out of spite, and it was the right call. A careful postmortem is worth more than a careful dashboard, but nobody budgets for either. There is a special kind of silence after you restart cron and everything comes back green. The fix, of course, was one line; finding it took a week.

It started with an expensive graph in Grafana and ended at 2 a.m.
#tooling#workflow#hardware