[00:02:57] <icinga-miraheze>	 PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues  
[00:04:12] <icinga-miraheze>	 PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues  
[00:04:32] <icinga-miraheze>	 PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues  
[00:04:36] <icinga-miraheze>	 PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues  
[00:04:42] <icinga-miraheze>	 PROBLEM - cp5 Puppet on cp5 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues  
[00:09:58] <ZppixBot>	 Hello home! If you have any questions feel free to ask and someone should answer soon.
[00:10:58] <icinga-miraheze>	 RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures  
[00:12:12] <icinga-miraheze>	 RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures  
[00:12:30] <icinga-miraheze>	 RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures  
[00:12:36] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures  
[00:12:40] <icinga-miraheze>	 RECOVERY - cp5 Puppet on cp5 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures  
[00:14:18] <sysadmin_wannabe>	 paladox, u there?
[00:14:25] <paladox>	 hi, yup
[11:19:11] <icinga-miraheze>	 PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb  
[11:19:41] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb  
[11:21:16] <icinga-miraheze>	 PROBLEM - cp5 Varnish Backends on cp5 is CRITICAL: 2 backends are down.  mw1 mw2  
[11:21:30] <icinga-miraheze>	 PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down.  mw1 mw2  
[11:21:36] <icinga-miraheze>	 PROBLEM - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is CRITICAL: CRITICAL - NGINX Error Rate is 73%  
[11:21:42] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online  
[11:22:04] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down.  mw1  
[11:23:36] <icinga-miraheze>	 RECOVERY - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is OK: OK - NGINX Error Rate is 24%  
[11:25:24] <icinga-miraheze>	 PROBLEM - cp5 HTTPS on cp5 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 3814 bytes in 1.081 second response time   
[11:25:42] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb, 172.104.111.8/cpweb, 2400:8902::f03c:91ff:fe07:444e/cpweb  
[11:26:04] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy  
[11:26:12] <icinga-miraheze>	 PROBLEM - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is CRITICAL: CRITICAL - NGINX Error Rate is 78%  
[11:26:54] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online  
[11:27:14] <icinga-miraheze>	 RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy  
[11:27:16] <icinga-miraheze>	 RECOVERY - cp5 Varnish Backends on cp5 is OK: All 5 backends are healthy  
[11:27:24] <icinga-miraheze>	 RECOVERY - cp5 HTTPS on cp5 is OK: HTTP OK: HTTP/1.1 200 OK - 23696 bytes in 2.152 second response time   
[11:27:42] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online  
[11:28:12] <icinga-miraheze>	 RECOVERY - cp5 HTTP 4xx/5xx ERROR Rate on cp5 is OK: OK - NGINX Error Rate is 30%  
[16:08:40] <sysadmin_wannabe>	 hey dudes :)
[20:41:03] <dayid>	 A bit ago I'd asked about importing my mediawiki database files from another instance - is there anyone in particular (or any forum/place in particular) where I should try to achieve that?
[20:41:23] <dayid>	 I'm unsure if I got a response - I finally silenced the monitoring/git alerts so the channel was a little clearer to my view
[20:42:40] <Voidwalker>	 preferably, import requests should be made on phabricator.miraheze.org
[20:47:12] <dayid>	 I'm perhaps lost -- that looks more like code management of actual infrastructure code - vs individual instances, no?
[20:48:44] <Voidwalker>	 phabricator is a system for creating and managing tasks, generally used for bug reports or feature requests
[20:50:16] <dayid>	 So you'd like me to file a feature request for an end-user to be able to accomplish that? I was under the impression it would be more of an individual ticket/issue type thing to have that accomplished.
[20:51:40] <Voidwalker>	 no, sorry, that was worded poorly
[20:52:57] <Voidwalker>	 what you would do is open up a request asking for an import to me made, the exact specifics of how it is done would depend on the files you have available for us, and how you can provide them
[20:53:28] <dayid>	 ah, ok -- I just didn't want to put in like a mainline "bug" or "feature request" -- like against the software/code itself - for one-personal thing ;)
[20:54:02] <Voidwalker>	 yeah, my bad :P
[20:54:35] <dayid>	 That would go under feature request as far as the phabricator UI though?
[20:58:17] <Voidwalker>	 it would be better to use this form: https://phabricator.miraheze.org/maniphest/task/edit/form/1/
[20:58:17] <ZppixBot>	 Title: [ Login ] - phabricator.miraheze.org
[20:58:47] <dayid>	 Great, thank you!
[21:24:47] <home>	 +Voidwalker are you here?
[21:24:54] <Voidwalker>	 yup
[21:28:09] <ZppixBot>	 Hello C____! If you have any questions feel free to ask and someone should answer soon.
[21:36:56] <ZppixBot>	 Hello cfkdsfe! If you have any questions feel free to ask and someone should answer soon.
[21:59:14] <Not-abbb>	 [02miraheze/mediawiki] 07paladox pushed 036 commits to 03REL1_31 [+0/-0/±17] 13https://git.io/fp1Hk
[21:59:15] <Not-abbb>	 [02miraheze/mediawiki] 07Seb35 03f74dcc3 - SQL syntax error in MS-SQL file Bug: T209870 Change-Id: I91e4f8472832c4bb17eb1d185db1bcbde57a9287 (cherry picked from commit e1100d2d53baa71d20cc282b6dc0a950b080aaad)
[21:59:17] <Not-abbb>	 [02miraheze/mediawiki] 07MatmaRex 037a6393f - LogFormatter: Fail softer when trying to link an invalid titles Old log entries contain titles that used to be valid, but now are not. Bug: T185049 Change-Id: Ia66d901aedf1b385574b3910b29f020b3fd4bd97 (cherry picked from commit 26bb9d9b23eb2075eefca2097ca393a9d4aa3264)
[21:59:18] <Not-abbb>	 [02miraheze/mediawiki] 07jdforrester 0363f8c9a - RELEASE-NOTES-1.31: Add in other cherry-picks since 1.31.1 was cut Gone through `git log --topo-order --no-merges --reverse 1.31.1..` from 1f664ea4 to 7a6393fc (HEAD as of writing); re-worded a couple, grouped the PHP version work together, and skipped a couple which were just follow-up tweaks or test fixes to ones already in the list. Change-Id:
[21:59:18] <Not-abbb>	 Ic04998209348abf73eefb1cad404700da91457ed
[21:59:20] <Not-abbb>	 [02miraheze/mediawiki] ... and 3 more commits.
[22:03:42] <JohnLewis>	 uh
[22:03:54] <JohnLewis>	 so we're on 1.31.1 but have 1.31.2 code?
[22:04:08] <paladox>	 JohnLewis yes?
[22:04:19] <paladox>	 Has a bug fix i want
[22:04:24] <JohnLewis>	 cherry pick
[22:04:28] <JohnLewis>	 don't do a half upgrade
[22:04:31] <paladox>	 ok
[22:04:34] <JohnLewis>	 we've spoken about this already
[22:04:45] <JohnLewis>	 we either maintain stable releases or we go cutting edge
[22:04:49] <paladox>	 Ok
[22:04:55] <JohnLewis>	 we can't do stable but cutting edge "if it suits us"
[22:05:01] <paladox>	 Ok
[22:09:19] <Not-abbb>	 [02miraheze/mediawiki] 07paladox pushed 036 commits to 03REL1_32 [+0/-0/±13] 13https://git.io/fp1QT
[22:09:20] <Not-abbb>	 [02miraheze/mediawiki] 07MaxSem 03c7505d6 - Use our fork of less.php Supports PHP 7.3, among other things Bug: T206975 Depends-On: I06f1e43b0f12f9b56f9dff55a92b5ae4546acfcc Change-Id: I84c5ed8ac0ae1c382ba035b37dc88ccd69494ac3
[22:09:22] <Not-abbb>	 [02miraheze/mediawiki] 07MaxSem 03ff52803 - Update git submodules * Update vendor from branch 'REL1_32' to 174d4390921e080caa1ff251f1be401e668bcc29 - Use our own fork of less.php Bug: T206975 Change-Id: I06f1e43b0f12f9b56f9dff55a92b5ae4546acfcc
[22:09:23] <Not-abbb>	 [02miraheze/mediawiki] 07jenkins-bot 038b5dd9b - Merge "Use our fork of less.php" into REL1_32
[22:09:25] <Not-abbb>	 [02miraheze/mediawiki] ... and 3 more commits.
[22:16:42] <icinga-miraheze>	 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]  
[22:40:42] <icinga-miraheze>	 RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures  
[23:13:41] <Not-abbb>	 [02miraheze/ManageWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fp1NZ
[23:13:42] <Not-abbb>	 [02miraheze/ManageWiki] 07JohnFLewis 03b75230d - changes to NS display code + allow non-controlling changes to core namespaces
[23:14:59] <travis-ci>	 miraheze/ManageWiki/master/b75230d - John Lewis The build was broken. https://travis-ci.org/miraheze/ManageWiki/builds/464098351
[23:15:25] <Not-abbb>	 [02miraheze/ManageWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fp1N4
[23:15:27] <Not-abbb>	 [02miraheze/ManageWiki] 07JohnFLewis 036fd6eed - changes to NS display code + allow non-controlling changes to core namespaces
[23:16:49] <travis-ci>	 miraheze/ManageWiki/master/6fd6eed - John Lewis The build was fixed. https://travis-ci.org/miraheze/ManageWiki/builds/464098790