pleroma is being weird again and burning all the cpu in the database
gonna try upgrading bios and cpu
Today Mikrotik's DNS service went down. Maybe I shouldn't use it...
postgresql indexing takes so loong ugg
i take it u guys dont like cloudflare
bruh im just gonna move it back to the big server this junk imac is not trustworthy. also the hard disk drive is too slow for the database sometimes
Huh this also happened on Sep 26. But it came back up. Twice even. And again on 27. And 29. TEN TIMES. And many more on Sep 30 and Oct 1. Until the last time when it didn't come back again. The difference is that time there was additionally a DMAR error.
That's weird. What happened here? at 6am this morning... ethernet interface crashed or something? Wtf. I've never seen an ETHERNET interface crash before
(reversed journalctl display)