Development log: 2022-09-29

2022 September 29

Made a mirror backup to Juno.

Made a backup AMI:
    Scanalyst Backup 2022-09-29 ami-0a8dd1d348e7cb480
        /           snap-0191f87734bed6bc4
        /server     snap-0d9ce824b0d65575d

The system had been up for 48 days.

Installed 13 update packages, 5 for security. including a new kernel.
    yum update

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


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

The Discourse Docker container started automatically after the reboot
and serves HTTP requests normally.

Bacula did not start automatically after the reboot.  After
investigation, I believe this was because /etc/rc.d/rc.local was not
marked executable.  I did:
    chmod 755 /etc/rc.d/rc.local
and we'll see what happens after the next reboot.

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

Back to the Discourse Upgrade manager page:


There was no need to rebuild the Discourse image after this update.
None of the plug-ins needed updates.

The Admin page now reports we're running on 2.9.0.beta10.

Rebooted to see if Bacula will start automatically.

After the reboot, Bacula started automatically and we can talk to the
client from the Director daemon on Pallas.

I genuinely wish I understood all this. Nonetheless, Iā€™m glad you know how and are willing to do it. I am still deep in the woods of merely trying to get my NAS running correctly. The more I learn, the more vulnerabilities I realize there are.