The BALUG Wiki is "temporarily" (mostly) down for a bit.
I'm integrating WordPress (not for BALUG, but for BerkeleyLUG)
on same host & server ... that required web server to use newer
php version to work with WordPress ... which has "temporarily"
(mostly) broken the BALUG Wiki.
Index pages themselves still appear to work, e.g.:
https://www.wiki.balug.org/wiki/doku.php?do=index&idx=balug
but contents pages, e.g.:
https://www.wiki.balug.org/wiki/doku.php?id=balug:cds_and_images_etc
presently fail.
I'm hoping/presuming it's just some config bit(s) I need to track down
and correct/adjust, then all should be fine again.
Unless someone convinces me otherwise (unlikely),
I'll probably proceed fairly soon, to reconfigure the
BALUG VM (Virtual Machine) - (host balug-sf-lug-v2.balug.org)
and likewise "vicki" (hostname vicki - and the sometimes /
semi-regular physical host of the BALUG VM)
to default to using UTC.
To minimize surprises/disruptions - in addition to this notice,
I'll probably make that change upon a (re)boot of those hosts
(e.g. on reboot, go to single user mode, reconfigure,
then reboot per normal to multi-user).
Rationale:
o security, etc. - many won't even consider looking at logs if they're
not in UTC
o no matter who uses it from where on the planet, one zone all can (well
approximately) reasonably agree upon
o no need/reason to change it in the (unlikely) even it moves to another
physical location, or timezone at existing physical location changes
o "principle of least surprise" - if it was a whole bunch 'o local folks
doing admin, etc. on the box, and especially more "jr." folks, local
would be of least surprise. But alas, yours truly does >>~=99.7 %
of the systems administration, etc. on those hosts, so that being
the case, and having been the case quite a while, and seeming improbable
to change ... for me, that "principle of least surprise", and other
reasons/advantages ... UTC
o Users can always use TZ setting to whatever they wish that's available,
we're only talking about the system default timezone, e.g.:
$ TZ=America/Los_Angeles; export TZ
Magic 8-ball (i.e., logcheck on ns1.linuxmafia.com) says:
System Events
=-=-=-=-=-=-=
May 30 10:05:36 linuxmafia named[11750]: zone balug.org/IN: serial number (1558725628) received from master 198.144.194.238#53 < ours (1558799284)
May 30 10:30:43 linuxmafia named[11750]: zone sf-lug.org/IN: serial number (1558622463) received from master 198.144.194.238#53 < ours (1558799278)
May 30 10:32:42 linuxmafia named[11750]: zone balug.org/IN: serial number (1558725628) received from master 198.144.194.238#53 < ours (1558799284)
May 30 10:57:43 linuxmafia named[11750]: zone balug.org/IN: serial number (1558725628) received from master 198.144.194.238#53 < ours (1558799284)
Er?
Michael, O Great Oracle of the DNS master, before I go expunging the
local cached zone on ns1.linuxmafia.com so as to converge in the master,
any thoughts or desire to act on your end? Normally, I would expect the
current situation to be _strenuously avoided_ by never taking S/Ns in a
retrograde direction on a zone's DNS master, so I infer that
investigation may be in order (or at least brief discussion).
Upon my recent "renewal" (replaced with new) TLS(/"SSL") certs for
[*.]balug.org, for the cert covering the web stuff, I also added:
*.staging.balug.org (*.balug.org itself also covers the bare
staging.balug.org).
Haven't added any [*.]staging.balug.org stuff to DNS, etc - at least yet,
other than that temporarily added for obtaining the cert itself.
And no rush to do so (time, priorities, ...).
Rationale(?):
I think [*.]staging.balug.org may be more logical/appropriate for
most of what [*.]new.balug.org gets used for these days (well, years now).
Might want to, at some point, phase out [*.]new.balug.org.
Once-upon-a-time www.new.balug.org was intended to and used as
the "go forward" of what www.balug.org itself would generally
become - and they were on separate hosts. Well, for many years now,
www.new.balug.org is on same host as [www.]balug.org,
and www.new.balug.org is typically and mostly (if not entirely)
used as essentially staging/preview of what www.balug.org will become,
typically updating content on www.new.balug.org (and checking/revising it)
before making those same content changes to www.balug.org