[00:00:52] PROBLEM - mw1 Puppet on mw1 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 6 minutes ago with 0 failures [00:01:03] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw2 [00:01:25] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 5 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [00:01:35] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:02:39] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw2 mw3 [00:02:42] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 4 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [00:02:46] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw3 [00:03:11] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [00:03:24] uh [00:04:13] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:04:23] PROBLEM - cp4 Stunnel Http for mw2 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:05:28] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.07, 7.17, 6.63 [00:06:28] RECOVERY - cp4 Stunnel Http for mw2 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24661 bytes in 2.897 second response time [00:09:01] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuTh [00:09:02] [02miraheze/puppet] 07paladox 03aed477f - Update mfschunkserver.cfg.erb [00:09:22] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 10.10, 8.48, 7.29 [00:10:36] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24661 bytes in 3.123 second response time [00:10:55] !log restart lizardfs-chunkserver on lizardfs[45] [00:10:55] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [00:13:28] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.14, 6.53, 5.49 [00:14:18] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:14:28] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:14:49] PROBLEM - mw1 HTTPS on mw1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:15:00] PROBLEM - mw3 HTTPS on mw3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:15:10] PROBLEM - mw2 HTTPS on mw2 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:15:36] PROBLEM - cp3 Stunnel Http for mw1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:15:51] PROBLEM - cp4 Stunnel Http for mw2 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:15:53] PROBLEM - cp2 Stunnel Http for mw1 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:15:57] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 2.41, 4.66, 4.94 [00:16:21] PROBLEM - cp4 Stunnel Http for mw1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:16:22] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 2.28, 6.29, 7.00 [00:16:38] PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:16:46] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [00:16:48] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.639 second response time [00:16:57] RECOVERY - mw1 HTTPS on mw1 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 442 bytes in 0.017 second response time [00:16:59] RECOVERY - mw3 HTTPS on mw3 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 442 bytes in 0.015 second response time [00:17:03] RECOVERY - mw2 HTTPS on mw2 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 442 bytes in 0.014 second response time [00:17:26] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 3.51, 5.32, 7.52 [00:17:34] RECOVERY - cp3 Stunnel Http for mw1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24661 bytes in 0.713 second response time [00:17:50] RECOVERY - cp2 Stunnel Http for mw1 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.392 second response time [00:18:18] RECOVERY - cp4 Stunnel Http for mw1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.053 second response time [00:20:35] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.52, 7.65, 7.36 [00:20:55] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24655 bytes in 0.004 second response time [00:21:29] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:21:32] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [00:22:01] RECOVERY - cp4 Stunnel Http for mw2 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24655 bytes in 0.006 second response time [00:22:01] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.690 second response time [00:22:32] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 5.73, 7.10, 7.21 [00:23:05] RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 8.434 second response time [00:23:29] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 1.374 second response time [00:23:33] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.389 second response time [00:23:42] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 11.10, 7.46, 7.56 [00:24:05] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [00:24:31] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.21, 7.85, 7.48 [00:24:54] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [00:25:01] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [00:26:27] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.49, 7.70, 7.46 [00:26:38] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [00:27:33] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.64, 7.34, 7.53 [00:28:10] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:28:36] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuk6 [00:28:38] [02miraheze/puppet] 07paladox 036014c2f - Revert "Send thumbnail generation requests to mw2 (also send thumbernails to mw2) (#1124)" This reverts commit 659a0eebf012b44cf9e99a78368777570406eaf7. [00:29:29] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.74, 8.26, 7.84 [00:34:09] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.47, 7.74, 7.43 [00:49:38] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.32, 7.82, 7.81 [00:51:34] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.18, 8.11, 7.90 [00:59:12] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.78, 7.52, 7.80 [01:01:12] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.04, 8.06, 7.96 [01:03:07] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.94, 7.93, 7.91 [01:05:06] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.56, 8.00, 7.93 [01:07:02] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.03, 7.77, 7.86 [01:11:00] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.69, 7.95, 7.88 [01:12:58] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.94, 7.91, 7.87 [01:14:55] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.31, 8.05, 7.92 [01:20:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuIt [01:20:14] [02miraheze/services] 07MirahezeSSLBot 03557551a - BOT: Updating services config for wikis [01:20:45] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.78, 7.51, 7.75 [01:22:24] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.69, 7.09, 7.95 [01:22:46] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.19, 7.78, 7.81 [01:24:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.97, 7.40, 7.66 [01:28:43] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.80, 7.59, 7.62 [01:31:45] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.03, 5.85, 5.18 [01:33:48] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.47, 5.40, 5.10 [01:34:08] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.12, 7.32, 7.50 [01:34:45] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.86, 7.76, 7.75 [01:36:08] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.44, 7.37, 7.49 [01:40:11] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.36, 7.56, 7.46 [01:46:12] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.47, 7.19, 7.32 [01:52:10] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.67, 7.49, 7.34 [01:58:08] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.38, 7.00, 7.24 [01:58:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 4.53, 6.08, 6.78 [02:02:09] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.34, 5.58, 6.59 [02:25:24] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.90, 6.73, 6.32 [02:27:19] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.02, 7.51, 6.64 [02:31:16] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.70, 7.69, 6.91 [02:31:46] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.83, 7.25, 6.66 [02:43:28] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.19, 6.65, 6.77 [02:46:43] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.08, 7.44, 7.13 [02:48:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.25, 7.31, 7.12 [02:56:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.45, 6.28, 6.71 [03:02:58] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 10.38, 7.51, 6.68 [03:04:48] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.06, 7.07, 6.82 [03:04:54] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.44, 7.58, 6.82 [03:08:44] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.30, 6.80, 6.77 [03:08:51] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.72, 6.26, 6.45 [03:20:47] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.53, 7.10, 6.78 [03:24:33] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.66, 6.82, 6.48 [03:26:29] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.81, 6.10, 6.25 [03:26:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.35, 6.68, 6.71 [03:35:34] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.50, 6.64, 5.25 [03:37:30] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.03, 5.74, 5.09 [03:42:26] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.74, 6.69, 6.45 [03:43:24] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.01, 7.19, 6.84 [03:46:18] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.17, 7.48, 6.82 [03:47:13] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.68, 7.71, 7.15 [03:50:15] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.31, 7.49, 6.96 [03:52:57] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.11, 6.31, 6.72 [03:54:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.27, 6.23, 6.55 [04:04:14] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 1 datacenter is down: 2400:6180:0:d0::403:f001/cpweb [04:05:10] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.71, 7.41, 7.03 [04:06:12] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [04:08:31] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.48, 7.54, 6.69 [04:18:14] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.77, 7.64, 7.59 [04:22:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.76, 6.41, 6.72 [04:30:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.25, 6.09, 6.77 [04:48:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.16, 6.49, 6.16 [04:50:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.10, 6.38, 6.16 [06:12:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.27, 6.47, 5.77 [06:16:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.08, 6.69, 6.04 [06:22:44] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.08, 6.64, 6.18 [06:24:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.93, 6.34, 6.12 [06:26:42] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2787 MB (11% inode=94%); [06:30:46] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.05, 6.70, 6.32 [06:34:46] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.60, 6.72, 6.41 [07:10:24] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.88, 6.35, 5.37 [07:12:20] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.29, 6.27, 5.45 [08:06:08] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.77, 6.87, 5.61 [08:08:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.40, 6.52, 5.63 [09:01:42] This user is now online in #wm-bot. I'll let you know when they show some activity (talk, etc.) [09:01:42] @notify Examknow you’ve got mail [09:06:44] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.63, 6.86, 6.11 [09:08:43] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.75, 7.53, 6.45 [09:10:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.62, 7.30, 6.48 [09:12:43] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.01, 6.80, 6.39 [09:23:50] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2647 MB (10% inode=94%); [09:25:33] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.95, 7.14, 6.73 [09:27:28] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.37, 7.86, 7.03 [09:33:15] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.66, 7.93, 7.39 [09:38:59] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 4.61, 5.93, 6.66 [10:12:52] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.32, 6.26, 5.52 [10:14:51] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.79, 6.10, 5.55 [10:16:16] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.00, 7.45, 6.44 [10:17:55] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.84, 6.56, 6.33 [10:18:12] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.11, 6.88, 6.35 [10:19:53] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.44, 6.63, 6.39 [10:20:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.70, 6.74, 6.35 [10:42:37] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.39, 7.34, 6.47 [10:44:37] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.88, 7.72, 6.72 [10:48:35] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.45, 6.25, 6.33 [10:54:42] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.88, 6.60, 6.43 [10:56:00] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.20, 6.68, 6.39 [10:56:42] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.98, 6.06, 6.26 [11:03:38] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.64, 6.76, 6.60 [11:10:04] Reception123: ? why are we having so much load issues [11:10:24] RhinosF1: no idea I've finished wikibackups [11:10:39] Reception123: I'll keep an eye out and try and catch it [11:20:25] revi: hi. you still planning on doing https://meta.miraheze.org/wiki/Community_noticeboard#CoCC_election ? [11:20:26] [ Community noticeboard - Miraheze Meta ] - meta.miraheze.org [11:20:29] If you're busy I can do it [11:23:03] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.09, 6.85, 6.49 [11:26:52] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.17, 6.81, 6.57 [11:28:47] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.72, 6.76, 6.58 [11:33:56] Reception123: yes, tonight [11:34:04] revi: ok, thanks [11:43:47] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 10.20, 7.16, 5.71 [11:44:09] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.92, 6.37, 5.69 [11:45:42] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.99, 6.82, 6.60 [11:45:48] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.31, 7.41, 5.99 [11:46:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.22, 6.44, 5.81 [11:51:46] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.92, 6.33, 5.97 [11:56:56] revi: can you look at updating your private wiki's ssl cert [11:57:14] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.49, 6.26, 6.50 [11:57:15] planned for now as well [11:57:22] ok [11:57:23] gonna do it this weekend or so [11:57:52] as long as it's done before icinga moans at me again [12:01:31] just suppress it /-p [12:03:04] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.31, 7.18, 6.76 [12:04:45] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.61, 7.38, 6.40 [12:04:59] hello [12:05:41] revi: i suppose I can if it gets past it [12:05:45] ErtasVideos: hi [12:06:21] finally someone active on irc [12:06:41] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.98, 6.45, 6.18 [12:06:54] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.63, 6.74, 6.71 [12:07:22] ErtasVideos: what do you need? [12:08:26] idk im bored [12:08:37] im on windows 2000 rn [12:08:59] because whynot [12:10:09] ErtasVideos: why don't you try #miraheze-offtopic, there's normally someone there and most of the time it links to discord which is pretty active as well [12:11:05] im actually on the discord but i want to talk here [12:14:52] oh ok [12:38:44] .mh sal [12:38:45] https://meta.miraheze.org/wiki/sal [12:38:55] .mh SAL [12:38:55] https://meta.miraheze.org/wiki/SAL [12:55:21] .tell johnlewis wiki exists errors don't work for blank dbs per exception bd7b358c2339fcd58a8330b0 [12:55:22] RhinosF1: I'll pass that on when johnlewis is around. [13:19:50] PROBLEM - studentwiki.ddns.net - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'studentwiki.ddns.net' expires in 15 day(s) (Wed 13 Nov 2019 01:17:03 PM GMT +0000). [13:20:11] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeunr [13:20:12] [02miraheze/ssl] 07MirahezeSSLBot 03c467a82 - Bot: Update SSL cert for studentwiki.ddns.net [13:20:14] PROBLEM - wiki.svenskabriardklubben.se - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.svenskabriardklubben.se' expires in 15 day(s) (Wed 13 Nov 2019 01:17:42 PM GMT +0000). [13:20:28] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuno [13:20:30] [02miraheze/ssl] 07MirahezeSSLBot 03e78e224 - Bot: Update SSL cert for wiki.svenskabriardklubben.se [13:21:20] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.86, 6.31, 5.96 [13:22:03] PROBLEM - holonet.pw - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'holonet.pw' expires in 15 day(s) (Wed 13 Nov 2019 01:19:35 PM GMT +0000). [13:22:20] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeunX [13:22:21] [02miraheze/ssl] 07MirahezeSSLBot 0362e2c11 - Bot: Update SSL cert for holonet.pw [13:23:29] PROBLEM - wiki.ngscott.net - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.ngscott.net' expires in 15 day(s) (Wed 13 Nov 2019 01:19:47 PM GMT +0000). [13:23:47] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeunS [13:23:48] [02miraheze/ssl] 07MirahezeSSLBot 03f0e7cd6 - Bot: Update SSL cert for wiki.ngscott.net [13:25:14] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.22, 7.06, 6.33 [13:27:10] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.08, 6.29, 6.13 [13:33:22] RECOVERY - wiki.ngscott.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.ngscott.net' will expire on Sun 26 Jan 2020 12:23:38 PM GMT +0000. [13:33:48] RECOVERY - studentwiki.ddns.net - LetsEncrypt on sslhost is OK: OK - Certificate 'studentwiki.ddns.net' will expire on Sun 26 Jan 2020 12:19:59 PM GMT +0000. [13:33:55] RECOVERY - holonet.pw - LetsEncrypt on sslhost is OK: OK - Certificate 'holonet.pw' will expire on Sun 26 Jan 2020 12:22:13 PM GMT +0000. [13:34:17] RECOVERY - wiki.svenskabriardklubben.se - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.svenskabriardklubben.se' will expire on Sun 26 Jan 2020 12:20:22 PM GMT +0000. [13:49:46] PROBLEM - wiki.dobots.nl - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.dobots.nl' expires in 15 day(s) (Wed 13 Nov 2019 01:47:13 PM GMT +0000). [13:50:01] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeucy [13:50:03] [02miraheze/ssl] 07MirahezeSSLBot 036d06731 - Bot: Update SSL cert for wiki.dobots.nl [13:52:07] PROBLEM - wiki.pupilliam.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.pupilliam.com' expires in 15 day(s) (Wed 13 Nov 2019 01:48:55 PM GMT +0000). [13:52:26] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeucd [13:52:27] [02miraheze/ssl] 07MirahezeSSLBot 03bc71d2c - Bot: Update SSL cert for wiki.pupilliam.com [13:53:10] PROBLEM - wiki.mikrodev.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.mikrodev.com' expires in 15 day(s) (Wed 13 Nov 2019 01:50:54 PM GMT +0000). [13:53:32] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeucb [13:53:34] [02miraheze/ssl] 07MirahezeSSLBot 033d80e15 - Bot: Update SSL cert for wiki.mikrodev.com [13:53:47] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'enc.for.uz' expires in 15 day(s) (Wed 13 Nov 2019 01:50:42 PM GMT +0000). [13:54:02] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeucA [13:54:04] [02miraheze/ssl] 07MirahezeSSLBot 03cb8a9ed - Bot: Update SSL cert for enc.for.uz [13:54:56] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.66, 7.19, 6.55 [13:55:27] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.57, 6.98, 6.36 [13:55:38] PROBLEM - wiki.campaign-labour.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.campaign-labour.org' expires in 15 day(s) (Wed 13 Nov 2019 01:52:19 PM GMT +0000). [13:55:55] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuch [13:55:57] [02miraheze/ssl] 07MirahezeSSLBot 03f5c6d47 - Bot: Update SSL cert for wiki.campaign-labour.org [13:57:23] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.96, 6.33, 6.20 [13:57:28] PROBLEM - wiki.bonessdiving.club - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.bonessdiving.club' expires in 15 day(s) (Wed 13 Nov 2019 01:53:42 PM GMT +0000). [13:57:43] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuCJ [13:57:45] [02miraheze/ssl] 07MirahezeSSLBot 038e6e4d5 - Bot: Update SSL cert for wiki.bonessdiving.club [13:58:52] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.88, 6.60, 6.45 [14:03:08] RECOVERY - wiki.mikrodev.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.mikrodev.com' will expire on Sun 26 Jan 2020 12:53:25 PM GMT +0000. [14:03:25] RECOVERY - wiki.bonessdiving.club - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.bonessdiving.club' will expire on Sun 26 Jan 2020 12:57:36 PM GMT +0000. [14:03:38] RECOVERY - wiki.campaign-labour.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.campaign-labour.org' will expire on Sun 26 Jan 2020 12:55:48 PM GMT +0000. [14:03:44] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Sun 26 Jan 2020 12:53:56 PM GMT +0000. [14:03:45] RECOVERY - wiki.dobots.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.dobots.nl' will expire on Sun 26 Jan 2020 12:49:55 PM GMT +0000. [14:04:09] RECOVERY - wiki.pupilliam.com - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.pupilliam.com' will expire on Sun 26 Jan 2020 12:52:17 PM GMT +0000. [14:15:11] PROBLEM - wiki.rmbrk.sk - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.rmbrk.sk' expires in 15 day(s) (Wed 13 Nov 2019 02:12:19 PM GMT +0000). [14:15:16] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.15, 6.73, 6.45 [14:15:27] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuCa [14:15:29] [02miraheze/ssl] 07MirahezeSSLBot 03fe9b7ab - Bot: Update SSL cert for wiki.rmbrk.sk [14:16:57] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.58, 7.05, 6.61 [14:18:54] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.85, 7.81, 6.94 [14:20:49] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.23, 7.76, 7.03 [14:21:01] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.03, 6.70, 6.56 [14:23:11] RECOVERY - wiki.rmbrk.sk - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.rmbrk.sk' will expire on Sun 26 Jan 2020 01:15:21 PM GMT +0000. [14:28:12] PROBLEM - vsfan.net - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'vsfan.net' expires in 15 day(s) (Wed 13 Nov 2019 02:25:14 PM GMT +0000). [14:28:26] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuCh [14:28:28] [02miraheze/ssl] 07MirahezeSSLBot 034278544 - Bot: Update SSL cert for vsfan.net [14:28:33] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.80, 6.60, 6.76 [14:29:27] PROBLEM - infectowiki.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'infectowiki.com' expires in 15 day(s) (Wed 13 Nov 2019 02:26:38 PM GMT +0000). [14:29:40] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuWv [14:29:42] [02miraheze/ssl] 07MirahezeSSLBot 037ab29d4 - Bot: Update SSL cert for infectowiki.com [14:31:36] PROBLEM - wiki.whentheycry.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'wiki.whentheycry.org' expires in 15 day(s) (Wed 13 Nov 2019 02:29:27 PM GMT +0000). [14:31:57] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuWk [14:31:59] [02miraheze/ssl] 07MirahezeSSLBot 031f0de58 - Bot: Update SSL cert for wiki.whentheycry.org [14:32:22] PROBLEM - tensegritywiki.com - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'tensegritywiki.com' expires in 15 day(s) (Wed 13 Nov 2019 02:30:15 PM GMT +0000). [14:32:38] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuWL [14:32:40] [02miraheze/ssl] 07MirahezeSSLBot 03ca8a30f - Bot: Update SSL cert for tensegritywiki.com [14:34:20] RECOVERY - vsfan.net - LetsEncrypt on sslhost is OK: OK - Certificate 'vsfan.net' will expire on Sun 26 Jan 2020 01:28:19 PM GMT +0000. [14:34:27] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.80, 7.12, 6.90 [14:37:58] Hello sphinx! If you have any questions, feel free to ask and someone should answer soon. [14:38:09] Hi [14:40:25] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.84, 7.51, 7.07 [14:40:39] Hello live_in_the_405! If you have any questions, feel free to ask and someone should answer soon. [14:41:52] sorry to be a bother, but I am trying to create a new account and am receiving the following error: [14:41:56] [a051414decbb06e88e0296f2] 2019-10-28 14:33:59: Fatal exception of type "Wikimedia\Rdbms\DBQueryError" [14:42:05] ^ paladox [14:42:07] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.68, 6.70, 5.72 [14:42:50] I’m mobile, you need to look in the exception log reception123 [14:43:26] RECOVERY - infectowiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'infectowiki.com' will expire on Sun 26 Jan 2020 01:29:34 PM GMT +0000. [14:43:42] RECOVERY - wiki.whentheycry.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.whentheycry.org' will expire on Sun 26 Jan 2020 01:31:50 PM GMT +0000. [14:44:03] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 6.16, 6.44, 5.74 [14:44:20] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.83, 7.75, 7.25 [14:44:32] RECOVERY - tensegritywiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'tensegritywiki.com' will expire on Sun 26 Jan 2020 01:32:32 PM GMT +0000. [14:52:11] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.08, 7.25, 7.10 [14:54:13] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.64, 7.32, 7.14 [14:56:12] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 10.22, 7.83, 7.30 [14:58:14] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.76, 7.56, 7.26 [15:10:14] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.06, 7.03, 6.98 [15:10:43] Error: 1146 Table 'mw1wiki.user' doesn't exist (mediawiki-internal-db-master.mir aheze.org) [15:10:44] ^ paladox [15:11:14] and ^ RhinosF1 [15:12:09] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.27, 6.96, 6.98 [15:12:57] That’s because rhinosF1 created a fake db [15:13:22] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.45, 7.44, 6.73 [15:15:19] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.34, 7.00, 6.65 [15:17:16] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.19, 6.40, 6.47 [15:18:08] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.54, 7.04, 6.94 [15:18:38] paladox: why is it blocking account creation? [15:19:07] Ask JohnLewis, seeing as it's CW :) [15:19:09] Reception123: you’re not confusing the log from the CW error I tested are you? [15:19:57] could be [15:20:07] live_in_the_405: on what wiki did you try to create the account? [15:20:08] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.97, 6.87, 6.88 [15:20:30] meta.miraheze.org [15:20:50] paladox: that's not CW [15:20:53] JohnLewis: 2019-10-28 - 12:55:22UTC tell JohnLewis wiki exists errors don't work for blank dbs per exception bd7b358c2339fcd58a8330b0 [15:20:56] ok [15:21:16] wiki exists error should work [15:21:26] the core check is "DOES THIS DB EXIST?" and if yes, it fails [15:21:35] JohnLewis: it doesn’t - not when it’s an empty dB - see that log [15:21:49] Tested using mw1wiki as the wiki being created [15:22:08] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.26, 7.13, 6.95 [15:22:42] Why is mw1 linked in CA? [15:22:56] i've never used miraheze before, so i'm attempting to create my first account on the service via this webform: https://meta.miraheze.org/wiki/Special:CreateAccount [15:22:57] [ Create account - Miraheze Meta ] - meta.miraheze.org [15:23:39] sounds like someone created the wiki, and didn't clean it up knowing it failed? [15:24:03] JohnLewis: hmm [15:24:34] JohnLewis yup [15:24:35] MariaDB [mhglobal]> select * from cw_wikis where wiki_dbname = 'mw1wiki'; [15:24:44] 20191028125221 [15:24:53] someone created it today?!?! [15:26:08] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.85, 7.81, 7.33 [15:26:13] paladox: that means when I tested that dummy dbs still generate a dB exists error and found that it doesn’t work it went through somehow [15:26:16] I removed the default fall back failure [15:26:30] but that still doesn't explain why someone knowingly didn't remove it knowing it failed [15:26:44] JohnLewis drop from cw_wikis where wiki_dbname = 'mw1wiki'; sane? [15:26:44] this issue is caused by the person who created the wiki, not by CW [15:26:57] paladox: WikiManager()->delete [15:26:57] *delete [15:27:02] oh [15:27:10] [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuln [15:27:12] [02miraheze/ManageWiki] 07translatewiki 033c14f15 - Localisation updates from https://translatewiki.net. [15:27:13] [ Main page - translatewiki.net ] - translatewiki.net. [15:27:13] [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeulc [15:27:15] [02miraheze/MirahezeMagic] 07translatewiki 03c1f0057 - Localisation updates from https://translatewiki.net. [15:27:16] [ Main page - translatewiki.net ] - translatewiki.net. [15:28:25] WikiManager()->delete(true); [15:28:27] JohnLewis ^ [15:28:59] paladox: WikiManager()?? [15:29:05] you have never done that [15:29:08] docs have never said that [15:29:10] oh right [15:29:24] new WikiManager->delete(true); [15:29:32] oh! [15:30:07] !log $wm = new WikiManager( 'mw1wiki' ); $wm->delete( true ); on mw1 [15:30:09] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.34, 7.57, 7.31 [15:30:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:30:37] JohnLewis hmm, dosen't seem to have removed it from cw_wikis [15:32:05] [02miraheze/CreateWiki] 07JohnFLewis pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeulR [15:32:07] [02miraheze/CreateWiki] 07JohnFLewis 038e13d60 - rearrange order of operations [15:32:09] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.42, 6.61, 6.99 [15:32:39] paladox: was there an error? [15:32:43] nope [15:33:11] is wiki_deleted = 1 on the entry? [15:33:24] nope [15:33:26] it's 0 [15:33:32] * paladox faceplams [15:33:37] *facepalms [15:33:43] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.72, 7.82, 6.86 [15:34:36] hmm [15:34:37] https://meta.miraheze.org/wiki/Special:ManageWiki/core/mw1wiki#mw-section-handling [15:34:39] [ Manage a wiki - Miraheze Meta ] - meta.miraheze.org [15:34:42] pressing save fails [15:34:50] i see in the console An invalid form control with name='wpsitename' is not focusable. [15:35:04] paladox: db... [15:35:06] use the damn db [15:35:10] ok [15:35:12] JohnLewis: don’t forget to update the actual running version of CW [15:35:17] RhinosF1: I know [15:35:26] I'd rather fix the actual issue than push a solution rn [15:36:24] !log update cw_wikis set wiki_deleted = 1 where wiki_dbname = 'mw1wiki'; - db4 [15:36:28] That’s a point [15:36:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:36:50] JohnLewis worked! [15:36:53] (it's gone now!) [15:40:08] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.34, 7.22, 7.04 [15:42:00] [02miraheze/mediawiki] 07JohnFLewis pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/Jeuli [15:42:02] [02miraheze/mediawiki] 07JohnFLewis 030196cdd - update CW [15:42:41] JohnLewis: can you test that account creation can’t break like that again? [15:43:10] RhinosF1: account creation will always break like that if a wiki fails half way through creation [15:43:25] JohnLewis: okay [15:43:34] the onus is on the creator to either fix it or notify a mw-admin immediately [15:44:07] would you like me to re-attempt to create that account now? [15:44:16] live_in_the_405: please :) [15:44:16] live_in_the_405 yes please! [15:45:54] An account has just been created so it must work [15:46:07] I'm in! Thank you all so much for working together and getting that fixed impressively quickly <3 [15:46:08] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.07, 7.75, 7.37 [15:46:55] live_in_the_405: you're welcome, any further issues you know where to find us! [15:49:03] JohnLewis: does i18n for https://meta.miraheze.org/wiki/Special:ManageWikiDefaultPermissions come from MW or CW? [15:49:03] [ Manage a wikifarm's default permissions - Miraheze Meta ] - meta.miraheze.org [15:49:08] That’s stupid, MW [15:49:15] And why isn’t it there? [15:49:20] * RhinosF1 looks at the code [15:49:41] awesome - I appreciate y'all! once I figure out my way around things i'll try to pitch in and help out. [15:50:14] awesome <3 [15:50:20] RhinosF1: it's a generally unmaintained piece of code now, it merged up into main code and it's not been looked at since being merged in. It functions, but visually it's not the best [15:51:06] RhinosF1: I guess you'd want a ticket for CSR? [15:51:07] :-p [15:51:32] JohnLewis: what should the i18n say? [15:51:47] revi: yes or I’ll forget [15:52:02] gud [15:52:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.48, 6.11, 6.73 [15:53:59] https://m.phab.wiki/4853 [15:54:00] [ ⚓ T4853 CSR request for private.revi.wiki for renewal 2019 ] - m.phab.wiki [15:54:32] RhinosF1: you know how to do CSR only right? [15:55:22] and now gonna do the electionz [15:57:27] RhinosF1: probs the same as it says on the non-default page [15:57:30] great :) [15:57:44] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeu8v [15:57:45] [02miraheze/puppet] 07paladox 03a01d655 - grafana: Set some security configs [15:58:35] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 10.31, 7.45, 5.83 [16:01:02] JohnLewis: ok will look tonight [16:01:20] Reception123: it’s documented so I should be fine [16:03:07] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.70, 7.30, 6.89 [16:06:23] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 5.42, 7.38, 6.65 [16:07:04] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.77, 7.29, 7.01 [16:08:22] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.37, 6.75, 6.51 [16:12:55] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.25, 6.52, 6.75 [16:16:48] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.76, 6.86, 6.85 [16:17:35] revi: https://phabricator.miraheze.org/T4853#92309 [16:17:36] [ ⚓ T4853 CSR request for private.revi.wiki for renewal 2019 ] - phabricator.miraheze.org [16:17:49] wellaware [16:18:10] :) [16:18:48] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.63, 6.31, 6.64 [16:19:06] lol "4 years cert but you need to replace it annually" https://usercontent.irccloud-cdn.com/file/CjMXLzGy/lol.png [16:19:27] strange [16:19:35] yeah lol-y [16:20:25] wait [16:20:31] you found a cheap cert revi [16:20:32] oh [16:20:35] that's not wildcard [16:20:39] nvm [16:20:40] nope [16:20:44] I don't do wildcard anyway [16:20:56] Reserved for cloudflare CA :P [16:21:04] or LE on my own server [16:21:45] lol [16:22:47] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 10.70, 8.62, 7.52 [16:26:16] live_in_the_405: wiki created [16:26:31] RhinosF1 TYVM! [16:28:40] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.96, 7.17, 7.25 [16:30:11] live_in_the_405: if you need help with applying for the custom domain let us know, you can find more information at [16:30:16] .mh Tech:SSL [16:30:17] https://meta.miraheze.org/wiki/Tech:SSL [16:30:54] .mh Custom Domains [16:30:54] https://Custom.miraheze.org/wiki/Domains [16:30:59] live_in_the_405: ^ [16:31:03] Nope [16:31:11] .mh Custom_Domains [16:31:11] https://meta.miraheze.org/wiki/Custom_Domains [16:31:14] That’s it [16:31:16] RhinosF1: thanks! i've got the CNAME created, so I'll create a ticket in phabricator for the LE cert v soon [16:31:54] live_in_the_405: fantastic, I’ll go learn how to use a bot I created in the meantime [16:32:16] It’s lower case [16:32:32] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.52, 7.49, 7.35 [16:34:29] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.59, 7.64, 7.42 [16:34:58] RhinosF1: ticket updated [16:41:05] revi: seen [16:42:53] paladox, Reception123: can you update that as I’ve switched to mobile? [16:43:03] RhinosF1 ? [16:43:39] https://m.phab.wiki/4853 I assume [16:43:41] [ ⚓ T4853 CSR request for private.revi.wiki for renewal 2019 ] - m.phab.wiki [16:44:11] FB is now telling me they've discovered the new certs [16:44:13] soooo quick [16:44:19] revi ah sectigo :P [16:44:27] I brought the cert from there for miraheze.org [16:44:31] (well from namecheap) [16:45:25] RhinosF1 what do i update? [16:45:51] Oh [16:45:53] the cert [16:45:57] i guess he means deploy [16:47:14] paladox: yes deploy the very [16:47:16] Cert [16:48:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.74, 6.01, 6.59 [16:48:11] I guess i deploy the bundle, right revi ? [16:48:27] Uh... I don't recall correctly these days [16:48:31] see the commit logs [16:48:33] (for that file) [16:48:45] ok [16:49:51] [02ssl] 07paladox created branch 03paladox-patch-3 - 13https://git.io/vxP9L [16:49:52] [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/Jeu4c [16:49:54] [02miraheze/ssl] 07paladox 03db747ab - Update private.revi.wiki certificate [16:49:55] [02ssl] 07paladox opened pull request 03#231: Update private.revi.wiki certificate - 13https://git.io/Jeu4C [16:50:16] reminder: IIRC there is an open PR on dns repo [16:52:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.85, 6.63, 7.91 [16:53:40] [02ssl] 07paladox closed pull request 03#231: Update private.revi.wiki certificate - 13https://git.io/Jeu4C [16:53:42] [02miraheze/ssl] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeu44 [16:53:43] [02miraheze/ssl] 07paladox 03b46e6bb - Update private.revi.wiki certificate (#231) [16:54:19] paladox: https://github.com/miraheze/dns/pull/114 [16:54:20] [ DNS Repo Purge (October 2019) by revi · Pull Request #114 · miraheze/dns · GitHub ] - github.com [16:54:27] revi: that one [16:55:07] RECOVERY - private.revi.wiki - Comodo on sslhost is OK: OK - Certificate 'private.revi.wiki' will expire on Sat 06 Nov 2021 11:59:59 PM GMT +0000. [16:55:11] [02miraheze/ssl] 07paladox deleted branch 03paladox-patch-3 [16:55:12] [02ssl] 07paladox deleted branch 03paladox-patch-3 - 13https://git.io/vxP9L [16:55:42] revi: that looks good, thanks for the quick help [16:57:10] revi deployed! [16:57:14] boom! [16:57:33] paladox: do the dns purge PR [16:58:09] Done [16:58:09] [02dns] 07paladox closed pull request 03#114: DNS Repo Purge (October 2019) - 13https://git.io/JecXs [16:58:10] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-8/±0] 13https://git.io/Jeu4o [16:58:12] [02miraheze/dns] 07revi 03aeef6ca - DNS Repo Purge (October 2019) (#114) * Remove astrapedia.ru > No entries found for the selected source(s). Signed-off-by: Yongmin Hong * Remove kkutu.wiki > Name Server: dns101.registrar-servers.com > Name Server: dns102.registrar-servers.com Signed-off-by: Yongmin Hong * Remove papelor.io > Name Server: NS29.DOMAINCONTROL.COM > Name Server: [16:58:12] NS30.DOMAINCONTROL.COM Signed-off-by: Yongmin Hong * Remove russopedia.info > NOT FOUND Signed-off-by: Yongmin Hong * Remove theliteratureproject.org > Name Server: ns1.mydomain.com > Name Server: ns2.mydomain.com Signed-off-by: Yongmin Hong * Remove toonpedia.cf > NS01.FREENOM.COM > NS02.FREENOM.COM > NS03.FREENOM.COM > NS04.FREENOM.COM Signed-off-by: Yongmin Hong [16:58:12] * Remove unrecnations.wiki > Name Server: NS13.DOMAINCONTROL.COM Signed-off-by: Yongmin Hong * Remove wikitranslate.tk > WHOIS lookup for WIKITRANSLATE.TK can temporarily not be answered. Please try again. Signed-off-by: Yongmin Hong [16:58:33] lol [16:59:24] miraheze/dns/master/aeef6ca - Yongmin Hong The build is still failing. https://travis-ci.org/miraheze/dns/builds/604010684 [17:00:18] # error: rfc1035: Zone miraheze.org.: Zonefile parse error at line 69: General parse error [17:00:18] 6809# fatal: rfc1035: Cannot load zonefile 'miraheze.org', failing [17:00:18] 6810The command "sudo gdnsd checkconf" exited with 42. [17:00:29] paladox, revi ? [17:00:52] I'm ignoring that [17:00:56] as it worked locally [17:01:06] it's failing at the challege i put it [17:01:07] *in [17:01:17] I think I didn't touch mh.o [17:01:17] paladox: travis being its moany self? [17:01:20] it works on ns1 so i'm taking that as the source of truth [17:01:33] i guess travis uses an older version? [17:01:49] I’ve rebooted travis to see if it was just being moody [17:01:59] If not then I’ll actually look [17:02:57] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 12.36, 8.92, 7.33 [17:03:03] miraheze/dns/master/aeef6ca - Yongmin Hong The build is still failing. https://travis-ci.org/miraheze/dns/builds/604010684 [17:12:41] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.23, 7.73, 7.72 [17:15:37] I'm more interested at the fact Travis has been failing for 5 days [17:15:42] and no one bothered to check it [17:15:49] paladox: ^ that's extremely poor practise [17:15:59] JohnLewis: on which repo [17:16:03] JohnLewis i knew about it [17:16:06] i checked it [17:16:11] It worked on ns1 [17:16:12] okay, and? [17:16:18] I ran the command [17:16:20] because it works, we don't need CI? [17:16:32] therefore meaning we fail to identify an actual broken change? [17:16:35] We do?? [17:16:42] JohnLewis: travis can be angry over anything at times [17:16:52] RhinosF1: yes, but when it's a legit failure [17:17:07] JohnLewis has a point :( [17:17:17] [02dns] 07paladox created branch 03paladox-patch-1 - 13https://git.io/vbQXl [17:17:19] [02miraheze/dns] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeuBv [17:17:20] [02miraheze/dns] 07paladox 030110a15 - Fix CAA [17:17:22] [02dns] 07paladox opened pull request 03#115: Fix CAA - 13https://git.io/JeuBT [17:17:23] JohnLewis ^? [17:17:56] JohnLewis: it’s DNS so I can’t define legit failure so but I’ve given up with it liking me at times and nothing has broke on ZppixBot [17:18:06] paladox: update the comment please [17:18:38] RhinosF1: if CI fails, you fix it. You don't deploy until it's fixed. If CI genuinely doesn't work, the priority is making it work not going blind [17:18:56] [02miraheze/dns] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeuBY [17:18:57] ok [17:18:58] [02miraheze/dns] 07paladox 03c998042 - Update miraheze.org [17:18:59] [02dns] 07paladox synchronize pull request 03#115: Fix CAA - 13https://git.io/JeuBT [17:19:08] that's extremely poor practise and anyone at Miraheze with elevated access who follows such a process will quickly find themselves losing their ability to deploy code [17:19:24] JohnLewis: I do with Miraheze make someone check but most of the time with ZppixBot it’s just line length [17:19:26] because ignoring CI is the cause of 90% of our outages at times [17:19:30] [02dns] 07paladox edited pull request 03#115: Add sectigo.com CAA using legacy RFC 3597 Syntax - 13https://git.io/JeuBT [17:19:40] JohnLewis better? [17:20:30] I'm confused [17:20:47] uh [17:20:48] wait [17:20:51] we have 2 CAA sections which aren't next to eachother? [17:21:28] you added the LE section way too early in the file [17:21:38] it should be around the CAA section I added [17:21:45] and they can be together [17:22:04] issuer; [one], [two] [17:22:26] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.28, 7.30, 7.27 [17:22:43] the 67 second is the iodef as well, so only one is needed not 2 [17:23:12] [02dns] 07paladox synchronize pull request 03#115: Add sectigo.com CAA using legacy RFC 3597 Syntax - 13https://git.io/JeuBT [17:23:13] [02miraheze/dns] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeuBW [17:23:15] [02miraheze/dns] 07paladox 034f16ad1 - Update miraheze.org [17:23:30] JohnLewis now does it look better? Because it does to me. [17:23:48] paladox: clearly my last comments were missed [17:23:59] namely, put them together in one and they should be where I put them, not you [17:24:24] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.26, 7.33, 7.29 [17:24:48] oh! [17:24:49] miraheze/dns/paladox-patch-1/4f16ad1 - paladox The build was broken. https://travis-ci.org/miraheze/dns/builds/604024377 [17:24:51] JohnLewis yes [17:24:55] because you've moved them from the area of policy record definitions and they're splitting nameserver and nameserver config [17:26:34] [02dns] 07paladox synchronize pull request 03#115: Add sectigo.com CAA using legacy RFC 3597 Syntax - 13https://git.io/JeuBT [17:26:35] [02miraheze/dns] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeuBo [17:26:37] [02miraheze/dns] 07paladox 03d08febd - Update miraheze.org [17:26:43] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.10, 7.35, 7.07 [17:26:53] JohnLewis is the syntax issue: 1, 2 or issue: 1, issue: 2 [17:27:33] it's a comment, it doesn't matter [17:27:45] issuer; [one], [two] is better reading though [17:27:59] ok! [17:28:14] miraheze/dns/paladox-patch-1/d08febd - paladox The build was fixed. https://travis-ci.org/miraheze/dns/builds/604025894 [17:28:22] [02dns] 07paladox synchronize pull request 03#115: Add sectigo.com CAA using legacy RFC 3597 Syntax - 13https://git.io/JeuBT [17:28:23] [02miraheze/dns] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeuB6 [17:28:24] JohnLewis done, better? [17:28:25] [02miraheze/dns] 07paladox 03700b811 - Update miraheze.org [17:28:34] if CI passes :P [17:28:43] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.23, 7.02, 6.98 [17:29:00] JohnLewis which it did :P [17:29:06] paladox: okay now that last commit is jsut bad [17:29:15] there is no need to copy me exactly [17:29:26] if I say ; but the comment consistently uses : [17:29:32] don't make the comment inconsistent [17:29:43] [02dns] 07paladox synchronize pull request 03#115: Add sectigo.com CAA using legacy RFC 3597 Syntax - 13https://git.io/JeuBT [17:29:44] ok, done [17:29:45] [02miraheze/dns] 07paladox pushed 031 commit to 03paladox-patch-1 [+0/-0/±1] 13https://git.io/JeuBP [17:29:46] [02miraheze/dns] 07paladox 03d177d22 - Update miraheze.org [17:30:11] yeah it's good [17:30:23] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.79, 7.51, 7.24 [17:31:28] [02dns] 07paladox closed pull request 03#115: Add sectigo.com CAA using legacy RFC 3597 Syntax - 13https://git.io/JeuBT [17:31:29] [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuBD [17:31:31] [02miraheze/dns] 07paladox 03614cfd5 - Add sectigo.com CAA using legacy RFC 3597 Syntax (#115) * Fix CAA * Update miraheze.org * Update miraheze.org * Update miraheze.org * Update miraheze.org * Update miraheze.org [17:31:32] JohnLewis merged [17:32:49] miraheze/dns/master/614cfd5 - paladox The build was fixed. https://travis-ci.org/miraheze/dns/builds/604028535 [17:32:51] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.96, 6.33, 6.69 [17:48:10] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.72, 7.11, 7.88 [17:53:34] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.82, 8.20, 7.25 [17:57:23] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 5.89, 7.29, 7.10 [17:59:18] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.44, 8.02, 7.40 [18:01:15] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.17, 7.73, 7.37 [18:04:53] [02ssl] 07paladox synchronize pull request 03#230: Change wildcard.miraheze.org to Comodo certificate - 13https://git.io/JeEUQ [18:04:55] [02miraheze/ssl] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/JeuRR [18:04:56] [02miraheze/ssl] 07paladox 0374d4dcf - Update wildcard.miraheze.org.crt [18:05:07] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.54, 8.20, 7.62 [18:12:49] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.08, 7.65, 7.63 [18:14:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.72, 6.08, 6.57 [18:18:43] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.64, 7.86, 7.67 [18:22:10] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.51, 6.74, 6.52 [18:24:08] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.01, 6.75, 6.56 [18:25:08] Hello lunascape20! If you have any questions, feel free to ask and someone should answer soon. [18:37:04] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 10.29, 8.20, 7.15 [18:37:07] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [18:37:29] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw1 [18:37:37] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 5 datacenters are down: 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [18:37:38] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw1 [18:38:59] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.46, 7.19, 6.88 [18:39:04] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [18:39:33] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [18:39:42] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [18:39:43] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [18:42:43] PROBLEM - bacula1 Bacula Private Git on bacula1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [18:42:50] PROBLEM - bacula1 Bacula Phabricator Static on bacula1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [18:43:55] paladox: why bacula down [18:44:02] it's not? [18:44:53] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.19, 7.96, 7.29 [18:45:03] paladox: check icinga web [18:45:12] https://icinga.miraheze.org/monitoring/host/show?host=bacula1 [18:45:13] [ Icinga Web 2 Login ] - icinga.miraheze.org [18:45:20] It’s just fell over [18:45:33] PROBLEM - bacula1 Bacula Private Git on bacula1 is WARNING: WARNING: Full, 4217 files, 8.761MB, 2019-10-15 18:59:00 (1.9 weeks ago) [18:45:36] PROBLEM - bacula1 Bacula Phabricator Static on bacula1 is WARNING: WARNING: Full, 81004 files, 2.632GB, 2019-10-11 03:03:00 (2.5 weeks ago) [18:45:42] well i'm sshd in [18:45:45] so it's not down [18:46:29] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb [18:46:59] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.39, 7.45, 6.30 [18:47:06] paladox: back [18:47:18] well it's not back as it's been up the entire time [18:47:35] paladox: Icinga has it marked down ping timeout 100% [18:47:46] yes [18:48:05] JohnLewis i guess would know as he's the network expert [18:48:10] but i'm ssh'd in [18:48:13] so the host is not down [18:48:16] paladox: it’s back now [18:48:24] As i said, it's not down [18:48:25] Could it have been something you were doing? [18:48:27] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [18:48:28] it never was down [18:48:36] it was always has been up [18:48:46] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.53, 7.11, 7.14 [18:48:50] *it has always been up [18:48:55] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.77, 7.21, 6.36 [18:49:12] All I know was we got 18:42:51 PROBLEM - bacula1 Bacula Phabricator Static on bacula1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. And then icinga said down when I looked but it’s saying up now [18:49:31] JohnLewis: what broke it? [18:49:46] Yup, that can either be the truth or something happen. I dunno, JohnLewis is best at answering that one. [18:50:05] https://grafana.miraheze.org/d/W9MIkA7iz/miraheze-cluster?orgId=1&var-job=node&var-node=misc1.miraheze.org&var-port=9100 shows up too [18:50:05] [ Grafana ] - grafana.miraheze.org [18:50:52] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 3.93, 6.04, 6.03 [18:54:33] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.84, 5.97, 6.60 [19:02:05] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.07, 6.73, 7.80 [19:05:56] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 10.05, 7.17, 6.29 [19:06:00] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 12.65, 8.27, 8.05 [19:07:52] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.77, 6.65, 6.20 [19:08:22] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.34, 7.12, 6.43 [19:08:29] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw3 [19:08:32] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [19:08:32] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw3 [19:08:48] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw2 [19:09:19] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [19:12:10] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 10.65, 8.26, 6.96 [19:14:29] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.06, 7.45, 6.83 [19:16:25] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 9.61, 8.32, 7.23 [19:16:55] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [19:17:05] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [19:18:22] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.06, 7.88, 7.22 [19:18:36] PROBLEM - mw1 Puppet on mw1 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 4 minutes ago with 0 failures [19:18:39] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.81, 7.83, 7.22 [19:19:05] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [19:19:11] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [19:20:33] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 9.55, 8.99, 7.73 [19:20:45] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.55, 8.74, 7.64 [19:21:07] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeu09 [19:21:09] [02miraheze/puppet] 07paladox 03f581e14 - mediawiki: Decrease php-fpm childs to 4 [19:21:25] !log depool and repool mw1 [19:21:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:22:38] !log depool and repool mw2 [19:22:41] PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 2.38, 6.20, 6.83 [19:22:48] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [19:23:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:24:12] !log depool and repool mw3 [19:24:31] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 3.95, 7.30, 7.43 [19:24:46] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 2.50, 4.85, 6.25 [19:25:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:26:22] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 1 datacenter is down: 2604:180:0:33b::2/cpweb [19:26:23] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw2 [19:26:24] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw2 [19:26:31] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 1.59, 5.27, 6.66 [19:27:08] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw3 [19:28:48] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [19:28:48] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [19:30:12] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 4.69, 5.77, 7.59 [19:32:45] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw2 mw3 [19:32:46] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw3 [19:33:58] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.11, 4.91, 6.80 [19:35:21] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [19:36:25] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [19:36:30] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [19:36:34] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [19:36:56] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [19:46:43] central notices should be setup now [19:47:29] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.57, 7.05, 6.80 [19:48:12] Voidwalker: good [19:49:02] I'm going to change the start time of the nominations one so that it displays now [19:49:23] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.59, 6.84, 6.76 [19:49:32] Voidwalker: shouldn’t the banners switch at the exact time the vote opens [19:49:44] it is [19:50:33] Voidwalker: they switch at 16:04 [19:50:48] ??? [19:51:18] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.16, 6.70, 6.72 [19:51:43] Voidwalker: the vote will open at 16:04 not midnight won’t it? [19:51:46] revi: ? [19:51:53] Voidwalker: also I don’t see a banner [19:52:07] yeah, don't know why the banner isn't appearing [19:53:54] Banner confuses me [19:53:59] changed the start time to yesterday and it should now be appearing [19:54:01] Because it’s active and listed [19:56:32] .in 12 hours poke Reception123 or Zppix [19:56:32] RhinosF1: Okay, I will set the reminder for: 2019-10-29 - 07:56:32GMT [20:06:26] Voidwalker: what’s up with the banners? [20:06:44] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.89, 7.30, 6.82 [20:06:46] don't know, is it not displaying [20:06:48] ? [20:07:09] because it is for me [20:08:03] Voidwalker: I still don’t see it [20:08:20] Voidwalker: it’s appeared now [20:14:44] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 4.90, 6.28, 6.58 [20:25:38] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.39, 7.04, 6.76 [20:27:32] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.80, 6.59, 6.62 [20:50:38] PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.10, 6.77, 6.17 [20:56:31] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 6.21, 6.74, 6.38 [20:59:56] !log depool and repool mw2 [21:00:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:02:32] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-7 [+0/-0/±1] 13https://git.io/Jeuuo [21:02:34] [02miraheze/puppet] 07paladox 03a0c4eac - mediawiki: Lower childs to 4 part 2 [21:02:35] [02puppet] 07paladox created branch 03paladox-patch-7 - 13https://git.io/vbiAS [21:02:37] [02puppet] 07paladox opened pull request 03#1125: mediawiki: Lower childs to 4 part 2 - 13https://git.io/JeuuK [21:02:54] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-7 [+0/-0/±1] 13https://git.io/Jeuu6 [21:02:56] [02miraheze/puppet] 07paladox 0342b2507 - Update mw2.yaml [21:02:57] [02puppet] 07paladox synchronize pull request 03#1125: mediawiki: Lower childs to 4 part 2 - 13https://git.io/JeuuK [21:03:05] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-7 [+0/-0/±1] 13https://git.io/Jeuui [21:03:07] [02miraheze/puppet] 07paladox 0369ca158 - Update mw3.yaml [21:03:08] [02puppet] 07paladox synchronize pull request 03#1125: mediawiki: Lower childs to 4 part 2 - 13https://git.io/JeuuK [21:03:09] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw1 [21:03:15] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw1 [21:03:15] [02puppet] 07paladox closed pull request 03#1125: mediawiki: Lower childs to 4 part 2 - 13https://git.io/JeuuK [21:03:16] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±3] 13https://git.io/JeuuP [21:03:18] [02miraheze/puppet] 07paladox 037b26b02 - mediawiki: Lower childs to 4 part 2 (#1125) * mediawiki: Lower childs to 4 part 2 * Update mw2.yaml * Update mw3.yaml [21:04:04] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:04:14] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:04:40] !log depool and repool mw[123] [21:04:43] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw2 [21:06:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:06:56] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [21:13:08] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [21:13:10] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [21:13:21] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [21:13:46] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [21:14:10] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [21:14:44] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [21:14:53] PROBLEM - mw3 Disk Space on mw3 is WARNING: DISK WARNING - free space: / 8427 MB (10% inode=98%); [21:15:10] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [21:16:50] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuux [21:16:52] [02miraheze/puppet] 07paladox 0380634a9 - Update mw1.yaml [21:17:01] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuup [21:17:03] [02miraheze/puppet] 07paladox 032e9f88f - Update mw2.yaml [21:17:13] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuuh [21:17:14] [02miraheze/puppet] 07paladox 03e9d34c3 - Update mw3.yaml [21:19:15] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [21:20:59] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [21:21:06] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-7 [21:21:08] [02puppet] 07paladox deleted branch 03paladox-patch-7 - 13https://git.io/vbiAS [21:21:10] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:21:21] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw2 mw3 [21:21:33] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw2 mw3 [21:21:48] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:22:09] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:22:27] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeuzU [21:22:28] [02miraheze/puppet] 07paladox 0338f79a0 - Update pool.pp [21:22:48] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw2 [21:48:45] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Jeuzy [21:48:46] [02miraheze/puppet] 07paladox 03957a600 - mediawiki: Raise childs to 6 [21:52:48] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [21:53:13] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [21:53:36] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [21:53:39] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [21:54:08] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [23:28:09] [02CreateWiki] 07RhinosF1 commented on pull request 03#122: see phab T4394 - 13https://git.io/Jeu2Q [23:28:10] [02CreateWiki] 07RhinosF1 closed pull request 03#122: see phab T4394 - 13https://git.io/JesQd [23:32:01] .gh miraheze/puppet [23:32:01] https://github.com/miraheze/puppet