Development Log: 2023-03-17

2023 March 17

Made a mirror backup to Juno.

Made a backup AMI:
    Scanalyst Backup 2023-03-17 ami-09ea87968630d8b41
        /           snap-0bb8ac1b46b8805a5
        /server     snap-036cc92464c885fd0

The system had been up for 50 days.

Installed 47 update packages, 41 for security.
    super
    yum update

Stopped Discourse.
    cd ~/discourse/image
    ./launcher stop app

Rebooted.

The system came up promptly after the reboot.  We are now running on
kernel 4.14.305-227.531.amzn2.x86_64.

On the Discourse Upgrade manager page:
    https://scanalyst.fourmilab.ch/admin/upgrade

I upgraded:
    docker_manager      (This upgrade must be run first:
                        the other upgrade buttons are
                        disabled until it has been updated.)

This took an extraordinarily long time: stuck for 30 minutes
after:
    Purging temp files
    Bundling assets
    W, [2023-03-17T19:56:56.388853 #2167]  WARN -- : Removed sourceMappingURL comment for missing asset 'test-support.map' from /var/www/discourse/app/assets/javascripts/discourse/dist/assets/test-support.js
    W, [2023-03-17T19:57:01.054555 #2167]  WARN -- : Removed sourceMappingURL comment for missing asset 'test-helpers.map' from /var/www/discourse/app/assets/javascripts/discourse/dist/assets/test-helpers.js
in a 100% CPU loop running ruby.

With docker_manager updated, I now proceeded to update:
    discourse-spoiler-alert
    discourse-chatbot
    discourse

The Admin page now reports we're running on 3.1.0.beta3.

Verified that spoilers are working after being updated.  Verified that 
Shalmaneser (discourse-chatbot) is working after being updated.
4 Likes