November 2018 - BALUG-Admin

outage: [www.]{sf-lug,balug}.org
by Michael Paoli 22 Nov '18

22 Nov '18

May be mostly moot by the time this makes it through to the BALUG list server and out. In any case ... ----- Forwarded message from Michael.Paoli(a)cal.berkeley.edu ----- Date: Tue, 20 Nov 2018 18:59:24 -0800 From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu> Subject: outage: [www.]{sf-lug,balug}.org To: SF-LUG <sf-lug(a)linuxmafia.com> And ... outage again :-\ Guestimating if it's the "usual", will likely be on-line again by sometime Wednesday evening (I may or may not get to it before then). Per earlier: impacts all [*.]sf-lug.{org,com} & [*.]balug.org SF-LUG lists remain up and on-line (at least as far as I'm aware). Also, DNS mostly not impacted (in general, slaves remain functional), though there may be some additional latencies on DNS due to failovers to other nameservers. > From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu> > Subject: "all better now:" Re: outage: [www.]{sf-lug,balug}.org > Date: Wed, 10 Jan 2018 20:15:04 -0800 > And ... again, same deal, went off-line at: > <~= 2018-01-11T01:23:21+00:00 2018-01-10T17:23:21-08:00 > and back on-line by: >> ~= 2018-01-11T04:04:06+00:00 2018-01-10T20:04:06-08:00 > ... again, swift kick to the power switch on DSL modem to reset it, > and "all better" - again ... at least for now. > >> From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu> >> Subject: "all better now:" Re: outage: [www.]{sf-lug,balug}.org >> (ETR: eveningish) >> Date: Wed, 06 Dec 2017 18:08:09 -0800 > >> And ... swift kick to the power switch on DSL modem to reset it, >> and "all better now". >> Looks like the outage started around: >> BALUG PING: ping6 2001:470:1f04:19e::2 FAILED 2017-12-06T20:53:56+00:00 >> GW PING: ping 198.144.194.233 FAILED 2017-12-06T20:54:09+00:00 >> and service restored a few minutes ago >> >> >>> From: "Michael Paoli" <Michael.Paoli(a)cal.berkeley.edu> >>> Subject: outage: [www.]{sf-lug,balug}.org (ETR: eveningish) >>> Date: Wed, 06 Dec 2017 14:46:38 -0800 >> >>> So, >>> >>> They were up and on-line this morning, at least as late as about >>> mid-morning or later, but off-line now. >>> POTS line appears to be working, but not IP, >>> likely the DSL modem needs to be reset (powercycled) again ... >>> but don't have means to do that remotely. >>> >>> Presumably I'll have this resolved sometime this evening once I'm >>> on-site again. >>> >>> impacts all [*.]sf-lug.{org,com} & [*.]balug.org >>> SF-LUG lists remain up and on-line (at least as far as I'm aware). ----- End forwarded message -----

2 2

Re: [BALUG-Admin] Login to BALUG Wiki (& registration, bit 'o history, etc.)
by Michael Paoli 17 Nov '18

17 Nov '18

Tossing this one onto (suitable) list, because ... well, why not! :-) > From: "Rick Moen" <rick(a)linuxmafia.com> > Subject: Re: Login to BALUG Wiki > Date: Thu, 15 Nov 2018 17:57:40 -0800 > Quoting Michael Paoli (Michael.Paoli(a)cal.berkeley.edu) > >> Seems more logical would to have that information on the >> "self-"registration wiki page ... otherwise folks may not see it >> anyway. > > After successful login, I put a notice on > https://www.wiki.balug.org/wiki/doku.php , near the top. Thanks ... I also tweaked the language (very) slightly just for slightly better approximation of (mostly historical) reality. > I ack your point that autoregistrations were few and far between, but > lack of any information about how to get a login meant that anyone > wanting to help would have no idea how to proceed. > > Sorry, but what 'self-' registraiton page? Not sure what this reference > is to. Heck, been so long I forget where the self-registration wiki page even is/was. >> I figured manual was "quite good enough" to stop the immediate issue >> (the high volume of bot registrations was causing the wiki to bog down >> and fail in annoying ways). > > I sympathise. > > Restoring login _with_ CAPTCHA plugin would be a 'have your cake and eat > it too' solution, IMO -- if/when you get around to it. Yep *somewhere* on the "todo" list. Background/history - have a look at: curl -s --range 134225-268633 https://www.archive.balug.org/log.txt And *also* very handy for me too ... looks like I'd *disabled* the registration page - so likely it doesn't show at all, or just won't let one self-register.

2 1

BALUG: Lists, stats, etc.
by Michael Paoli 02 Nov '18

02 Nov '18

dates, lists, number of members: YYYY-MM-DD announce talk admin 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 1