---------- 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
Should be "all better now".
Attempted to fix a minor bug last month,
didn't get it quite right, that then caused this month's
to not go out (on time). Fixed, that,
correctly this time, and now appears all is well
(reran the program slightly later this month after the fix).
Context was already within single quotes ('),
so needed to properly be '\'' to get a net single quote at that level.
Had earlier fixed whitespace after -m option - where shouldn't have
been, but that then caused the loop to error out, until the other issue
was properly corrected.
# rlog lists_monthly 2>&1 | sed -ne '/^revision 1\.6$/q;/^-\{28\}$/,$p'
----------------------------
revision 1.10 locked by: root;
date: 2026/03/02 06:07:30; author: root; state: Exp; lines: +1 -1
properly fix syntax around (intended) log message for context
----------------------------
revision 1.9
date: 2026/02/09 22:35:01; author: root; state: Exp; lines: +1 -2
http --> https; remove set -x
----------------------------
revision 1.8
date: 2026/02/09 22:28:06; author: root; state: Exp; lines: +1 -1
fix syntax on (intended) log message
----------------------------
revision 1.7
date: 2025/07/02 14:44:38; author: root; state: Exp; lines: +8 -0
filter out list has no members stdout output line in case list
membership [for --role] is empty
----------------------------
# rcsdiff -U 0 -r1.7 lists_monthly 2>&1
===================================================================
RCS file: RCS/lists_monthly,v
retrieving revision 1.7
diff -U 0 -r1.7 lists_monthly
--- lists_monthly 2025/07/02 14:44:38 1.7
+++ lists_monthly 2026/03/02 06:07:30
@@ -51 +51 @@
- ci -d -f -l -M -m 'membership update' membership
>>/dev/null 2>&1
+ ci -d -f -l -M -m'\''membership update'\'' membership
>>/dev/null 2>&1
@@ -62 +61,0 @@
- set -x
@@ -68 +67 @@
- echo '\''http://www.balug.org/#Lists'\''
+ echo '\''https://www.balug.org/#Lists'\''
#
On Sun, Mar 1, 2026 at 10:15 PM Michael Paoli via BALUG-Admin
<balug-admin(a)lists.balug.org> wrote:
> Date: Mon, 02 Mar 2026 06:15:38 +0000 (UTC)
> Subject: [BALUG-Admin] BALUG: Lists, stats, etc.
> dates, lists, number of members:
> YYYY-MM-DD announce talk admin
> 2026-03-02 456 238 31
> 2026-02-01 457 237 31
> 2026-01-01 457 236 31
...