[01:02:52] <icinga-miraheze>	 PROBLEM - cp4 Current Load on cp4 is CRITICAL: CRITICAL - load average: 5.04, 2.96, 1.29
[01:06:46] <icinga-miraheze>	 RECOVERY - cp4 Current Load on cp4 is OK: OK - load average: 0.28, 1.48, 1.06
[03:19:17] <peter_li>	 Hello, I need help with common.css upload to my wiki: https://wiki.mxlinuxusers.de/wiki/Hauptseite How and where can I place this file?
[03:19:18] <ZppixBot>	 [ MX Linux Users DE Wiki ] - wiki.mxlinuxusers.de
[03:19:42] <Voidwalker>	 peter_li, https://wiki.mxlinuxusers.de/wiki/MediaWiki:Common.css
[03:19:42] <ZppixBot>	 [ MediaWiki:Common.css – MX Linux Users DE Wiki ] - wiki.mxlinuxusers.de
[03:20:29] <Voidwalker>	 just put the css code on that page, and wait (it takes a few minutes to go through)
[03:22:26] <peter_li>	 May I ask why this is not better declared in the FAQ?
[03:27:09] <Voidwalker>	 it is kind of described, but I'm not sure how to do it better
[03:29:25] <Voidwalker>	 the page does need a bit of an overhaul though
[03:50:47] <peter_li>	 Thanks, so I understand to use the sidebar, too.
[03:51:44] <peter_li>	 Last question for now: Why is my uploaded logo-image not viewable?
[04:02:17] <Voidwalker>	 it needs to be prefixed with // or https://
[06:26:52] <icinga-miraheze>	 RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 5398 MB (22% inode=95%);
[08:40:26] <icinga-miraheze>	 PROBLEM - db4 Disk Space on db4 is CRITICAL: DISK CRITICAL - free space: / 40285 MB (10% inode=97%);
[09:26:23] <Not-7290>	 [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fjWta
[09:26:24] <Not-7290>	 [02miraheze/ssl] 07Reception123 031de9c57 - add archive.mmartists.net cert
[13:00:28] <icinga-miraheze>	 PROBLEM - absurdopedia.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[13:02:25] <icinga-miraheze>	 RECOVERY - absurdopedia.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'absurdopedia.wiki' will expire on Sat 15 Jun 2019 12:09:11 PM GMT +0000.
[14:46:37] <icinga-miraheze>	 PROBLEM - puppet1 Current Load on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:46:56] <icinga-miraheze>	 PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 3 backends are down. mw1 mw2 mw3
[14:47:05] <icinga-miraheze>	 PROBLEM - misc2 Disk Space on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:47:08] <icinga-miraheze>	 PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 3 backends are down. mw1 mw2 mw3
[14:47:14] <icinga-miraheze>	 PROBLEM - misc2 HTTPS on misc2 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[14:47:16] <icinga-miraheze>	 PROBLEM - misc3 Disk Space on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:47:17] <icinga-miraheze>	 PROBLEM - puppet1 Disk Space on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:47:29] <icinga-miraheze>	 PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 3 backends are down. mw1 mw2 mw3
[14:47:37] <icinga-miraheze>	 PROBLEM - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is CRITICAL: CRITICAL - NGINX Error Rate is 90%
[14:47:50] <icinga-miraheze>	 PROBLEM - misc2 Current Load on misc2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:47:59] <icinga-miraheze>	 PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:48:03] <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
[14:48:06] <icinga-miraheze>	 PROBLEM - mw3 HTTPS on mw3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds
[14:48:10] <icinga-miraheze>	 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
[14:48:11] <icinga-miraheze>	 PROBLEM - misc3 Puppet on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:48:15] <icinga-miraheze>	 PROBLEM - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is CRITICAL: CRITICAL - NGINX Error Rate is 78%
[14:48:16] <icinga-miraheze>	 PROBLEM - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is WARNING: WARNING - NGINX Error Rate is 54%
[14:48:21] <icinga-miraheze>	 PROBLEM - misc3 Current Load on misc3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds.
[14:48:43] <icinga-miraheze>	 RECOVERY - puppet1 Current Load on puppet1 is OK: OK - load average: 0.01, 0.31, 0.44
[14:49:00] <icinga-miraheze>	 RECOVERY - misc2 Disk Space on misc2 is OK: DISK OK - free space: / 50308 MB (81% inode=99%);
[14:49:09] <icinga-miraheze>	 RECOVERY - misc2 HTTPS on misc2 is OK: HTTP OK: HTTP/1.1 200 OK - 41137 bytes in 0.235 second response time
[14:49:11] <icinga-miraheze>	 RECOVERY - misc3 Disk Space on misc3 is OK: DISK OK - free space: / 57441 MB (93% inode=99%);
[14:49:12] <icinga-miraheze>	 RECOVERY - puppet1 Disk Space on puppet1 is OK: DISK OK - free space: / 56025 MB (91% inode=99%);
[14:49:49] <icinga-miraheze>	 RECOVERY - misc2 Current Load on misc2 is OK: OK - load average: 0.92, 1.00, 1.12
[14:49:55] <icinga-miraheze>	 RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 7 minutes ago with 0 failures
[14:50:02] <icinga-miraheze>	 RECOVERY - mw3 HTTPS on mw3 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 444 bytes in 0.057 second response time
[14:50:06] <icinga-miraheze>	 RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 7 minutes ago with 0 failures
[14:50:14] <icinga-miraheze>	 RECOVERY - cp4 HTTP 4xx/5xx ERROR Rate on cp4 is OK: OK - NGINX Error Rate is 10%
[14:50:20] <icinga-miraheze>	 RECOVERY - misc3 Current Load on misc3 is OK: OK - load average: 0.39, 0.16, 0.11
[14:50:56] <icinga-miraheze>	 RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy
[14:51:08] <icinga-miraheze>	 RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy
[14:51:29] <icinga-miraheze>	 RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy
[14:51:37] <icinga-miraheze>	 RECOVERY - cp2 HTTP 4xx/5xx ERROR Rate on cp2 is OK: OK - NGINX Error Rate is 4%
[14:52:03] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[14:52:09] <icinga-miraheze>	 RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online
[14:52:15] <icinga-miraheze>	 PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 3 minutes ago with 1 failures. Failed resources (up to 3 shown): File[/etc/logrotate.d/nginx]
[14:52:16] <icinga-miraheze>	 RECOVERY - cp3 HTTP 4xx/5xx ERROR Rate on cp3 is OK: OK - NGINX Error Rate is 3%
[14:56:10] <icinga-miraheze>	 RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[15:07:04] <icinga-miraheze>	 PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[15:08:10] <icinga-miraheze>	 PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[15:20:12] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjW3v
[15:20:14] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot 038b47f91 - BOT: Updating services config for wikis
[18:05:12] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjWGl
[18:05:13] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot 0377f5da5 - BOT: Updating services config for wikis
[18:15:12] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjWGr
[18:15:13] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot 03a0844e6 - BOT: Updating services config for wikis
[20:40:13] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjWnh
[20:40:15] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot 030675729 - BOT: Updating services config for wikis
[22:20:25] <Not-7290>	 [02miraheze/ManageWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjWCB
[22:20:26] <Not-7290>	 [02miraheze/ManageWiki] 07paladox 03d886285 - $previousClosed -> $closed
[22:22:50] <Not-7290>	 [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_32 [+0/-0/±2] 13https://git.io/fjWCu
[22:22:51] <Not-7290>	 [02miraheze/mediawiki] 07paladox 03b12058b - Update MW && Tabs
[22:33:28] <paladox>	 !log disable blogpage on flawlessfandomuserswiki - T4361
[22:33:31] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[22:44:13] <Zppix>	 I wonder if i could have ZppixBot auto display phab tasks like stashbot when a message includes T###
[22:44:32] <Zppix>	 But only do it in here since its phab module is miraheze specfic
[22:44:38] <Zppix>	 MacFan4000: any idea ^
[22:49:40] <MacFan4000>	 IDK
[22:49:49] <MacFan4000>	 I’m not that great in python
[22:50:48] <Zppix>	 MacFan4000: the phab module was done by code in wasnt it?
[22:50:57] <Zppix>	 MacFan4000: if so then that guy is MIA
[22:53:11] <JohnLewis>	 Mamma MIA :P
[22:54:14] <Zppix>	 JohnLewis: lmao
[22:56:13] * paladox wonders how JohnLewis came up with mamma mia :P
[22:59:11] <Zppix>	 paladox: he added mama infront of mia
[22:59:19] <paladox>	 heh
[23:17:56] <JohnLewis>	 :P
[23:18:01] <JohnLewis>	 that
[23:44:37] <MacFan4000>	 Zppix: yes it was
[23:47:50] <MacFan4000>	 Hmm, actually stashbot is python