Server Post Mortem 7-Jun-2016

Null

Ooperator
kiwifarms.net
Joined
Nov 14, 2012
Prologue:
The Kiwi Farms uses two servers to manage load. These are called the Pawns. Our second pawn runs FreeBSD.

Timeline:
1. (Months ago) I install Nginx on our new pawn running FreeBSD. I configure it correctly, but save a change that never gets applied because it doesn't work on FreeBSD Nginx.
2. I go to sleep this morning.
3. Our host reboots the machine that our second Pawn is on.
4. When the machine loads, it attempts to load the erroneous configuration file. It can't apply it and it doesn't have a preloaded configuration to ignore it for like it did months ago.
5. Pawn 2 goes into a permanent failure state and Pawn 1 remains up. 50% of incoming connections are dropped at a coinflip.

Solution:
1. Temporarily route all traffic through Pawn 1.
2. Fix Pawn 2.
3. Have you fucking lazy kikes call my fucking phone number like I've been telling you to do if the server has a problem so you don't need to endure 6 goddamn hours of intermittent errors.


PHONE
+1 (757) 932-5494

I usually don't answer but I do receive voice mail and text messages.
 
Last edited:
Oh wow, I didn't know your phone number was public.
 
You could direct us at the hotpocket cucks responsible for calling you so we can mock them.
 
We've let you down grand master Null.

I must now commit sudoku.

I bring terrible news - @A Hot Potato was not kidding. We broke into his office and we were too late:


dqkY0o1.png


He is survived by his proxy accounts and a collection of Warhammer Fantasy miniatures.
 
I think Sammy will announce your phone number on his blog.
:julay::epik:
 
Prologue:
The Kiwi Farms uses two servers to manage load. These are called the Pawns. Our second pawn runs FreeBSD.

Timeline:
1. (Months ago) I install Nginx on our new pawn running FreeBSD. I configure it correctly, but save a change that never gets applied because it doesn't work on FreeBSD Nginx.
2. I go to sleep this morning.
3. Our host reboots the machine that our second Pawn is on.
4. When the machine loads, it attempts to load the erroneous configuration file. It can't apply it and it doesn't have a preloaded configuration to ignore it for like it did months ago.
5. Pawn 2 goes into a permanent failure state and Pawn 1 remains up. 50% of incoming connections are dropped at a coinflip.

Solution:
1. Temporarily route all traffic through Pawn 1.
2. Fix Pawn 2.
3. Have you fucking lazy kikes call my fucking phone number like I've been telling you to do if the server has a problem so you don't need to endure 6 goddamn hours of intermittent errors.


PHONE
+1 (757) 932-5494

I usually don't answer but I do receive voice mail and text messages.
I'll call you anytime there is a problem. My name is JULLLAAAAAAAYYYYYY.
 
Back