[00:01:56] RECOVERY - cp8 Disk Space on cp8 is OK: DISK OK - free space: / 3944 MB (20% inode=93%); [07:12:37] PROBLEM - cp3 Stunnel Http for mw1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [07:15:59] RECOVERY - cp3 Stunnel Http for mw1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15350 bytes in 0.684 second response time [08:10:04] PROBLEM - puppet2 Disk Space on puppet2 is WARNING: DISK WARNING - free space: / 1417 MB (10% inode=87%); [08:29:20] RECOVERY - puppet2 Disk Space on puppet2 is OK: DISK OK - free space: / 2336 MB (17% inode=87%); [09:29:25] PROBLEM - cp3 Stunnel Http for test2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [09:29:54] PROBLEM - cp3 Stunnel Http for test1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [09:30:26] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 128.199.139.216/cpweb [09:33:40] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [09:33:49] PROBLEM - cp3 Stunnel Http for test2 on cp3 is WARNING: HTTP WARNING: HTTP/1.1 404 Not Found - 322 bytes in 0.004 second response time [09:34:04] RECOVERY - cp3 Stunnel Http for test1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15344 bytes in 1.353 second response time [09:34:29] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [09:41:28] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 10 backends are healthy [09:48:41] PROBLEM - cp3 Stunnel Http for test2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [09:53:11] PROBLEM - cp3 Stunnel Http for test2 on cp3 is WARNING: HTTP WARNING: HTTP/1.1 404 Not Found - 322 bytes in 0.003 second response time [10:04:44] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw2 [10:12:22] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 10 backends are healthy [10:20:08] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JvinM [10:20:10] [02miraheze/services] 07MirahezeSSLBot 03af53ae2 - BOT: Updating services config for wikis [10:38:44] PROBLEM - cp3 Stunnel Http for test2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [10:43:50] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 1 datacenter is down: 128.199.139.216/cpweb [10:45:20] PROBLEM - cp3 Stunnel Http for mw7 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [10:45:34] PROBLEM - cp3 HTTPS on cp3 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:46:20] PROBLEM - cp3 Disk Space on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [10:47:15] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [10:49:30] RECOVERY - cp3 Stunnel Http for mw7 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15316 bytes in 0.763 second response time [10:49:41] RECOVERY - cp3 HTTPS on cp3 is OK: HTTP OK: HTTP/1.1 301 Moved Permanently - 1569 bytes in 1.002 second response time [10:50:15] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 3125 MB (12% inode=94%); [10:51:01] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 10 backends are healthy [10:51:31] PROBLEM - cp3 Stunnel Http for test2 on cp3 is WARNING: HTTP WARNING: HTTP/1.1 404 Not Found - 322 bytes in 0.004 second response time [10:51:36] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [11:08:44] PROBLEM - puppet2 Disk Space on puppet2 is WARNING: DISK WARNING - free space: / 1420 MB (10% inode=87%); [11:22:41] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 2 backends are down. mw1 mw2 [11:23:19] PROBLEM - cp3 Stunnel Http for test1 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:23:52] PROBLEM - cp3 Stunnel Http for mw2 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [11:26:10] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 10 backends are healthy [11:26:32] RECOVERY - cp3 Stunnel Http for test1 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15344 bytes in 0.993 second response time [11:27:12] RECOVERY - cp3 Stunnel Http for mw2 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 15324 bytes in 2.021 second response time [12:56:21] PROBLEM - puppet2 Disk Space on puppet2 is CRITICAL: DISK CRITICAL - free space: / 790 MB (5% inode=87%); [15:13:48] Hi! How can I edit robots.txt on my miraheze wiki? [15:27:46] I'll be back in about 30mins... [15:35:19] PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:35:36] PROBLEM - phab1 Puppet on phab1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:35:50] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:35:51] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:35:57] PROBLEM - cp8 Puppet on cp8 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:00] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:17] PROBLEM - cloud1 Puppet on cloud1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:18] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:25] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:38] PROBLEM - mon1 Puppet on mon1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:42] PROBLEM - rdb1 Puppet on rdb1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:43] PROBLEM - cp6 Puppet on cp6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:47] PROBLEM - puppet2 Puppet on puppet2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:36:48] PROBLEM - mw6 Puppet on mw6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:07] PROBLEM - cp7 Puppet on cp7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:07] PROBLEM - mail1 Puppet on mail1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:09] PROBLEM - jobrunner1 Puppet on jobrunner1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:11] PROBLEM - mw4 Puppet on mw4 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:11] PROBLEM - bacula2 Puppet on bacula2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:12] PROBLEM - services1 Puppet on services1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:13] PROBLEM - lizardfs6 Puppet on lizardfs6 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:14] PROBLEM - test1 Puppet on test1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:14] PROBLEM - mw7 Puppet on mw7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:17] PROBLEM - test2 Puppet on test2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:43] PROBLEM - db7 Puppet on db7 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:43] PROBLEM - gluster1 Puppet on gluster1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:48] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:37:59] PROBLEM - services2 Puppet on services2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:38:08] PROBLEM - mw5 Puppet on mw5 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:40:38] Well, I was early... [15:45:56] Gustavfn you cannot edit robot.txt, though we have https://github.com/miraheze/mw-config/blob/master/LocalSettings.php#L2505 [15:45:57] [ mw-config/LocalSettings.php at master · miraheze/mw-config · GitHub ] - github.com [15:46:03] PROBLEM - rdb2 Puppet on rdb2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:47:08] paladox: Can I change that file...? [15:47:11] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:47:19] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:47:33] We provide that through ManageWiki, though it's restricted so i would have to edit for you. [15:47:41] PROBLEM - cloud2 Puppet on cloud2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:47:45] Oh, that would be great. [15:48:45] I see that "default robot policy" is grey:ed out. [15:49:04] I want to disallow all robots, google, etc. [15:49:19] yeh, do you have the config in mind? [15:49:25] e.g value i mean [15:50:03] Not sure what it could be. Robots.txt mostly contain "disallow." [15:50:54] Maybe "noindex,nofollow" from here: https://www.mediawiki.org/wiki/Manual:$wgDefaultRobotPolicy [15:50:55] [ Manual:$wgDefaultRobotPolicy - MediaWiki ] - www.mediawiki.org [15:51:54] ok, i'll set that [15:51:57] Gustavfn which wiki? [15:52:21] paladox: Femman. [15:52:59] done [15:53:17] Thx. [15:53:51] Can't see the change. [15:54:25] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JviB4 [15:54:27] [02miraheze/puppet] 07paladox 03d77b080 - Update init.pp [15:54:31] RECOVERY - puppet2 Disk Space on puppet2 is OK: DISK OK - free space: / 7407 MB (55% inode=87%); [15:54:49] Gustavfn i did it on https://femman.miraheze.org/wiki/Special:ManageWiki/settings [15:54:49] [ Behörighetsfel - Femman ] - femman.miraheze.org [15:55:17] "Default Robot Policy" has changed but robots.txt has not. [15:55:40] RECOVERY - cloud1 Puppet on cloud1 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [15:55:43] Maybe nginx has cached that file. [15:56:07] RECOVERY - puppet2 Puppet on puppet2 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [15:57:43] Gustavfn url to this file? [15:57:48] https://femman.miraheze.org/robots.txt [15:58:26] that file comes from https://github.com/miraheze/puppet/blob/master/modules/mediawiki/files/robots.php [15:58:26] [ puppet/robots.php at master · miraheze/puppet · GitHub ] - github.com [15:59:23] Oh. It doesn't use "Default Robot Policy" [15:59:25] https://github.com/wikimedia/mediawiki/blob/78bc3ae2557a1f90d9bff11688dff76bf5642efe/includes/page/Article.php#L990 [15:59:25] [ mediawiki/Article.php at 78bc3ae2557a1f90d9bff11688dff76bf5642efe · wikimedia/mediawiki · GitHub ] - github.com [15:59:51] Is it in HTML? [16:00:07] Gustavfn yes [16:00:16] https://www.mediawiki.org/wiki/Manual:$wgDefaultRobotPolicy [16:00:16] [ Manual:$wgDefaultRobotPolicy - MediaWiki ] - www.mediawiki.org [16:00:42] [16:01:36] Oh! [16:02:59] Can't find it in the source of https://femman.miraheze.org/wiki/Huvudsida [16:03:00] [ Femman ] - femman.miraheze.org [16:03:14] RECOVERY - bacula2 Puppet on bacula2 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [16:03:17] RECOVERY - db7 Puppet on db7 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [16:03:22] RECOVERY - mail1 Puppet on mail1 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [16:03:49] RECOVERY - gluster1 Puppet on gluster1 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [16:03:59] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:03:59] RECOVERY - mw5 Puppet on mw5 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [16:04:01] RECOVERY - services2 Puppet on services2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:04:06] !log increzse puppet2 disk by 10g [16:04:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [16:04:21] RECOVERY - cloud2 Puppet on cloud2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:04:34] RECOVERY - phab1 Puppet on phab1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:04:41] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:04:41] Is miraheze on some kind of cloud? [16:04:43] RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:09] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:05:13] RECOVERY - cp8 Puppet on cp8 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [16:05:13] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:05:22] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:26] RECOVERY - rdb2 Puppet on rdb2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:26] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:45] RECOVERY - mw6 Puppet on mw6 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:45] RECOVERY - mon1 Puppet on mon1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:45] RECOVERY - rdb1 Puppet on rdb1 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [16:05:51] RECOVERY - cp6 Puppet on cp6 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:05:53] RECOVERY - mw4 Puppet on mw4 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:06:29] RECOVERY - jobrunner1 Puppet on jobrunner1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:06:38] RECOVERY - cp7 Puppet on cp7 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [16:06:41] RECOVERY - lizardfs6 Puppet on lizardfs6 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:06:41] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:06:41] RECOVERY - mw7 Puppet on mw7 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [16:06:41] RECOVERY - test2 Puppet on test2 is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [16:06:43] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [16:07:02] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [16:07:07] Gustavfn: paladox can correct me if i am wrong, but we are on cloud hosts [16:07:26] well we're calling our 2 dedicated servers the cloud. [16:07:33] :) [16:09:10] Could you code a setting which robots.php uses to disallow stuff...? Maybe a setting for disallowing all or what is in it now. [16:10:00] Do you know why noindex,nofollow isn't on "Huvudsida" (it's Main_Page in English, I think.) [16:12:53] Gustavfn it should be in the html [16:12:55] i checked. [16:13:36] It's in https://femman.miraheze.org/wiki/MediaWiki:Common.css but not https://femman.miraheze.org/wiki/Huvudsida [16:13:37] [ Behörighetsfel - Femman ] - femman.miraheze.org [16:13:37] [ Femman ] - femman.miraheze.org [16:19:03] i see [16:19:04] [16:19:06] on that page [16:19:13] Or read robot code from /wiki/MediaWiki:Robots.txt and if there's none default to what's in robots.php [16:19:14] Oh. [16:19:39] I see it now! Thanks! [16:25:29] If I want a Facebook like button on my site I have to register a site or something on Facebook right? [16:25:31] RECOVERY - services1 Puppet on services1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [16:44:20] What's your totalt cost per month? [16:44:52] total [16:46:32] .mh Finance [16:46:32] https://meta.miraheze.org/wiki/Finance [16:46:41] Gustavfn: ^ see that [16:53:07] I see that you are well financed. [16:54:39] Bye! [17:37:43] well not exactly but ok [20:50:10] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2648 MB (10% inode=94%); [21:20:45] PROBLEM - cp8 Disk Space on cp8 is WARNING: DISK WARNING - free space: / 2110 MB (10% inode=93%);