Hey Steemians. I had to do some land surveying work in the woods today and THE WORLD LITERALLY ENDED.
LITERALLY!
Well, maybe not literally. My witness server experienced a hiccup during a routine weekly update that caused logrotate on my server to quit functioning. This, along with AN EVER LOVING SHIT LOAD OF ASCII CATS (eyes @abit), then caused my main hard disk to fill with trash logs that would normally be properly managed and only really available if debugging is necessary.
Of course, no disk space = programs eat shit. They don't work right, if even at all.
All of the problems have been corrected and the server is replaying the blockchain. Witness operations will resume AS SOON AS POSSIBLE.
Lessons Learned
Going forward, I will be setting up multiple monitoring systems for basic computing resources that need to be managed to have steemd constantly run without issue. On top of this, I have already began creating an ansible playbook that will be available for anyone to use that will allow a COMPLETE witness server setup from creating server to witnessing blocks with minimal alteration to a single config file. I am mainly making the playbook to use in my own automation.
Vote for @netuoso as Witness
(This is a big one because I lost a few votes since I was unable to return to my server and perform the necessary disable + block replay as fast as I would have liked; and your support makes me smile, of course)
- Go to https://steemit.com/~witnesses
- Scroll to the bottom
- Type netuoso into the box and click Vote
