TF2 replays have been disabled indefinitely Only took a week for similar issues as before to resurface, and there's absolutely no reason why replays should affect the hard disk as 100% of their files are stored in ram (/tmp). So for unknown reasons, we simply cannot support them. Edit: At some point in the future I will evaluate replays via localhost ftp, as we ran that way successfully for a number of months a while ago
Well seems my internet in halls is not good enough to use KVM (ping 2000ms+, massive packet loss without dedi as VPN), so here's to hoping I can get home in time to get things fixed before GD support closes in ~50 mins (otherwise high risk of 12 hour downtime)
Have set up grub2 such that by default it boots into one of the two recovery partitions - have to explicitly tell it to boot into normal OS prior to a manual reboot, so in the case of unexpected reboot/crash/etc, the chances of the server becoming 'stuck' are extremely low. Additionally can now get into recovery without going through KVM Created a simple script for recovery to get back into normal OS again without any fuss Configured SSH server on both recovery partitions, so no need for KVM in order to control recovery non-techie version: the thing that i broke everything trying to set up is now working 100% massively reduced instances where KVM is needed massively reduced chance of downtime of more than a few minutes, it would literally have to be a hardware failure i am a wizard
Have updated to munin 2.0, at the expense of many plugins and my custom theme but oh well http://munin.weeaboo.com/com/weeaboo.com/index.html
Have updated everything for the first time in a few months Unfortunately this has come at the cost of my custom version of murmur, so the [[limit]] system and the forum sidebar widget for mumble will not work until further notice
And if anyone cares, all issues are due to this major breaking change: https://www.archlinux.org/news/qt4-replaces-qt/