Sorry for the downtime.
Root-cause: /var/log/syslog filled our disk up. I've increased the disk space and resolved my syslog problem to it shouldn't repeat.
Side Effects: The disk space issue also caused the CPU to spike which ate my CPU credits (classic AWS)... so I've moved to a new instance type temporarily at the cost of some bison bucks. The joy of being a sysadmin :)
Lessons learned: Monitoring didn't work since I've moved to Singapore and got a new number. I'll fix that tonight.
Well @geordie... SAY HELLO TO MY LIL FRIEND
Happy First month!
https://aus.social is 4 weeks old?!
Thank you so much to our 160 members...
1) Upgraded the server from T2.Small to T2.Medium. (Double the CPU and Double the Memory)
2) Upgraded our instance to 2.5.0 RC1. Just to finally get inline with a point release. :)
Backups were taken incase of failure but everything has tested fine.... Please report any weirdness
Welcome to thundertoot! A Mastodon Instance for 'straya