[BALUG-Admin] "oops" ...: Re: BALUG VM Debian oldstable --> stable

Michael Paoli Michael.Paoli@cal.berkeley.edu
Sat Feb 22 20:37:19 UTC 2020

Hit some snags on the email configuration (and it's integration
with list, anti-spam, etc.) ... don't really have the time to
untangle and fix that at present, so ...
rolled back to snapshot I took before starting the
upgrade attempt.  So, all is again as it was some
several hours earlier.

I'll go at it again when I have more time ... may
be a while.  I'll probably take the mock / dry run one I
did earlier, drop it from network connectivity, and
see if I can fire up all the services - and what needs
fixing (likely the only reason that one made it through
earlier, as various services, including MTA, were kept
down the whole time.  With the services up, some
are restarted, and, well, some of those failed on various
configuration issues.  Not just MTA, but that was looking
the most complex to untangle among the issues ... the rest
didn't seem that bad, but would take bit 'o work too).

> From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
> To: BALUG-Admin <balug-admin@lists.balug.org>
> Subject: BALUG VM Debian oldstable --> stable
> Date: Sat, 22 Feb 2020 07:58:52 -0800

> The BALUG.org Virtual Machine (VM)
> balug / balug-sf-lug-v2.balug.org
> which also hosts most all things, not only BALUG.org,
> but also SF-LUG.org (excepting it's lists) and BerkeleyLUG.com,
> I'm intending to upgrade the operating system soon.
> Expecting some modest outages with some service restarts and reboots,
> etc.  But expecting for the most part it will remain up.
> I did also earlier upgrade "vicki"
> https://lists.balug.org/pipermail/balug-admin/2020-February/001016.html
> just fine,
> and also successfully completed a dry run test upgrade:
> created LVM snapshot of the running balug VM,
> copied snapshot to LVM volume,
> built VM around that volume - and configured to be
> highly similar to balug (differing only in Ethernet
> MAC address and VM related UUID(s) and name
> and networking (different subnet/network/vLAN)),
> disabled network link at VM before "powering up" the VM,
> reconfigured network so as to not conflict with balug,
> disabled services (most especially anything that would attempt
> to send email), enabled network link and networking,
> went through the full upgrade process - all went well,
> no issues of any significance encountered.
> Anyway, now I move on to the "real deal" (the actual balug VM).
> I'll report if any significant issues come up - otherwise
> presume all has gone fine and the upgrade will be completed soon (likely
> today).

More information about the BALUG-Admin mailing list