[00:04:31] RECOVERY - jobrunner2 Puppet on jobrunner2 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [00:04:55] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [00:04:58] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 24.23, 19.99, 16.39 [00:05:19] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [00:06:52] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:06:55] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 17.22, 19.45, 16.66 [00:08:22] RECOVERY - bacula2 Bacula Private Git on bacula2 is OK: OK: Full, 5331 files, 16.83MB, 2021-01-24 00:06:00 (2.4 minutes ago) [00:16:29] PROBLEM - mon1 Current Load on mon1 is WARNING: WARNING - load average: 3.77, 3.06, 2.44 [00:18:29] RECOVERY - mon1 Current Load on mon1 is OK: OK - load average: 2.95, 2.86, 2.43 [00:40:07] [02miraheze/mediawiki] 07Universal-Omega pushed 031 commit to 03REL1_35 [+0/-0/±1] 13https://git.io/JtsxI [00:40:09] [02miraheze/mediawiki] 07Universal-Omega 03a9c951e - Update Cosmos [02:03:28] [02miraheze/mediawiki] 07Universal-Omega pushed 031 commit to 03REL1_35 [+0/-0/±1] 13https://git.io/JtGJ0 [02:03:29] [02miraheze/mediawiki] 07Universal-Omega 03ce88051 - Update Cosmos [09:44:27] [02ManageWiki] 07R4356th synchronize pull request 03#231: WIP: Add documentation for messages - 13https://git.io/JtsXr [09:45:30] miraheze/ManageWiki - R4356th the build passed. [09:45:44] [02ManageWiki] 07R4356th edited pull request 03#231: WIP: Add documentation for messages - 13https://git.io/JtsXr [10:00:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtGQO [10:00:14] [02miraheze/services] 07MirahezeSSLBot 0331fb453 - BOT: Updating services config for wikis [13:47:12] PROBLEM - zw.fontainebleau-avon.fr - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for zw.fontainebleau-avon.fr could not be found [13:47:13] PROBLEM - speleo.wiki - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for speleo.wiki could not be found [13:47:14] PROBLEM - wikiescola.com.br - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wikiescola.com.br could not be found [13:47:15] PROBLEM - vedopedia.witches-empire.com - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for vedopedia.witches-empire.com could not be found [13:47:17] PROBLEM - gp.ct777.cf - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for gp.ct777.cf could not be found [13:47:17] PROBLEM - miraheze.ga - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for miraheze.ga could not be found [13:47:19] PROBLEM - civclassic.civwiki.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for civclassic.civwiki.org could not be found [13:47:19] PROBLEM - housing.wiki - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for housing.wiki could not be found [13:54:04] RECOVERY - zw.fontainebleau-avon.fr - reverse DNS on sslhost is OK: rDNS OK - zw.fontainebleau-avon.fr reverse DNS resolves to cp6.miraheze.org [13:54:05] RECOVERY - speleo.wiki - reverse DNS on sslhost is OK: rDNS OK - speleo.wiki reverse DNS resolves to cp6.miraheze.org [13:54:06] RECOVERY - wikiescola.com.br - reverse DNS on sslhost is OK: rDNS OK - wikiescola.com.br reverse DNS resolves to cp7.miraheze.org [13:54:11] RECOVERY - vedopedia.witches-empire.com - reverse DNS on sslhost is OK: rDNS OK - vedopedia.witches-empire.com reverse DNS resolves to cp6.miraheze.org [13:54:12] RECOVERY - gp.ct777.cf - reverse DNS on sslhost is OK: rDNS OK - gp.ct777.cf reverse DNS resolves to cp7.miraheze.org [13:54:13] RECOVERY - miraheze.ga - reverse DNS on sslhost is OK: rDNS OK - miraheze.ga reverse DNS resolves to cp7.miraheze.org [13:54:16] RECOVERY - civclassic.civwiki.org - reverse DNS on sslhost is OK: rDNS OK - civclassic.civwiki.org reverse DNS resolves to cp7.miraheze.org [13:54:16] RECOVERY - housing.wiki - reverse DNS on sslhost is OK: rDNS OK - housing.wiki reverse DNS resolves to cp7.miraheze.org [15:26:14] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 128.199.139.216/cpweb [15:28:09] PROBLEM - de.gyaanipedia.com - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for de.gyaanipedia.com could not be found [15:28:14] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [15:35:05] RECOVERY - de.gyaanipedia.com - reverse DNS on sslhost is OK: rDNS OK - de.gyaanipedia.com reverse DNS resolves to cp7.miraheze.org [15:43:05] PROBLEM - puppet2 APT on puppet2 is CRITICAL: APT CRITICAL: 4 packages available for upgrade (2 critical updates). [15:57:24] [02ManageWiki] 07Universal-Omega reviewed pull request 03#231 commit - 13https://git.io/JtZJQ [16:05:19] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 6 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 51.77.107.210/cpweb, 51.89.160.142/cpweb, 2001:41d0:800:105a::10/cpweb, 2607:5300:205:200::2ac4/cpweb [16:07:13] PROBLEM - kkutu.wiki - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for kkutu.wiki could not be found [16:07:15] PROBLEM - froggy.info - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for froggy.info could not be found [16:07:17] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [16:07:17] PROBLEM - linkwiki.cf - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for linkwiki.cf could not be found [16:07:27] PROBLEM - vmcodex.net - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for vmcodex.net could not be found [16:13:58] RECOVERY - kkutu.wiki - reverse DNS on sslhost is OK: rDNS OK - kkutu.wiki reverse DNS resolves to cp6.miraheze.org [16:14:01] RECOVERY - froggy.info - reverse DNS on sslhost is OK: rDNS OK - froggy.info reverse DNS resolves to cp7.miraheze.org [16:14:04] RECOVERY - linkwiki.cf - reverse DNS on sslhost is OK: rDNS OK - linkwiki.cf reverse DNS resolves to cp7.miraheze.org [16:14:06] RECOVERY - vmcodex.net - reverse DNS on sslhost is OK: rDNS OK - vmcodex.net reverse DNS resolves to cp7.miraheze.org [16:17:18] [02miraheze/ssl] 07Reception123 pushed 032 commits to 03master [+2/-0/±2] 13https://git.io/JtZU2 [16:17:20] [02miraheze/ssl] 07Reception123 03d1d8af5 - add pt.graalmilitary.com cert [16:17:21] [02miraheze/ssl] 07Reception123 03d34b1c9 - add egoish.org cerrt [16:25:06] [02ManageWiki] 07R4356th reviewed pull request 03#231 commit - 13https://git.io/JtZUx [16:29:17] [02ManageWiki] 07R4356th reviewed pull request 03#231 commit - 13https://git.io/JtZTI [16:35:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtZTn [16:35:13] [02miraheze/services] 07MirahezeSSLBot 03de5257a - BOT: Updating services config for wikis [16:40:24] hi @Hispano76 , are you here? where is the community noticeboard for Miraheze? [16:41:08] [[CN]] [16:41:08]

https://meta.miraheze.org/wiki/CN [16:41:10] [ Community noticeboard - Miraheze Meta ] - meta.miraheze.org [16:41:45] Ok, thanks [16:43:15] i want to talk about the request being proposed here: https://phabricator.miraheze.org/T6768 how do i talk about this topic on the noticeboard? [16:43:16] [ ⚓ T6768 Request to add some features of wikipedia ES spanish into tuscriaturas miraheze wiki ] - phabricator.miraheze.org [16:43:57] Click Add Topic? Though you are likely to get a faster answer here. [16:44:46] So, is better to talk about it on the discord channel? [16:45:00] Yeah. [16:46:03] Hispano76 suggested the noticeboard, so that's what i was gonna do [16:47:16] but ok. The wikipedia ES template has some features that are only usable by wikipedia. Is there any way to find a replacement in Miraheze for that features? [16:48:13] i think Category tree, Special:AllPages and • Random page are already possible, but Category intersection and graphic are a different thing [16:53:35] PROBLEM - ping6 on cp3 is WARNING: PING WARNING - Packet loss = 0%, RTA = 251.11 ms [17:05:34] PROBLEM - ping6 on cp3 is CRITICAL: PING CRITICAL - Packet loss = 16%, RTA = 255.55 ms [17:07:43] dmehus: Wiki still not deleted: https://xiaoshenbike.miraheze.org/wiki/%E9%A6%96%E9%A1%B5 [17:07:44] blackwidowmovie0: 2021-01-21 - 19:14:19UTC ask blackwidowmovie0 How did you manage to get yourself killed? [17:08:33] blackwidowmovie0: it says 404 [17:08:33] RhinosF1: Freenode kept on disconnecting/reconnecting me, and the utility bot took it as spam [17:08:37] Ah [17:08:41] RhinosF1: Not for me [17:08:43] yesah [17:08:45] *yeah [17:08:50] the bot killed me :p [17:09:12] Universal_Omega: do you see 404 on ^ [17:09:20] Could it be cache? [17:09:29] Never visited before [17:09:31] the wiki [17:09:34] PROBLEM - ping6 on cp3 is WARNING: PING WARNING - Packet loss = 0%, RTA = 257.34 ms [17:09:56] I mean ManageWiki cache [17:09:58] I do see 404 [17:10:04] RhinosF1: ^ https://usercontent.irccloud-cdn.com/file/9QysXcbn/Screen%20Shot%202021-01-24%20at%209.09.48%20AM.png [17:10:34] Universal_Omega: what does deleted.dblist look like on each server or individual json file? [17:11:05] Or whatever the cache file is called [17:11:33] RECOVERY - ping6 on cp3 is OK: PING OK - Packet loss = 0%, RTA = 248.52 ms [17:12:39] RhinosF1: I checked that wiki on every server (including test2) and it says 404 on them all. [17:12:56] Universal_Omega: weird [17:13:10] RhinosF1: It doesn't look like MediaWiki [17:13:20] it looks self-hosted [17:13:37] since there is no sidebar, no skin, and the layout is terrible [17:13:55] It looks like rendering died [17:14:09] Which would imply varnish is at fault [17:14:24] paladox, SPF|Cloud: can we purge it? [17:15:12] RhinosF1: This is what I see. https://usercontent.irccloud-cdn.com/file/AgoMQC24/rhinos.png [17:15:36] PROBLEM - ping6 on cp3 is WARNING: PING WARNING - Packet loss = 0%, RTA = 251.96 ms [17:16:04] blackwidowmovie0: yes that's what happens when rendering gets screwed up and varnish serves something half useful [17:16:22] got it [17:16:23] it [17:16:29] * it is closed, though [17:16:34] but not deleted [17:17:05] It's deleted according to MediaWiki [17:17:43] yeah, but why can I view it? [17:17:52] maybe the front page is cached in varnish/whatever you use but the styles aren't? [17:17:53] if no one else can [17:18:03] it's a 404 for me [17:18:21] let me try again [17:18:24] cleared cache [17:18:38] I still see it [17:18:57] Majavah: that's what I think too [17:19:18] But that needs someone with varnishadm to kick it [17:19:41] RhinosF1: That would imply that everyone can view the front page, but with Varnish being funny [17:19:46] but only I can [17:20:47] blackwidowmovie0: it would imply everyone on a certain cache proxy can [17:20:56] But it's the only logic answer [17:21:00] RhinosF1: I'm logged out right now [17:21:10] You would be anyway [17:21:17] You can't login to a nonexistent wiki [17:21:35] status update [17:21:37] https://meta.miraheze.org/wiki/User_talk:Sangong [17:21:47] dmehus locked perpetrator [17:21:56] !log cp9: ban req.http.Host == xiaoshenbike.miraheze.org [17:21:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [17:22:00] Majavah: main page is cached for anons I believe [17:22:06] blackwidowmovie0: now try [17:22:24] RhinosF1: 404 [17:23:04] RhinosF1: I'd login, but I can't, as I don't have my phone on me right now for 2FA [17:24:26] blackwidowmovie0: cp9 was playing up [17:24:33] paladox: why did it not auto purge? [17:24:46] RhinosF1: I recall that being a problematic cp [17:24:51] we don't purge [17:24:59] We should [17:25:02] Or that happens [17:25:14] How long does the cache last? [17:25:32] i think 30 minutes to an hour [17:26:13] then it would have been gone soon enough [17:26:49] RhinosF1: https://phabricator.miraheze.org/T6431 [17:27:40] That was fixed [17:27:49] since resolved, but possibly acting up again [17:27:59] They moved it to another physical server [17:28:07] Rack [17:28:07] ok [17:29:20] Reception123: Can I have my phab account re-enable [17:29:24] *re-enabled [17:29:33] RECOVERY - ping6 on cp3 is OK: PING OK - Packet loss = 0%, RTA = 248.29 ms [17:32:43] Did you not break them conditions within hours ? [17:32:55] it was 4 days, RhinosF1 [17:33:56] blackwidowmovie0: how do we know that won't happen again [17:35:46] RhinosF1: You don't, but if I do, you can easily press the disable button [17:35:51] I will try [17:36:00] you just have to trust me [17:36:08] Yes I know that [17:36:19] But why should Reception123 trust you [17:37:04] I don't have a reason to mess things up [17:37:07] I like Miraheze [17:37:18] why would I intentionally disrupt it? [17:40:29] I don't think you intentionally do things to distrupt things [17:40:37] I just think you don't realise what you're doing [17:41:46] @blackwidowmovie0 What's reason for requesting to be undisabled on Phabricator for a third time? In other words, what do you need to do on Phabricator you can't ask here in #miraheze, in #miraheze-offtopic, or DM any sysadmin? [17:45:46] dmehus: Custom domain requests, filing bug reports, etc. [17:46:30] RhinosF1: That's fair, I guess [17:46:44] @blackwidowmovie0 Custom domain requests, for yourself or for others? [17:46:48] both [17:47:39] As far as filing bug reports, you can report those here in #miraheze and someone can make a task for you. I personally think it's too soon, as I haven't seen enough positive behavioural change on Miraheze and the Wikimedia wikis, but will let Reception123 decide [17:48:55] dmehus: Wikimedia is irrelevant on Miraheze [17:49:07] dmehus: It's been 2 months from yesterday [17:49:34] @blackwidowmovie0 Not really. You've confirmed your account there, and the behaviour I've seen there is a continued pattern of disruption, good-faith or not. [17:49:50] I'd ask @Naleksuh for his thoughts to you being undisabled on Phabricator. [17:50:22] blackwidowmovie0: No [17:51:12] Yeah, and plus, @blackwidowmovie0, how long it's been doesn't matter as much as we need to see a demonstrated behavioural improvement. I'm not seeing enough to justify an undisabling, sorry. :( [17:51:59] dmehus: I don't think Naleksuh's opinion matters in this particular issue [17:52:10] he is a security reviewer, not a sysadmin [17:52:15] not a GS, or a Steward [17:52:20] not even a meta admin [17:52:21] @blackwidowmovie0 Why not? He's observed your behaviour closely. [17:52:27] too closely [17:52:37] I value his opinion because of that, not because of titles he may or may not have [17:52:38] and he's very critical of me [17:52:46] Not true. [17:52:49] Also wikipedia *is* relevant on miraheze, although the reverse is not true [17:52:55] He's critical of your behaviour, not you. [17:53:36] dmehus: You said contribute positively [17:53:41] I have, on my wikis [17:53:59] To be fair I also wouldn't see why my opinion would matter...but since I was asked for it I have it [17:54:01] Gave [17:55:10] Naleksuh: I think your opinion would matter if you were a Meta admin (I could see you as one in the near future), as titles *do* matter, in some issues [17:55:16] I've seen some improvement, but I've seen a continued pattern of asking about steward elections, an ArbCom for Simple English Wikipedia, despite others not viewing it as needed, and you continuing to hat collect on the Wikimedia wikis. That demonstrates to me you're not "getting" what has been expressed to you by Reception123, Naleksuh, NDKilla, myself, and others [17:55:41] blackwidowmovie0: Considering the comments above and my own views, I don't see an improvement in your general behavior. I don't think you intentionally do wrong things on Phabricator, but you have been doing them nevertheless [17:55:46] and it's disruptive to our workflow [17:55:58] @blackwidowmovie0 I disagree. I value Naleksuh's opinion regardless of titles; if he's been in a position to observe your behaviour elsewhere, that matters huge to me [17:55:59] so for the time being, until I see your behavior improve I don't feel re-enabling you would be appropriate at this time [17:56:03] Reception123: I can accept your decision [17:56:21] blackwidowmovie0: glad to hear it. If I see you improve in the future, I will consider re-enabling [17:56:37] Yeah. [17:56:39] 👍 [17:56:40] dmehus: I don't think we need his monitoring, considering the fact you're apparently stalking my global contributions [17:56:51] I am not. [17:56:59] then how do you know what I [17:57:05] *I'm doing? [17:57:05] Please refrain from casting aspersions, @blackwidowmovie0 [17:57:19] dmehus: I am simply inferring based on what you're telling me [17:57:55] @blackwidowmovie0 You asked me to monitor your behaviour globally to demonstrate whether you are improving. It was not limited to Miraheze behaviour [17:57:59] ` I've seen a continued pattern of asking about steward elections, an ArbCom for Simple English Wikipedia, despite others not viewing it as needed, and you continuing to hat collect on the Wikimedia wikis` Nos. 1 and 2 are true, as I am tring to help. Hat collecting is false and simply an insult [17:58:15] dmehus: I meant Miraheze, but that's fine [17:58:42] Your behaviour elsewhere is relevant, especially since you haven't been that active on-wiki on Miraheze [17:59:02] I asked about steward elections, because I wanted to help set up, so I *can* be helpful [17:59:07] [02ManageWiki] 07R4356th synchronize pull request 03#231: WIP: Add documentation for messages - 13https://git.io/JtsXr [17:59:14] Wikipedia actions are used on miraheze [17:59:14] Granted the reverse is not true though [17:59:25] I added userpage links, which were reverted by Praxidicae, no clue as to why [17:59:47] Naleksuh: that's fine, but I don't see the point of checking my every contribution [17:59:56] @blackwidowmovie0 We really should move this to #miraheze-offtopic if you wish to continue to discuss this [18:00:05] dmehus: sure [18:00:11] miraheze/ManageWiki - R4356th the build passed. [18:00:15] @blackwidowmovie0 Thanks :) [18:05:19] [02ManageWiki] 07Universal-Omega synchronize pull request 03#231: WIP: Add documentation for messages - 13https://git.io/JtsXr [18:06:15] miraheze/ManageWiki - Universal-Omega the build passed. [18:06:51] [02ManageWiki] 07R4356th edited pull request 03#231: Add documentation for messages - 13https://git.io/JtsXr [18:11:32] [02ManageWiki] 07Universal-Omega closed pull request 03#231: Add documentation for messages - 13https://git.io/JtsXr [18:11:33] [02miraheze/ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtZLN [18:11:35] [02miraheze/ManageWiki] 07R4356th 03c545007 - Add documentation for messages (#231) * Add documentation for API messages Translations may often not include technical terms. These warn them. * Document more messages "Used as a log message" is not really helpful. * Consistency with the quotes * Complete documenting all log entries and update two existing strings' doc * More messages * One last string and [18:11:35] indentation * Fix indentation Co-authored-by: Universal Omega <54654040+Universal-Omega@users.noreply.github.com> [18:12:04] Paladox or RhinosF1, when you are free, can you look on: https://phabricator.miraheze.org/T6768 and see if some of that features can be implemented? I think Category tree, Special:AllPages and Random page are already possible in Miraheze, but Category intersection and graphic are a different thing [18:12:05] [ ⚓ T6768 Request to add some features of wikipedia ES spanish into tuscriaturas miraheze wiki ] - phabricator.miraheze.org [18:12:22] If this is not the time or place, i can put a request on CN [18:12:31] miraheze/ManageWiki - Universal-Omega the build passed. [18:31:35] How do I convert the talk discussion over to flow for all discussions on my wiki? [18:37:37] You ask us nicely [18:38:11] darkmatterman40: You have to enable StructuredDiscussions in Special:ManageWiki/extensions [18:38:23] Okay. [18:38:33] after that, Special:ManageWiki/namespaces, and go to the talk sections of those [18:38:39] pick `Flow` [18:38:55] then delete all talk pages in the namespaces that you selected [18:39:02] and Flow should pop up [18:39:05] darkmatterman450 is asking about existing ones [18:39:05] That is most helpful. [18:39:08] And just no [18:39:19] darkmatterman450: we can run a script to archive them on mass [18:39:26] To a subpage [18:39:35] And then add flow pages [18:39:39] @RhinosF1 That's more helpful. [18:39:58] [02puppet] 07JohnFLewis commented on pull request 03#1600: [POC|DNM] data: apply changes from T6757 - 13https://git.io/JtZtj [18:40:00] [02puppet] 07JohnFLewis closed pull request 03#1600: [POC|DNM] data: apply changes from T6757 - 13https://git.io/Jt38B [18:40:08] It's on https://vivapinatagameplay.miraheze.org [18:40:10] [ Viva Pinata Gameplay Wiki ] - vivapinatagameplay.miraheze.org [18:41:39] darkmatterman450: we can run https://github.com/wikimedia/mediawiki-extensions-Flow/blob/master/maintenance/convertNamespaceFromWikitext.php if you say what namespace [18:41:40] [ mediawiki-extensions-Flow/convertNamespaceFromWikitext.php at master · wikimedia/mediawiki-extensions-Flow · GitHub ] - github.com [18:42:00] File a task and I can do tommorow if no one beats me to it [18:43:11] darkmatterman450: You could make an archive, but there isn't a way to make existing discussions threads on Flow, with all messages and users intact [18:43:11] At least, I don't think there is [18:43:20] Okay, I'll be right back. [18:46:19] blackwidowmovie0: no, it does it to a subpage [18:54:40] PROBLEM - wiki.worldsofweary.com - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.worldsofweary.com could not be found [18:54:41] PROBLEM - www.portalsofphereon.com - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.portalsofphereon.com could not be found [18:54:45] PROBLEM - wiki.abyogsms.org.in - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.abyogsms.org.in could not be found [19:01:46] RECOVERY - www.portalsofphereon.com - reverse DNS on sslhost is OK: rDNS OK - www.portalsofphereon.com reverse DNS resolves to cp7.miraheze.org [19:01:46] RECOVERY - wiki.abyogsms.org.in - reverse DNS on sslhost is OK: rDNS OK - wiki.abyogsms.org.in reverse DNS resolves to cp6.miraheze.org [19:01:47] RECOVERY - wiki.worldsofweary.com - reverse DNS on sslhost is OK: rDNS OK - wiki.worldsofweary.com reverse DNS resolves to cp6.miraheze.org [19:03:00] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 2400:6180:0:d0::403:f001/cpweb [19:03:26] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 8 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 51.77.107.210/cpweb, 51.89.160.142/cpweb, 2001:41d0:800:1056::2/cpweb, 2001:41d0:800:105a::10/cpweb, 51.222.27.129/cpweb, 2607:5300:205:200::2ac4/cpweb [19:03:32] PROBLEM - mw5 Current Load on mw5 is CRITICAL: CRITICAL - load average: 11.60, 8.70, 6.13 [19:03:46] PROBLEM - mw4 Current Load on mw4 is CRITICAL: CRITICAL - load average: 12.82, 8.93, 6.16 [19:04:56] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [19:07:21] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [19:07:25] PROBLEM - mw5 Current Load on mw5 is WARNING: WARNING - load average: 5.89, 8.52, 6.76 [19:07:44] RECOVERY - mw4 Current Load on mw4 is OK: OK - load average: 5.18, 8.05, 6.53 [19:09:22] RECOVERY - mw5 Current Load on mw5 is OK: OK - load average: 4.79, 7.08, 6.43 [19:10:22] paladox: Is paladox_ your account? [19:12:33] You can see from the cloak and fact it's voiced [19:15:03] RhinosF1: Just checking. Also, see your Discord [19:15:57] blackwidowmovie0: can you just tell me on irc? [19:16:16] in DMs? [19:16:42] Ok [20:42:30] @RhinosF1 We can use the same hostmask on multiple accounts? Didn't know that [20:42:45] dmehus: yes [20:42:51] Well no [20:42:55] But it's 1 account [20:43:02] I assume you mean multiple nicks [20:43:08] yeah [20:43:14] That's my point, they're both logged in as Paladox [20:43:15] multiple nicks it looks like [20:43:20] ah, gotcha [20:44:10] so you could use @miraheze/RhinosF1 for a nick RhinosF1 and a nick Carrhino if you wanted to, provided both were logged in to the same RhinosF1 account [20:44:29] It's spelt with one r [20:44:32] But yes [20:44:41] ah, ok, heh [20:45:57] Look at MirahezeLogbot and icinga-miraheze as an example [20:46:11] Or MirahezeBot and MirahezeBotBeta [22:36:40] * hispano76 greetings [22:45:56] [02mw-config] 07dmehus opened pull request 03#3677: Blacklist sensitive user rights from being `*` - 13https://git.io/JtZCZ [22:46:59] miraheze/mw-config - dmehus the build passed. [22:49:00] [02mw-config] 07dmehus commented on pull request 03#3677: Blacklist sensitive user rights from being `*` - 13https://git.io/JtZCW [23:30:20] PROBLEM - jobrunner2 Current Load on jobrunner2 is CRITICAL: CRITICAL - load average: 6.46, 5.56, 4.33 [23:42:05] PROBLEM - jobrunner2 Current Load on jobrunner2 is WARNING: WARNING - load average: 5.04, 5.75, 5.27 [23:46:00] RECOVERY - jobrunner2 Current Load on jobrunner2 is OK: OK - load average: 3.25, 4.79, 5.02