[00:06:43] RECOVERY - bacula1 Bacula Private Git on bacula1 is OK: OK: Full, 1637 files, 1.913MB, 2018-11-11 00:05:00 (1.7 minutes ago) [00:36:25] [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpt2F [00:36:27] [02miraheze/mw-config] 07paladox 035fbc13a - fix path to geodata sql file [00:45:30] Wiki-1776 hi [00:46:22] !log php importImages.php /home/paladox/test/images --overwrite --search-recursively --wiki=nonciclopediawiki --user='Maintenance script' on mw1 [00:46:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [02:33:22] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 76234 MB (20% inode=96%); [02:43:22] RECOVERY - db4 Disk Space on db4 is OK: DISK OK - free space: / 77826 MB (21% inode=96%); [02:47:30] PROBLEM - www.alwiki.net - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection. [02:49:30] RECOVERY - www.alwiki.net - LetsEncrypt on sslhost is OK: OK - Certificate 'www.alwiki.net' will expire on Tue 04 Dec 2018 02:52:04 PM GMT +0000. [03:02:53] PROBLEM - www.alwiki.net - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Cannot make SSL connection. [05:43:23] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 76905 MB (20% inode=96%); [06:53:13] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 1 datacenter is down: 172.104.111.8/cpweb [06:55:13] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [12:52:36] PROBLEM - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is WARNING: WARNING - NGINX Error Rate is 49% [12:58:37] RECOVERY - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is OK: OK - NGINX Error Rate is 35% [14:10:43] PROBLEM - cp4 HTTPS on cp4 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 3801 bytes in 0.010 second response time [14:11:29] PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [14:11:31] PROBLEM - cp5 HTTPS on cp5 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 3814 bytes in 1.077 second response time [14:11:35] PROBLEM - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is CRITICAL: CRITICAL - NGINX Error Rate is 89% [14:11:49] PROBLEM - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is WARNING: WARNING - NGINX Error Rate is 41% [14:12:37] PROBLEM - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is WARNING: WARNING - NGINX Error Rate is 48% [14:13:33] RECOVERY - cp5 HTTPS on cp5 is OK: HTTP OK: HTTP/1.1 200 OK - 23556 bytes in 2.107 second response time [14:13:45] RECOVERY - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is OK: OK - NGINX Error Rate is 35% [14:15:35] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [14:16:35] RECOVERY - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is OK: OK - NGINX Error Rate is 18% [14:16:42] RECOVERY - cp4 HTTPS on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 23565 bytes in 0.010 second response time [14:17:27] RECOVERY - cp5 Varnish Backends on cp5 is OK: All 5 backends are healthy [14:17:36] RECOVERY - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is OK: OK - NGINX Error Rate is 6% [14:19:22] RECOVERY - db4 Disk Space on db4 is OK: DISK OK - free space: / 77821 MB (21% inode=96%); [14:49:06] PROBLEM - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is WARNING: WARNING - NGINX Error Rate is 42% [14:51:04] RECOVERY - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is OK: OK - NGINX Error Rate is 4% [17:45:22] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 76910 MB (20% inode=96%); [17:50:45] [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/fptjK [17:50:47] [02miraheze/ssl] 07paladox 03c57d829 - Add www.apcwiki.org ssl cert [17:50:48] [02ssl] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vxP9L [17:50:49] [02ssl] 07paladox opened pull request 03#75: Add www.apcwiki.org ssl cert - 13https://git.io/fptji [17:51:25] [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-1 [+1/-0/±0] 13https://git.io/fptjX [17:51:26] [02miraheze/ssl] 07paladox 03f8c0581 - Create www.apcwiki.org.crt [17:51:28] [02ssl] 07paladox synchronize pull request 03#75: Add www.apcwiki.org ssl cert - 13https://git.io/fptji [17:52:51] [02ssl] 07paladox closed pull request 03#75: Add www.apcwiki.org ssl cert - 13https://git.io/fptji [17:52:52] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fptjD [17:52:54] [02miraheze/ssl] 07paladox 030cc6624 - Add www.apcwiki.org ssl cert (#75) * Add www.apcwiki.org ssl cert * Create www.apcwiki.org.crt [17:56:55] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [17:56:57] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [17:57:05] HTTP CRITICAL - Unable to open TCP socket [17:58:55] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [17:58:57] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [17:59:08] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpqeL [17:59:09] [02miraheze/ssl] 07paladox 033790533 - Update www.apcwiki.org.crt [17:59:59] RECOVERY - mw1 HTTPS on mw1 is OK: HTTP OK: HTTP/1.1 200 OK - 22759 bytes in 0.007 second response time [18:01:03] RECOVERY - cp4 HTTPS on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 23533 bytes in 0.026 second response time [18:03:21] [02ssl] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vxP9L [18:03:22] [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fpqeC [18:03:24] [02miraheze/ssl] 07paladox 03dfb7759 - Add hi.gyaanipedia.co.in ssl cert [18:03:25] [02ssl] 07paladox opened pull request 03#76: Add hi.gyaanipedia.co.in ssl cert - 13https://git.io/fpqeW [18:05:00] [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-2 [+1/-0/±0] 13https://git.io/fpqez [18:05:01] [02miraheze/ssl] 07paladox 03a955769 - Create hi.gyaanipedia.co.in.crt [18:05:03] [02ssl] 07paladox synchronize pull request 03#76: Add hi.gyaanipedia.co.in ssl cert - 13https://git.io/fpqeW [18:05:11] [02ssl] 07paladox closed pull request 03#76: Add hi.gyaanipedia.co.in ssl cert - 13https://git.io/fpqeW [18:05:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpqeg [18:05:14] [02miraheze/services] 07MirahezeSSLBot 039824edf - BOT: Updating services config for wikis [18:05:16] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fpqea [18:05:17] [02miraheze/ssl] 07paladox 03e40cd2c - Add hi.gyaanipedia.co.in ssl cert (#76) * Add hi.gyaanipedia.co.in ssl cert * Create hi.gyaanipedia.co.in.crt [18:05:19] [02ssl] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vxP9L [18:05:20] [02miraheze/ssl] 07paladox deleted branch 03paladox-patch-2 [18:10:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fpqeA [18:10:14] [02miraheze/services] 07MirahezeSSLBot 034df64e2 - BOT: Updating services config for wikis [21:53:33] So I'm really not a fan of unsolicited spam to join someone's website.. which is what's happening here. https://en.gyaanipedia.co.in/wiki/Special:RecentChanges?hidebots=1&limit=50&days=7&enhanced=1&urlversion=2 [21:53:34] Title: [ Recent changes - Gyaanipedia ] - en.gyaanipedia.co.in [21:54:13] They're just creating talk pages.. which sends out emails to the user who owns them. [21:56:46] Yeah... I do agree [21:59:00] JohnLewis would that fall under a breach of ToS? [21:59:11] no? [21:59:20] ok [21:59:31] JohnLewis so we doin't have a policy that states do not spam users/ [21:59:32] *? [21:59:45] You guys really should have one.. [21:59:51] we don't really... [22:00:06] (that was to paladox not AlexZ_ :) ) [22:00:17] JohnLewis we should make one then. [22:00:25] you know the process [22:00:43] JohnLewis i do not? [22:00:49] this would be my first time.... [22:01:19] the same process as every other policy that exists beside ToS, PP and Content policy [22:01:32] I was not here for any of those [22:01:48] you were definitely around for the last few policies we've made [22:02:02] JohnLewis which policies are we talking about? [22:02:10] because changes to PP was done by labster [22:02:40] ToS says "Conducting any activity on Miraheze which is illegal in California or the Netherlands" Spam certainly isn't legal in my state of CA. :P [22:02:51] JohnLewis ^^ [22:03:09] now that you will have to take up with labster [22:03:41] but I feel like permanently revoking a users right to use Miraheze for this is... too... officious [22:04:09] maybe a warning, and if continue a block? [22:04:36] kinda defeats the point of Miraheze [22:05:12] JohnLewis not really? We are not here to allow them to use our services to spam :) [22:05:14] to be a nanny over every action someone can do with the only policy in place to quote is "Terms of Service" which when quoted, really implies an all-or-nothing thing [22:05:43] Voidwalker: ^^ input please [22:05:46] They created 22 talk pages in total, so that's going to be 22 emails folks didn't ask for. [22:06:03] AlexZ_: actually fun fact, most of those users won't get emails [22:06:48] why's that? [22:06:48] most of those users are locked accounts accounts created for impersonation and ironically enough have miraheze.org emails as the target because someone thought that'll be fun to do [22:07:15] * AlexZ_ cringes [22:07:20] yep [22:07:29] we did too when we got all the creation emails [22:07:52] we're wondering why Legoktm has signed up using our staff email :P [22:08:10] lol [22:08:11] and why the IP is a proxy in Asia :D [22:09:10] lol [22:12:07] it'd be an annoying thing to police [22:12:38] In any case, I'm almost certain they knew what they were doing when creating the talk pages. Not sure how you folks have CentralAuth setup, but accounts really shouldn't be created, thus no email, until a user actually visits a site. [22:13:00] yeah, that's what bother's me [22:13:01] AlexZ_: oddly enough that is how we do it [22:13:08] so [22:13:20] weird.. then [22:13:28] I won't to know how those accounts got created? because being locked they shouldn't have unless someone ran createLocalAccount.php [22:13:32] *want to know [22:16:32] AlexZ_: your account was made when edits were imported (likely containing edit(s) you made) [22:16:57] so, presumably MW and CA spotted this, saw you had a global account and went "ah, let's associate this" [22:19:52] hmmm [22:19:54] 2018-11-11 18:37:34 mw1 gyaanipediawiki: Attaching local user Az1568@gyaanipediawiki by 'login' [22:20:29] lol edits I made in Aug of 2008, well glad to see I'm still being credited. :p [22:20:42] lol [22:22:20] yep, first reference of Az1568 outside of CA was at ~21:50 today [22:22:31] so almost certainly CA it looks to me? [22:26:05] ya seems like it [22:50:23] <_LuCiFeR_> 0101:01)