the entire timeline from the past ~18 or so hours of the server being "wtf" is unloading but I won't read it, it was never meant to be
let's see how horribly corrupt the database has become after what looks to be disk corruption
I LOVE JOURNALING FILESYSTEMS!
angersock on lobste.rs' experience with experimenting with kindness in comments http://angersock.com/blog/2017/11/24/the-friendlysock-experiment-subjective-results
slow day on the fediverse, people must be out having fun on a Friday night instead of talking to other nerds
@nev @vfrmedia You do NOT want to mess with a moose if it is even mildly ill-disposed toward you. A friend of mine (a professional forester) nearly got trampled one day out in the bush.
One time one of my kids was walking home to Telkwa from Smithers on the highway and a moose gave chase to him; he was terrified. We've all heard of things like this:
I'd always rather meet a bear than a moose in the bush.
looks like I need to watch the Eric Andre show somehow
Okay so some of the stuff I've seen on here, like Minitel or gopher or tilde (https://medium.com/message/tilde-club-i-had-a-couple-drinks-and-woke-up-with-1-000-nerds-a8904f0a2ebf), it feels like steampunk, but for the 1990s instead of the 1890s
What to call it?
so I was just told to run "RAILS_ENV=production bundle exec rake mastodon:feeds:build" to rebuild the home timelime after rm'ing your Redis DB, won't do it because I got my fill reading of what recovered from my FTL
firefox running inside windows 2000 running inside firefox
technology is incredible
Now, to get reintegrated into the fediverse again
OK, here's how to survive #redis keeling over and dying on you, nothing that you will destroy the HTL as a result:
# rm /var/db/redis/dump.rdb
# service redis restart
Just to be sure, restart all Mastodon daemons; though you might be able to get away with workers and streams only
# service nginx restart
# service mastodon_web restart
# service mastodon_workers restart
# service mastodon_streams restart
time to restart the daemons!
OK, refresh, and public timeline evaporates
so having to murderize your corrupt Redis DB doesn't do anything other than destroy the home timeline; and while redis was unconscious, I couldn't get toots from after it died
OK, had to restart redis