[00:03:43] <icinga-miraheze>	 PROBLEM - mw4 Current Load on mw4 is CRITICAL: CRITICAL - load average: 4.05, 3.37, 2.25
[00:05:37] <icinga-miraheze>	 RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 0.81, 2.46, 2.06
[00:27:32] <ZppixBot>	 Hello Ahmed03! If you have any questions feel free to ask and someone should answer soon.
[00:53:16] <icinga-miraheze>	 PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[01:04:16] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.56, 6.40, 4.37
[01:06:12] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.20, 5.64, 4.35
[02:30:38] <hispano76_>	 hii
[02:43:15] <icinga-miraheze>	 RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:00:23] <Not-f817>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeJFa
[05:00:24] <Not-f817>	 [02miraheze/mw-config] 07Reception123 037fd4120 - wgFriendingEnabled to false for ATT
[05:06:15] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.95, 5.61, 3.76
[05:06:18] <Not-f817>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeJFi
[05:06:20] <Not-f817>	 [02miraheze/mw-config] 07Reception123 035824d48 - extra friend settings for ATT
[05:07:25] <ZppixBot>	 Hello nurav! If you have any questions feel free to ask and someone should answer soon.
[05:08:12] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.55, 5.32, 3.86
[05:13:11] <icinga-miraheze>	 PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw2
[05:13:26] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw2
[05:13:39] <icinga-miraheze>	 PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw1 mw2
[05:14:25] <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, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[05:14:42] <icinga-miraheze>	 PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 5 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[05:16:25] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[05:16:42] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[05:17:11] <icinga-miraheze>	 RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy
[05:17:26] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 6 backends are healthy
[05:17:39] <icinga-miraheze>	 RECOVERY - cp2 Varnish Backends on cp2 is OK: All 6 backends are healthy
[05:33:10] <icinga-miraheze>	 PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:33:16] <icinga-miraheze>	 PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:33:21] <icinga-miraheze>	 PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:33:27] <icinga-miraheze>	 PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:33:44] <icinga-miraheze>	 PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:33:52] <icinga-miraheze>	 PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:33:53] <icinga-miraheze>	 PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 18 failures. Last run 2 minutes ago with 18 failures. Failed resources (up to 3 shown)
[05:34:03] <icinga-miraheze>	 PROBLEM - lizardfs4 Puppet on lizardfs4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:34:21] <icinga-miraheze>	 PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 385 failures. Last run 2 minutes ago with 385 failures. Failed resources (up to 3 shown)
[05:34:22] <icinga-miraheze>	 PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 3 minutes ago with 9 failures. Failed resources (up to 3 shown)
[05:34:30] <icinga-miraheze>	 PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 3 minutes ago with 13 failures. Failed resources (up to 3 shown)
[05:34:33] <icinga-miraheze>	 PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 3 minutes ago with 9 failures. Failed resources (up to 3 shown)
[05:34:44] <icinga-miraheze>	 PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:34:44] <icinga-miraheze>	 PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:34:55] <icinga-miraheze>	 PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[05:35:23] <icinga-miraheze>	 PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 389 failures. Last run 3 minutes ago with 389 failures. Failed resources (up to 3 shown)
[05:35:44] <icinga-miraheze>	 PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 251 failures. Last run 3 minutes ago with 251 failures. Failed resources (up to 3 shown): File[/root/ufw-fix],File[/usr/local/bin/gen_fingerprints],File[/etc/vim/vimrc.local],File[/etc/default/varnish]
[05:35:45] <icinga-miraheze>	 PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 153 failures. Last run 3 minutes ago with 153 failures. Failed resources (up to 3 shown): File[/etc/rsyslog.conf],File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades]
[05:43:44] <icinga-miraheze>	 RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures
[05:43:52] <icinga-miraheze>	 RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures
[05:43:53] <icinga-miraheze>	 RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures
[05:44:04] <icinga-miraheze>	 RECOVERY - lizardfs4 Puppet on lizardfs4 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures
[05:44:13] <icinga-miraheze>	 RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures
[05:44:22] <icinga-miraheze>	 RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:44:30] <icinga-miraheze>	 RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:44:32] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:44:44] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:44:45] <icinga-miraheze>	 RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures
[05:44:55] <icinga-miraheze>	 RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:45:09] <icinga-miraheze>	 RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures
[05:45:15] <icinga-miraheze>	 RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:45:21] <icinga-miraheze>	 RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:45:25] <icinga-miraheze>	 RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:45:27] <icinga-miraheze>	 RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[05:45:36] <RhinosF1>	 Reception123: see CN - exception with flow
[05:45:37] <ZppixBot>	 RhinosF1: 2019-09-09 - 04:27:04BST <Zppix> tell RhinosF1 you can use .announce since your not a bot admin
[05:45:42] <icinga-miraheze>	 RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures
[05:45:47] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures
[05:45:57] <RhinosF1>	 ZppixBot: I can try
[05:46:07] <RhinosF1>	 At least you work
[05:47:24] <Reception123>	 Flow has never been my thing :(
[05:51:22] <RhinosF1>	 Reception123: log?
[05:52:48] <Reception123>	 Mobile :(
[05:53:00] <RhinosF1>	 Reception123: :(
[06:26:29] <icinga-miraheze>	 RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3097 MB (12% inode=94%);
[10:03:15] <icinga-miraheze>	 PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[10:43:15] <icinga-miraheze>	 RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[11:58:51] <ZppixBot>	 Hello dwalden! If you have any questions feel free to ask and someone should answer soon.
[11:58:56] <Zppix>	 RhinosF1:  I meant can't fyi
[11:59:21] <dwalden>	 We have made a small change to MediaWiki core
[11:59:24] <dwalden>	 https://phabricator.wikimedia.org/T232004
[11:59:24] <ZppixBot>	 [ ⚓ T232004 NamespaceInfo::$canonicalNames is missing NS_MAIN ] - phabricator.wikimedia.org
[11:59:27] <dwalden>	 Which changes $wgCanonicalNamespaceNames
[11:59:29] <dwalden>	 This appears to change the variable set on this line of code
[11:59:32] <dwalden>	 https://github.com/miraheze/ManageWiki/blob/master/maintenance/populateNamespaces.php#L19
[11:59:33] <ZppixBot>	 [ ManageWiki/populateNamespaces.php at master · miraheze/ManageWiki · GitHub ] - github.com
[11:59:35] <dwalden>	 Would someone be able to comment whether this might be a problem for you
[11:59:37] <dwalden>	 and whether I should raise a bug (and how would you like this done)?
[11:59:40] <dwalden>	 The change is on the latest 1.34, so I don't believe will affect you yet, but possibly in the future
[11:59:58] <Zppix>	 Thank you very much for letting us know!
[12:00:37] <Zppix>	 you can create a task on phabricator.miraheze.org
[12:32:43] <Zppix>	 dwalden:  ^^
[12:51:51] <dwalden>	 Thank you. Raised as https://phabricator.miraheze.org/T4710
[12:51:52] <ZppixBot>	 [ ⚓ T4710 Changes made to $wgCanonicalNamespaceNames in MediaWiki 1.34 ] - phabricator.miraheze.org
[12:54:57] <Zppix>	 Your welcome, thanks for letting us know dwalden
[14:58:54] <RhinosF1>	 paladox: you able to check a flow exception?
[14:59:04] <RhinosF1>	 DBQuery
[15:02:01] <paladox>	 hi, yup
[15:02:15] <RhinosF1>	 paladox: https://phabricator.miraheze.org/T4709
[15:02:15] <ZppixBot>	 [ ⚓ T4709 Bug in the Flow extension ] - phabricator.miraheze.org
[15:02:29] <RhinosF1>	 [65e7c79dfe278b96d761808a] Caught exception of type Wikimedia\Rdbms\DBQueryError
[15:04:07] <paladox>	 RhinosF1 https://phabricator.miraheze.org/T4709#89634
[15:04:08] <ZppixBot>	 [ ⚓ T4709 Bug in the Flow extension ] - phabricator.miraheze.org
[15:04:44] <RhinosF1>	 paladox: how far back are the logs?
[15:04:54] <paladox>	 what do you mean?
[15:05:13] <paladox>	 the logs are there for 7 days.
[15:05:41] <RhinosF1>	 paladox: ah, see my comment above about the task reported nearly 2wk ago
[15:06:15] <RhinosF1>	 paladox: any clue how to fix?
[15:06:19] <paladox>	 https://phabricator.miraheze.org/T4655 will not be in the logs if it's more then 7 days.
[15:06:20] <ZppixBot>	 [ ⚓ T4655 Flow doesn't work after importing xml dump ] - phabricator.miraheze.org
[15:07:02] <RhinosF1>	 paladox: correct, now how do we fix that - the most sense I can get out is 'Error: 1406 Data too long for column 'ref_src_wiki' at row 1 (mediawiki-internal-db-master.miraheze.org)'
[15:07:14] <paladox>	 the table will need fixing
[15:07:19] <paladox>	 so it's a upstream issue
[15:07:30] <paladox>	 the limit needs to be increased for ref_src_wiki
[15:07:42] <RhinosF1>	 paladox: okay, will do soon
[15:12:21] <RhinosF1>	 paladox: https://phabricator.wikimedia.org/T232351
[15:12:21] <ZppixBot>	 [ ⚓ T232351 Increase data limit for 'ref_src_wiki' column ] - phabricator.wikimedia.org
[15:12:39] <paladox>	 thanks
[15:12:43] <RhinosF1>	 np
[16:25:09] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeq2K
[16:25:11] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot 03090c5f2 - BOT: Updating services config for wikis
[17:04:56] <Not-f817>	 [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeqaC
[17:04:57] <Not-f817>	 [02miraheze/mw-config] 07Reception123 03a1fc1e2 - rm double setting
[17:23:23] <Not-f817>	 [02miraheze/IncidentReporting] 07translatewiki pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JeqaQ
[17:23:25] <Not-f817>	 [02miraheze/IncidentReporting] 07translatewiki 03f630ea3 - Localisation updates from https://translatewiki.net.
[17:23:26] <Not-f817>	 [02miraheze/CreateWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/Jeqa7
[17:23:28] <Not-f817>	 [02miraheze/CreateWiki] 07translatewiki 0387a4f34 - Localisation updates from https://translatewiki.net.
[17:23:29] <Not-f817>	 [02miraheze/WikiDiscover] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeqa5
[17:23:31] <Not-f817>	 [02miraheze/WikiDiscover] 07translatewiki 0359997cc - Localisation updates from https://translatewiki.net.
[17:23:32] <Not-f817>	 [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/Jeqad
[17:23:34] <Not-f817>	 [02miraheze/MirahezeMagic] 07translatewiki 039bb4f17 - Localisation updates from https://translatewiki.net.
[17:23:35] <Not-f817>	 [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/JeqaF
[17:23:37] <Not-f817>	 [02miraheze/ManageWiki] 07translatewiki 03f30dfaf - Localisation updates from https://translatewiki.net.
[17:25:10] <hispano76_>	 hi
[17:25:30] <Reception123>	 hi hispano76_ 
[17:28:04] <Zppix>	 Reception123:  on metawiki what is the usergroup for flooder called in the backend? 
[17:28:27] <Zppix>	 what does mediawiki consider it to be called
[17:28:39] <Zppix>	 oh nvm
[17:28:52] <Zppix>	 Voidwalker:  on massGBBlock.js can you change flooder to flood
[17:29:02] <Reception123>	 :)
[17:29:10] <Zppix>	 for some reason the userright is named flood in the api
[17:29:15] <Voidwalker>	 oh, sure
[17:29:24] <Zppix>	 thanks
[17:29:57] <Voidwalker>	 Zppix, done
[17:30:01] <Zppix>	 saw ty
[17:41:17] <Zppix>	 @The_Pioneer just an fyi on the wiki request you were unclear about I ended up declining it https://meta.miraheze.org/wiki/Special:RequestWikiQueue/9179#mw-section-comments
[17:41:19] <ZppixBot>	 [ Wiki requests queue - Miraheze Meta ] - meta.miraheze.org
[17:42:08] <MH-Discord>	 <Zppix> @The Pioneer ^
[17:42:40] <RhinosF1>	 Ah good someone saw that
[17:43:22] <Zppix>	 Yeah its unclear purpose and from what I did see I wasn't too sure that it would attract the most "friendliest" of crowds so to speak
[17:43:57] <RhinosF1>	 Yeah agreed
[17:44:56] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 10.41, 6.87, 4.79
[17:48:55] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.26, 7.50, 5.54
[17:54:48] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.52, 7.61, 6.16
[17:56:44] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 5.93, 7.07, 6.13
[17:58:42] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.02, 6.26, 5.94
[18:35:57] <RhinosF1>	 SPF|Cloud: pinging NDK said would do vote now so just you on my access request
[18:51:35] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 10.69, 7.72, 6.11
[18:53:33] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.39, 7.30, 6.16
[18:57:25] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.19, 6.56, 6.16
[19:03:18] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.63, 6.87, 6.42
[19:05:15] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 3.66, 5.65, 6.02
[19:08:54] <RhinosF1>	 Reception123: NDK +1
[19:09:08] <RhinosF1>	 SPF|Cloud: do you want to put a formal +1 on?
[19:09:19] <Reception123>	 RhinosF1: ack, need SPFs clear approval before on-boarding
[19:09:35] * RhinosF1 prods SPF|Cloud with a stick
[19:10:05] <Reception123>	 RhinosF1: that's not a great thing to do to the guy approving your request xD
[19:10:39] <RhinosF1>	 Reception123: true
[19:10:47] * RhinosF1 taps him nicely
[19:17:01] <Zppix>	 testing if ZppixBot can be seen from discord
[19:17:07] <Zppix>	 .ping
[19:17:07] <ZppixBot>	 Pong!
[19:17:30] <Zppix>	 ugh the bot didnt connect to discord
[19:21:02] <RhinosF1>	 .ping
[19:21:02] <ZppixBot>	 Pong!
[19:21:36] <RhinosF1>	 Nope Zppix
[19:21:55] <Zppix>	 RhinosF1:  Im aware the relay is having some issues connecting to discord
[19:22:06] <Zppix>	 Bot relay will be done until i can get it fixed (atleast on discord)
[19:22:23] <RhinosF1>	 s/done/down
[19:22:29] <icinga-miraheze>	 PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2649 MB (10% inode=94%);
[19:24:16] <paladox>	 !log creating glusterfs[12] instances in the cloud
[19:24:22] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[19:24:37] <Zppix>	 Stupid bots
[19:24:51] <Zppix>	 NO discord the login for the bot isnt INCORRECT your INCORRECT
[19:26:18] <Zppix>	 Ugh now I remember why I dont bother working on this bot unless I need to
[19:27:11] <RhinosF1>	 Heh Zppix, it's okay - took me ages to first get my bouncer going then work out the password for Qui
[19:27:37] <Zppix>	 RhinosF1:  the problem is Discord's API is shit
[19:28:00] <RhinosF1>	 Zppix: oh
[19:28:13] <Zppix>	 RhinosF1:  if discord isn't happy then basically thats the equivilent of telling you fuck off
[19:29:53] <RhinosF1>	 Zppix: ah, I set up 2FA last night for discord then it went and kicked me out my tab open on mobile
[19:30:13] <Zppix>	 paladox:  on github how do I make it so I update it so my fork matches the master?
[19:30:43] <RhinosF1>	 .source
[19:30:43] <ZppixBot>	 RhinosF1: My code can be found here: https://github.com/Pix1234/ZppixBot-Source
[19:31:33] <paladox>	 Zppix you can click the pull request button
[19:31:38] <RhinosF1>	 paladox: do you just want to make your copy match master?
[19:31:40] <paladox>	 or just check it out locally
[19:31:53] <RhinosF1>	 Use compare between the two and push it
[19:31:54] <paladox>	 and git pull <repo> <branch>
[19:31:56] <Zppix>	 paladox:  but when i do that it wants to create a pr of my changes to the master
[19:32:14] <Zppix>	 I want the master's changes in my fork
[19:32:20] <paladox>	 yup, or do git pull <repo> <branch>
[19:32:24] <paladox>	 which is the easiest
[19:32:30] <paladox>	 and i do that with mediawiki :)
[19:32:51] <Zppix>	 is there a way i can just do that but only affect a certain dir in the repo?
[19:33:23] <Zppix>	 paladox:  i want to update my lib folder with this https://github.com/reactiflux/discord-irc/tree/master/lib
[19:33:24] <ZppixBot>	 [ discord-irc/lib at master · reactiflux/discord-irc · GitHub ] - github.com
[19:33:33] <Zppix>	 but only my lib folder
[19:33:36] <paladox>	 git pull https://github.com/reactiflux/discord-irc/tree/master/lib
[19:33:37] <ZppixBot>	 [ discord-irc/lib at master · reactiflux/discord-irc · GitHub ] - github.com
[19:33:37] <paladox>	 oh
[19:33:49] <paladox>	 i have no idea how to pull certain folders
[19:34:06] <Zppix>	 I guess I could download each file in the lib and just push it
[19:34:13] <Zppix>	 but i would lose commit history
[19:34:43] <Zppix>	 which isnt to much a concern for me tbh
[19:43:25] <Zppix>	 its still screwing up with discord login :/
[19:43:41] <icinga-miraheze>	 PROBLEM - glusterfs1 Puppet on glusterfs1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file
[19:44:31] <RhinosF1>	 Zppix: is it an API key or PW to login? Tried cancelling the key if it's and re getting one
[19:44:53] <Zppix>	 API key and i just tried to recreate one and it still does it
[19:45:21] <RhinosF1>	 Zppix: all the right perms?
[19:45:40] <icinga-miraheze>	 RECOVERY - glusterfs1 Puppet on glusterfs1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures
[19:45:59] <Not-f817>	 [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeqoU
[19:46:01] <Not-f817>	 [02miraheze/dns] 07paladox 0339e802e - Add glusterfs[12] to dns
[19:46:02] <Zppix>	 RhinosF1:  its not a perm issue it wont even login
[19:47:20] <hispano76_>	 hii
[19:47:56] <RhinosF1>	 Zppix: strange
[19:48:38] <RhinosF1>	 Zppix: have you tried using a typing the API URL into a web browser and see if that gives a clearer error
[19:48:47] <Zppix>	 RhinosF1:  theres no API url
[19:48:58] <RhinosF1>	 Zppix: oh, is for some
[19:51:32] <Zppix>	 this is going to make me go batshit...
[19:53:58] <icinga-miraheze>	 PROBLEM - glusterfs2 Puppet on glusterfs2 is UNKNOWN: NRPE: Unable to read output
[19:54:18] <RhinosF1>	 Zppix: IT can do on bad days
[19:54:23] <Zppix>	 paladox:  fix this 
[19:54:27] <Zppix>	 please
[19:54:31] <paladox>	 fix what?
[19:54:35] <Zppix>	 IRC rleay
[19:54:36] <Zppix>	 relay
[19:54:53] <paladox>	 you'll need to look in the error log, i guess
[19:54:58] <paladox>	 but i doin't do discord :)
[19:55:14] <Zppix>	 https://www.irccloud.com/pastebin/Y7MP4vPU/
[19:55:14] <ZppixBot>	 [ Snippet | IRCCloud ] - www.irccloud.com
[19:55:22] <Zppix>	 the login details are correct
[19:55:26] <Zppix>	 so idk
[19:55:27] <paladox>	 2019-09-09T19:51:08.684547+00:00 app[bot.1]: (node:21) UnhandledPromiseRejectionWarning: Error: Incorrect login details were provided.
[19:55:34] <paladox>	 how sure?
[19:55:57] <RhinosF1>	 Zppix: checked every character - format change?
[19:55:57] <Zppix>	 30000%
[19:56:15] <Zppix>	 I legit copied and pasted the token
[19:57:04] <RhinosF1>	 Zppix: hmm
[19:57:23] <paladox>	 put some debug lines where it logins? :)
[19:57:38] <RhinosF1>	 Zppix: what API version u on?
[19:57:40] <Zppix>	 all this crap just to unignore ZppixBot 
[19:58:00] <Zppix>	 RhinosF1:  *shrugs* whatever the discord-irc requires
[19:58:10] <Zppix>	 https://github.com/reactiflux/discord-irc
[19:58:11] <ZppixBot>	 [ GitHub - reactiflux/discord-irc: Connects Discord and IRC channels by sending messages back and forth. ] - github.com
[19:58:15] <Zppix>	 this is my code https://github.com/Pix1234/discord-irc
[19:58:16] <ZppixBot>	 [ GitHub - Pix1234/discord-irc: Connects Discord and IRC channels by sending messages back and forth. ] - github.com
[20:02:04] <RhinosF1>	 Zppix: it should be V6 for the API
[20:02:26] <Zppix>	 what ver am i using
[20:03:11] <RhinosF1>	 Not sure
[20:03:20] <Zppix>	 I gave you the link to my code
[20:03:20] <RhinosF1>	 Try updating node.js
[20:03:51] <icinga-miraheze>	 RECOVERY - glusterfs2 Puppet on glusterfs2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[20:03:52] <Zppix>	 im running v12
[20:04:04] <RhinosF1>	 Fine then
[20:04:08] <RhinosF1>	 Hmm
[20:04:42] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 11.68, 6.89, 4.65
[20:08:37] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 5.78, 7.66, 5.56
[20:09:23] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.56, 6.32, 5.15
[20:10:16] <Zppix>	 ffs
[20:10:34] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 4.14, 6.33, 5.32
[20:10:59] <Zppix>	 Im going to humour myself and add ZppixBot back to ignore
[20:15:51] <Zppix>	 paladox:  can you revert my commits on https://github.com/Pix1234/discord-irc from today?
[20:15:52] <ZppixBot>	 [ GitHub - Pix1234/discord-irc: Connects Discord and IRC channels by sending messages back and forth. ] - github.com
[20:15:57] <Zppix>	 I dont know how
[20:17:19] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 5.42, 6.84, 5.96
[20:17:28] <paladox>	 git revert
[20:17:29] <paladox>	 Or git checkout the commit and git push force
[20:17:38] <paladox>	 git push origin master —force
[20:19:19] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 3.51, 5.86, 5.71
[20:24:20] <Zppix>	 paladox:  how would i revert to a specific commit
[20:35:38] <paladox>	 Zppix git checkout
[20:35:44] <Zppix>	 I tried that
[20:35:50] <paladox>	 git checkout <commit-id>
[20:35:54] <paladox>	 you need to use git log
[20:39:35] <Zppix>	 I think i got it
[20:41:28] <Zppix>	 omfg
[20:41:35] <RhinosF1>	 Zppix: what?
[20:41:54] <Zppix>	 I reverted to before I changed anything and just put in the new token and nothing
[20:41:59] <Zppix>	 it still is broken
[20:42:16] <RhinosF1>	 then the token is wrong
[20:42:37] <Zppix>	 compare the token in the repo to this 
[20:42:41] <Zppix>	 https://usercontent.irccloud-cdn.com/file/88AlLAJB/image.png
[20:44:46] <RhinosF1>	 Zppix: hmm
[20:44:58] * RhinosF1 can't see an error
[20:45:14] <Zppix>	 thats because its copy and psated
[20:47:08] <RhinosF1>	 Zppix: i'll give you that then - you're right. Have you checked ....?
[20:47:14] * RhinosF1 needs to think
[20:49:53] <RhinosF1>	 Zppix: have you checked the secret?
[20:51:50] <Zppix>	 it doesnt take a secret
[20:52:37] <RhinosF1>	 Zppix: One guide mentioned one on the 'general information' page
[20:52:44] <Zppix>	 where/
[20:52:47] <Zppix>	 on what repo
[20:52:59] <RhinosF1>	 Zppix: https://discordpy.readthedocs.io/en/latest/discord.html
[20:53:00] <ZppixBot>	 [ Creating a Bot Account — discord.py 1.3.0a documentation ] - discordpy.readthedocs.io
[20:53:07] <Zppix>	 thats for python
[20:53:17] <Zppix>	 this is nodejs
[20:53:23] <RhinosF1>	 Zppix: then should that key be public?
[20:53:44] <Zppix>	 If i cant even get into what makes you think anyone else can
[20:54:01] <RhinosF1>	 true :)
[20:57:21] <Zppix>	 Relay may be down until further notice
[20:57:22] <Zppix>	 which sucks
[20:58:19] <Zppix>	 im just not in the mood to fix it right now
[21:02:42] <icinga-miraheze>	 PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[21:12:37] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.22, 6.16, 5.57
[21:12:40] <icinga-miraheze>	 RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures
[21:20:23] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.32, 7.18, 6.41
[21:22:19] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.74, 6.18, 6.13
[21:35:09] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeqKj
[21:35:10] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot 0350448f0 - BOT: Updating services config for wikis
[21:53:07] <ZppixBot>	 Hello Tks4Fish! If you have any questions feel free to ask and someone should answer soon.
[21:55:08] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeq6s
[21:55:10] <Not-f817>	 [02miraheze/services] 07MirahezeSSLBot 033a165dc - BOT: Updating services config for wikis
[22:03:32] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.99, 5.62, 4.62
[22:05:27] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 3.74, 4.94, 4.49
[23:57:31] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.10, 5.91, 4.43
[23:59:26] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.80, 5.46, 4.44