[00:24:49] [02miraheze/IncidentReporting] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjjDP [00:24:51] [02miraheze/IncidentReporting] 07paladox 03d002878 - round $outageTotal [00:25:09] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjjDX [00:25:10] [02miraheze/services] 07MirahezeSSLBot 03bc831b3 - BOT: Updating services config for wikis [00:26:12] paladox: why jsut outage total? [00:26:16] why not visible too? [00:26:23] also where is the Changelog entry? [00:26:23] oh [00:26:26] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/fjjD1 [00:26:27] [02miraheze/mediawiki] 07paladox 03e3d422c - Update IncidentReporting [00:26:28] right [00:26:34] err, let me add that [00:26:42] and then the version change [00:26:56] [02miraheze/IncidentReporting] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjjDM [00:26:58] [02miraheze/IncidentReporting] 07paladox 03314ee33 - Round $outageVisible [00:27:45] [02IncidentReporting] 07paladox created branch 03paladox-patch-2 - 13https://git.io/fh5YJ [00:27:46] [02miraheze/IncidentReporting] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fjjDD [00:27:48] [02miraheze/IncidentReporting] 07paladox 03494221f - Bump version to 1.0.3 [00:27:49] [02IncidentReporting] 07paladox opened pull request 03#4: Bump version to 1.0.3 - 13https://git.io/fjjDy [00:28:06] [02miraheze/IncidentReporting] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fjjDS [00:28:07] [02miraheze/IncidentReporting] 07paladox 0333af133 - Update extension.json [00:28:09] [02IncidentReporting] 07paladox synchronize pull request 03#4: Bump version to 1.0.3 - 13https://git.io/fjjDy [00:28:23] [02IncidentReporting] 07paladox closed pull request 03#4: Bump version to 1.0.3 - 13https://git.io/fjjDy [00:28:25] [02miraheze/IncidentReporting] 07paladox pushed 033 commits to 03master [+0/-0/±4] 13https://git.io/fjjD9 [00:28:26] [02miraheze/IncidentReporting] 07paladox 03418cdb1 - Merge pull request #4 from miraheze/paladox-patch-2 Bump version to 1.0.3 [00:28:56] JohnLewis done ^ [00:28:57] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/fjjDH [00:28:59] [02miraheze/mediawiki] 07paladox 03757e577 - Update IncidentReporting [00:29:04] k [00:29:50] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/fjjDQ [00:29:52] [02miraheze/mediawiki] 07paladox 032939fba - Update ArticleFeedbackv5 [00:30:19] [02miraheze/IncidentReporting] 07paladox deleted branch 03paladox-patch-2 [00:30:20] [02IncidentReporting] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/fh5YJ [00:32:16] miraheze/IncidentReporting/paladox-patch-2/33af133 - paladox The build has errored. https://travis-ci.com/miraheze/IncidentReporting/builds/126304734 [00:34:03] !log UPDATE `incidents` SET i_outage_total = '51',i_outage_visible = '53.15' WHERE i_id = '21'; - db4 [00:34:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [00:34:25] paladox: why 53.13? [00:34:39] I was only looking at trying to fix the query :) [00:34:42] but good idea [00:34:44] need to do both [00:39:39] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [00:41:07] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [00:41:19] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[git_pull_MediaWiki core] [00:41:32] that's due to the ddos attack against wikimedia [00:41:38] it carn't access phabricator [01:13:41] PROBLEM - wiki.lostminecraftminers.org - LetsEncrypt on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [01:14:11] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjjyZ [01:14:13] [02miraheze/puppet] 07paladox 03abef6e4 - lizardfs:client: Set atboot to false [01:26:43] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [01:26:51] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [01:28:43] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [01:28:48] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [01:39:50] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjjy2 [01:39:51] [02miraheze/puppet] 07paladox 03c0630c2 - Revert "lizardfs:client: Set atboot to false" This reverts commit abef6e4369a07ae2bac64bcd763405efe2d189a7. [01:53:59] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [01:56:33] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [02:05:37] [ANNOUNCEMENT] Attention: For those unaware, Wikimedia is under a DDoS attack, so it may be unreachable, for updates please watch @wikipedia on twitter or #wikimedia-tech [02:36:23] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [06:22:17] PROBLEM - lizardfs4 Puppet on lizardfs4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [06:26:11] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2989 MB (12% inode=94%); [07:02:17] RECOVERY - lizardfs4 Puppet on lizardfs4 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [07:33:26] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [09:03:26] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:13:10] Reception123: ping [09:29:53] hi [12:15:18] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjj5d [12:15:19] [02miraheze/puppet] 07paladox 033c9ec0e - disable enable_proton by default [12:45:22] PROBLEM - misc3 Puppet on misc3 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 3 minutes ago with 0 failures [12:49:17] PROBLEM - misc3 restbase on misc3 is CRITICAL: connect to address 185.52.1.71 and port 7231: Connection refused [12:51:15] RECOVERY - misc3 restbase on misc3 is OK: TCP OK - 0.005 second response time on 185.52.1.71 port 7231 [12:59:49] Jesus i feel bad for wmf operations rn [13:00:28] PROBLEM - misc3 electron on misc3 is CRITICAL: connect to address 185.52.1.71 and port 3000: Connection refused [13:17:52] Zppix: tools still down [13:18:54] Ik [13:19:06] ZppixBot: ping [13:19:12] .ping [13:19:13] Pong! [13:19:31] You use to be able to mention its name and a cmd :/ [13:19:54] Zppix: let's hope the promised restart doesn't come [13:20:07] It probably will [13:24:26] Zppix: I should be around all day if it does [13:24:46] Ditto [13:28:08] Zppix: any way to clear a notification from a private wiki? [13:28:15] Idk [13:28:27] RhinosF1: update from operations its quiet for now [13:28:47] Zppix: due same time as last night so 3 hours [13:29:22] 18 hour long ddos RhinosF1 thats got to be a record [13:29:48] Zppix: actual DDoS was 9 hours but for time to recover probably [13:29:50] I'm surprised it could happen to Wikipedia... [13:30:08] RECOVERY - misc3 electron on misc3 is OK: TCP OK - 0.001 second response time on 185.52.1.71 port 3000 [13:30:25] Reception123: everything that has a internet connection it can happen to, no one is invulnerable [13:31:56] Reception123: it was at least 2.5x normal traffic [13:32:08] Up to 10x based on estimates [13:32:08] Zppix: yeah, though it had to be a large attack still [13:32:28] It was [13:32:30] Reception123: I'll pm you cause not sure how public the rate was [13:32:41] Pm me too? [13:33:26] ok [13:33:39] Zppix, Reception123: done [13:38:31] saw [13:41:15] Seen [13:59:46] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2640 MB (10% inode=94%); [14:11:02] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:13:37] Hey Voidwalker [14:13:57] hi [14:14:47] Voidwalker: you forgot something you said you'd do the other day [14:15:14] yeah [14:15:14] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2661 MB (11% inode=94%); [14:15:25] Voidwalker: any chance of a close? [14:35:14] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2617 MB (10% inode=94%); [15:33:34] PROBLEM - lizardfs4 Puppet on lizardfs4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:53:34] RECOVERY - lizardfs4 Puppet on lizardfs4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:01:38] paladox: I noticed a bug in Incident Reporting, shouldn't the log drop /edit off the page name? [18:05:35] Yes i would think so. [18:08:59] paladox: then we have a bug? Phab or a chance of a quick fix [18:09:40] i could have sworn i remember discovering it. But forgot if it's intentional. So for now put it in phab. [18:10:38] Will do in a minute [18:12:18] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [18:13:26] paladox: https://phabricator.miraheze.org/T4704 [18:13:27] [ ⚓ T4704 Remove /edit from Incident Reporting logs ] - phabricator.miraheze.org [18:13:34] thanks [18:16:12] I really should make ZppixBot not treat phab links as a link but as if it was a .task [18:16:18] but i cant be arsed [18:16:37] Np, can you look at the issue with Saved filters on RC as well paladox [18:16:48] I wondered what happened to my filter [18:17:34] https://phabricator.miraheze.org/T4703 [18:17:35] [ ⚓ T4703 The website won't remember options I set, such as syntax highlighting or RC saved filters ] - phabricator.miraheze.org [18:22:18] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [19:08:26] !log editing /etc/network/interfaces on misc3 [19:09:21] uh [19:09:24] umounting again [19:10:17] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [19:10:31] PROBLEM - misc3 Current Load on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:33] PROBLEM - misc3 SSH on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:10:35] PROBLEM - misc3 electron on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:10:38] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [19:10:39] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:40] PROBLEM - cp3 Stunnel Http for misc3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:43] PROBLEM - mw1 HTTPS on mw1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:10:45] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [19:10:46] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:10:53] PROBLEM - cp4 Stunnel Http for mw2 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:01] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:01] PROBLEM - cp3 Stunnel Http for mw1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:04] PROBLEM - mw3 HTTPS on mw3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:11:05] PROBLEM - misc3 Lizardfs Master Port 3 on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:11:10] what did you do :P [19:11:12] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:12] PROBLEM - misc3 zotero on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:11:17] PROBLEM - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is WARNING: WARNING - NGINX Error Rate is 44% [19:11:18] PROBLEM - cp2 Stunnel Http for mw1 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:23] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:23] PROBLEM - misc3 lizard.miraheze.org HTTPS on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:11:29] PROBLEM - Host misc3 is DOWN: PING CRITICAL - Packet loss = 100% [19:11:34] PROBLEM - cp2 Stunnel Http for misc3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:39] PROBLEM - cp4 Stunnel Http for misc3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:11:55] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [19:11:56] PROBLEM - cp4 Stunnel Http for mw1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:12:03] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:12:11] back [19:12:22] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [19:12:28] PROBLEM - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is WARNING: WARNING - NGINX Error Rate is 45% [19:12:30] PROBLEM - mw1 MirahezeRenewSsl on mw1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:12:31] PROBLEM - mw1 SSH on mw1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:12:38] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24516 bytes in 0.392 second response time [19:12:38] RECOVERY - cp3 Stunnel Http for misc3 on cp3 is OK: HTTP OK: Status line output matched "401" - 381 bytes in 0.501 second response time [19:12:53] RECOVERY - cp4 Stunnel Http for mw2 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24522 bytes in 0.508 second response time [19:12:56] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24500 bytes in 0.633 second response time [19:12:59] RECOVERY - mw3 HTTPS on mw3 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 442 bytes in 0.006 second response time [19:13:06] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24500 bytes in 0.005 second response time [19:13:17] RECOVERY - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is OK: OK - NGINX Error Rate is 2% [19:13:18] PROBLEM - mw1 php-fpm on mw1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:13:19] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24500 bytes in 0.675 second response time [19:13:29] RECOVERY - Host misc3 is UP: PING OK - Packet loss = 0%, RTA = 0.67 ms [19:13:29] PROBLEM - misc3 Lizardfs Master Port 1 on misc3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:13:32] RECOVERY - cp2 Stunnel Http for misc3 on cp2 is OK: HTTP OK: Status line output matched "401" - 381 bytes in 0.302 second response time [19:13:35] RECOVERY - misc3 Lizardfs Master Port 1 on misc3 is OK: TCP OK - 0.003 second response time on 185.52.1.71 port 9419 [19:13:36] RECOVERY - cp4 Stunnel Http for misc3 on cp4 is OK: HTTP OK: Status line output matched "401" - 381 bytes in 0.007 second response time [19:13:50] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:14:01] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24516 bytes in 0.392 second response time [19:14:16] PROBLEM - mw1 Disk Space on mw1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:14:17] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [19:14:24] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:14:28] RECOVERY - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is OK: OK - NGINX Error Rate is 6% [19:14:45] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [19:16:39] RECOVERY - mw1 MirahezeRenewSsl on mw1 is OK: TCP OK - 7.000 second response time on 185.52.1.75 port 5000 [19:16:42] RECOVERY - mw1 SSH on mw1 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u6 (protocol 2.0) [19:16:51] RECOVERY - mw1 HTTPS on mw1 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 442 bytes in 0.010 second response time [19:17:11] RECOVERY - cp3 Stunnel Http for mw1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24500 bytes in 0.662 second response time [19:17:21] RECOVERY - mw1 php-fpm on mw1 is OK: PROCS OK: 4 processes with command name 'php-fpm7.2' [19:17:54] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 15 minutes ago with 0 failures [19:17:55] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 6 backends are healthy [19:18:01] RECOVERY - cp4 Stunnel Http for mw1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24516 bytes in 0.027 second response time [19:18:22] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [19:18:23] RECOVERY - mw1 Disk Space on mw1 is OK: DISK OK - free space: / 32319 MB (42% inode=98%); [19:18:32] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 2.61, 0.84, 0.29 [19:18:38] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 6 backends are healthy [19:19:40] RECOVERY - cp2 Stunnel Http for mw1 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24516 bytes in 0.394 second response time [19:22:43] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [19:32:58] paladox: i think miraheze is a little woozy [19:33:07] heh, it was my fault [19:33:13] quickly got it up [19:33:22] *back [19:37:44] Zppix: https://mobile.twitter.com/UKDrillas/status/1170417459582705664 [19:37:45] [ Twitter ] - mobile.twitter.com [19:39:39] RhinosF1: meh [19:39:42] RhinosF1: hes lying [19:40:05] paladox: they're laughing at you :P [19:40:17] hahaha [19:40:19] but yeah, I wouldn't trust anything they say [19:40:33] Zppix: exactly what a doxxed person would say [19:47:59] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjjh0 [19:48:01] [02miraheze/puppet] 07paladox 03df784bc - mediawiki: Make php fpm childs configurable [21:08:11] paladox: does miraheze not do ipv6? [21:08:34] We have a ipv6 for some of our servers. [21:09:16] oh [21:09:41] paladox: hows the RN issue ? [21:10:10] Zppix resolved (if you mean from yesturday) [21:10:40] i have a new one opened today, different issue. [21:10:42] paladox: How come i dont get an favicon on meta [21:11:19] i get one Zppix [21:11:41] i dont think its my cache let me see [21:11:57] paladox: i cleared my cache and dont get any [21:12:08] hmm [21:13:01] Zppix https://meta.miraheze.org/favicon.ico [21:13:04] does that work? [21:13:59] wfm [21:14:16] do you want my connection info paladox ? [21:14:30] could be a bad cache on cp [21:14:31] ok, what browser do you use? [21:14:40] paladox: firefox latest on x32 win [21:15:33] !log ban req.http.Host == meta.miraheze.org && req.url ~ "^/favicon.ico" - cp2 [21:15:37] Zppix try now please [21:15:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:16:04] just for reference im on cp2 [21:16:17] paladox: have one now [21:16:22] great :) [21:16:39] mind if I do https://phabricator.miraheze.org/T4702 ? [21:16:40] [ ⚓ T4702 Add some feature and extensions ] - phabricator.miraheze.org [21:16:45] was i right then paladox ? [21:20:29] Voidwalker: is it possible with your script to make it force any action to be marked as bot even w/o flooder right? if so i can look at modifying it for you so you dont have to do the work [21:20:38] massgblock script* [21:21:02] not that I'm aware of [21:21:35] best you could do is make the script force you into a group before executing [21:22:01] Voidwalker: I ask because i almost blocked an entire asn w/o flooder luckily i close the tab before it got to far [21:22:14] Voidwalker: hmm ill look into doing that and ill let you know [21:22:31] sure [21:22:39] should it force users to be in flooder? or does steward grant use of bot flag? [21:23:41] since the script is a CVT tool, I'd say you should go for flooder, or allow the user to specify what group (but default to flooder or something similar) [21:24:20] Voidwalker: I think for now ill just require flooder unless the user is in group steward? [21:25:54] how does that make sense for the steward? [21:26:15] Voidwalker: oh i was under the impression steward was by default able to use bot flag [21:26:16] nm [21:26:40] but I'd say, go for what change you want to make, and I'll see about making my change to it later [21:26:52] ok [21:28:55] Zppix: I guess [21:29:23] oh, paladox, should I do https://phabricator.miraheze.org/T4702 ? [21:29:24] [ ⚓ T4702 Add some feature and extensions ] - phabricator.miraheze.org [21:29:47] I have the page ready in a tab, so it can be done immediately [21:33:47] [02ssl] 07RhinosF1 opened pull request 03#216: Remove cert ( wiki.lostminecraftminers.org ) - 13https://git.io/fjjjd [21:34:02] [02ssl] 07RhinosF1 edited pull request 03#216: Remove cert ( wiki.lostminecraftminers.org ) - 13https://git.io/fjjjd [21:34:44] [02ssl] 07RhinosF1 synchronize pull request 03#216: Remove cert ( wiki.lostminecraftminers.org ) - 13https://git.io/fjjjd [21:35:10] paladox: ^ [21:35:21] whelp, done it anyway, don't yell at me plox :) [21:36:50] Voidwalker: meh, done for his other wiki [21:37:09] (he literally copied the task description) [21:38:46] I'll be back later, hope nothing catches fire :P [21:39:21] Voidwalker: give me a sec adding naf now if paladox will merge [21:39:46] [02mw-config] 07RhinosF1 opened pull request 03#2752: add .naf per T4702 - 13https://git.io/fjjjx [22:08:05] Voidwalker: it works https://publictestwiki.com/wiki/User:Zppix/testgblock.js [22:08:06] [ User:Zppix/testgblock.js - TestWiki ] - publictestwiki.com [22:08:35] well done Zppix - can you poke about wm-bot again? [22:08:53] yea [22:09:41] thx Zppix [22:11:56] RhinosF1: {{done}} [22:12:16] :) [22:17:36] RhinosF1: twitter suspended ukdrillas [22:18:40] Zppix: that might be for the best [22:19:01] hopefully it means he's about to arrested and it was co-ordinated [22:19:40] *shrugs* [22:20:16] Voidwalker yes please :) [22:20:38] paladox: can you merge my patches /mw-config and /ssl [22:20:43] [02ssl] 07paladox closed pull request 03#216: Remove cert ( wiki.lostminecraftminers.org ) - 13https://git.io/fjjjd [22:20:44] yup, done [22:20:45] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-1/±1] 13https://git.io/JeeeV [22:20:46] [02miraheze/ssl] 07RhinosF1 0364aac82 - Remove cert ( wiki.lostminecraftminers.org ) (#216) * Remove cert ( wiki.lostminecraftminers.org ) domain inactive * rmv wiki.lostminecraftminers.org [22:22:49] [02ssl] 07RhinosF1 opened pull request 03#217: rmv wiki.articmetrosystem.tk - 13https://git.io/Jeeer [22:23:02] paladox: and mw-config + another ssl incoming [22:23:31] i'm leaving the mw config change for now (asking anothe oper about it first) [22:23:32] Zppix, that's one way to do it, yeah [22:23:55] paladox: k [22:24:00] [02ssl] 07RhinosF1 synchronize pull request 03#217: rmv wiki.articmetrosystem.tk - 13https://git.io/Jeeer [22:24:22] paladox: looks like it's used by win rar to me [22:24:33] and ^ that's the other ssl patch [22:24:48] [02ssl] 07paladox closed pull request 03#217: rmv wiki.articmetrosystem.tk - 13https://git.io/Jeeer [22:24:49] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-1/±1] 13https://git.io/Jeeei [22:24:51] paladox: puppet just crashed [22:24:51] [02miraheze/ssl] 07RhinosF1 0321e0817 - rmv wiki.articmetrosystem.tk (#217) * rmv wiki.articmetrosystem.tk domain not pointed and inactive on who.is * Update certs.yaml [22:24:54] done [22:25:00] Voidwalker: well its ready to go live if you want to update your script [22:25:12] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:25:17] paladox: puppet is moaning about that change saying lost file [22:25:30] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:25:43] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:25:45] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:25:57] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:26:13] icinga-miraheze: I just removed it! [22:26:23] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:26:29] thanks icinga-miraheze, very helpful [22:26:39] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:27:08] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [22:27:29] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[wiki.lostminecraftminers.org] [22:27:32] should recover now [22:27:33] lol [22:27:39] (/Stage[main]/Ssl::Hiera/Ssl::Hiera::Certs[lostminecraftminers]/File[wiki.lostminecraftminers.org]) Could not evaluate: Could not retrieve information from environment production source(s) puppet:///ssl/certificates/wiki.lostminecraftminers.org.crt [22:27:47] was the error i was seeing [22:28:13] paladox: yes that [22:28:34] anyways brb [22:30:42] Voidwalker: i guess thats one way [22:31:23] yeah, I thought why enclose the whole thing when a return statement is easier :P [22:32:40] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [22:32:47] here we go! [22:33:28] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [22:33:45] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:33:50] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [22:33:54] Zppix, added to the script [22:34:35] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:34:52] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:35:29] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:35:44] all back [22:37:56] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.31, 6.39, 4.27 [22:39:51] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.28, 6.38, 4.52 [22:58:37] Voidwalker: probably because im not the best in javascript so i thought if and else never failed me [22:59:43] I'm going to make it better in the future, but I got a lot on my plate to work on [23:00:40] Voidwalker: i cant possibly see how you can make the script better tbh [23:01:37] I was thinking of adding an additional field to the interface that allows you to promote yourself if you're not currently in the group [23:02:33] also considering adding a way to bypass the flooder check, but adding in another check to make sure you can actually block and stuff [23:02:36] meh thats just quality of life, the change me/you made is more important as you don't want to flood rc with blocks [23:02:50] why would you want to bypass flooder check [23:03:32] honestly, no idea (which puts it very low on my list of priorities) [23:09:59] I’m kind of around [23:10:03] (Mobile now) [23:13:23] paladox: are you sure your not a square [23:18:15] hello [23:18:53] any bouncer irc services you recommend? [23:25:12] Zppix: Lol [23:25:13] Hispano76: I use xshellz