[00:03:26] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTtu [00:03:28] [02miraheze/puppet] 07paladox 03ecd6830 - Update client.pp [00:06:30] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTt1 [00:06:31] [02miraheze/puppet] 07paladox 03f580b1e - puppetmaster: symlink some files from /usr/bin/** to /opt [00:11:43] RECOVERY - test1 Puppet on test1 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [00:15:43] PROBLEM - test1 Puppet on test1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [00:19:12] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTqd [00:19:13] [02miraheze/puppet] 07paladox 0398691e7 - Disable test1 puppetmaster (no longer one) [00:25:38] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTmR [00:25:40] [02miraheze/puppet] 07paladox 03e4988a8 - Update v6.pp [00:26:39] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTm0 [00:26:40] [02miraheze/puppet] 07paladox 034b3e5bd - fix syntax [00:27:28] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTmz [00:27:29] [02miraheze/puppet] 07paladox 033b2e5f1 - Update client.pp [00:29:42] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTma [00:29:43] [02miraheze/puppet] 07paladox 0356f17f6 - Increase puppet server heap to 250mb [00:30:37] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTmw [00:30:39] [02miraheze/puppet] 07paladox 036e0b2b2 - Update init.pp [00:49:54] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTYJ [00:49:56] [02miraheze/puppet] 07paladox 0342c02cd - Update site.pp [01:23:38] test [01:26:06] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTYN [01:26:08] [02miraheze/puppet] 07paladox 0388f91f1 - Update puppet_6.conf.erb [01:32:17] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTOk [01:32:19] [02miraheze/puppet] 07paladox 03d0dd9c2 - Update v6.pp [01:41:48] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTOl [01:41:50] [02miraheze/puppet] 07paladox 0396f5ecd - set puppetserver_heap_heap to 320m for puppet1 [02:01:22] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:03:22] PROBLEM - misc3 Puppet on misc3 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [02:03:23] known ^^ [02:03:56] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTO9 [02:03:58] [02miraheze/puppet] 07paladox 03ab5918a - Update check_puppet_run.erb [02:05:19] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTO7 [02:05:21] [02miraheze/puppet] 07paladox 03b3df99b - Update check_puppet_run.erb [02:05:53] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [02:07:52] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTOF [02:07:54] [02miraheze/puppet] 07paladox 03e3f7509 - misc3: upgrade puppet to v6 [02:11:44] PROBLEM - misc3 Puppet on misc3 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [02:11:45] Hello sparr! If you have any questions feel free to ask and someone should answer soon. [02:12:02] hello there! someone suggested that I consider miraheze in my quest to start a wiki [02:13:44] hi [02:15:00] sparr yep, see https://meta.miraheze.org [02:15:01] Title: [ Meta ] - meta.miraheze.org [02:15:11] where you can find more info on all the things we provide :) [02:15:44] !log depool mw1 [02:15:47] uh [02:15:48] wrong one [02:15:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [02:16:00] oh well might as well do that one then [02:17:10] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhT3s [02:17:12] [02miraheze/puppet] 07paladox 03c87b32b - mw1: Upgrade to puppet v6 [02:18:35] PROBLEM - mw1 Puppet on mw1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [02:22:35] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhT38 [02:22:36] [02miraheze/puppet] 07paladox 03c8af5db - Update puppet1.yaml [02:31:17] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [02:34:01] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhT3K [02:34:02] [02miraheze/puppet] 07paladox 03e66173b - Update puppet_6.conf.erb [02:35:41] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [02:36:53] !log repool mw1 [02:36:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [02:37:31] I have questions about how I might accomplish some things with the default extensions here. Is that on topic here, or should I try #mediawiki? [02:38:30] sparr if the question is about what extensions we have / or what default ones we have then here is fine :) [02:38:42] ok [02:39:30] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhT3P [02:39:31] [02miraheze/puppet] 07paladox 037233a7a - mw2: Upgrade to puppet v6 [02:40:11] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Catalog fetch fail. Either compilation failed or puppetmaster has issues [02:42:11] PROBLEM - mw2 Puppet on mw2 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [02:44:11] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [02:44:52] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhT3M [02:44:54] [02miraheze/puppet] 07paladox 032070f83 - mw3: Upgrade to puppet v6 [02:45:48] how do I supply the ssl cert for a custom domain? [02:46:25] PROBLEM - mw3 Puppet on mw3 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [02:49:15] sparr if it's a public cert then it can be done through phabricator (phab.miraheze.org) for the private cert, you can send it through email. [02:49:24] JohnLewis ^^ (am i correct in that statement?) [02:49:44] huh? [02:50:23] there's only public certs [02:50:23] JohnLewis see sp.arr question above. [02:50:25] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [02:50:38] ah, ok. [02:52:35] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhT3j [02:52:36] [02miraheze/puppet] 07paladox 030becaa6 - misc2: Upgrade puppet to v6 [02:54:11] PROBLEM - misc2 Puppet on misc2 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [02:58:11] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [02:58:59] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTst [02:59:00] [02miraheze/puppet] 07paladox 034e866e9 - ns1: Upgrade puppet to v6 [03:01:13] PROBLEM - ns1 Puppet on ns1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [03:04:07] gonna bite the bullet and give this a try. been wanting to start this wiki for about a decade now :) [03:04:26] (actually been hoping someone else would start it, but you can't always get what you want) [03:04:47] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTsn [03:04:49] [02miraheze/puppet] 07paladox 0340a7bd9 - lizardfs1: Upgrade puppet to v6 [03:05:13] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:05:40] PROBLEM - lizardfs1 Puppet on lizardfs1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [03:09:40] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [03:09:58] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTsB [03:10:00] [02miraheze/puppet] 07paladox 03171d7fd - lizardfs2: Upgrade puppet to v6 [03:12:07] PROBLEM - lizardfs2 Puppet on lizardfs2 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [03:17:15] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTsV [03:17:17] [02miraheze/puppet] 07paladox 035506dc9 - bacula1: Upgrade puppet to v6 [03:18:07] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:19:32] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [03:23:31] PROBLEM - bacula1 Puppet on bacula1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [03:25:32] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [03:26:34] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTs1 [03:26:35] [02miraheze/puppet] 07paladox 033f5603c - misc4: Upgrade puppet to v6 [03:27:07] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [03:31:07] PROBLEM - misc4 Puppet on misc4 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [03:47:07] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [03:47:23] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGI [03:47:25] [02miraheze/puppet] 07paladox 0383d8d30 - db4: Upgrade puppet to v6 [03:48:34] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [03:52:34] PROBLEM - db4 Puppet on db4 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [04:05:53] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTG0 [04:05:54] [02miraheze/puppet] 07paladox 03c865380 - misc1: Upgrade puppet to v6 [04:06:34] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:08:20] PROBLEM - misc1 Puppet on misc1 is UNKNOWN: UNKNOWN: Failed to check. Reason is: no_summary_file [04:11:43] PROBLEM - test1 Puppet on test1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:44] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:47] PROBLEM - mw3 JobChron Service on mw3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:48] PROBLEM - misc3 Parsoid on misc3 is CRITICAL: connect to address 127.0.0.2 and port 8142: Connection refused [04:11:49] PROBLEM - misc4 Disk Space on misc4 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:50] PROBLEM - mw2 Current Load on mw2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:52] PROBLEM - misc3 Current Load on misc3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:55] PROBLEM - misc3 Restbase on misc3 is CRITICAL: connect to address 127.0.0.2 and port 7231: Connection refused [04:11:56] PROBLEM - lizardfs1 Current Load on lizardfs1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:11:57] PROBLEM - test1 php7.2-fpm on test1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:01] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:03] PROBLEM - misc4 Current Load on misc4 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:14] PROBLEM - mw3 JobRunner Service on mw3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:14] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:17] PROBLEM - misc3 Disk Space on misc3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:17] PROBLEM - lizardfs2 Disk Space on lizardfs2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:18] PROBLEM - lizardfs2 Lizardfs Chunkserver Port on lizardfs2 is CRITICAL: connect to address 127.0.0.2 and port 9422: Connection refused [04:12:18] PROBLEM - lizardfs1 Lizardfs Chunkserver Port on lizardfs1 is CRITICAL: connect to address 127.0.0.2 and port 9422: Connection refused [04:12:21] PROBLEM - puppet1 Disk Space on puppet1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:25] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:27] PROBLEM - misc2 Disk Space on misc2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:27] PROBLEM - misc2 Prometheus on misc2 is CRITICAL: connect to address 127.0.0.2 and port 9090: Connection refused [04:12:34] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:35] PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:38] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:40] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:41] PROBLEM - mw1 MirahezeRenewSsl on mw1 is CRITICAL: connect to address 127.0.0.2 and port 5000: Connection refused [04:12:48] PROBLEM - misc4 lizard.miraheze.org HTTPS on misc4 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 200 OK [04:12:53] PROBLEM - mw2 php7.2-fpm on mw2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:12:59] PROBLEM - lizardfs2 Current Load on lizardfs2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:00] PROBLEM - puppet1 Current Load on puppet1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:00] PROBLEM - mw1 Current Load on mw1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:01] PROBLEM - mw3 php7.2-fpm on mw3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:03] PROBLEM - misc4 Lizardfs Master Port 3 on misc4 is CRITICAL: connect to address 127.0.0.2 and port 9421: Connection refused [04:13:03] PROBLEM - ns1 Disk Space on ns1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:05] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:06] PROBLEM - test1 Current Load on test1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:10] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:14] PROBLEM - mw2 Disk Space on mw2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:18] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:24] PROBLEM - misc4 phd on misc4 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:25] PROBLEM - misc4 Lizardfs Master Port 2 on misc4 is CRITICAL: connect to address 127.0.0.2 and port 9420: Connection refused [04:13:26] PROBLEM - mw1 php7.2-fpm on mw1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:26] PROBLEM - misc2 Redis Process on misc2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:32] PROBLEM - test1 Disk Space on test1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:34] PROBLEM - misc4 phab.miraheze.wiki HTTPS on misc4 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 404 Not Found [04:13:36] PROBLEM - misc2 Current Load on misc2 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:36] PROBLEM - lizardfs1 Disk Space on lizardfs1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:38] PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:41] PROBLEM - ns1 Current Load on ns1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:43] PROBLEM - mw3 Disk Space on mw3 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:43] PROBLEM - misc4 Lizardfs Master Port 1 on misc4 is CRITICAL: connect to address 127.0.0.2 and port 9419: Connection refused [04:13:43] PROBLEM - mw1 Disk Space on mw1 is CRITICAL: CHECK_NRPE: Error - Could not connect to 127.0.0.2: Connection reset by peer [04:13:55] bah [04:22:16] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+1/-0/±0] 13https://git.io/fhTGX [04:22:18] [02miraheze/puppet] 07paladox 03afd0dab - Add new virtual_ip_address facter [04:23:31] [02puppet] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbiAS [04:23:32] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTGy [04:23:34] [02miraheze/puppet] 07paladox 030b4b975 - monitoring: Use new virtual_ip_address instead of $::ipaddress [04:23:35] [02puppet] 07paladox opened pull request 03#951: monitoring: Use new virtual_ip_address instead of $::ipaddress - 13https://git.io/fhTGS [04:23:58] [02puppet] 07paladox closed pull request 03#951: monitoring: Use new virtual_ip_address instead of $::ipaddress - 13https://git.io/fhTGS [04:24:00] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGH [04:24:01] [02miraheze/puppet] 07paladox 035a11feb - monitoring: Use new virtual_ip_address instead of $::ipaddress (#951) [04:24:03] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [04:24:04] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [04:24:18] [02puppet] 07paladox closed pull request 03#946: create a new defined type monitoring::wiki - 13https://git.io/fhfx4 [04:24:19] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+1/-0/±0] 13https://git.io/fhTGQ [04:24:21] [02miraheze/puppet] 07mutante 033d4f622 - create a new defined type monitoring::wiki (#946) This is a new defined type to make it simple to add monitoring for Miraheze user wikis. The only mandatory parameter will be the name of any Miraheze wiki. In the simplest form just a one line will be needed such as: monitoring::wiki { 's23': } to add an Icinga2 monitoring check for [04:24:21] https://s23.miraheze.org/wiki/Main_Page The test page defaults to Main_Page but can be adjusted. Protocol and domain default to https and miraheze.org but can be adjusted. The HTTP version defaults to 1.1 and can be changed to 2 if needed. Note that "upcase" from stdlib is used to get the uppercase "HTTPS" in the Icinga monitoring output. Because this is a defined type it can be used with an array to iterate over. So [04:24:21] the idea is to follow-up with a profile class that uses this and simply has an array with names of wikis and adding monitoring will be super easy. [04:24:23] Title: [ s23 ] - s23.miraheze.org [04:25:32] mutante: does that monitoring check pass/fail based on content or http code or something else? [04:25:53] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown) [04:28:03] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [04:31:20] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGF [04:31:22] [02miraheze/puppet] 07paladox 0346a7b7e - Update virtual_processor_count.rb [04:31:33] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGb [04:31:34] [02miraheze/puppet] 07paladox 03249db58 - Update virtual_ip_address.rb [04:31:47] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [04:32:44] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGN [04:32:45] [02miraheze/puppet] 07paladox 030be9ae2 - Update virtual_ip_address.rb [04:33:33] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGx [04:33:34] [02miraheze/puppet] 07paladox 03c2720fb - Update virtual_ip_address.rb [04:33:50] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTGp [04:33:51] [02miraheze/puppet] 07paladox 03d21d271 - Update virtual_processor_count.rb [04:34:39] PROBLEM - lizardfs2 Puppet on lizardfs2 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:03] PROBLEM - ns1 Current Load on ns1 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:11] PROBLEM - misc2 Current Load on misc2 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:11] PROBLEM - lizardfs1 Disk Space on lizardfs1 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:12] PROBLEM - lizardfs2 Current Load on lizardfs2 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:23] PROBLEM - lizardfs1 Puppet on lizardfs1 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:25] PROBLEM - misc2 Redis Process on misc2 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:29] PROBLEM - ns1 Disk Space on ns1 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:29] PROBLEM - misc3 Current Load on misc3 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:43] PROBLEM - misc2 Puppet on misc2 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:46] PROBLEM - lizardfs1 Current Load on lizardfs1 is WARNING: Could not resolve hostname : No address associated with hostname [04:35:51] RECOVERY - puppet1 Disk Space on puppet1 is OK: DISK OK - free space: / 58406 MB (95% inode=99%); [04:35:57] PROBLEM - misc2 Disk Space on misc2 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:02] PROBLEM - misc3 Disk Space on misc3 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:07] PROBLEM - lizardfs2 Disk Space on lizardfs2 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:16] RECOVERY - puppet1 Current Load on puppet1 is OK: OK - load average: 1.60, 1.02, 0.92 [04:36:16] PROBLEM - misc3 Puppet on misc3 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:19] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:36:28] PROBLEM - ns1 GDNSD Datacenters on ns1 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:32] PROBLEM - ns1 Puppet on ns1 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:37] PROBLEM - misc3 Electron on misc3 is CRITICAL: TCP CRITICAL - Invalid hostname, address or socket [04:36:42] PROBLEM - Host lizardfs2 is DOWN: check_ping: Invalid hostname/address - Usage:check_ping -H -w ,% -c ,% [-p packets] [-t timeout] [-4 [04:36:43] PROBLEM - bacula1 Puppet on bacula1 is WARNING: Could not resolve hostname : No address associated with hostname [04:36:51] RECOVERY - mw2 php7.2-fpm on mw2 is OK: PROCS OK: 6 processes with command name 'php-fpm7.2' [04:36:53] RECOVERY - mw2 Disk Space on mw2 is OK: DISK OK - free space: / 57170 MB (74% inode=99%); [04:36:53] PROBLEM - db4 MySQL on db4 is UNKNOWN: check_mysql: Invalid hostname/address - Usage: check_mysql [-d database] [-H host] [-P port] [-s socket] [-u user] [-p password] [-S] [-l] [-a cert] [-k key] [-C ca-cert] [-D ca-dir] [-L ciphers] [-f optfile] [-g group] [04:36:54] RECOVERY - mw1 Disk Space on mw1 is OK: DISK OK - free space: / 52865 MB (68% inode=98%); [04:36:55] RECOVERY - misc2 Current Load on misc2 is OK: OK - load average: 0.59, 0.31, 0.22 [04:36:59] RECOVERY - mw3 Disk Space on mw3 is OK: DISK OK - free space: / 58613 MB (76% inode=99%); [04:37:02] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [04:37:03] PROBLEM - test1 Puppet on test1 is UNKNOWN: NRPE: Unable to read output [04:37:05] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [04:37:06] RECOVERY - lizardfs1 Lizardfs Chunkserver Port on lizardfs1 is OK: TCP OK - 0.001 second response time on 81.4.101.157 port 9422 [04:37:07] RECOVERY - misc4 Lizardfs Master Port 1 on misc4 is OK: TCP OK - 0.001 second response time on 185.52.3.121 port 9419 [04:37:11] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [04:37:13] PROBLEM - bacula1 Bacula Private Git on bacula1 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:13] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 0.16, 0.05, 0.02 [04:37:16] RECOVERY - misc3 Current Load on misc3 is OK: OK - load average: 0.09, 0.05, 0.01 [04:37:17] RECOVERY - test1 Disk Space on test1 is OK: DISK OK - free space: / 15448 MB (37% inode=98%); [04:37:17] PROBLEM - bacula1 Current Load on bacula1 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:20] RECOVERY - misc3 Restbase on misc3 is OK: TCP OK - 0.001 second response time on 185.52.1.144 port 7231 [04:37:20] PROBLEM - bacula1 Bacula Databases db4 on bacula1 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:21] RECOVERY - misc4 phab.miraheze.wiki HTTPS on misc4 is OK: HTTP OK: Status line output matched "HTTP/1.1 200" - 17649 bytes in 0.080 second response time [04:37:21] PROBLEM - ns1 SSH on ns1 is UNKNOWN: Usage:check_ssh [-4 [04:37:25] PROBLEM - bacula1 Disk Space on bacula1 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:27] RECOVERY - mw1 Current Load on mw1 is OK: OK - load average: 1.73, 1.28, 1.23 [04:37:29] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [04:37:35] RECOVERY - mw2 Current Load on mw2 is OK: OK - load average: 0.96, 0.92, 0.88 [04:37:35] RECOVERY - lizardfs1 Disk Space on lizardfs1 is OK: DISK OK - free space: / 40994 MB (26% inode=98%); [04:37:39] PROBLEM - bacula1 Bacula Phabricator Static on bacula1 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:40] RECOVERY - mw3 JobChron Service on mw3 is OK: PROCS OK: 1 process with args 'redisJobChronService' [04:37:42] RECOVERY - misc4 Disk Space on misc4 is OK: DISK OK - free space: / 48676 MB (79% inode=99%); [04:37:42] RECOVERY - misc4 Current Load on misc4 is OK: OK - load average: 0.11, 0.14, 0.10 [04:37:44] PROBLEM - db4 Puppet on db4 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:45] RECOVERY - mw3 JobRunner Service on mw3 is OK: PROCS OK: 1 process with args 'redisJobRunnerService' [04:37:45] RECOVERY - misc2 Redis Process on misc2 is OK: PROCS OK: 1 process with args 'redis-server' [04:37:47] RECOVERY - test1 php7.2-fpm on test1 is OK: PROCS OK: 3 processes with command name 'php-fpm7.2' [04:37:47] RECOVERY - lizardfs1 Current Load on lizardfs1 is OK: OK - load average: 0.01, 0.03, 0.00 [04:37:49] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [04:37:53] RECOVERY - misc2 Disk Space on misc2 is OK: DISK OK - free space: / 32983 MB (80% inode=99%); [04:37:55] RECOVERY - mw1 MirahezeRenewSsl on mw1 is OK: TCP OK - 0.003 second response time on 185.52.1.75 port 5000 [04:37:56] PROBLEM - db4 Current Load on db4 is WARNING: Could not resolve hostname : No address associated with hostname [04:37:57] RECOVERY - mw3 php7.2-fpm on mw3 is OK: PROCS OK: 5 processes with command name 'php-fpm7.2' [04:37:58] RECOVERY - misc3 Disk Space on misc3 is OK: DISK OK - free space: / 58350 MB (94% inode=99%); [04:37:59] PROBLEM - Host bacula1 is DOWN: check_ping: Invalid hostname/address - Usage:check_ping -H -w ,% -c ,% [-p packets] [-t timeout] [-4 [04:38:00] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 1.68, 1.32, 1.14 [04:38:04] PROBLEM - Host ns1 is DOWN: check_ping: Invalid hostname/address - Usage:check_ping -H -w ,% -c ,% [-p packets] [-t timeout] [-4 [04:38:07] PROBLEM - db4 SSH on db4 is UNKNOWN: Usage:check_ssh [-4 [04:38:11] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:38:17] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [04:38:22] RECOVERY - misc4 lizard.miraheze.org HTTPS on misc4 is OK: HTTP OK: Status line output matched "HTTP/1.1 401 Unauthorized" - 381 bytes in 0.018 second response time [04:38:29] RECOVERY - Host lizardfs2 is UP: PING OK - Packet loss = 0%, RTA = 0.37 ms [04:38:30] RECOVERY - misc4 Lizardfs Master Port 2 on misc4 is OK: TCP OK - 0.001 second response time on 185.52.3.121 port 9420 [04:38:34] RECOVERY - misc3 Electron on misc3 is OK: TCP OK - 0.001 second response time on 185.52.1.144 port 3000 [04:38:40] RECOVERY - misc4 Lizardfs Master Port 3 on misc4 is OK: TCP OK - 0.000 second response time on 185.52.3.121 port 9421 [04:38:45] RECOVERY - misc2 Prometheus on misc2 is OK: TCP OK - 0.003 second response time on 81.4.127.174 port 9090 [04:38:56] RECOVERY - misc4 phd on misc4 is OK: PROCS OK: 1 process with args 'phd' [04:38:56] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 2 minutes ago with 0 failures [04:39:00] PROBLEM - db4 Current Load on db4 is CRITICAL: connect to address ::1 port 5666: Connection refusedconnect to host ::1 port 5666: Connection refused [04:39:13] PROBLEM - db4 MySQL on db4 is CRITICAL: Can't connect to MySQL server on '::1' (111 "Connection refused") [04:39:16] RECOVERY - mw1 php7.2-fpm on mw1 is OK: PROCS OK: 6 processes with command name 'php-fpm7.2' [04:39:30] PROBLEM - db4 Puppet on db4 is CRITICAL: connect to address ::1 port 5666: Connection refusedconnect to host ::1 port 5666: Connection refused [04:39:30] RECOVERY - misc3 Parsoid on misc3 is OK: TCP OK - 0.004 second response time on 185.52.1.144 port 8142 [04:39:38] PROBLEM - db4 Disk Space on db4 is CRITICAL: connect to address ::1 port 5666: Connection refusedconnect to host ::1 port 5666: Connection refused [04:40:01] RECOVERY - db4 SSH on db4 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u4 (protocol 2.0) [04:40:02] RECOVERY - Host bacula1 is UP: PING OK - Packet loss = 0%, RTA = 0.06 ms [04:40:02] PROBLEM - bacula1 Bacula Daemon on bacula1 is CRITICAL: connect to address ::1 port 5666: Connection refusedconnect to host ::1 port 5666: Connection refused [04:40:02] PROBLEM - bacula1 Bacula Static on bacula1 is CRITICAL: connect to address ::1 port 5666: Connection refusedconnect to host ::1 port 5666: Connection refused [04:40:03] PROBLEM - bacula1 SSH on bacula1 is UNKNOWN: Usage:check_ssh [-4 [04:40:04] RECOVERY - Host ns1 is UP: PING OK - Packet loss = 0%, RTA = 98.80 ms [04:40:10] RECOVERY - bacula1 SSH on bacula1 is OK: SSH OK - OpenSSH_7.4p1 Debian-10+deb9u4 (protocol 2.0) [04:40:15] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [04:40:41] RECOVERY - ns1 Disk Space on ns1 is OK: DISK OK - free space: / 11173 MB (90% inode=99%); [04:53:21] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTZt [04:53:23] [02miraheze/puppet] 07paladox 0313dd66e - Update virtual_ip_address.rb [04:54:05] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTZq [04:54:06] [02miraheze/puppet] 07paladox 0393d1ae5 - Update virtual_ip_address.rb [04:55:15] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhTZm [04:55:17] [02miraheze/puppet] 07paladox 0354303a0 - Update virtual_ip_address.rb [04:56:36] RECOVERY - db4 Current Load on db4 is OK: OK - load average: 2.75, 2.09, 1.81 [04:56:48] RECOVERY - db4 MySQL on db4 is OK: Uptime: 568106 Threads: 83 Questions: 700102202 Slow queries: 0 Opens: 46958028 Flush tables: 1 Open tables: 800 Queries per second avg: 1232.344 [04:56:54] PROBLEM - db4 Disk Space on db4 is WARNING: DISK WARNING - free space: / 45172 MB (12% inode=96%); [04:56:57] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [04:57:55] RECOVERY - bacula1 Bacula Databases db4 on bacula1 is OK: OK: Diff, 57131 files, 62.12GB, 2018-12-16 02:19:00 (1.4 weeks ago) [04:58:03] RECOVERY - bacula1 Current Load on bacula1 is OK: OK - load average: 0.02, 0.02, 0.00 [04:58:05] RECOVERY - bacula1 Disk Space on bacula1 is OK: DISK OK - free space: / 138949 MB (29% inode=99%); [04:58:07] RECOVERY - bacula1 Bacula Private Git on bacula1 is OK: OK: Full, 2152 files, 3.472MB, 2018-12-23 00:05:00 (3.2 days ago) [04:58:11] RECOVERY - bacula1 Bacula Phabricator Static on bacula1 is OK: OK: Diff, 3523 files, 11.02MB, 2018-12-16 03:26:00 (1.4 weeks ago) [04:58:12] RECOVERY - bacula1 Bacula Daemon on bacula1 is OK: PROCS OK: 2 processes with UID = 110 (bacula) [04:58:15] RECOVERY - bacula1 Bacula Static on bacula1 is OK: OK: Diff, 148035 files, 7.376GB, 2018-12-16 03:21:00 (1.4 weeks ago) [04:58:20] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:47:46] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 23 failures. Last run 2 minutes ago with 23 failures. Failed resources (up to 3 shown) [08:48:07] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 180 failures. Last run 2 minutes ago with 180 failures. Failed resources (up to 3 shown) [08:48:11] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 20 failures. Last run 2 minutes ago with 20 failures. Failed resources (up to 3 shown) [08:48:26] PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 2 minutes ago with 10 failures. Failed resources (up to 3 shown) [08:48:40] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 3 minutes ago with 16 failures. Failed resources (up to 3 shown) [08:48:46] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown) [08:48:56] PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 3 minutes ago with 11 failures. Failed resources (up to 3 shown) [08:49:09] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 27 failures. Last run 3 minutes ago with 27 failures. Failed resources (up to 3 shown) [08:49:24] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 3 minutes ago with 15 failures. Failed resources (up to 3 shown) [08:49:27] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 3 minutes ago with 10 failures. Failed resources (up to 3 shown) [08:49:27] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 60 failures. Last run 3 minutes ago with 60 failures. Failed resources (up to 3 shown) [08:49:31] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 176 failures. Last run 3 minutes ago with 176 failures. Failed resources (up to 3 shown) [08:52:11] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [08:52:26] RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [08:52:40] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [08:52:45] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [08:52:56] RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:53:09] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:53:24] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:53:26] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:53:26] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:53:31] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:53:45] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [08:54:07] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [14:22:08] Hello AmandaCath! If you have any questions feel free to ask and someone should answer soon. [14:22:15] Hey [14:22:22] I’m back! [14:26:43] ZppixBot: why did you welcome me like I’m a newbie? [14:27:01] it welcomes everyone who joins AmandaCath [14:27:21] paladox: it never welcomed me before [14:27:26] it was disabled [14:27:30] due to freenode spam [14:27:33] which has stopped now [14:27:37] so it was eneabled [14:27:44] I shortened my nick to make it more accessible in the Logs [14:27:57] So I was wondering if that was it [14:28:31] ah ok [14:29:09] Anyway belated Merry Christmas to those that celebrate it [14:29:49] merry christmas to you too :) [14:32:30] Dumb client app froze up [14:32:55] [02puppet] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbiAS [14:32:57] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTVy [14:32:58] [02miraheze/puppet] 07paladox 0358c615f - base: symlink hiera and facter commands [14:33:02] [02puppet] 07paladox opened pull request 03#952: base: symlink hiera and facter commands - 13https://git.io/fhTVS [14:33:08] But anyway, you can say “Happy Boxing Day” to a Canadian the day after Christmas.. [14:33:58] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTVH [14:34:00] [02miraheze/puppet] 07paladox 031bd3090 - Update puppet.pp [14:34:01] [02puppet] 07paladox synchronize pull request 03#952: base: symlink hiera and facter commands - 13https://git.io/fhTVS [14:34:18] [02puppet] 07paladox closed pull request 03#952: base: symlink hiera and facter commands - 13https://git.io/fhTVS [14:34:20] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fhTV7 [14:34:21] [02miraheze/puppet] 07paladox 034243711 - base: symlink hiera and facter commands (#952) * base: symlink hiera and facter commands * Update puppet.pp [14:34:22] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [14:34:24] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [14:45:40] [02puppet] 07paladox created branch 03paladox-patch-2 - 13https://git.io/vbiAS [14:45:41] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTws [14:45:43] [02miraheze/puppet] 07paladox 03c4e84e2 - puppetmaster: Rename puppetserver_heap to puppetserver_java_opts [14:45:44] [02puppet] 07paladox opened pull request 03#953: puppetmaster: Rename puppetserver_heap to puppetserver_java_opts - 13https://git.io/fhTwG [14:46:57] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTwc [14:46:58] [02miraheze/puppet] 07paladox 0395502df - Update init.pp [14:47:00] [02puppet] 07paladox synchronize pull request 03#953: puppetmaster: Rename puppetserver_heap to puppetserver_java_opts - 13https://git.io/fhTwG [14:47:14] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTwW [14:47:16] [02miraheze/puppet] 07paladox 036905d4c - Update v6.pp [14:47:17] [02puppet] 07paladox synchronize pull request 03#953: puppetmaster: Rename puppetserver_heap to puppetserver_java_opts - 13https://git.io/fhTwG [14:47:44] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTw4 [14:47:46] [02miraheze/puppet] 07paladox 039c2844b - Update puppetserver.erb [14:47:47] [02puppet] 07paladox synchronize pull request 03#953: puppetmaster: Rename puppetserver_heap to puppetserver_java_opts - 13https://git.io/fhTwG [14:48:24] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-2 [+0/-0/±1] 13https://git.io/fhTw0 [14:48:26] [02miraheze/puppet] 07paladox 03ed3de1b - Update puppet1.yaml [14:48:27] [02puppet] 07paladox synchronize pull request 03#953: puppetmaster: Rename puppetserver_heap to puppetserver_java_opts - 13https://git.io/fhTwG [14:48:32] [02puppet] 07paladox closed pull request 03#953: puppetmaster: Rename puppetserver_heap to puppetserver_java_opts - 13https://git.io/fhTwG [14:48:34] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±4] 13https://git.io/fhTwz [14:48:35] [02miraheze/puppet] 07paladox 03ca5e2b5 - puppetmaster: Rename puppetserver_heap to puppetserver_java_opts (#953) * puppetmaster: Rename puppetserver_heap to puppetserver_java_opts * Update init.pp * Update v6.pp * Update puppetserver.erb * Update puppet1.yaml [14:48:44] [02puppet] 07paladox deleted branch 03paladox-patch-2 - 13https://git.io/vbiAS [14:48:45] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-2 [14:51:59]