[00:00:07] RECOVERY - cp37 Puppet on cp37 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [00:00:17] RECOVERY - cp51 Puppet on cp51 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [00:00:24] RECOVERY - db181 Puppet on db181 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [00:00:32] RECOVERY - os161 Puppet on os161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:00:34] RECOVERY - cloud16 Puppet on cloud16 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [00:00:41] RECOVERY - graylog161 Puppet on graylog161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:01:03] RECOVERY - puppet181 Puppet on puppet181 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:02:18] RECOVERY - swiftproxy171 Puppet on swiftproxy171 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [00:02:21] RECOVERY - swiftproxy161 Puppet on swiftproxy161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:02:27] RECOVERY - db182 Puppet on db182 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:02:38] RECOVERY - os151 Puppet on os151 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [00:03:19] RECOVERY - mwtask181 Puppet on mwtask181 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [00:05:08] RECOVERY - mw151 Puppet on mw151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:05:18] RECOVERY - mem151 Puppet on mem151 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:05:18] RECOVERY - cloud15 Puppet on cloud15 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:06:21] RECOVERY - cp27 Puppet on cp27 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [00:07:37] RECOVERY - ldap171 Puppet on ldap171 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:07:48] RECOVERY - mw162 Puppet on mw162 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [00:08:15] RECOVERY - mwtask171 Puppet on mwtask171 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [00:08:41] RECOVERY - jobchron171 Puppet on jobchron171 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [00:09:31] RECOVERY - phorge171 Puppet on phorge171 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [00:10:02] RECOVERY - mw161 Puppet on mw161 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [01:44:01] any beta stewards/other global permissions available? need a perm fixed to test a PR(cc @reception123 ) [01:44:19] PROBLEM - wiki.mahdiruiz.line.pm - Cloudflare on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [01:44:41] hush [01:55:15] What needs doing? [01:56:33] crate on metabeta still just has the legacy `managewiki` right from when it was all one thing, could you grant it `managewiki-permissions` and the other core one so i can fix it up and set up the ability to grant groups as well> [01:58:57] Done [02:01:17] thank you! [02:01:27] time to take over beta [02:03:24] huh wiki creator dont exist on beta [02:03:36] since i need to test that for now ill just make one rq ig [02:05:28] [1/2] wha [02:05:29] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1280710293068185710/saEnowM.png?ex=66d911e8&is=66d7c068&hm=6fe1f2ca3446f4bd745d15ebae6d4edd9f811895c6d0649b5869ea1513960864& [02:06:23] Pretty sure createwiki rights aren’t manageable via the ManageWiki UI [02:06:38] ..por que [02:07:30] why is `view-private-ssl-requests` in MW and createwiki isn't... [02:07:32] welp [02:07:39] ill have to figure this out tmr [02:09:15] if its assigned in config will creating a wikicreator group on beta inherit the rights? [02:09:54] or is it on prod meta only [02:11:21] Hmm that perm probably should have been added to the list [02:11:55] yeeah [02:12:06] https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L3402 controls what is assignable via the UI [02:12:23] [1/2] oh it worked [02:12:23] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1280712032169099377/pAk92Uc.png?ex=66d91386&is=66d7c206&hm=eebb4b0b282ae831b3edcc74c4549c8fec02d91e42f460424b0cd995c02aa872& [02:12:41] ironically the delete wiki request isn't in the same way [02:12:45] https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L3293 [02:12:45] fuckin weird [02:12:52] ill make a pr tmr maybe [02:12:52] already is assigned [02:13:22] why did we do this [02:13:34] whahttps://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L3240 [02:13:59] reading this makes me cry [02:14:33] oh fuck ut [02:15:37] i almost thought it didnt work [02:15:39] well [02:15:51] it wont if you dont give yourself the right PIXL [02:16:12] or also good [02:16:17] the right to give yourself the right [02:17:20] [1/2] okay cool [02:17:20] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1280713279408439308/5Xe5KYO.png?ex=66d914b0&is=66d7c330&hm=64a7f209069f59b7738f4c65d254f019681632a3a1c38c2872302a4c8443de3d& [02:18:01] MacFan4000: is the box checked f youhttps://meta.mirabeta.org/wiki/Special:RequestWikiQueue/21 ? [02:22:56] anyways i eep now bye bte world [02:23:35] [02mw-config] 07MacFan4000 pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/mw-config/compare/cf7ab9f07d55...66d1da5107c5 [02:23:38] [02mw-config] 07MacFan4000 0366d1da5 - add handle-ssl-requests and view-private-ssl-requests and request-ssl to wgManageWikiPermissionsDisallowedRights [02:23:48] !log [@test151] starting deploy of {'config': True} to test151 [02:23:49] !log [@test151] finished deploy of {'config': True} to test151 - SUCCESS in 0s [02:23:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:23:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [02:24:29] miraheze/mw-config - MacFan4000 the build passed. [03:02:57] PROBLEM - mon181 Backups Grafana on mon181 is WARNING: FILE_AGE WARNING: /var/log/grafana-backup.log is 864155 seconds old and 93 bytes [03:13:33] PROBLEM - wonderfuleveryday.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wonderfuleveryday.org' expires in 15 day(s) (Fri 20 Sep 2024 03:07:54 AM GMT +0000). [03:13:48] [02ssl] 07WikiTideSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/754debc7c884...1b73d17ec33d [03:13:50] [02ssl] 07WikiTideSSLBot 031b73d17 - Bot: Update SSL cert for wonderfuleveryday.org [03:52:25] [Grafana] FIRING: The mediawiki job queue has more than 2000 unclaimed jobs https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [04:11:37] RECOVERY - wonderfuleveryday.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wonderfuleveryday.org' will expire on Tue 03 Dec 2024 02:15:11 AM GMT +0000. [04:31:40] PROBLEM - irad.wiki - LetsEncrypt on sslhost is CRITICAL: Name or service not knownHTTP CRITICAL - Unable to open TCP socket [05:39:08] PROBLEM - swiftobject161 NTP time on swiftobject161 is CRITICAL: NTP CRITICAL: No response from NTP server [05:39:33] PROBLEM - swiftproxy171 HTTPS on swiftproxy171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 503 Service Unavailable [05:39:59] PROBLEM - swiftproxy171 HTTP on swiftproxy171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host: HTTP/1.1 503 Service Unavailable [05:40:37] PROBLEM - ping6 on cp51 is CRITICAL: CRITICAL - Host Unreachable (2407:3641:2161:9774::1) [05:41:23] PROBLEM - swiftobject161 NTP time on swiftobject161 is UNKNOWN: check_ntp_time: Invalid hostname/address - time.cloudflare.comUsage: check_ntp_time -H [-4|-6] [-w ] [-c ] [-v verbose] [-o