[00:06:37] <icinga-miraheze>	 PROBLEM - lizardfs4 SSH on lizardfs4 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[00:06:48] <icinga-miraheze>	 PROBLEM - lizardfs4 Lizardfs Chunkserver Port on lizardfs4 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[00:06:53] <paladox>	 uh
[00:07:22] <paladox>	 i'll have to look later
[00:07:26] <icinga-miraheze>	 PROBLEM - Host lizardfs5 is DOWN: PING CRITICAL - Packet loss = 100%
[00:07:36] <paladox>	 well that's bad
[00:08:26] <Voidwalker>	 seems like MySQL isn't the only thing going weird on ya
[00:08:29] <icinga-miraheze>	 PROBLEM - lizardfs4 Puppet on lizardfs4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:08:30] <icinga-miraheze>	 PROBLEM - cp2 HTTPS on cp2 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 4042 bytes in 0.405 second response time
[00:08:55] <icinga-miraheze>	 PROBLEM - lizardfs4 Disk Space on lizardfs4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:09:06] <icinga-miraheze>	 PROBLEM - lizardfs4 Current Load on lizardfs4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:10:07] <SPF|Cloud>	 there are actually people who have to wake up in about 6.5 hours..
[00:10:35] <icinga-miraheze>	 PROBLEM - Host lizardfs4 is DOWN: PING CRITICAL - Packet loss = 100%
[00:10:49] <icinga-miraheze>	 PROBLEM - cp3 HTTPS on cp3 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Backend fetch failed - 4055 bytes in 0.716 second response time
[00:11:53] <paladox>	 !log rebooting lizardfs[45]
[00:12:14] <icinga-miraheze>	 PROBLEM - bacula1 Bacula Static on bacula1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds.
[00:13:32] <Voidwalker>	 well, have fun, I guess
[00:22:49] <SPF|Cloud>	 still debugging our database servers.
[00:26:16] <icinga-miraheze>	 RECOVERY - db4 MySQL on db4 is OK: Uptime: 193 Threads: 48 Questions: 1443 Slow queries: 93 Opens: 114 Flush tables: 1 Open tables: 108 Queries per second avg: 7.476
[00:26:16] <icinga-miraheze>	 RECOVERY - misc4 phabricator.miraheze.org HTTPS on misc4 is OK: HTTP OK: HTTP/1.1 200 OK - 19058 bytes in 0.278 second response time
[00:26:46] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy
[00:27:01] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[00:27:22] <icinga-miraheze>	 RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy
[00:28:16] <icinga-miraheze>	 RECOVERY - misc1 webmail.miraheze.org HTTPS on misc1 is OK: HTTP OK: Status line output matched "HTTP/1.1 401 Unauthorized" - 5799 bytes in 0.060 second response time
[00:28:18] <icinga-miraheze>	 RECOVERY - misc4 phab.miraheze.wiki HTTPS on misc4 is OK: HTTP OK: Status line output matched "HTTP/1.1 200" - 17724 bytes in 0.080 second response time
[00:28:37] <icinga-miraheze>	 RECOVERY - bacula1 Bacula Static on bacula1 is OK: OK: Full, 334656 files, 62.59GB, 2019-10-16 06:23:00 (1.1 weeks ago)
[00:28:41] <icinga-miraheze>	 RECOVERY - Host lizardfs4 is UP: PING OK - Packet loss = 0%, RTA = 0.62 ms
[00:29:44] <icinga-miraheze>	 RECOVERY - lizardfs4 Disk Space on lizardfs4 is OK: DISK OK - free space: / 56798 MB (18% inode=90%);
[00:30:05] <paladox>	 \o/
[00:30:30] <icinga-miraheze>	 RECOVERY - lizardfs4 SSH on lizardfs4 is OK: SSH OK - OpenSSH_7.9p1 Debian-10+deb10u1 (protocol 2.0)
[00:30:47] <SPF|Cloud>	 there seem to be a lot of aborted mysql connections
[00:31:02] <icinga-miraheze>	 RECOVERY - lizardfs4 Lizardfs Chunkserver Port on lizardfs4 is OK: TCP OK - 0.001 second response time on 81.4.122.238 port 9422
[00:32:19] <icinga-miraheze>	 PROBLEM - cp3 Stunnel Http for mw1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:32:31] <icinga-miraheze>	 PROBLEM - mw2 HTTPS on mw2 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[00:33:00] <icinga-miraheze>	 RECOVERY - Host lizardfs5 is UP: PING WARNING - Packet loss = 80%, RTA = 0.70 ms
[00:33:00] <icinga-miraheze>	 RECOVERY - lizardfs4 Puppet on lizardfs4 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures
[00:33:01] <icinga-miraheze>	 PROBLEM - lizardfs5 Lizardfs Chunkserver Port on lizardfs5 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[00:33:01] <icinga-miraheze>	 PROBLEM - lizardfs5 Current Load on lizardfs5 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:02] <icinga-miraheze>	 PROBLEM - lizardfs4 Current Load on lizardfs4 is WARNING: WARNING - load average: 1.75, 3.54, 2.52
[00:33:03] <icinga-miraheze>	 PROBLEM - lizardfs5 SSH on lizardfs5 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[00:33:03] <icinga-miraheze>	 PROBLEM - lizardfs5 Disk Space on lizardfs5 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:03] <icinga-miraheze>	 PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:06] <icinga-miraheze>	 PROBLEM - lizardfs5 Disk Space on lizardfs5 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:07] <icinga-miraheze>	 RECOVERY - lizardfs5 Disk Space on lizardfs5 is OK: DISK OK - free space: / 56807 MB (18% inode=90%);
[00:33:15] <icinga-miraheze>	 PROBLEM - cp2 Stunnel Http for mw2 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:34] <icinga-miraheze>	 PROBLEM - cp4 Stunnel Http for mw2 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:47] <icinga-miraheze>	 PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:33:51] <icinga-miraheze>	 PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:34:11] <icinga-miraheze>	 PROBLEM - cp2 Stunnel Http for mw1 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:34:23] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 3 backends are down. mw1 mw2 mw3
[00:34:35] <icinga-miraheze>	 PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:34:42] <icinga-miraheze>	 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
[00:34:45] <icinga-miraheze>	 RECOVERY - lizardfs5 SSH on lizardfs5 is OK: SSH OK - OpenSSH_7.9p1 Debian-10+deb10u1 (protocol 2.0)
[00:35:04] <icinga-miraheze>	 PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 3 backends are down. mw1 mw2 mw3
[00:35:13] <icinga-miraheze>	 RECOVERY - lizardfs5 Lizardfs Chunkserver Port on lizardfs5 is OK: TCP OK - 0.001 second response time on 81.4.122.196 port 9422
[00:35:15] <icinga-miraheze>	 RECOVERY - mw2 HTTPS on mw2 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 442 bytes in 0.021 second response time
[00:35:17] <icinga-miraheze>	 RECOVERY - cp2 HTTPS on cp2 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 1504 bytes in 0.713 second response time
[00:35:24] <icinga-miraheze>	 PROBLEM - test1 HTTPS on test1 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[00:35:36] <icinga-miraheze>	 PROBLEM - cp4 Stunnel Http for test1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:35:39] <icinga-miraheze>	 RECOVERY - lizardfs4 Current Load on lizardfs4 is OK: OK - load average: 1.05, 2.51, 2.28
[00:35:49] <icinga-miraheze>	 PROBLEM - mw1 Puppet on mw1 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 13 minutes ago with 0 failures
[00:36:22] <icinga-miraheze>	 RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 34 minutes ago with 0 failures
[00:36:31] <icinga-miraheze>	 RECOVERY - cp2 Stunnel Http for mw1 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 2.526 second response time
[00:36:39] <icinga-miraheze>	 RECOVERY - cp3 HTTPS on cp3 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 1504 bytes in 0.874 second response time
[00:37:02] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[00:37:06] <icinga-miraheze>	 PROBLEM - cp4 Stunnel Http for mw1 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:37:27] <icinga-miraheze>	 RECOVERY - lizardfs5 Current Load on lizardfs5 is OK: OK - load average: 1.66, 2.59, 1.39
[00:37:35] <icinga-miraheze>	 RECOVERY - test1 HTTPS on test1 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 444 bytes in 0.156 second response time
[00:37:35] <icinga-miraheze>	 RECOVERY - cp3 Stunnel Http for mw1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 6.564 second response time
[00:37:36] <icinga-miraheze>	 RECOVERY - cp4 Stunnel Http for test1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24638 bytes in 0.243 second response time
[00:38:02] <icinga-miraheze>	 PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[00:38:21] <icinga-miraheze>	 PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 309 bytes in 0.003 second response time
[00:39:10] <icinga-miraheze>	 RECOVERY - cp4 Stunnel Http for mw1 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 9.783 second response time
[00:39:56] <SPF|Cloud>	 heading off for today, it was a pleasure
[00:40:12] <SPF|Cloud>	 mutante: thank you for the hint in the right direction
[00:40:13] <icinga-miraheze>	 RECOVERY - cp2 Stunnel Http for mw2 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24655 bytes in 0.389 second response time
[00:40:27] <icinga-miraheze>	 RECOVERY - cp4 Stunnel Http for mw2 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24655 bytes in 0.005 second response time
[00:41:02] <icinga-miraheze>	 RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24661 bytes in 2.540 second response time
[00:41:06] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[00:42:08] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.62, 6.92, 4.31
[00:42:26] <mutante>	 SPF|Cloud: glad it helped !:)
[00:42:53] <SPF|Cloud>	 yeah. I am a bit ashamed I didn't see that
[00:42:58] <icinga-miraheze>	 PROBLEM - mw2 Puppet on mw2 is WARNING: WARNING: Puppet is currently disabled, message: paladox, last run 10 minutes ago with 0 failures
[00:43:26] <SPF|Cloud>	 alas, at least we are back online without data loss. that is the most important thing
[00:43:28] <mutante>	 don't be. same thing happens to all
[00:43:33] <mutante>	 exactly
[00:43:33] <SPF|Cloud>	 !log restarted dovecot
[00:43:42] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[00:44:07] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.51, 7.72, 4.90
[00:44:10] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.43, 6.30, 3.68
[00:46:09] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.34, 6.52, 4.07
[00:48:04] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 6.59, 6.47, 4.34
[00:50:20] <Not-def6>	 [02miraheze/mw-config] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je00u
[00:50:22] <Not-def6>	 [02miraheze/mw-config] 07paladox 03741480e - Update Sitenotice.php
[00:51:59] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 9.94, 8.38, 5.60
[00:52:12] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy
[00:52:15] <icinga-miraheze>	 RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.411 second response time
[00:52:16] <icinga-miraheze>	 RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.642 second response time
[00:52:18] <icinga-miraheze>	 RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy
[00:52:30] <icinga-miraheze>	 RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24639 bytes in 0.010 second response time
[00:53:24] <icinga-miraheze>	 RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy
[00:53:54] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 4.91, 6.94, 5.39
[00:55:51] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.00, 6.43, 5.39
[00:56:04] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.84, 7.88, 7.07
[01:00:00] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.10, 6.07, 6.52
[01:06:55] <icinga-miraheze>	 RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[01:07:10] <icinga-miraheze>	 RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures
[01:15:17] <ZppixBot>	 Hello nerdopoly4! If you have any questions, feel free to ask and someone should answer soon.
[01:15:57] <icinga-miraheze>	 PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 1 minute ago with 1 failures. Failed resources (up to 3 shown): File[vise.dayid.org_private]
[01:23:38] <icinga-miraheze>	 RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures
[01:25:42] <Not-def6>	 [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0Ee
[01:25:43] <Not-def6>	 [02miraheze/dns] 07paladox 03d876cde - Update miraheze.org
[01:27:12] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures
[01:27:14] <travis-ci>	 miraheze/dns/master/d876cde - paladox The build was broken. https://travis-ci.org/miraheze/dns/builds/602103236
[01:28:35] <Not-def6>	 [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0Ef
[01:28:36] <Not-def6>	 [02miraheze/dns] 07paladox 0332c6275 - Update miraheze.org
[01:30:13] <travis-ci>	 miraheze/dns/master/32c6275 - paladox The build is still failing. https://travis-ci.org/miraheze/dns/builds/602103906
[01:32:54] <Not-def6>	 [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0EJ
[01:32:56] <Not-def6>	 [02miraheze/dns] 07paladox 03c8a2208 - Update miraheze.org
[01:33:55] <Not-def6>	 [02miraheze/dns] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0EU
[01:33:56] <Not-def6>	 [02miraheze/dns] 07paladox 03eaf5545 - Update miraheze.org
[01:34:27] <07IACV0C4>	 miraheze/dns/master/c8a2208 - paladox The build is still failing. https://travis-ci.org/miraheze/dns/builds/602105053
[01:34:27] <ZppixBot>	 Hello 07IACV0C4! If you have any questions, feel free to ask and someone should answer soon.
[01:34:28] <ZppixBot>	 [ Travis CI - Test and Deploy Your Code with Confidence ] - travis-ci.org
[01:35:16] <paladox>	 works locally
[01:36:52] <travis-ci>	 miraheze/dns/master/eaf5545 - paladox The build is still failing. https://travis-ci.org/miraheze/dns/builds/602105240
[01:37:08] <paladox>	 i ran checkconf locally
[01:37:09] <paladox>	 and works
[04:42:37] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.20, 6.71, 5.95
[04:44:39] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.03, 6.17, 5.85
[06:26:23] <icinga-miraheze>	 RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3004 MB (12% inode=94%);
[09:25:11] <Not-def6>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0VG
[09:25:13] <Not-def6>	 [02miraheze/services] 07MirahezeSSLBot 0393e8023 - BOT: Updating services config for wikis
[09:40:11] <Not-def6>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0Vz
[09:40:13] <Not-def6>	 [02miraheze/services] 07MirahezeSSLBot 0359be352 - BOT: Updating services config for wikis
[13:30:13] <Not-def6>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0Kh
[13:30:14] <Not-def6>	 [02miraheze/services] 07MirahezeSSLBot 0365f623c - BOT: Updating services config for wikis
[13:34:31] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.63, 6.82, 5.96
[13:38:34] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.72, 6.15, 5.92
[13:44:35] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.79, 7.01, 6.33
[13:48:38] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.63, 6.80, 6.40
[13:52:46] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.64, 6.99, 6.60
[13:56:50] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.31, 7.98, 7.06
[13:58:52] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 5.76, 7.09, 6.84
[14:00:54] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.04, 6.76, 6.75
[14:08:55] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 10.43, 8.28, 7.29
[14:10:04] <icinga-miraheze>	 PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2647 MB (10% inode=94%);
[14:10:54] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.94, 7.64, 7.17
[14:14:54] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.55, 5.98, 6.59
[14:24:46] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.34, 7.48, 6.73
[14:26:43] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.11, 7.31, 6.75
[14:30:38] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.43, 7.65, 6.97
[14:32:37] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.99, 7.70, 7.07
[14:32:57] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.28, 7.59, 6.92
[14:34:36] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.79, 8.17, 7.32
[14:36:25] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.57, 8.06, 6.69
[14:38:24] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 6.47, 7.47, 6.65
[14:38:29] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.54, 7.52, 7.26
[14:40:28] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.25, 6.46, 6.36
[14:42:27] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.03, 7.99, 7.49
[14:44:28] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.01, 7.52, 7.37
[14:48:26] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.86, 8.43, 7.74
[14:49:04] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.03, 7.87, 7.87
[14:51:04] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.75, 8.65, 8.15
[14:51:34] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.46, 7.05, 6.52
[14:53:33] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.41, 7.43, 6.72
[14:55:33] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.92, 7.61, 6.87
[14:59:31] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.49, 6.51, 6.59
[15:02:14] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.12, 7.42, 7.98
[15:03:10] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.63, 7.31, 7.95
[15:12:03] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.22, 7.48, 7.59
[15:13:15] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.61, 7.53, 7.66
[15:14:04] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.71, 7.17, 7.46
[15:30:06] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.53, 7.60, 7.43
[15:34:03] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.45, 7.79, 7.56
[15:40:04] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.80, 7.88, 7.60
[15:43:29] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.00, 7.37, 7.98
[15:45:29] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 8.25, 7.62, 8.00
[15:46:06] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.72, 7.72, 7.68
[15:47:28] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.67, 7.28, 7.83
[15:56:03] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.34, 7.73, 7.59
[15:58:03] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.09, 7.39, 7.47
[16:00:04] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.27, 7.72, 7.58
[16:02:04] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.47, 7.21, 7.41
[16:05:31] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.69, 5.96, 6.79
[16:13:38] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.48, 6.76, 5.82
[16:15:37] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 5.27, 6.20, 5.73
[16:18:06] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.21, 7.32, 7.29
[16:20:05] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.11, 7.07, 7.22
[16:30:13] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.08, 7.60, 7.27
[16:32:14] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.91, 7.59, 7.30
[16:58:03] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.61, 6.32, 6.71
[17:05:08] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.07, 6.55, 5.98
[17:07:10] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.69, 6.35, 5.99
[17:31:09] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.54, 6.81, 6.20
[17:33:09] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 6.16, 6.54, 6.17
[17:45:09] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.55, 7.35, 6.77
[17:47:06] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.09, 6.46, 6.50
[17:53:07] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.37, 7.20, 6.76
[17:55:09] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.77, 6.74, 6.66
[18:04:48] <ZppixBot>	 Hello ATY! If you have any questions, feel free to ask and someone should answer soon.
[18:05:54] <ATY>	 hello
[18:06:20] <Voidwalker>	 hi
[18:07:30] <ATY>	 can you help me change the behaviour of the miraheze wiki editor maybe?
[18:08:29] <Voidwalker>	 what kind of change are we talking about here?
[18:08:51] <ATY>	 just this second guessing the software wants to do all the time
[18:09:21] <Voidwalker>	 how do you mean?
[18:09:22] <ATY>	 like if you click "edit source" a box pops up asking do you want to edit the source, or the visual editor?
[18:09:30] <ATY>	 and same if you click "edit"
[18:09:48] <ATY>	 there are only 2 buttons... i have figured them out and don't need to be priompted each time
[18:10:16] <Voidwalker>	 oh, there's an issue where the popups for visual editor are not properly disabled like they should be
[18:10:33] <ATY>	 it happens with both editors
[18:11:01] <ATY>	 must be a setting somewhere... i just can't find it
[18:11:30] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 6.83, 6.91, 6.69
[18:11:45] <Voidwalker>	 no, the extension VisualEditor provides these popups and it's not allowing them to be dismissed properly
[18:11:59] <Voidwalker>	 we have a task about it here: https://phabricator.miraheze.org/T4813
[18:12:00] <ZppixBot>	 [ ⚓ T4813 "Welcome to 'wiki name'" appears every time the source or visual editor is opened ] - phabricator.miraheze.org
[18:12:04] <ATY>	 oh so i would ahve to compelte disable the extension?
[18:12:19] <Voidwalker>	 or wait for the fix
[18:13:04] <ATY>	 i see
[18:13:25] <ATY>	 well that answers that i guess
[18:13:27] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 6.38, 6.70, 6.63
[18:13:46] <ATY>	 will it be automatic or should i check something somewhere at some point?
[18:14:20] <Voidwalker>	 it will be automatic
[18:14:23] <ATY>	 i clicked "subscribe" on the right nav bar of the link
[18:14:28] <ATY>	 ok
[18:15:04] <ATY>	 can i bump it somehow or should i jsut leave it be? (I don't know the ettiquette)
[18:15:25] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is CRITICAL: CRITICAL - load average: 8.81, 7.31, 6.46
[18:16:32] <Voidwalker>	 it's being investigated upstream, but we're really not sure where the issue is
[18:16:47] <ATY>	 Ah it isn't just this site it's everywhere?
[18:17:14] <ATY>	 Also, this happens if you are in source editing and you click "show preview". is that the same bug or a seperate one do you think?
[18:17:27] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.05, 7.01, 6.76
[18:17:27] <ATY>	 it's very confusing
[18:18:15] <Voidwalker>	 probably
[18:18:39] <ATY>	 should i add to the thread you linked? 
[18:19:01] <Voidwalker>	 yeah, might be a good idea to make sure everything is on the task
[18:19:24] <ATY>	 OK, I will.
[18:19:26] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.92, 7.41, 6.69
[18:23:10] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 12.10, 8.37, 6.45
[18:25:43] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 9.15, 7.51, 6.99
[18:25:44] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.60, 6.32, 6.52
[18:26:34] <ATY>	 actually should i put it on the "upstream" thread instead? https://phabricator.wikimedia.org/T231763
[18:26:34] <ZppixBot>	 [ ⚓ T231763 Don't show VE help/welcome messages to users if seen before ] - phabricator.wikimedia.org
[18:27:40] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.24, 7.37, 7.01
[18:28:18] <ATY>	 umm.. do all these messages starting with "PROBLEM" mean this is a bad time to be asking questions? I can wait til later.
[18:30:49] <Voidwalker>	 no not really,
[18:30:52] <Voidwalker>	 they do that
[18:31:25] <ATY>	 ok just checking
[18:31:28] <Voidwalker>	 I'd recommend putting it on the local task, and we can move it around later
[18:31:35] <ATY>	 OK great
[18:32:09] <ATY>	 i tried using ublock origin to block the window but i couldn't do it. i'm not very skilled at it though. 
[18:33:41] <icinga-miraheze>	 PROBLEM - mw2 Current Load on mw2 is WARNING: WARNING - load average: 7.05, 6.90, 6.60
[18:34:09] <ATY>	 do most people who use this work in the source editor?
[18:35:00] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 6.13, 7.52, 7.40
[18:35:39] <icinga-miraheze>	 RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 4.65, 6.25, 6.41
[18:36:12] <Voidwalker>	 I don't actually know
[18:37:43] <ATY>	 i hypothesize they do because this is so very obnoxious.. it would not be low priority if lots of ppl were using it
[18:37:58] <ATY>	 probably all these smart ppl who breathe code
[18:38:48] <ATY>	 is there a way to save work other than "save changes" then re opening it for editing? 
[18:39:12] <ATY>	 i'm a compulsive ctrl/cmd-S person but it seems here you have to close and open each time you save
[18:42:44] <Voidwalker>	 not that I know of, but there might be some gadgets out there
[18:42:54] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.08, 5.95, 6.66
[18:45:54] <ATY>	 OK, just wanted to know if I was missing something obvious
[18:55:17] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.54, 6.07, 6.64
[19:23:00] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 7.39, 6.82, 6.30
[19:24:59] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 9.90, 7.95, 6.78
[19:26:59] <icinga-miraheze>	 PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.66, 7.06, 6.55
[19:28:54] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 4.53, 7.01, 6.72
[19:28:59] <icinga-miraheze>	 RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.82, 6.68, 6.48
[19:34:43] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 4.69, 6.17, 6.47
[20:11:05] <Not-def6>	 [02miraheze/ManageWiki] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je0y7
[20:11:06] <Not-def6>	 [02miraheze/ManageWiki] 07translatewiki 0309a169a - Localisation updates from https://translatewiki.net.
[20:11:07] <ZppixBot>	 [ Main page - translatewiki.net ] - translatewiki.net.
[20:11:08] <Not-def6>	 [02miraheze/MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/Je0y5
[20:11:10] <Not-def6>	 [02miraheze/MirahezeMagic] 07translatewiki 03d57356c - Localisation updates from https://translatewiki.net.
[20:11:10] <ZppixBot>	 [ Main page - translatewiki.net ] - translatewiki.net.
[20:25:16] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is CRITICAL: CRITICAL - load average: 13.78, 9.23, 7.14
[20:43:52] <Zppix>	 JohnLewis:  you seem to know alot hows your knowledge of music copyright laws?
[20:50:11] <JohnLewis>	 Zppix: what makes you think I know a lot? :P
[20:50:52] <Zppix>	 JohnLewis:  i mean you did have a part in writing like 90% of MH policy, but nevermind i found someone else
[20:55:10] <icinga-miraheze>	 PROBLEM - mw1 Current Load on mw1 is WARNING: WARNING - load average: 4.95, 5.88, 7.62
[21:01:06] <icinga-miraheze>	 RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 5.56, 5.06, 6.64
[21:13:41] <Not-def6>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-5 [+0/-0/±1] 13https://git.io/Je09f
[21:13:42] <Not-def6>	 [02miraheze/puppet] 07paladox 03234b622 - Add roundcube mail filter
[21:13:44] <Not-def6>	 [02puppet] 07paladox created branch 03paladox-patch-5 - 13https://git.io/vbiAS
[21:13:46] <Not-def6>	 [02puppet] 07paladox opened pull request 03#1119: Add roundcube mail filter - 13https://git.io/Je09J
[21:48:47] <ZppixBot>	 Hello ATY_! If you have any questions, feel free to ask and someone should answer soon.
[22:23:10] <icinga-miraheze>	 PROBLEM - bacula1 Bacula Private Git on bacula1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds.
[22:25:40] <icinga-miraheze>	 PROBLEM - bacula1 Bacula Private Git on bacula1 is WARNING: WARNING: Full, 4217 files, 8.761MB, 2019-10-15 18:59:00 (1.3 weeks ago)
[22:40:21] <icinga-miraheze>	 PROBLEM - mw3 Disk Space on mw3 is WARNING: DISK WARNING - free space: / 8416 MB (10% inode=99%);