[00:03:43] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 2604:180:0:33b::2/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [00:04:49] 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 [00:08:52] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:09:55] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [00:17:06] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 2 datacenters are down: 107.191.126.23/cpweb, 128.199.139.216/cpweb [00:17:50] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 2 datacenters are down: 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb [00:19:03] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [00:19:46] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [01:10:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9gv [01:10:09] [02miraheze/services] 07MirahezeSSLBot 031d3a5f0 - BOT: Updating services config for wikis [01:33:59] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [01:41:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [01:53:53] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [02:03:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:05:07] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9gF [02:05:09] [02miraheze/services] 07MirahezeSSLBot 03c3124aa - BOT: Updating services config for wikis [02:34:06] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [02:42:27] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [02:42:35] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 1 datacenter is down: 128.199.139.216/cpweb [02:44:30] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [02:50:39] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw3 [02:51:05] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 3 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb [02:52:36] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 6 backends are healthy [02:54:22] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Service[ufw] [02:57:03] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [03:02:24] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [03:43:55] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[ssh],Package[exim4],Service[postfix],Exec[ufw-logging-low] [03:51:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [04:23:57] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 2 minutes ago with 2 failures. Failed resources (up to 3 shown): Exec[ufw-enable],Exec[ops_ensure_members] [04:41:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [04:53:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[ssh],Package[exim4],Service[postfix],Exec[ufw-logging-low] [05:03:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:23:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [05:26:08] PROBLEM - cp3 Disk Space on cp3 is CRITICAL: DISK CRITICAL - free space: / 1446 MB (5% inode=94%); [05:28:08] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 1446 MB (6% inode=94%); [05:30:11] PROBLEM - cp3 Disk Space on cp3 is CRITICAL: DISK CRITICAL - free space: / 1444 MB (5% inode=94%); [05:31:52] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:26:12] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2465 MB (10% inode=94%); [06:35:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [06:41:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [07:06:17] PROBLEM - cp3 Disk Space on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [07:08:13] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2434 MB (10% inode=94%); [07:33:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ops_ensure_members] [07:41:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [08:53:52] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [09:03:51] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [09:34:02] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 1 minute ago with 1 failures. Failed resources (up to 3 shown): Exec[ops_ensure_members] [09:41:53] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [09:45:56] Hihihihihi [09:46:01] Byr [09:46:04] bye [11:33:51] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 1 failures. Last run 2 minutes ago with 1 failures. Failed resources (up to 3 shown): Exec[ops_ensure_members] [11:41:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [13:03:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown): Package[openssh-server],Service[ssh],Package[exim4],Service[postfix] [13:11:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:23:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [14:33:53] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:37:14] PROBLEM - cyberlaw.ccdcoe.org - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'cyberlaw.ccdcoe.org' expires in 15 day(s) (Fri 27 Dec 2019 02:33:35 PM GMT +0000). [14:37:27] [02miraheze/ssl] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9S0 [14:37:29] [02miraheze/ssl] 07MirahezeSSLBot 03719cb70 - Bot: Update SSL cert for cyberlaw.ccdcoe.org [14:43:13] RECOVERY - cyberlaw.ccdcoe.org - LetsEncrypt on sslhost is OK: OK - Certificate 'cyberlaw.ccdcoe.org' will expire on Tue 10 Mar 2020 01:37:21 PM GMT +0000. [14:43:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown): Service[prometheus-node-exporter],Service[nagios-nrpe-server],Package[openssh-client],Package[openssh-server] [14:51:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [15:05:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 3 minutes ago with 11 failures. Failed resources (up to 3 shown): Service[ssh],Package[exim4],Service[postfix],Exec[ufw-logging-low] [15:11:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [15:39:50] PROBLEM - db4 Disk Space on db4 is CRITICAL: DISK CRITICAL - free space: / 21975 MB (5% inode=96%); [16:06:15] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9Qv [16:06:16] [02miraheze/puppet] 07paladox 03295cb5a - Add google.com to our iframe whitelist Bug: T4978 [16:09:51] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9Qt [16:09:53] [02miraheze/puppet] 07paladox 0301dc650 - Revert "Add google.com to our iframe whitelist" This reverts commit 295cb5a3d72e6ac640d7299e1280874a6665c9f8. [16:12:17] paladox: ? [16:12:23] ? [16:12:45] paladox: why we taking it out? [16:12:56] See my commit above [16:15:11] paladox: ah k [16:15:27] Weve got a few other whitelist requests [16:23:50] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [16:29:03] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/Je9QF [16:29:05] [02miraheze/puppet] 07paladox 032dda2da - vanish: Remove data schemas from CSP It's not recommended according to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-src [16:29:05] [ CSP: frame-src - HTTP | MDN ] - developer.mozilla.org [16:29:06] [02puppet] 07paladox created branch 03paladox-patch-4 - 13https://git.io/vbiAS [16:29:09] [02puppet] 07paladox opened pull request 03#1160: vanish: Remove data schemas from CSP - 13https://git.io/Je9Qb [16:34:46] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je97O [16:34:48] [02miraheze/puppet] 07paladox 03e68dd2a - varnish: Change order in CSP [16:35:41] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je97n [16:35:43] [02miraheze/puppet] 07paladox 03698049a - Revert "varnish: Change order in CSP" This reverts commit e68dd2a3ba7c8dd9240dda914d8bfbb462bf3bdc. [16:51:50] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [16:54:23] PROBLEM - prfm.wiki - LetsEncrypt on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [17:14:09] RECOVERY - prfm.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'prfm.wiki' will expire on Wed 29 Jan 2020 01:07:14 PM GMT +0000. [17:18:08] PROBLEM - prfm.wiki - LetsEncrypt on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [19:09:01] Hello TLWXPUser! If you have any questions, feel free to ask and someone should answer soon. [19:09:15] xpuser can into irc :D [19:17:21] Hello PF94! If you have any questions, feel free to ask and someone should answer soon. [19:17:49] Hey PF94 [19:18:06] hi i'm just waiting for my friend's wiki to be appected [19:18:26] Btw, What's is the approximate eta for a wiki to be accepted [19:18:38] as i'm slowly, ***slowly*** moving from shoutwiki (which is dormant) to miraheze [19:18:39] "What's is" am so dumb [19:18:43] When someone does it [19:18:47] btw what's the discord [19:18:50] I can look [19:18:59] PF94: discord.is/miraheze [19:19:13] ty [19:19:48] ping? [19:21:19] Wiki requests answered and created! [19:22:07] Woah, Thanks kindly stranger! [19:22:28] so, hey [19:22:30] just to avoid confusion [19:22:32] No problem [19:22:34] on miraheze, i'mD reamIsland [19:22:38] DreamIsland* [19:23:37] !log sudo -u www-data php /srv/mediawiki/w/extensions/CreateWiki/maintenance/renameWiki.php --wiki=loginwiki --rename wikiwiki xyssponwiki paladox [19:23:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:24:45] !log create database wikiwiki; (db4) [19:24:50] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 22291 MB (6% inode=96%); [19:24:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:25:21] interesting [19:26:23] Dude i like miraheze ways to administrate a wiki more since shoutwiki did have nothing compared to miraheze [19:26:28] nice, i verifeid [19:26:30] I give big thanks to the devs [19:26:51] RECOVERY - db4 Disk Space on db4 is OK: DISK OK - free space: / 40714 MB (11% inode=96%); [19:27:28] !log MatomoAnalyticsHooks::wikiCreation( 'xyssponwiki' ); (mw1) [19:27:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [19:29:24] anyways [19:29:37] so, i moved my wiki from shoutwiki to miraheze as there was a vandalism problem going on [19:29:55] and we were trying to move to another host, and the news of another host kinda disappeared [19:32:59] [02ssl] 07Pix1234 opened pull request 03#243: add wiki.xysspon.com cert - 13https://git.io/Je9Nd [19:35:41] PF94: ah, any issues then just pop into #miraheze-cvt and well be happy to help combat them [19:36:03] wow, how many irc channels do you have [19:36:09] PF94: enough :P [19:36:19] Hello XPUser! If you have any questions, feel free to ask and someone should answer soon. [19:36:29] oh hey xpuser [19:36:32] If i am aorund you can just ping me and i can handle it as im apart of CVT PF94 [19:36:52] btw [19:36:57] xpuser may connect as "xpuser" or "tlwxpuser" [19:37:07] and his wifi crashed, oof. [19:37:29] .add_user tlwxpuser [19:37:33] .help .add_user [19:37:37] .help add_user [19:37:37] huh? [19:37:46] im making it so it doesnt welcome him anymore [19:37:58] .ping [19:37:58] Pong! [19:38:01] .help [19:38:02] I've posted a list of my commands at https://clbin.com/tRVeK - You can see more info about any of these commands by doing .help (e.g. .help time) [19:38:13] hey xpuser [19:38:13] [02ssl] 07Reception123 commented on pull request 03#243: add wiki.xysspon.com cert - 13https://git.io/Je9Nh [19:38:22] mind if you add me as sysop on the new geekia? [19:38:32] ZppixBot: the command is "add_known" i think [19:38:36] Zppix: ^ [19:38:37] k6ka: it is [19:38:37] [02ssl] 07Reception123 closed pull request 03#243: add wiki.xysspon.com cert - 13https://git.io/Je9Nd [19:38:39] [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/Je9Ae [19:38:40] [02miraheze/ssl] 07Pix1234 031a00b69 - add wiki.xysspon.com cert (#243) * Create wiki.xysspon.com.crt * Update certs.yaml [19:38:41] i rarely use the command :P [19:38:42] damn you Tab [19:38:54] .add_known tlwxpuser [19:38:54] tlwxpuser is already added to known users list of channel #miraheze [19:39:17] btw [19:39:22] i noticed that the most popular wikis [19:39:40] are like Atrocious (insert popular site here) wikis [19:40:02] we host all the tropes [19:40:17] i'm sure most of these come from, wikia? [19:40:20] yes [19:40:34] a lot of the wikis are ones transfering from wika [19:40:46] i was planning to move the nintendogs wikia, but apparantly it's too hard since i'm not sure how do i move the userbase without having my fandom account terminated [19:40:52] .t paladox [19:40:53] 2019-12-11 - 19:40:52GMT [19:41:31] oh, i've also realized i've been on this irc before, under the name of dreamisland back in jan 6 2019 [19:41:35] big oof. [19:42:28] wait, why can't i connect to miraheze anymore [19:42:34] is it ethier windows 10 or firefox? [19:42:42] PF94: whats the error? [19:42:52] miraheze loads slower than shoutwiki [19:43:04] PF94: that happens sometimes it should resolve shortly [19:43:18] btw a few days ago [19:43:23] someone else opened a wiki with a simillar domain [19:43:41] can't post the links, since i'm avoiding to look like if i'm advertising [19:43:55] PROBLEM - cp4 Stunnel Http for mw3 on cp4 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:44:05] PF94: drop Zppix a pm about it and well have a look [19:44:09] oof, even the bots are acting up [19:44:19] yeah pm me if you want [19:44:25] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [19:44:50] btw, so, i'm going to beta test my wiki [19:45:52] RECOVERY - cp4 Stunnel Http for mw3 on cp4 is OK: HTTP OK: HTTP/1.1 200 OK - 24662 bytes in 1.646 second response time [19:46:23] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24662 bytes in 1.586 second response time [19:47:23] hey uh, is there any way to remove the modern mediawiki alarms? [19:47:32] they're known to act up with older themes (such as nostalgia) [19:48:25] wait, that's weird, they don't shot up [19:48:29] show*** aa [19:50:08] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9A3 [19:50:09] [02miraheze/services] 07MirahezeSSLBot 037fd7410 - BOT: Updating services config for wikis [19:50:27] so, i hope the servers get better [19:52:40] PF94: right now the servers are as good as we can get at the moment we are working on getting more infastructure though [19:52:48] nice [19:54:39] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [20:02:30] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [20:30:08] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je9xZ [20:30:10] [02miraheze/services] 07MirahezeSSLBot 032836747 - BOT: Updating services config for wikis [20:43:21] * hispano76 greeting [20:43:47] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 2 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [20:45:52] Hey hispano76 [20:46:49] hi RhinosF1 :) [20:47:49] How is hispano76 [20:49:40] RhinosF1: Perfect! [20:49:53] :) [20:50:29] Nice to hear! [20:51:43] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [21:05:38] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Service[ssh],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [21:13:38] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [21:26:26] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 40290 MB (10% inode=96%); [21:35:19] test [22:13:08] RECOVERY - prfm.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.prfm.xyz' will expire on Thu 10 Dec 2020 10:05:02 PM GMT +0000. [22:24:58] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [22:32:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:35:31] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 132 failures. Last run 2 minutes ago with 132 failures. Failed resources (up to 3 shown) [22:36:00] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 3 minutes ago with 13 failures. Failed resources (up to 3 shown) [22:36:05] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 3 minutes ago with 3 failures. Failed resources (up to 3 shown) [22:36:18] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 3 minutes ago with 13 failures. Failed resources (up to 3 shown) [22:36:21] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 162 failures. Last run 3 minutes ago with 162 failures. Failed resources (up to 3 shown): File[www.evanswiki.org],File[www.evanswiki.org_private],File[electowiki.org],File[electowiki.org_private] [22:44:25] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [22:44:32] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:44:50] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:45:29] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:46:25] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [22:55:00] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [23:02:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [23:14:58] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 8 failures. Last run 3 minutes ago with 8 failures. Failed resources (up to 3 shown): Exec[ufw-logging-low],Exec[ufw-allow-tcp-from-any-to-any-port-22],Exec[ufw-allow-tcp-from-any-to-any-port-5666],Exec[ufw-allow-tcp-from-185.52.3.121-to-any-port-9100] [23:22:58] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [23:39:51] how do i uh, enable comments on my wiki [23:43:51] PF94: hum, see Special:ManageWiki/extensions your wiki ? [23:44:42] yeah [23:44:43] i enabled it [23:44:47] i don't see them below my pages [23:46:10] Have you seen how it is configured in the respective extension in Mediawiki? One is to add I think [23:47:38] PF94: ? [23:48:08] wait [23:48:12] so i have to add to each article [23:48:52] yes [23:49:22] I'm not sure if there can be another way. [23:52:28] paladox: couldn't use the PageNotice extension to add on pages that exist with #ifexist? [23:55:32] :thinking: [23:56:10] wait, how do i even use PageNotice [23:56:43] hispano76 i'm not sure :( [23:56:48] Haven't used the extension [23:57:06] https://www.mediawiki.org/wiki/Extension:PageNotice [23:57:06] [ Extension:PageNotice - MediaWiki ] - www.mediawiki.org [23:57:47] ah fiddlesticks, well, it doesn't seem to be on Special:ManageWiki