---------- Forwarded message ---------
From: Michael Paoli <michael.paoli(a)berkeley.edu>
Date: Thu, May 14, 2026 at 2:07 PM
Subject: work-around in place: Re: outage: balug.org, berkeleylug.com,
sf-lug.org, ...
Work-around* in place.
So, things should be meta-stable for now.
Reduced redundancy at present.
Hopefully back to nominal redundancy
soonish (more hardware work to do).
*yanked storage, installed it on another
computer** for now, reconfigured
(because different Ethernet MAC addresses)
booted & running that for now
**https://www.wiki.balug.org/wiki/doku.php?id=system:vicki_documentation
and that documentation is out-of-date,
vicki hasn't been nominal primary host for a long time.
It has only 2GiB of RAM, older CPUs, is rather loud
1U form factor, and sucks a lot of power
relative to what it does. In any case,
for now the VM is atop that.
On Thu, May 14, 2026 at 9:02 AM Michael Paoli
<michael.paoli(a)berkeley.edu> wrote:
>
> outage: balug.org, berkeleylug.com, sf-lug.org, ...
>
> Hardware issue.
> Don't have estimate for when will be back online,
> with bit of luck, etc. hoping for later today PDT.
> Data almost certainly fine, but getting it back online ...
> shall see.
>
> At present that impacts most content on domains
> balug.org, berkeleylug.com, sf-lug.org, etc.
> (but not the BerkeleyLUG nor SF-LUG lists).
> and almost everything with at least IPs that
> match these:
> 96.86.170.224/29
> 2001:470:66:76f::/64
> 2001:470:67:76f::/64
> 2001:470:1f04:19e::/64
> 2001:470:1f05:19e::/64
> 2603:3024:1b29:2::/64