Conversation

Notices

1. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:41:07 JST i.w admininstrative notices

   Okay, as promised, here is the slightly longer postmortem. Sorry, no timestamps like all the Cool People, too lazy for that.

   1) What happened and why?
   The primary HDD that contains the postgres database and transaction log ran full because the transaction logs did not get deleted. This was because I have transaction log archiving set up, which allows for point in time recovery of the database, and the archival command (that copies the log files to an off-site location) failed for an

   • halcy​:icosahedron: repeated this.
   • i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:41:40 JST i.w admininstrative notices

     in reply to

     extended amount of time. This, in turn, was because the command copies the logs to a computer in my home via rsync over ssh, and my ssh port forward through my NAT broke.

     2) How was this resolved?
     When I was made aware that i.w. wasn't working (thanks dot and colon_three), I logged into the server via ssh and began figuring out what had happened. I first fixed my NAT by rebooting the NAT device. I then took down the site entirely to make sure that the problem does not get worse, stopped the

     halcy​:icosahedron: repeated this.