[00:08:05] !ops ```Error 503 Backend fetch failed, forwarded for , 127.0.0.1 [00:08:05] (Varnish XID 86311990) via cp9.miraheze.org at Thu, 21 Jan 2021 00:07:02 GMT.``` [00:08:48] ^ Seems to be resolved [01:09:36] 👀 didnt we just have a discussion about using that stalkword... use SRE instead [01:39:01] PROBLEM - wiki.joust.ro - reverse DNS on sslhost is CRITICAL: rDNS CRITICAL - wiki.joust.ro All nameservers failed to answer the query. [01:45:40] RECOVERY - wiki.joust.ro - reverse DNS on sslhost is OK: rDNS OK - wiki.joust.ro reverse DNS resolves to cp7.miraheze.org [02:47:12] @Zppix Yes we did, but as RhinosF1 told me, no the "stalkwords" or whatever have been removed while the bot is revamped. [03:51:58] PROBLEM - holonet.pw - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for holonet.pw could not be found [03:58:39] RECOVERY - holonet.pw - reverse DNS on sslhost is OK: rDNS OK - holonet.pw reverse DNS resolves to cp7.miraheze.org [04:00:13] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtYYt [04:00:14] [02miraheze/services] 07MirahezeSSLBot 03f42a34d - BOT: Updating services config for wikis [05:12:36] PROBLEM - dbbackup1 Current Load on dbbackup1 is WARNING: WARNING - load average: 3.99, 2.89, 1.74 [05:14:35] RECOVERY - dbbackup1 Current Load on dbbackup1 is OK: OK - load average: 2.58, 2.61, 1.77 [06:03:36] PROBLEM - dbbackup1 Current Load on dbbackup1 is WARNING: WARNING - load average: 3.76, 3.14, 2.65 [06:05:36] RECOVERY - dbbackup1 Current Load on dbbackup1 is OK: OK - load average: 3.10, 3.30, 2.78 [06:21:34] PROBLEM - dbbackup1 Current Load on dbbackup1 is CRITICAL: CRITICAL - load average: 4.06, 3.04, 2.58 [06:23:34] PROBLEM - dbbackup1 Current Load on dbbackup1 is WARNING: WARNING - load average: 3.83, 3.32, 2.75 [06:27:36] RECOVERY - dbbackup1 Current Load on dbbackup1 is OK: OK - load average: 2.04, 2.85, 2.71 [08:21:36] PROBLEM - dbbackup1 Current Load on dbbackup1 is WARNING: WARNING - load average: 3.49, 2.99, 2.48 [08:23:36] RECOVERY - dbbackup1 Current Load on dbbackup1 is OK: OK - load average: 1.91, 2.59, 2.39 [10:02:10] hello [10:02:34] I want to know if I can set something in order to make that an article can't be searcheable from the search bar [10:02:52] an article=a page [14:14:33] [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtYQj [14:14:34] [02miraheze/MirahezeMagic] 07translatewiki 03139df4a - Localisation updates from https://translatewiki.net. [14:14:35] [ Main page - translatewiki.net ] - translatewiki.net [14:14:36] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JtY7e [14:14:37] [02miraheze/ManageWiki] 07translatewiki 037b5fc69 - Localisation updates from https://translatewiki.net. [14:14:38] [ Main page - translatewiki.net ] - translatewiki.net [14:15:35] miraheze/MirahezeMagic - translatewiki the build passed. [14:15:41] miraheze/ManageWiki - translatewiki the build passed. [14:15:50] @Jakeukalane Yes, you can actually. I'm not sure if you can specify searchability on a page-specific basis, but you can specify it on a namespace basis in Special:ManageWiki/namespaces or on a site-wide basis in Special:ManageWiki/settings. @revi would might know if you can specify searchability (not indexing) on a page-specific basis, though [14:16:48] __NOINDEX__ [14:17:07] Or, to achieve otherwise, __INDEX__ [14:17:23] No not indexing, @revi. Whether it you can find it in the search bar [14:17:43] that's another config value [14:18:01] but only for including it in search by default [14:18:07] (or not) [14:18:36] @revi oh [14:18:56] basic rule of thumb is, if you do not wish to be searched, it should not exist. [14:19:37] also PSA: no @ when pinging me. [14:19:55] revi, yeah, true... [14:20:05] very annoying discord shows me notif counts even if the channel is muted [14:20:56] revi, yes! I don't like that. I wish Discord would make the notification counts disappear when server muted. I basically ignore Discord notification counts as they're more or less useless to me [14:21:25] I always strive to keep the notification count to 0 ~~inbox zero~~ [14:21:26] so [14:21:49] yeah [14:21:54] yeah, I hate how when I get pinged here I also get pinged in #irc-relay and there's nothing I can do about it :( [14:22:10] I always complain 'no @' [14:22:43] I use a different username on Discord than IRC [14:22:52] I am Doug on Discord and dmehus on IRC 😛 [14:22:58] @Doug oh true, lucky you [14:23:15] @Doug and dmehus [14:23:16] and yes, I agree with revi I don't like the automatic @ to go to Discord [14:23:18] * revi annoys them [14:23:31] if someone wants to ping someone from IRC to discord they can add the @ themselves tbh [14:23:36] revi 😛 [14:23:50] well, I can live with discord side ping [14:24:03] what's more annyoing is the ... no ping prevention [14:24:09] @Universal Omega is also smart too as he uses Universal_Omega on IRC, with only an underscore difference that prevents double pings [14:24:29] annoying* [14:24:55] heh maybe Reception123 should become Reception321 on IRC 😛 [14:26:31] lol [14:26:49] :D [14:36:55] lol [16:06:41] thank you all :D very useful [16:29:21] !log MariaDB [bimagvwiki]> INSERT INTO content_models (model_id, model_name) VALUES ( 1, 'wikitext'); [16:29:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:29:25] !log MariaDB [bimagvwiki]> INSERT INTO content_models (model_id, model_name) VALUES ( 2, 'css'); [16:29:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:29:29] !log MariaDB [bimagvwiki]> INSERT INTO content_models (model_id, model_name) VALUES (3, 'javascript'); [16:29:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:29:39] !log MariaDB [bimagvwiki]> INSERT INTO content_models (model_id, model_name) VALUES ( 4, 'Scribunto'); [16:29:41] !log MariaDB [bimagvwiki]> INSERT INTO content_models (model_id, model_name) VALUES ( 5, 'json') [16:29:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:29:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:31:49] !log MariaDB [bimagvwiki]> INSERT INTO slot_roles (role_id, role_name) VALUES (1, 'main'); [16:31:55] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:35:14] !log reception@jobrunner1:/srv/mediawiki/w/maintenance$ sudo -u www-data php deleteBatch.php --wiki metawiki --r "[[phab:T6751|Requested]]" /home/reception/meta.txt [16:35:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:48:34] PROBLEM - data.maantietaja.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for data.maantietaja.org could not be found [17:00:10] PROBLEM - cp6 Current Load on cp6 is CRITICAL: CRITICAL - load average: 3.28, 9.27, 5.84 [17:04:10] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 0.83, 4.57, 4.67 [17:16:59] PROBLEM - cp9 Current Load on cp9 is CRITICAL: CRITICAL - load average: 2.24, 1.98, 1.38 [17:18:59] RECOVERY - cp9 Current Load on cp9 is OK: OK - load average: 0.73, 1.52, 1.28 [19:13:41] .op [19:14:01] .deop [19:14:19] .ask blackwidowmovie0 How did you manage to get yourself killed? [19:14:19] RhinosF1: I'll pass that on when blackwidowmovie0 is around. [19:32:44] [02miraheze/mediawiki] 07Universal-Omega pushed 031 commit to 03REL1_35 [+0/-0/±1] 13https://git.io/JtOOD [19:32:46] [02miraheze/mediawiki] 07Universal-Omega 035771053 - Update Report [19:40:53] PROBLEM - jobrunner1 Puppet on jobrunner1 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] [19:41:20] PROBLEM - mw4 Puppet on mw4 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] [19:41:43] PROBLEM - test2 Puppet on test2 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] [19:42:32] PROBLEM - jobrunner2 Puppet on jobrunner2 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] [19:42:45] PROBLEM - mw6 Puppet on mw6 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] [19:42:56] PROBLEM - mw5 Puppet on mw5 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] [19:43:03] PROBLEM - mw7 Puppet on mw7 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] [19:46:45] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:46:55] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:47:02] RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:47:19] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [19:49:32] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 18.26, 20.73, 17.98 [19:51:30] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 13.52, 18.34, 17.45 [20:03:43] RECOVERY - test2 Puppet on test2 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [20:04:33] RECOVERY - jobrunner2 Puppet on jobrunner2 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [20:04:54] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [20:27:38] PROBLEM - podpedia.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for podpedia.org could not be found [20:27:39] PROBLEM - tep.wiki - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for tep.wiki could not be found [20:27:40] PROBLEM - www.baharna.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.baharna.org could not be found [20:27:43] PROBLEM - www.johanloopmans.nl - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.johanloopmans.nl could not be found [20:27:47] PROBLEM - www.lukaibrisimovic.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.lukaibrisimovic.org could not be found [20:34:30] RECOVERY - www.lukaibrisimovic.org - reverse DNS on sslhost is OK: rDNS OK - www.lukaibrisimovic.org reverse DNS resolves to cp7.miraheze.org [20:34:33] RECOVERY - podpedia.org - reverse DNS on sslhost is OK: rDNS OK - podpedia.org reverse DNS resolves to cp7.miraheze.org [20:34:37] RECOVERY - tep.wiki - reverse DNS on sslhost is OK: rDNS OK - tep.wiki reverse DNS resolves to cp7.miraheze.org [20:34:37] RECOVERY - www.baharna.org - reverse DNS on sslhost is OK: rDNS OK - www.baharna.org reverse DNS resolves to cp6.miraheze.org [20:34:42] RECOVERY - www.johanloopmans.nl - reverse DNS on sslhost is OK: rDNS OK - www.johanloopmans.nl reverse DNS resolves to cp7.miraheze.org [21:00:15] PROBLEM - cp6 Current Load on cp6 is WARNING: WARNING - load average: 5.56, 5.78, 3.76 [21:02:11] RECOVERY - cp6 Current Load on cp6 is OK: OK - load average: 2.47, 4.63, 3.59 [21:25:53] PROBLEM - ping4 on cp3 is CRITICAL: PING CRITICAL - Packet loss = 28%, RTA = 280.23 ms [21:29:53] PROBLEM - ping4 on cp3 is WARNING: PING WARNING - Packet loss = 0%, RTA = 280.86 ms [21:31:52] RECOVERY - ping4 on cp3 is OK: PING OK - Packet loss = 0%, RTA = 242.25 ms [22:00:18] PROBLEM - www.baharna.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for www.baharna.org could not be found [22:00:56] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 22.50, 18.98, 15.53 [22:02:52] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 24.06, 20.81, 16.60 [22:06:46] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 17.00, 19.61, 17.16 [22:07:16] RECOVERY - www.baharna.org - reverse DNS on sslhost is OK: rDNS OK - www.baharna.org reverse DNS resolves to cp6.miraheze.org [22:08:18] PROBLEM - jobrunner1 Current Load on jobrunner1 is CRITICAL: CRITICAL - load average: 6.20, 4.97, 3.57 [22:16:18] PROBLEM - jobrunner1 Current Load on jobrunner1 is WARNING: WARNING - load average: 5.54, 5.73, 4.57 [22:18:48] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 22.92, 21.66, 19.30 [22:20:58] PROBLEM - cloud1 Current Load on cloud1 is CRITICAL: CRITICAL - load average: 31.06, 26.69, 21.53 [22:21:58] PROBLEM - cp3 Stunnel Http for mw4 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [22:22:28] RECOVERY - jobrunner1 Current Load on jobrunner1 is OK: OK - load average: 3.69, 4.76, 4.57 [22:23:57] RECOVERY - cp3 Stunnel Http for mw4 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15073 bytes in 0.929 second response time [22:24:50] PROBLEM - cloud1 Current Load on cloud1 is WARNING: WARNING - load average: 17.44, 21.61, 20.66 [22:26:46] RECOVERY - cloud1 Current Load on cloud1 is OK: OK - load average: 15.43, 19.40, 19.94 [22:45:54] PROBLEM - guia.esporo.net - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for guia.esporo.net could not be found [22:45:55] PROBLEM - wiki.make717.org - reverse DNS on sslhost is WARNING: rDNS WARNING - reverse DNS entry for wiki.make717.org could not be found [22:52:52] RECOVERY - guia.esporo.net - reverse DNS on sslhost is OK: rDNS OK - guia.esporo.net reverse DNS resolves to cp7.miraheze.org [22:52:53] RECOVERY - wiki.make717.org - reverse DNS on sslhost is OK: rDNS OK - wiki.make717.org reverse DNS resolves to cp6.miraheze.org