[00:15:05] PROBLEM - cp37 Disk Space on cp37 is WARNING: DISK WARNING - free space: / 49095MiB (10% inode=99%); [01:57:36] [02mw-config] 07enews opened pull request #5811: Adding RobloxURI to cafewiki allowed protocols - T13215 (07miraheze:03master...07enews:03master) 13https://github.com/miraheze/mw-config/pull/5811 [02:09:24] miraheze/mw-config - enews the build passed. [02:43:40] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [02:49:47] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.52 ms [03:01:06] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 70%, RTA = 31.58 ms [03:02:00] [02mw-config] 07enews commented on pull request #5811: Added Urbanshade and UTG/UFG as their request 13https://github.com/miraheze/mw-config/pull/5811#issuecomment-2646042814 [03:05:09] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.56 ms [03:44:03] PROBLEM - holocron.net - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'holocron.net' expires in 14 day(s) (Mon 24 Feb 2025 03:12:55 AM GMT +0000). [03:44:14] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/5e9d593284a33f9d6adaaaa9a7d7afb4a742be25 [03:44:14] 02ssl/03master 07WikiTideSSLBot 035e9d593 Bot: Update SSL cert for holocron.net [03:59:23] hi. i just migrated from Fandom and now my project namespace is different from the original one. What should I do to change it? [04:33:53] can anyone help me? [04:37:30] Guest26: go to Special:ManageWiki/namespaces [04:39:19] thanks.btw, can I use AWB in miraheze? [04:42:03] RECOVERY - holocron.net - LetsEncrypt on sslhost is OK: OK - Certificate 'holocron.net' will expire on Sat 10 May 2025 02:45:38 AM GMT +0000. [04:44:39] Guest26: it's not disallowed, so yes [04:45:41] though apparently there's some TLS oddities? https://issue-tracker.miraheze.org/T13045 [05:13:16] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 70%, RTA = 31.60 ms [05:19:18] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.59 ms [05:29:32] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 44%, RTA = 31.54 ms [05:31:30] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.61 ms [05:39:47] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [05:41:45] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.59 ms [06:12:53] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 80%, RTA = 31.61 ms [06:16:56] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.60 ms [06:58:14] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [07:08:29] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.60 ms [08:13:07] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [08:17:10] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.60 ms [08:21:46] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 7.67, 6.42, 4.79 [08:23:46] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 5.09, 5.94, 4.81 [08:29:24] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [08:31:23] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.60 ms [09:21:21] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 90%, RTA = 31.61 ms [09:25:24] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.62 ms [09:36:47] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [09:40:51] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.55 ms [10:22:14] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [10:24:12] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.65 ms [10:37:39] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [10:43:47] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.53 ms [10:51:05] PROBLEM - cp37 Disk Space on cp37 is CRITICAL: DISK CRITICAL - free space: / 27189MiB (5% inode=99%); [11:17:44] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [11:19:43] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.58 ms [12:12:13] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 30.15, 17.16, 8.03 [12:12:28] Oh piss off [12:16:31] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [12:17:41] RhinosF1: Man versus Machine [12:22:12] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 8.27, 11.83, 10.69 [12:22:38] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.67 ms [12:28:12] PROBLEM - db171 Current Load on db171 is CRITICAL: LOAD CRITICAL - total load average: 12.26, 10.49, 10.31 [12:42:12] PROBLEM - db171 Current Load on db171 is WARNING: LOAD WARNING - total load average: 3.79, 10.54, 11.97 [12:46:12] RECOVERY - db171 Current Load on db171 is OK: LOAD OK - total load average: 3.56, 6.02, 9.73 [13:17:05] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 37%, RTA = 31.58 ms [13:21:08] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 32.21 ms [13:50:25] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 70%, RTA = 31.60 ms [13:58:36] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.67 ms [14:02:56] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [14:09:03] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.58 ms [14:33:11] PROBLEM - changeprop151 Current Load on changeprop151 is CRITICAL: LOAD CRITICAL - total load average: 10.35, 17.18, 10.15 [14:35:05] RECOVERY - changeprop151 Current Load on changeprop151 is OK: LOAD OK - total load average: 5.33, 13.46, 9.60 [15:14:11] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 16%, RTA = 31.55 ms [15:18:14] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.95 ms [16:28:14] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [16:34:21] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.66 ms [17:18:07] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [17:20:05] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.64 ms [17:53:59] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [17:55:58] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.55 ms [18:20:30] PROBLEM - changeprop151 Current Load on changeprop151 is WARNING: LOAD WARNING - total load average: 13.10, 13.76, 6.88 [18:22:30] RECOVERY - changeprop151 Current Load on changeprop151 is OK: LOAD OK - total load average: 3.08, 9.77, 6.26 [19:47:08] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [19:49:06] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 32.54 ms [20:28:30] PROBLEM - changeprop151 Current Load on changeprop151 is WARNING: LOAD WARNING - total load average: 15.26, 14.93, 7.32 [20:30:30] RECOVERY - changeprop151 Current Load on changeprop151 is OK: LOAD OK - total load average: 3.21, 10.52, 6.63 [21:00:00] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [21:08:11] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.61 ms [22:08:04] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 37%, RTA = 31.56 ms [22:12:07] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.52 ms [22:16:26] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [22:22:34] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.56 ms [22:52:04] [02mw-config] 07Friskygote opened pull request #5812: T13218: Change footer icons for Outlaster Wiki (outlasterwiki) (07miraheze:03master...07Friskygote:03T13218) 13https://github.com/miraheze/mw-config/pull/5812 [22:52:58] miraheze/mw-config - Friskygote the build passed. [23:02:16] Should I unclaim the ticket when PR is awaiting merge/rejection? [23:07:21] [02mw-config] 07AgentIsai merged 07Friskygote's pull request #5812: T13218: Change footer icons for Outlaster Wiki (outlasterwiki) (07miraheze:03master...07Friskygote:03T13218) 13https://github.com/miraheze/mw-config/pull/5812 [23:07:21] [02mw-config] 07AgentIsai pushed 1 new commit to 03master 13https://github.com/miraheze/mw-config/commit/8381d27db429c71fc117b8851af8d6fe76992f2d [23:07:21] 02mw-config/03master 07Frisk 038381d27 T13218: Change footer icons for Outlaster Wiki (outlasterwiki) (#5812)… [23:08:24] [02mw-config] 07AgentIsai merged 07enews's pull request #5811: Adding RobloxURI to cafewiki allowed protocols - T13215 (07miraheze:03master...07enews:03master) 13https://github.com/miraheze/mw-config/pull/5811 [23:08:24] [02mw-config] 07AgentIsai pushed 1 new commit to 03master 13https://github.com/miraheze/mw-config/commit/33f1eaaefc1e67e5529754f3d17df1617294a991 [23:08:24] 02mw-config/03master 07enews 0333f1eaa Adding RobloxURI to cafewiki allowed protocols - T13215 (#5811)… [23:08:25] miraheze/mw-config - AgentIsai the build passed. [23:08:33] guess now I don't have to in this case, though it would still be good to know if I should for the future :D [23:09:06] [02mw-config] 07AgentIsai merged 07songnguxyz's pull request #5806: Add 'wgPortableInfoboxCustomImageWidth' and 'wgEnableProtectionIndicators' to ManageWiki (07miraheze:03master...07wikilophocmatngu:031.43_conf) 13https://github.com/miraheze/mw-config/pull/5806 [23:09:08] [02mw-config] 07AgentIsai pushed 1 new commit to 03master 13https://github.com/miraheze/mw-config/commit/5b071d43c112bd758f86cb48c6e1d4d693d5e299 [23:09:10] 02mw-config/03master 07Vũ Minh Nguyên 035b071d4 Add 'wgPortableInfoboxCustomImageWidth' and 'wgEnableProtectionIndicators' to ManageWiki (#5806)… [23:09:27] miraheze/mw-config - AgentIsai the build passed. [23:09:52] Frisk: no, you can keep it claimed even after the PR is merged [23:10:04] miraheze/mw-config - AgentIsai the build passed. [23:10:06] You did all the work so the task is yours [23:10:21] PROBLEM - ping6 on mattermost1 is CRITICAL: PING CRITICAL - Packet loss = 100% [23:11:22] sure, just weren't sure if when PR is awaiting approval and technically nothing is happening with it - it makes sense for it to retain "this is being done by someone" status, but yeah, thanks for the answer, I'll keep that in mind for the future :) [23:11:49] no worries [23:12:20] RECOVERY - ping6 on mattermost1 is OK: PING OK - Packet loss = 0%, RTA = 31.57 ms