[00:12:43] JohnLewis: You here? [00:13:20] Examknow: hi [00:13:35] have you seen my RfP on meta? [00:13:43] nope [00:14:29] I kind of need support votes ;) [00:15:06] I never comment unless I have a strong view either way, I recuse to close usually :) [00:15:22] k [00:16:00] plus a steward is unlikely to close a request with zero !votes as unsuccessful for such a right anyway [00:17:46] I guess your right [00:44:27] Hi! Here is the list of currently open high priority tasks on Phabricator [00:44:34] No updates for 5 days - https://phabricator.miraheze.org/T4647 - Migrate to the "Massive KVM VPS" plans - authored by Paladox, assigned to Paladox [00:44:41] No updates for 16 days - https://phabricator.miraheze.org/T4638 - Job Queue Fatal Exceptions - authored by RhinosF1, assigned to None [01:59:07] PROBLEM - public.revi.wiki - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'public.revi.wiki' expires in 15 day(s) (Sat 14 Sep 2019 01:55:27 AM GMT +0000). [01:59:21] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjxcx [01:59:23] [02miraheze/ssl] 07MirahezeSSLBot 0342fa2be - Bot: Update SSL cert for public.revi.wiki [02:00:15] PROBLEM - udc-japan.xyz - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'udc-japan.xyz' expires in 15 day(s) (Sat 14 Sep 2019 01:56:32 AM GMT +0000). [02:00:28] PROBLEM - zw.fontainebleau-avon.fr - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'zw.fontainebleau-avon.fr' expires in 15 day(s) (Sat 14 Sep 2019 01:57:24 AM GMT +0000). [02:00:49] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjxch [02:00:50] [02miraheze/ssl] 07MirahezeSSLBot 039abe119 - Bot: Update SSL cert for udc-japan.xyz [02:01:01] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjxcj [02:01:03] [02miraheze/ssl] 07MirahezeSSLBot 037924670 - Bot: Update SSL cert for zw.fontainebleau-avon.fr [02:03:07] RECOVERY - public.revi.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'public.revi.wiki' will expire on Wed 27 Nov 2019 12:59:13 AM GMT +0000. [02:04:15] RECOVERY - udc-japan.xyz - LetsEncrypt on sslhost is OK: OK - Certificate 'udc-japan.xyz' will expire on Wed 27 Nov 2019 01:00:42 AM GMT +0000. [02:04:28] RECOVERY - zw.fontainebleau-avon.fr - LetsEncrypt on sslhost is OK: OK - Certificate 'zw.fontainebleau-avon.fr' will expire on Wed 27 Nov 2019 01:00:55 AM GMT +0000. [05:02:41] PROBLEM - cp4 Current Load on cp4 is WARNING: WARNING - load average: 2.00, 1.26, 0.76 [05:04:40] RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 1.09, 1.11, 0.76 [05:56:04] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fjxWF [05:56:05] [02miraheze/ssl] 07Reception123 03c7c389f - add wiki.articmetrosystem.tk cert [06:26:51] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2992 MB (12% inode=94%); [06:33:32] Morning Reception123 [06:38:57] hi [06:48:19] @seen Examknow [06:48:19] RhinosF1: Last time I saw Examknow they were quitting the network with reason: Quit: Connection closed for inactivity N/A at 8/29/2019 4:27:13 AM (2h21m6s ago) [07:11:00] RhinosF1: oh boy, I'm getting a cookiewarning now logged in... [07:11:43] Reception123: oh ye, I didn't see it earlier so I'm not sure. it's awkward at times [07:11:43] you? [07:11:49] Reception123: ^ [07:12:28] it resets seemingly random (mainly after faults) but it shouldn't persist [07:12:31] paladox: ? [07:13:19] I haven't had it show up like that before [07:13:26] every page I go to it shows up npw [07:13:27] *now [07:13:38] Reception123: something has gone very wrong [07:13:49] but I'm not sure when, it was fine last nice [07:13:53] but I don't know what... [07:13:56] s/nice/night [07:13:56] RhinosF1 meant to say: but I'm not sure when, it was fine last night [07:14:00] because yeah, if it was my changes, it couldn't have just started now [07:14:06] * RhinosF1 should concentrate [07:14:20] Reception123: hmmm [07:14:33] icinga-miraheze: nows your time to say somethings failed [07:17:48] [02mw-config] 07Reception123 closed pull request 03#2747: add wgManageWikiForceSidebarLinks to MWS - 13https://git.io/fjxGv [07:17:50] [02miraheze/mw-config] 07Reception123 pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fjx8f [07:17:51] [02miraheze/mw-config] 07The-Voidwalker 03bc3d239 - add wgManageWikiForceSidebarLinks to MWS (#2747) * add wgManageWikiForceSidebarLinks to MWS * also add to LS [07:18:37] RhinosF1: now it went away, I'm confused [07:19:43] Reception123: still persisting for me [07:20:04] comes back on reload [07:21:36] hmm [07:21:55] hmm [07:44:44] RhinosF1: I’m not sure why that’s happening [07:45:32] paladox: hmmm [09:02:06] paladox, Reception123, SPF|Cloud: Error 503 Backend fetch failed, forwarded for 86.160.232.254, 127.0.0.1 [09:02:06] (Varnish XID 81363243) via cp4 at Thu, 29 Aug 2019 09:00:58 GMT. [09:02:10] see icinga web [09:02:36] improving [09:02:43] but mw1 still not recovered [09:03:01] just cp2 error rate to drop back now [09:13:49] Hmm [09:17:41] paladox: one of those quick random downtimes again it looks like [09:23:43] Yeh [09:24:51] paladox: we need to look into them [09:25:54] Yup [12:35:41] !log added simswiki to discord webhooks [12:35:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [12:44:47] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 213 failures. Last run 2 minutes ago with 213 failures. Failed resources (up to 3 shown) [12:44:57] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 147 failures. Last run 2 minutes ago with 147 failures. Failed resources (up to 3 shown) [12:45:09] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 25 failures. Last run 2 minutes ago with 25 failures. Failed resources (up to 3 shown) [12:45:41] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown) [12:45:52] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Puppet has 218 failures. Last run 2 minutes ago with 218 failures. Failed resources (up to 3 shown): File[wiki.mikrodev.com],File[wiki.mikrodev.com_private],File[wiki.campaign-labour.org],File[wiki.campaign-labour.org_private] [12:45:58] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 173 failures. Last run 3 minutes ago with 173 failures. Failed resources (up to 3 shown) [12:46:08] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 3 minutes ago with 9 failures. Failed resources (up to 3 shown) [12:46:10] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 167 failures. Last run 2 minutes ago with 167 failures. Failed resources (up to 3 shown): File[wikiescola.com.br_private],File[wiki.jacksonheights.nyc],File[wiki.jacksonheights.nyc_private],File[wiki.besuccess.com] [12:46:46] oh come on not again [12:46:47] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 175 failures. Last run 4 minutes ago with 175 failures. Failed resources (up to 3 shown) [12:47:12] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 254 failures. Last run 3 minutes ago with 254 failures. Failed resources (up to 3 shown): File[wiki.tulpa.info_private],File[marinebiodiversitymatrix.org],File[marinebiodiversitymatrix.org_private],File[lodge.jsnydr.com] [12:48:45] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [12:53:41] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [12:54:02] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [12:54:05] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [12:54:08] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:54:47] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:55:09] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:55:09] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [12:55:10] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [12:56:09] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:58:13] Hello pieteek[m]! If you have any questions feel free to ask and someone should answer soon. [14:04:48] Can I ask some kind of a technical question? Well. Thanks. I'm administrator of Nonsensopedia wiki, together with 209po (bureaucrat) we came up with the idea that next to the standard tabs - an article and a user talk page - add a third one: authors. We would like this page to have a clear number of people who participated in creating this page. Just nickname, under nickname. This page should be editable to be able to [14:04:49] add someone's nickname or to erase it. Is this possible to do? [14:15:17] pieteek[m]: so this would be on the top left side of a page? [14:15:45] Yes. [14:15:58] Next to "User talk" button [14:16:22] paladox: I think there would have to be an extension for that, but I'm not sure if that exists already [14:16:55] Or something like that, I don't know how is this named in English, but in Polish this is "discussion" tab [14:17:20] Reception123: ? [14:17:21] Reception123: ? [14:17:22] Uh, sorry for double posting [14:17:36] paladox: hm? They would have to get an extension to add a tab next to the classic "user" and "user talk", no? [14:17:54] Okay, I checked, this is just "Talk" - my mistake [14:19:10] I was talking about the article page, not the user page. Sorry. [14:19:26] okay [14:19:27] paladox: ^ [14:20:20] Oh I’m not sure [14:20:40] paladox: but probably an extension right? [14:20:52] Maybe [14:22:39] pieteek[m]: yeah, you'd probably have to check at MediaWiki.org, since that would be some developer work [14:22:43] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2648 MB (10% inode=94%); [14:28:28] Got it, thanks [14:28:44] you're welcome [14:28:53] let us know if you need anything else [14:29:35] I found this: https://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_add/remove_tabs_throughout_my_wiki? [14:29:35] [ Manual:FAQ - MediaWiki ] - www.mediawiki.org [14:38:26] pieteek[m]: you could try that, but not sure if it can add a new tab [18:00:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjxVG [18:00:12] [02miraheze/services] 07MirahezeSSLBot 03f0759d2 - BOT: Updating services config for wikis [18:01:49] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.19, 6.72, 5.35 [18:05:49] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.77, 6.77, 5.69 [18:23:50] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.34, 6.47, 6.07 [18:24:57] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±5] 13https://git.io/fjxVV [18:24:58] [02miraheze/ManageWiki] 07translatewiki 0333faf51 - Localisation updates from https://translatewiki.net. [18:25:00] [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjxVw [18:25:01] [02miraheze/MirahezeMagic] 07translatewiki 034a95914 - Localisation updates from https://translatewiki.net. [18:25:50] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.29, 6.03, 5.95 [19:09:50] PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is CRITICAL: CRITICAL - NGINX Error Rate is 77% [19:11:50] RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 2% [21:05:10] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjxof [21:05:12] [02miraheze/services] 07MirahezeSSLBot 039d91c7d - BOT: Updating services config for wikis [21:05:50] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 10.92, 9.00, 6.59 [21:07:50] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.56, 7.91, 6.48 [21:15:27] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 11.61, 8.12, 5.09 [21:15:50] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.54, 7.60, 6.81 [21:17:49] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.93, 6.91, 6.63 [21:19:50] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.77, 6.72, 6.58 [22:14:10] hey Reception123 [22:14:12] Reguyla: [22:14:22] Howdy [22:14:24] * RhinosF1 is rubbish at tab to auto-nick [22:14:32] Reguyla: how r u? can we help? [22:14:55] Doing ok, not really. Haven't been on IRC in months [22:15:14] Reguyla: welcome back, do you have a wiki? [22:16:41] Yeah I basically run the Military wiki on Fandom [22:16:56] Reguyla: thought of moving to us? [22:17:25] Yep, haven't really decided though [22:17:56] Reguyla: we'll be happy to welcome you if you do. All the info on moving is on meta.miraheze.org [22:21:12] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 5.19, 6.15, 7.83 [22:22:39] Thanks [22:23:12] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.96, 6.89, 7.87 [22:23:18] np, I'm off to sleep but if you need anything JohnLewis or paladox will likely be somewhere [22:29:41] sure thing, take care [22:30:31] night [22:31:09] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.07, 7.75, 7.97 [22:33:08] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.57, 8.23, 8.12 [22:47:12] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.25, 6.66, 5.62 [22:49:08] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.21, 7.21, 5.94 [22:49:12] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 3.42, 6.23, 7.55 [22:53:09] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 2.99, 4.66, 6.62 [22:58:44] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 5.52, 7.19, 6.81 [23:00:39] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 4.75, 6.39, 6.57 [23:10:17] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 6.99, 8.78, 7.69 [23:12:13] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.40, 7.83, 7.46 [23:16:03] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 3.69, 5.96, 6.80