senooken JP Social
  • FAQ
  • Login
senooken JP Socialはsenookenの専用分散SNSです。
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by i.w admininstrative notices (polyhedral@icosahedron.website)

  1. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Friday, 08-Feb-2019 20:59:17 JST i.w admininstrative notices i.w admininstrative notices

    And we're back! AHEAD of schedule!

    Lets see if everything will go smoothly forever this time.

    In conversation Friday, 08-Feb-2019 20:59:17 JST from icosahedron.website permalink
  2. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Friday, 08-Feb-2019 04:32:23 JST i.w admininstrative notices i.w admininstrative notices
    in reply to

    update: scaleways console is weirdly slow slow so new time is when this toot turns 14h

    In conversation Friday, 08-Feb-2019 04:32:23 JST from icosahedron.website permalink
  3. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Friday, 08-Feb-2019 03:24:42 JST i.w admininstrative notices i.w admininstrative notices

    when this toot is 1h old, i.w. will go down for 4 hours (estimated)

    In conversation Friday, 08-Feb-2019 03:24:42 JST from icosahedron.website permalink
  4. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Sunday, 27-Jan-2019 01:29:11 JST i.w admininstrative notices i.w admininstrative notices

    going to have to reboot in a few, should not be more than 10m downtime

    In conversation Sunday, 27-Jan-2019 01:29:11 JST from icosahedron.website permalink
  5. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Saturday, 26-Jan-2019 08:08:11 JST i.w admininstrative notices i.w admininstrative notices

    And we're back!

    i.w is now on a slightly more powerful machine, and volumes have been reorganized to give us plenty of space for the database to grow (and everything is on LVM now to make changes easy, when they become neccesary).

    Sorry that that took a bit longer than expected - please allow for some hiccups while federation catches up.

    Next: Upgrade to 2.7, after the new setup has proven stable.

    In conversation Saturday, 26-Jan-2019 08:08:11 JST from icosahedron.website permalink
  6. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Friday, 25-Jan-2019 21:37:15 JST i.w admininstrative notices i.w admininstrative notices

    timing update update: nvm that, 30min from now

    In conversation Friday, 25-Jan-2019 21:37:15 JST from icosahedron.website permalink
  7. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Friday, 25-Jan-2019 19:24:48 JST i.w admininstrative notices i.w admininstrative notices

    Hey, everybody!

    icosahedron.website will be going down for scheduled maintenance (adding a volume, moving the database) sometime in the near future!

    Please wait warmly.

    In conversation Friday, 25-Jan-2019 19:24:48 JST from icosahedron.website permalink
  8. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:43:21 JST i.w admininstrative notices i.w admininstrative notices

    In other, 2.7 news: I'll upgrade when I have some time, not before friday. If anybody wants me to Not Update for a reason, please tell.

    In conversation Monday, 21-Jan-2019 18:43:21 JST from icosahedron.website permalink
  9. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:42:20 JST i.w admininstrative notices i.w admininstrative notices

    logs will stay on the main HDD, but since the main DB will be someplace else, it'll allow for more time before things break hard.
    * I will make postgres monitoring yell into a place that is not The Void when things go wrong so that next time I will actually notice.
    * I will make a buffer file that I can easily delete to free up some space when needed in case the disk runs full again in the future

    In conversation Monday, 21-Jan-2019 18:42:20 JST from icosahedron.website permalink
  10. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:42:16 JST i.w admininstrative notices i.w admininstrative notices

    database, freed up some space by cleaning out some temporary files and restarted the database. As it now had some space to work with, and the archival command worked again, it started copying over all the old transaction logs and eventually cleaned them out and resumed normal operations.

    3) What will be done to prevent this in the future?
    Various things:
    * I will move the main database files to its own drive. This is going to be neccesary in the near future anyways. The transaction

    In conversation Monday, 21-Jan-2019 18:42:16 JST from icosahedron.website permalink
  11. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:41:40 JST i.w admininstrative notices 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

    In conversation Monday, 21-Jan-2019 18:41:40 JST from icosahedron.website permalink
  12. i.w admininstrative notices (polyhedral@icosahedron.website)'s status on Monday, 21-Jan-2019 18:41:07 JST i.w admininstrative notices 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

    In conversation Monday, 21-Jan-2019 18:41:07 JST from icosahedron.website permalink

User actions

    i.w admininstrative notices

    i.w admininstrative notices

    icosahedron.website administrative notices account. Follow for announcements. External emergency account: @polyhedral@inkweb.network

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          15496
          Member since
          20 Nov 2018
          Notices
          12
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          senooken JP Social is a social network, courtesy of senooken. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All senooken JP Social content and data are available under the Creative Commons Attribution 3.0 license.