[00:21:05] test [00:21:23] 123 [00:21:58] there we go http://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-operations/20140831.txt [00:30:44] PROBLEM - mailman_qrunner on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/qrunner [00:31:04] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [00:31:44] RECOVERY - mailman_qrunner on sodium is OK: PROCS OK: 8 processes with UID = 38 (list), regex args /mailman/bin/qrunner [00:32:03] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [00:51:03] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [00:52:04] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [00:53:04] jgage, do you happen to still be there? [00:56:44] hi [00:57:33] hey, /msg [01:44:43] PROBLEM - Puppet freshness on analytics1020 is CRITICAL: Last successful Puppet run was Sat 30 Aug 2014 21:42:47 UTC [01:44:51] oh yeah [01:44:56] got a bit distracted with that [01:45:00] * jgage fixes [01:46:03] RECOVERY - Puppet freshness on analytics1020 is OK: puppet ran at Sun Aug 31 01:45:53 UTC 2014 [01:46:03] PROBLEM - puppet last run on analytics1020 is CRITICAL: CRITICAL: Puppet last ran 14580 seconds ago, expected 14400 [01:47:03] RECOVERY - puppet last run on analytics1020 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [01:47:07] hah, i wonder how you got distracted [01:47:23] hehe nbd [01:47:58] Jamesofur, thanks [01:51:24] jeremyb, Was that message intended for jgage? [01:53:20] Krenair, yes, see jgage at 01:44 UTC [01:53:41] Okay. You pinged someone else :) [01:55:22] Krenair, i was thanking Jamesofur for his reply to my msg on RT [02:00:00] !log Stopped HHVM jobrunner and disabled Puppet on mw1053 due to bug 70177. [02:00:13] Logged the message, Master [02:00:27] jackmcbarn: ^ [02:00:39] ori: thanks [02:00:53] jackmcbarn: thanks again for pointing out the issue in the first place. [02:03:02] jackmcbarn: re: your comment (https://bugzilla.wikimedia.org/show_bug.cgi?id=70177#c4), the bug in the timer is also making it actually slower, because concurrent requests can prevent each other from finishing [02:03:27] ori: yes, but it'd still really be a stretch to call it performance [02:03:32] yes, agreed. [02:05:10] jeremyb: welcome :) [02:05:31] Jamesofur, is this RT thing anything to do with OTRS? [02:05:42] it was yes [02:06:45] Jamesofur, does it involve my RT account? [02:07:20] Krenair: don't think so, it was about trying to ensure legal/sensitive emails don't get dumped into spam [02:07:44] Ah okay. [02:08:01] is there something I should respond too about your RT account/OTRS? [02:09:33] It's just that I saw that ticket earlier, then someone mentioned they'd removed a couple of people's (one of who was me. the other person is more important for this ticket) access to see that and a few others [02:10:39] * Jamesofur has never quite understood RTs system of who can view what [02:11:02] Hey james :) [02:11:32] hoy RD :) [02:11:44] If I, as an OTRS admin wanted to be able to see a few tickets on RT, and create one even, who do I need to talk to. Was about to send a note to Philippe/Maggie [02:12:02] I did not realize I had an account created a few weeks ago by THO. [02:12:08] Until I was informed today [02:12:15] (When I asked for a status update on one ticket) [02:12:20] RD: You can create tickets by emailing the respective addresses [02:12:29] Earlier I had the ability to create tickets under ops-requests [02:12:33] Yes, JohnFLewis. I know. [02:12:38] Now when I go to the form, 'queue' is blank [02:13:16] The weird thing is that these tickets I could see were not listed in the SelfService open/closed lists, with the exception of a seemingly random one. [02:13:38] RD: That's the only way without the fuffle of signing NDAs and getting an op to give you access etc. [02:13:56] JohnFLewis: I'm asking LCA for direction ;-) I know. [02:14:06] :p [02:15:03] Ops is the one who controls the access, though we can certainly help vouch for you. Why don't you email us (Maggie/Philippe is fine since they work most closely but feel free to copy me in because I work with ops the most) and we'll try to beat some heads [02:15:21] Will do [02:15:32] often the easiest way to actually 'create' tickets is still email, that's just because RT is kinda a crappy way to create tickets, but for viewing etc access can be useful [02:16:47] I elected jeremy to create one for me earlier and perhaps thats why he told me I had an account ;-) [02:17:02] It does not sound like a user friendly experience [02:17:30] RT is weird with how it handles accounts [02:18:28] !log LocalisationUpdate completed (1.24wmf18) at 2014-08-31 02:17:24+00:00 [02:18:35] Logged the message, Master [02:24:12] Jamesofur, personally, I prefer the web UI for making new tickets [02:24:23] jeremyb: to each their own :) [02:24:29] but i surely have more RT experience than your average LCA person :) [02:25:52] I've played around quite extensively in the back end of it (trying to decide if it was useful for us as a case/ticket system) just don't like it lol. Complicated can be good but it was more complicated then it needed to be which tends to be bad [02:27:21] (for ticket creation it's probably just a matter of 'an extra interface' easier to do rare tickets from the mailbox that's already up) [02:29:46] !log LocalisationUpdate completed (1.24wmf19) at 2014-08-31 02:28:42+00:00 [02:29:52] Logged the message, Master [03:15:48] !log LocalisationUpdate ResourceLoader cache refresh completed at Sun Aug 31 03:14:41 UTC 2014 (duration 14m 40s) [03:15:55] Logged the message, Master [03:18:13] RECOVERY - HTTP error ratio anomaly detection on labmon1001 is OK: OK: No anomaly detected [03:18:23] RECOVERY - HTTP error ratio anomaly detection on tungsten is OK: OK: No anomaly detected [03:50:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [04:39:31] ori: i'm still seeing pages parsed by mw1053 with script errors [04:39:38] (new ones) [04:50:53] PROBLEM - mailman_qrunner on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/qrunner [04:51:03] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [04:51:54] mailman's flappy [04:52:04] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [04:52:53] RECOVERY - mailman_qrunner on sodium is OK: PROCS OK: 8 processes with UID = 38 (list), regex args /mailman/bin/qrunner [05:11:03] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [05:11:53] PROBLEM - mailman_qrunner on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/qrunner [05:12:03] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [05:12:53] RECOVERY - mailman_qrunner on sodium is OK: PROCS OK: 8 processes with UID = 38 (list), regex args /mailman/bin/qrunner [05:51:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [06:25:34] PROBLEM - Disk space on elastic1015 is CRITICAL: DISK CRITICAL - free space: / 138 MB (0% inode=96%): [06:28:14] PROBLEM - puppet last run on iron is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:14] PROBLEM - puppet last run on db1002 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:33] PROBLEM - puppet last run on mw1170 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:33] PROBLEM - puppet last run on mw1092 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:44] PROBLEM - puppet last run on mw1065 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:54] PROBLEM - puppet last run on labsdb1003 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:54] PROBLEM - puppet last run on mw1118 is CRITICAL: CRITICAL: Puppet has 1 failures [06:29:03] PROBLEM - puppet last run on mw1119 is CRITICAL: CRITICAL: Puppet has 2 failures [06:29:13] PROBLEM - puppet last run on mw1052 is CRITICAL: CRITICAL: Puppet has 1 failures [06:29:14] PROBLEM - puppet last run on cp4003 is CRITICAL: CRITICAL: Puppet has 1 failures [06:37:43] PROBLEM - puppet last run on db1035 is CRITICAL: CRITICAL: Puppet has 1 failures [06:45:33] RECOVERY - puppet last run on mw1170 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [06:45:53] RECOVERY - puppet last run on labsdb1003 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:46:03] RECOVERY - puppet last run on mw1119 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:46:13] RECOVERY - puppet last run on iron is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:46:13] RECOVERY - puppet last run on mw1052 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:46:14] RECOVERY - puppet last run on cp4003 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:46:33] RECOVERY - puppet last run on mw1092 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:46:44] RECOVERY - puppet last run on mw1065 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:46:54] RECOVERY - puppet last run on mw1118 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [06:49:03] RECOVERY - Disk space on ms1004 is OK: DISK OK [06:52:03] PROBLEM - Disk space on ms1004 is CRITICAL: DISK CRITICAL - free space: / 20 MB (0% inode=94%): /var/lib/ureadahead/debugfs 20 MB (0% inode=94%): [06:55:43] RECOVERY - puppet last run on db1035 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [07:06:13] RECOVERY - puppet last run on db1002 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [07:52:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [08:23:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [09:30:53] PROBLEM - mailman_qrunner on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/qrunner [09:31:13] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [09:32:13] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [09:32:53] RECOVERY - mailman_qrunner on sodium is OK: PROCS OK: 8 processes with UID = 38 (list), regex args /mailman/bin/qrunner [09:51:13] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [09:52:13] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [09:53:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [10:24:13] PROBLEM - puppet last run on elastic1007 is CRITICAL: CRITICAL: Puppet last ran 14451 seconds ago, expected 14400 [10:24:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [10:38:13] PROBLEM - DPKG on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:13] PROBLEM - puppet last run on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:13] PROBLEM - swift-container-server on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:14] PROBLEM - swift-object-auditor on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:14] PROBLEM - check if dhclient is running on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:14] PROBLEM - swift-account-replicator on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:14] PROBLEM - swift-container-replicator on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:33] PROBLEM - RAID on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:33] PROBLEM - swift-account-auditor on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:33] PROBLEM - swift-container-updater on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:33] PROBLEM - swift-account-server on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:33] PROBLEM - swift-container-auditor on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:43] PROBLEM - swift-object-server on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:43] PROBLEM - swift-object-replicator on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:38:43] PROBLEM - swift-account-reaper on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:39:03] PROBLEM - swift-object-updater on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:39:03] PROBLEM - SSH on ms-be1010 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [10:39:34] PROBLEM - Disk space on elastic1015 is CRITICAL: DISK CRITICAL - free space: / 1063 MB (3% inode=96%): [10:50:43] PROBLEM - NTP on ms-be1010 is CRITICAL: NTP CRITICAL: No response from NTP server [10:51:13] PROBLEM - check configured eth on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:51:43] PROBLEM - Disk space on ms-be1010 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [10:55:54] PROBLEM - puppet last run on cp1044 is CRITICAL: CRITICAL: Puppet has 23 failures [10:56:03] PROBLEM - puppet last run on strontium is CRITICAL: CRITICAL: Puppet has 24 failures [10:56:03] PROBLEM - puppet last run on mw1152 is CRITICAL: CRITICAL: Puppet has 51 failures [10:56:04] PROBLEM - puppet last run on wtp1010 is CRITICAL: CRITICAL: Puppet has 22 failures [10:56:13] PROBLEM - puppet last run on amssq31 is CRITICAL: CRITICAL: Puppet has 10 failures [10:56:13] PROBLEM - puppet last run on mw1093 is CRITICAL: CRITICAL: Puppet has 38 failures [10:56:13] PROBLEM - puppet last run on elastic1003 is CRITICAL: CRITICAL: Puppet has 20 failures [10:56:13] PROBLEM - puppet last run on rbf1001 is CRITICAL: CRITICAL: Epic puppet fail [10:56:14] PROBLEM - puppet last run on mw1086 is CRITICAL: CRITICAL: Epic puppet fail [10:56:14] PROBLEM - puppet last run on search1022 is CRITICAL: CRITICAL: Puppet has 21 failures [10:56:14] PROBLEM - puppet last run on mw1027 is CRITICAL: CRITICAL: Epic puppet fail [10:56:14] PROBLEM - puppet last run on analytics1018 is CRITICAL: CRITICAL: Puppet has 15 failures [10:56:15] PROBLEM - puppetmaster backend https on strontium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8141: HTTP/1.1 500 Internal Server Error [10:56:15] PROBLEM - puppet last run on mw1016 is CRITICAL: CRITICAL: Puppet has 7 failures [10:56:23] PROBLEM - puppet last run on cp4020 is CRITICAL: CRITICAL: Puppet has 9 failures [10:56:24] PROBLEM - puppet last run on cp3005 is CRITICAL: CRITICAL: Epic puppet fail [10:56:33] PROBLEM - puppet last run on bast1001 is CRITICAL: CRITICAL: Epic puppet fail [10:56:33] PROBLEM - puppet last run on cp1067 is CRITICAL: CRITICAL: Puppet has 26 failures [10:56:33] PROBLEM - puppet last run on iodine is CRITICAL: CRITICAL: Puppet has 1 failures [10:56:47] PROBLEM - puppet last run on cp1040 is CRITICAL: CRITICAL: Epic puppet fail [10:56:47] PROBLEM - puppet last run on mw1010 is CRITICAL: CRITICAL: Puppet has 34 failures [10:56:47] PROBLEM - puppet last run on copper is CRITICAL: CRITICAL: Puppet has 16 failures [10:56:47] PROBLEM - puppet last run on db1072 is CRITICAL: CRITICAL: Epic puppet fail [10:56:54] PROBLEM - puppet last run on mw1215 is CRITICAL: CRITICAL: Puppet has 62 failures [10:56:54] PROBLEM - puppet last run on virt1008 is CRITICAL: CRITICAL: Puppet has 27 failures [10:56:54] PROBLEM - puppet last run on mw1113 is CRITICAL: CRITICAL: Epic puppet fail [10:56:54] PROBLEM - puppet last run on chromium is CRITICAL: CRITICAL: Epic puppet fail [10:56:54] PROBLEM - puppet last run on mw1110 is CRITICAL: CRITICAL: Epic puppet fail [10:56:54] PROBLEM - puppet last run on mw1203 is CRITICAL: CRITICAL: Puppet has 48 failures [10:56:55] PROBLEM - puppet last run on mw1142 is CRITICAL: CRITICAL: Puppet has 59 failures [10:57:03] PROBLEM - puppet last run on mw1220 is CRITICAL: CRITICAL: Puppet has 69 failures [10:57:03] PROBLEM - puppet last run on terbium is CRITICAL: CRITICAL: Puppet has 84 failures [10:57:03] PROBLEM - puppet last run on mw1066 is CRITICAL: CRITICAL: Puppet has 68 failures [10:57:03] PROBLEM - puppet last run on mw1155 is CRITICAL: CRITICAL: Epic puppet fail [10:57:03] PROBLEM - puppet last run on search1004 is CRITICAL: CRITICAL: Puppet has 38 failures [10:57:03] PROBLEM - puppet last run on mw1064 is CRITICAL: CRITICAL: Puppet has 53 failures [10:57:03] PROBLEM - puppet last run on mw1021 is CRITICAL: CRITICAL: Epic puppet fail [10:57:04] PROBLEM - puppet last run on db71 is CRITICAL: CRITICAL: Puppet has 15 failures [10:57:04] PROBLEM - puppet last run on mw1037 is CRITICAL: CRITICAL: Epic puppet fail [10:57:13] PROBLEM - puppet last run on mw1112 is CRITICAL: CRITICAL: Puppet has 65 failures [10:57:13] PROBLEM - puppet last run on ms-be1002 is CRITICAL: CRITICAL: Puppet has 14 failures [10:57:13] PROBLEM - puppet last run on cp3011 is CRITICAL: CRITICAL: Epic puppet fail [10:57:13] PROBLEM - puppet last run on ms-fe1002 is CRITICAL: CRITICAL: Puppet has 25 failures [10:57:13] PROBLEM - puppet last run on osm-cp1001 is CRITICAL: CRITICAL: Epic puppet fail [10:57:13] PROBLEM - puppet last run on mw1107 is CRITICAL: CRITICAL: Puppet has 60 failures [10:57:14] PROBLEM - puppet last run on mw1104 is CRITICAL: CRITICAL: Epic puppet fail [10:57:14] PROBLEM - puppet last run on cp1068 is CRITICAL: CRITICAL: Epic puppet fail [10:57:15] PROBLEM - puppet last run on dysprosium is CRITICAL: CRITICAL: Epic puppet fail [10:57:15] PROBLEM - puppet last run on mw1154 is CRITICAL: CRITICAL: Epic puppet fail [10:57:15] PROBLEM - puppet last run on mw1193 is CRITICAL: CRITICAL: Puppet has 62 failures [10:57:16] PROBLEM - puppet last run on db1045 is CRITICAL: CRITICAL: Puppet has 21 failures [10:57:17] PROBLEM - puppet last run on mw1131 is CRITICAL: CRITICAL: Epic puppet fail [10:57:17] PROBLEM - puppet last run on eeden is CRITICAL: CRITICAL: Epic puppet fail [10:57:17] PROBLEM - puppet last run on ssl3001 is CRITICAL: CRITICAL: Puppet has 22 failures [10:57:18] PROBLEM - puppet last run on cp3018 is CRITICAL: CRITICAL: Puppet has 14 failures [10:57:19] PROBLEM - puppet last run on search1012 is CRITICAL: CRITICAL: Puppet has 41 failures [10:57:19] PROBLEM - puppet last run on mw1135 is CRITICAL: CRITICAL: Epic puppet fail [10:57:19] PROBLEM - puppet last run on mw1090 is CRITICAL: CRITICAL: Puppet has 73 failures [10:57:20] PROBLEM - puppet last run on mw1143 is CRITICAL: CRITICAL: Puppet has 58 failures [10:57:20] PROBLEM - puppet last run on mw1071 is CRITICAL: CRITICAL: Puppet has 62 failures [10:57:21] PROBLEM - puppet last run on mw1204 is CRITICAL: CRITICAL: Puppet has 58 failures [10:57:21] PROBLEM - puppet last run on mw1207 is CRITICAL: CRITICAL: Epic puppet fail [10:57:23] PROBLEM - puppet last run on lvs4004 is CRITICAL: CRITICAL: Epic puppet fail [10:57:23] PROBLEM - puppet last run on cp4012 is CRITICAL: CRITICAL: Puppet has 24 failures [10:57:23] PROBLEM - puppet last run on cp4009 is CRITICAL: CRITICAL: Puppet has 24 failures [10:57:24] PROBLEM - puppet last run on cp4011 is CRITICAL: CRITICAL: Epic puppet fail [10:57:24] PROBLEM - puppet last run on cp4002 is CRITICAL: CRITICAL: Puppet has 18 failures [10:57:25] PROBLEM - puppet last run on lvs3003 is CRITICAL: CRITICAL: Puppet has 22 failures [10:57:25] PROBLEM - puppet last run on amssq39 is CRITICAL: CRITICAL: Puppet has 27 failures [10:57:33] PROBLEM - puppet last run on mw1128 is CRITICAL: CRITICAL: Epic puppet fail [10:57:33] PROBLEM - puppet last run on db1056 is CRITICAL: CRITICAL: Puppet has 19 failures [10:57:43] PROBLEM - puppet last run on db1035 is CRITICAL: CRITICAL: Puppet has 26 failures [10:57:43] PROBLEM - puppet last run on wtp1008 is CRITICAL: CRITICAL: Epic puppet fail [10:57:53] PROBLEM - puppet last run on db60 is CRITICAL: CRITICAL: Puppet has 25 failures [10:57:53] PROBLEM - puppet last run on mexia is CRITICAL: CRITICAL: Epic puppet fail [10:57:54] PROBLEM - puppet last run on wtp1001 is CRITICAL: CRITICAL: Puppet has 19 failures [10:57:54] PROBLEM - puppet last run on cp1045 is CRITICAL: CRITICAL: Puppet has 20 failures [10:57:54] PROBLEM - puppet last run on virt1005 is CRITICAL: CRITICAL: Epic puppet fail [10:58:03] PROBLEM - puppet last run on cp1053 is CRITICAL: CRITICAL: Puppet has 24 failures [10:58:03] PROBLEM - puppet last run on ms-be1015 is CRITICAL: CRITICAL: Epic puppet fail [10:58:03] PROBLEM - puppet last run on cp1066 is CRITICAL: CRITICAL: Epic puppet fail [10:58:13] PROBLEM - puppet last run on tmh1001 is CRITICAL: CRITICAL: Epic puppet fail [10:58:13] PROBLEM - puppet last run on palladium is CRITICAL: CRITICAL: Epic puppet fail [10:58:13] PROBLEM - puppet last run on mc1015 is CRITICAL: CRITICAL: Epic puppet fail [10:58:14] PROBLEM - puppet last run on mw1158 is CRITICAL: CRITICAL: Puppet has 73 failures [10:58:14] PROBLEM - puppet last run on cp1054 is CRITICAL: CRITICAL: Puppet has 24 failures [10:58:14] PROBLEM - puppet last run on es1004 is CRITICAL: CRITICAL: Epic puppet fail [10:58:14] PROBLEM - puppet last run on db1037 is CRITICAL: CRITICAL: Puppet has 18 failures [10:58:14] PROBLEM - puppet last run on labsdb1005 is CRITICAL: CRITICAL: Epic puppet fail [10:58:14] PROBLEM - puppet last run on amssq37 is CRITICAL: CRITICAL: Puppet has 17 failures [10:58:15] PROBLEM - puppet last run on db1005 is CRITICAL: CRITICAL: Epic puppet fail [10:58:15] PROBLEM - puppet last run on lvs1004 is CRITICAL: CRITICAL: Puppet has 29 failures [10:58:16] PROBLEM - puppet last run on db1027 is CRITICAL: CRITICAL: Epic puppet fail [10:58:17] PROBLEM - puppet last run on lvs1003 is CRITICAL: CRITICAL: Puppet has 20 failures [10:58:17] PROBLEM - puppet last run on mw1103 is CRITICAL: CRITICAL: Epic puppet fail [10:58:23] PROBLEM - puppet last run on fenari is CRITICAL: CRITICAL: Puppet has 49 failures [10:58:24] PROBLEM - puppet last run on cp3019 is CRITICAL: CRITICAL: Epic puppet fail [10:58:34] PROBLEM - puppet last run on search1003 is CRITICAL: CRITICAL: Epic puppet fail [10:58:34] PROBLEM - puppet last run on mw1018 is CRITICAL: CRITICAL: Puppet has 64 failures [10:58:43] PROBLEM - puppet last run on mw1073 is CRITICAL: CRITICAL: Epic puppet fail [10:58:44] PROBLEM - puppet last run on analytics1012 is CRITICAL: CRITICAL: Puppet has 19 failures [10:58:44] PROBLEM - puppet last run on mw1019 is CRITICAL: CRITICAL: Epic puppet fail [10:58:53] PROBLEM - puppet last run on mw1047 is CRITICAL: CRITICAL: Puppet has 58 failures [10:58:54] PROBLEM - puppet last run on ssl1003 is CRITICAL: CRITICAL: Puppet has 20 failures [10:58:54] PROBLEM - puppet last run on analytics1031 is CRITICAL: CRITICAL: Epic puppet fail [10:58:54] PROBLEM - puppet last run on virt1009 is CRITICAL: CRITICAL: Epic puppet fail [10:59:03] PROBLEM - puppet last run on bast2001 is CRITICAL: CRITICAL: Epic puppet fail [10:59:03] PROBLEM - puppet last run on ms-be1014 is CRITICAL: CRITICAL: Puppet has 19 failures [10:59:03] PROBLEM - puppet last run on mw1157 is CRITICAL: CRITICAL: Epic puppet fail [10:59:03] PROBLEM - puppet last run on elastic1013 is CRITICAL: CRITICAL: Epic puppet fail [10:59:03] PROBLEM - puppet last run on ms-be3004 is CRITICAL: CRITICAL: Epic puppet fail [10:59:03] PROBLEM - puppet last run on cp3021 is CRITICAL: CRITICAL: Puppet has 18 failures [10:59:04] PROBLEM - puppet last run on db1009 is CRITICAL: CRITICAL: Epic puppet fail [10:59:04] PROBLEM - puppet last run on virt0 is CRITICAL: CRITICAL: Epic puppet fail [10:59:04] PROBLEM - puppet last run on db1068 is CRITICAL: CRITICAL: Epic puppet fail [10:59:05] PROBLEM - puppet last run on mw1095 is CRITICAL: CRITICAL: Puppet has 59 failures [10:59:13] PROBLEM - puppet last run on lvs3002 is CRITICAL: CRITICAL: Epic puppet fail [10:59:13] PROBLEM - puppet last run on lanthanum is CRITICAL: CRITICAL: Epic puppet fail [10:59:13] PROBLEM - puppet last run on elastic1009 is CRITICAL: CRITICAL: Epic puppet fail [10:59:13] PROBLEM - puppet last run on amssq50 is CRITICAL: CRITICAL: Puppet has 22 failures [10:59:13] PROBLEM - puppet last run on mw1194 is CRITICAL: CRITICAL: Puppet has 65 failures [10:59:13] PROBLEM - puppet last run on mw1078 is CRITICAL: CRITICAL: Puppet has 73 failures [10:59:13] PROBLEM - puppet last run on elastic1010 is CRITICAL: CRITICAL: Epic puppet fail [10:59:14] PROBLEM - puppet last run on cp3017 is CRITICAL: CRITICAL: Puppet has 23 failures [10:59:14] PROBLEM - puppet last run on erbium is CRITICAL: CRITICAL: Epic puppet fail [10:59:15] PROBLEM - puppet last run on mw1137 is CRITICAL: CRITICAL: Puppet has 64 failures [10:59:16] PROBLEM - puppet last run on mw1199 is CRITICAL: CRITICAL: Puppet has 75 failures [10:59:16] PROBLEM - puppet last run on analytics1021 is CRITICAL: CRITICAL: Puppet has 18 failures [10:59:23] PROBLEM - puppet last run on cp4016 is CRITICAL: CRITICAL: Puppet has 24 failures [10:59:23] PROBLEM - puppet last run on cp4010 is CRITICAL: CRITICAL: Puppet has 20 failures [10:59:23] PROBLEM - puppet last run on amssq52 is CRITICAL: CRITICAL: Epic puppet fail [10:59:33] PROBLEM - puppet last run on mw1058 is CRITICAL: CRITICAL: Puppet has 72 failures [10:59:33] PROBLEM - puppet last run on search1019 is CRITICAL: CRITICAL: Puppet has 44 failures [10:59:33] PROBLEM - puppet last run on neon is CRITICAL: CRITICAL: Epic puppet fail [10:59:43] PROBLEM - puppet last run on hydrogen is CRITICAL: CRITICAL: Epic puppet fail [10:59:54] PROBLEM - puppet last run on search1008 is CRITICAL: CRITICAL: Puppet has 47 failures [10:59:54] PROBLEM - puppet last run on zinc is CRITICAL: CRITICAL: Puppet has 21 failures [10:59:54] PROBLEM - puppet last run on mw1214 is CRITICAL: CRITICAL: Epic puppet fail [11:00:03] PROBLEM - puppet last run on mw1179 is CRITICAL: CRITICAL: Puppet has 63 failures [11:00:03] PROBLEM - puppet last run on mw1085 is CRITICAL: CRITICAL: Puppet has 58 failures [11:00:03] PROBLEM - puppet last run on mw1101 is CRITICAL: CRITICAL: Puppet has 55 failures [11:00:03] PROBLEM - puppet last run on mw1070 is CRITICAL: CRITICAL: Puppet has 63 failures [11:00:03] PROBLEM - puppet last run on cp1064 is CRITICAL: CRITICAL: Puppet has 15 failures [11:00:04] PROBLEM - puppet last run on labsdb1002 is CRITICAL: CRITICAL: Puppet has 16 failures [11:00:13] PROBLEM - puppet last run on es1003 is CRITICAL: CRITICAL: Epic puppet fail [11:00:13] PROBLEM - puppet last run on mw1075 is CRITICAL: CRITICAL: Puppet has 64 failures [11:00:13] PROBLEM - puppet last run on mw1127 is CRITICAL: CRITICAL: Epic puppet fail [11:00:13] PROBLEM - puppet last run on cp3007 is CRITICAL: CRITICAL: Puppet has 21 failures [11:00:13] PROBLEM - puppet last run on mw1182 is CRITICAL: CRITICAL: Epic puppet fail [11:00:13] PROBLEM - puppet last run on labsdb1007 is CRITICAL: CRITICAL: Epic puppet fail [11:00:14] PROBLEM - puppet last run on analytics1029 is CRITICAL: CRITICAL: Epic puppet fail [11:00:14] PROBLEM - puppet last run on cp1057 is CRITICAL: CRITICAL: Epic puppet fail [11:00:14] PROBLEM - puppet last run on db1049 is CRITICAL: CRITICAL: Puppet has 18 failures [11:00:15] PROBLEM - puppet last run on search1009 is CRITICAL: CRITICAL: Epic puppet fail [11:00:16] PROBLEM - puppet last run on mw1015 is CRITICAL: CRITICAL: Puppet has 55 failures [11:00:16] PROBLEM - puppet last run on mw1102 is CRITICAL: CRITICAL: Puppet has 65 failures [11:00:17] PROBLEM - puppet last run on mw1017 is CRITICAL: CRITICAL: Puppet has 55 failures [11:00:23] PROBLEM - puppet last run on lvs4001 is CRITICAL: CRITICAL: Epic puppet fail [11:00:23] PROBLEM - puppet last run on cp4015 is CRITICAL: CRITICAL: Puppet has 27 failures [11:00:23] PROBLEM - puppet last run on amssq45 is CRITICAL: CRITICAL: Puppet has 24 failures [11:00:33] PROBLEM - puppet last run on wtp1014 is CRITICAL: CRITICAL: Puppet has 24 failures [11:00:33] PROBLEM - puppet last run on ocg1002 is CRITICAL: CRITICAL: Epic puppet fail [11:00:34] PROBLEM - puppet last run on lvs1006 is CRITICAL: CRITICAL: Epic puppet fail [11:00:34] PROBLEM - puppet last run on mw1094 is CRITICAL: CRITICAL: Epic puppet fail [11:00:34] PROBLEM - puppet last run on ms-be1005 is CRITICAL: CRITICAL: Epic puppet fail [11:00:43] PROBLEM - puppet last run on analytics1024 is CRITICAL: CRITICAL: Puppet has 19 failures [11:00:43] PROBLEM - puppet last run on cp4013 is CRITICAL: CRITICAL: Puppet has 24 failures [11:00:43] PROBLEM - puppet last run on mw1035 is CRITICAL: CRITICAL: Epic puppet fail [11:00:53] PROBLEM - puppet last run on mw1169 is CRITICAL: CRITICAL: Puppet has 61 failures [11:00:54] PROBLEM - puppet last run on ssl1004 is CRITICAL: CRITICAL: Puppet has 16 failures [11:00:54] PROBLEM - puppet last run on mw1020 is CRITICAL: CRITICAL: Puppet has 61 failures [11:00:54] PROBLEM - puppet last run on analytics1034 is CRITICAL: CRITICAL: Epic puppet fail [11:00:54] PROBLEM - puppet last run on elastic1016 is CRITICAL: CRITICAL: Puppet has 19 failures [11:01:03] PROBLEM - puppet last run on mw1184 is CRITICAL: CRITICAL: Puppet has 54 failures [11:01:03] PROBLEM - puppet last run on search1014 is CRITICAL: CRITICAL: Epic puppet fail [11:01:03] PROBLEM - puppet last run on cp1065 is CRITICAL: CRITICAL: Epic puppet fail [11:01:03] PROBLEM - puppet last run on search1021 is CRITICAL: CRITICAL: Puppet has 60 failures [11:01:03] PROBLEM - puppet last run on es1005 is CRITICAL: CRITICAL: Puppet has 19 failures [11:01:03] PROBLEM - puppet last run on db1041 is CRITICAL: CRITICAL: Puppet has 25 failures [11:01:03] PROBLEM - puppet last run on amslvs4 is CRITICAL: CRITICAL: Epic puppet fail [11:01:04] PROBLEM - puppet last run on tmh1002 is CRITICAL: CRITICAL: Puppet has 28 failures [11:01:13] PROBLEM - puppet last run on db1058 is CRITICAL: CRITICAL: Puppet has 24 failures [11:01:13] PROBLEM - puppet last run on mw1096 is CRITICAL: CRITICAL: Epic puppet fail [11:01:13] PROBLEM - puppet last run on amssq57 is CRITICAL: CRITICAL: Epic puppet fail [11:01:13] PROBLEM - puppet last run on mw1036 is CRITICAL: CRITICAL: Epic puppet fail [11:01:14] PROBLEM - puppet last run on db1010 is CRITICAL: CRITICAL: Epic puppet fail [11:01:14] PROBLEM - puppet last run on db1019 is CRITICAL: CRITICAL: Puppet has 27 failures [11:01:14] PROBLEM - puppet last run on analytics1019 is CRITICAL: CRITICAL: Epic puppet fail [11:01:14] PROBLEM - puppet last run on mc1008 is CRITICAL: CRITICAL: Epic puppet fail [11:01:15] PROBLEM - puppet last run on mw1083 is CRITICAL: CRITICAL: Puppet has 52 failures [11:01:15] PROBLEM - puppet last run on mw1013 is CRITICAL: CRITICAL: Epic puppet fail [11:01:15] PROBLEM - puppet last run on mw1138 is CRITICAL: CRITICAL: Epic puppet fail [11:01:23] PROBLEM - puppet last run on mw1191 is CRITICAL: CRITICAL: Puppet has 68 failures [11:01:34] PROBLEM - puppet last run on cp1051 is CRITICAL: CRITICAL: Puppet has 18 failures [11:01:34] PROBLEM - puppet last run on mw1136 is CRITICAL: CRITICAL: Puppet has 59 failures [11:01:44] PROBLEM - puppet last run on cp1069 is CRITICAL: CRITICAL: Puppet has 24 failures [11:01:54] PROBLEM - puppet last run on mw1161 is CRITICAL: CRITICAL: Epic puppet fail [11:01:54] PROBLEM - puppet last run on wtp1021 is CRITICAL: CRITICAL: Puppet has 26 failures [11:01:54] PROBLEM - puppet last run on wtp1024 is CRITICAL: CRITICAL: Epic puppet fail [11:01:54] PROBLEM - puppet last run on labsdb1001 is CRITICAL: CRITICAL: Epic puppet fail [11:01:54] PROBLEM - puppet last run on analytics1036 is CRITICAL: CRITICAL: Epic puppet fail [11:01:54] PROBLEM - puppet last run on mw1132 is CRITICAL: CRITICAL: Epic puppet fail [11:01:55] PROBLEM - puppet last run on analytics1015 is CRITICAL: CRITICAL: Epic puppet fail [11:01:55] PROBLEM - puppet last run on praseodymium is CRITICAL: CRITICAL: Puppet has 18 failures [11:02:03] PROBLEM - puppet last run on db1024 is CRITICAL: CRITICAL: Puppet has 19 failures [11:02:03] PROBLEM - puppet last run on es1009 is CRITICAL: CRITICAL: Epic puppet fail [11:02:03] PROBLEM - puppet last run on zirconium is CRITICAL: CRITICAL: Puppet has 48 failures [11:02:03] PROBLEM - puppet last run on es10 is CRITICAL: CRITICAL: Puppet has 13 failures [11:02:03] PROBLEM - puppet last run on es7 is CRITICAL: CRITICAL: Puppet has 15 failures [11:02:03] PROBLEM - puppet last run on ytterbium is CRITICAL: CRITICAL: Epic puppet fail [11:02:13] PROBLEM - puppet last run on ssl3003 is CRITICAL: CRITICAL: Epic puppet fail [11:02:13] PROBLEM - puppet last run on amssq58 is CRITICAL: CRITICAL: Puppet has 25 failures [11:02:13] PROBLEM - puppet last run on mw1196 is CRITICAL: CRITICAL: Puppet has 70 failures [11:02:13] PROBLEM - puppet last run on es1006 is CRITICAL: CRITICAL: Puppet has 16 failures [11:02:13] PROBLEM - puppet last run on db1007 is CRITICAL: CRITICAL: Epic puppet fail [11:02:20] PROBLEM - puppet last run on mw1147 is CRITICAL: CRITICAL: Puppet has 67 failures [11:02:23] PROBLEM - puppet last run on tarin is CRITICAL: CRITICAL: Puppet has 21 failures [11:02:23] PROBLEM - puppet last run on cp4017 is CRITICAL: CRITICAL: Puppet has 21 failures [11:02:33] PROBLEM - puppet last run on cp1043 is CRITICAL: CRITICAL: Epic puppet fail [11:02:53] PROBLEM - puppet last run on mw1040 is CRITICAL: CRITICAL: Puppet has 61 failures [11:02:53] PROBLEM - puppet last run on vanadium is CRITICAL: CRITICAL: Epic puppet fail [11:02:53] PROBLEM - puppet last run on virt1002 is CRITICAL: CRITICAL: Puppet has 19 failures [11:02:53] PROBLEM - puppet last run on mc1010 is CRITICAL: CRITICAL: Epic puppet fail [11:02:54] PROBLEM - puppet last run on mw1192 is CRITICAL: CRITICAL: Puppet has 59 failures [11:03:03] PROBLEM - puppet last run on cp1059 is CRITICAL: CRITICAL: Puppet has 23 failures [11:03:03] PROBLEM - puppet last run on mw1109 is CRITICAL: CRITICAL: Puppet has 61 failures [11:03:03] PROBLEM - puppet last run on mw1218 is CRITICAL: CRITICAL: Puppet has 67 failures [11:03:03] PROBLEM - puppet last run on mc1011 is CRITICAL: CRITICAL: Puppet has 23 failures [11:03:03] PROBLEM - puppet last run on mw1089 is CRITICAL: CRITICAL: Epic puppet fail [11:03:03] PROBLEM - puppet last run on ms-be1001 is CRITICAL: CRITICAL: Epic puppet fail [11:03:04] PROBLEM - puppet last run on cp3022 is CRITICAL: CRITICAL: Puppet has 26 failures [11:03:04] PROBLEM - puppet last run on cp3013 is CRITICAL: CRITICAL: Puppet has 22 failures [11:03:04] PROBLEM - puppet last run on mc1004 is CRITICAL: CRITICAL: Puppet has 22 failures [11:03:05] PROBLEM - puppet last run on mw1028 is CRITICAL: CRITICAL: Epic puppet fail [11:03:13] PROBLEM - puppet last run on analytics1039 is CRITICAL: CRITICAL: Puppet has 19 failures [11:03:13] PROBLEM - puppet last run on mw1005 is CRITICAL: CRITICAL: Epic puppet fail [11:03:13] PROBLEM - puppet last run on cp3006 is CRITICAL: CRITICAL: Epic puppet fail [11:03:13] PROBLEM - puppet last run on cp3015 is CRITICAL: CRITICAL: Epic puppet fail [11:03:13] PROBLEM - puppet last run on mw1216 is CRITICAL: CRITICAL: Puppet has 61 failures [11:03:13] PROBLEM - puppet last run on mc1009 is CRITICAL: CRITICAL: Epic puppet fail [11:03:14] PROBLEM - puppet last run on rdb1004 is CRITICAL: CRITICAL: Epic puppet fail [11:03:14] PROBLEM - puppet last run on ms1001 is CRITICAL: CRITICAL: Epic puppet fail [11:03:15] PROBLEM - puppet last run on mw1062 is CRITICAL: CRITICAL: Puppet has 62 failures [11:03:15] PROBLEM - puppet last run on search1020 is CRITICAL: CRITICAL: Puppet has 36 failures [11:03:15] PROBLEM - puppet last run on mw1048 is CRITICAL: CRITICAL: Epic puppet fail [11:03:16] PROBLEM - puppet last run on dbstore1001 is CRITICAL: CRITICAL: Puppet has 19 failures [11:03:17] PROBLEM - puppet last run on mw1038 is CRITICAL: CRITICAL: Puppet has 59 failures [11:03:17] PROBLEM - puppet last run on mw1130 is CRITICAL: CRITICAL: Puppet has 55 failures [11:03:17] PROBLEM - puppet last run on mw1072 is CRITICAL: CRITICAL: Epic puppet fail [11:03:18] PROBLEM - puppet last run on mw1124 is CRITICAL: CRITICAL: Puppet has 66 failures [11:03:23] PROBLEM - puppet last run on cp4007 is CRITICAL: CRITICAL: Puppet has 21 failures [11:03:23] PROBLEM - puppet last run on amslvs2 is CRITICAL: CRITICAL: Epic puppet fail [11:03:24] PROBLEM - puppet last run on amssq44 is CRITICAL: CRITICAL: Epic puppet fail [11:03:33] PROBLEM - puppet last run on logstash1003 is CRITICAL: CRITICAL: Puppet has 23 failures [11:03:43] PROBLEM - puppet last run on db1065 is CRITICAL: CRITICAL: Puppet has 19 failures [11:03:43] PROBLEM - puppet last run on wtp1019 is CRITICAL: CRITICAL: Puppet has 25 failures [11:03:43] PROBLEM - puppet last run on wtp1017 is CRITICAL: CRITICAL: Puppet has 21 failures [11:03:43] PROBLEM - puppet last run on wtp1009 is CRITICAL: CRITICAL: Epic puppet fail [11:03:44] PROBLEM - puppet last run on es1001 is CRITICAL: CRITICAL: Epic puppet fail [11:03:44] PROBLEM - puppet last run on ocg1001 is CRITICAL: CRITICAL: Puppet has 14 failures [11:03:53] PROBLEM - puppet last run on mw1134 is CRITICAL: CRITICAL: Epic puppet fail [11:03:53] PROBLEM - puppet last run on logstash1001 is CRITICAL: CRITICAL: Epic puppet fail [11:03:54] PROBLEM - puppet last run on ms-fe1003 is CRITICAL: CRITICAL: Puppet has 19 failures [11:04:03] PROBLEM - puppet last run on pc1001 is CRITICAL: CRITICAL: Puppet has 26 failures [11:04:03] PROBLEM - puppet last run on db1017 is CRITICAL: CRITICAL: Puppet has 14 failures [11:04:03] PROBLEM - puppet last run on mw1080 is CRITICAL: CRITICAL: Puppet has 76 failures [11:04:03] PROBLEM - puppet last run on mw1067 is CRITICAL: CRITICAL: Puppet has 70 failures [11:04:03] PROBLEM - puppet last run on cp1049 is CRITICAL: CRITICAL: Puppet has 21 failures [11:04:03] PROBLEM - puppet last run on carbon is CRITICAL: CRITICAL: Puppet has 32 failures [11:04:13] PROBLEM - puppet last run on mw1140 is CRITICAL: CRITICAL: Epic puppet fail [11:04:13] PROBLEM - puppet last run on mw1115 is CRITICAL: CRITICAL: Puppet has 68 failures [11:04:13] PROBLEM - puppet last run on caesium is CRITICAL: CRITICAL: Epic puppet fail [11:04:13] PROBLEM - puppet last run on mw1045 is CRITICAL: CRITICAL: Epic puppet fail [11:04:13] PROBLEM - puppet last run on mw1145 is CRITICAL: CRITICAL: Epic puppet fail [11:04:13] PROBLEM - puppet last run on ms-be1013 is CRITICAL: CRITICAL: Puppet has 24 failures [11:04:13] PROBLEM - puppet last run on cp1070 is CRITICAL: CRITICAL: Epic puppet fail [11:04:14] PROBLEM - puppet last run on dbproxy1002 is CRITICAL: CRITICAL: Puppet has 17 failures [11:04:14] PROBLEM - puppet last run on db1029 is CRITICAL: CRITICAL: Puppet has 25 failures [11:04:15] PROBLEM - puppet last run on mw1041 is CRITICAL: CRITICAL: Epic puppet fail [11:04:15] PROBLEM - puppet last run on amssq59 is CRITICAL: CRITICAL: Puppet has 23 failures [11:04:16] PROBLEM - puppet last run on cp3008 is CRITICAL: CRITICAL: Epic puppet fail [11:04:16] PROBLEM - puppet last run on mw1059 is CRITICAL: CRITICAL: Epic puppet fail [11:04:17] PROBLEM - puppet last run on mw1200 is CRITICAL: CRITICAL: Epic puppet fail [11:04:17] PROBLEM - puppet last run on ms-be1004 is CRITICAL: CRITICAL: Puppet has 20 failures [11:04:18] PROBLEM - puppet last run on mw1031 is CRITICAL: CRITICAL: Puppet has 65 failures [11:04:18] PROBLEM - puppet last run on mw1106 is CRITICAL: CRITICAL: Epic puppet fail [11:04:19] PROBLEM - puppet last run on mw1141 is CRITICAL: CRITICAL: Puppet has 68 failures [11:04:20] PROBLEM - puppet last run on mw1006 is CRITICAL: CRITICAL: Epic puppet fail [11:04:23] PROBLEM - puppet last run on cp4006 is CRITICAL: CRITICAL: Epic puppet fail [11:04:23] PROBLEM - puppet last run on cp3020 is CRITICAL: CRITICAL: Epic puppet fail [11:04:33] PROBLEM - puppet last run on mc1016 is CRITICAL: CRITICAL: Puppet has 23 failures [11:04:33] PROBLEM - puppet last run on helium is CRITICAL: CRITICAL: Epic puppet fail [11:04:54] PROBLEM - puppet last run on analytics1025 is CRITICAL: CRITICAL: Puppet has 19 failures [11:04:54] PROBLEM - puppet last run on wtp1020 is CRITICAL: CRITICAL: Epic puppet fail [11:04:54] PROBLEM - puppet last run on netmon1001 is CRITICAL: CRITICAL: Puppet has 30 failures [11:04:54] PROBLEM - puppet last run on analytics1033 is CRITICAL: CRITICAL: Puppet has 13 failures [11:04:54] PROBLEM - puppet last run on elastic1004 is CRITICAL: CRITICAL: Puppet has 21 failures [11:05:03] PROBLEM - puppet last run on searchidx1001 is CRITICAL: CRITICAL: Epic puppet fail [11:05:03] PROBLEM - puppet last run on mw1063 is CRITICAL: CRITICAL: Puppet has 60 failures [11:05:03] PROBLEM - puppet last run on ms-be1006 is CRITICAL: CRITICAL: Epic puppet fail [11:05:03] PROBLEM - puppet last run on mw1160 is CRITICAL: CRITICAL: Epic puppet fail [11:05:03] PROBLEM - puppet last run on snapshot1003 is CRITICAL: CRITICAL: Epic puppet fail [11:05:03] PROBLEM - puppet last run on analytics1020 is CRITICAL: CRITICAL: Epic puppet fail [11:05:04] PROBLEM - puppet last run on cerium is CRITICAL: CRITICAL: Puppet has 21 failures [11:05:04] PROBLEM - puppet last run on mw1007 is CRITICAL: CRITICAL: Puppet has 54 failures [11:05:04] PROBLEM - puppet last run on magnesium is CRITICAL: CRITICAL: Puppet has 25 failures [11:05:13] PROBLEM - puppet last run on amssq54 is CRITICAL: CRITICAL: Puppet has 18 failures [11:05:13] PROBLEM - puppet last run on mw1197 is CRITICAL: CRITICAL: Puppet has 65 failures [11:05:13] PROBLEM - puppet last run on db1031 is CRITICAL: CRITICAL: Epic puppet fail [11:05:13] PROBLEM - puppet last run on mw1100 is CRITICAL: CRITICAL: Epic puppet fail [11:05:13] PROBLEM - puppet last run on mc1006 is CRITICAL: CRITICAL: Epic puppet fail [11:05:14] PROBLEM - puppet last run on amssq43 is CRITICAL: CRITICAL: Puppet has 17 failures [11:05:14] PROBLEM - puppet last run on amssq61 is CRITICAL: CRITICAL: Epic puppet fail [11:05:14] PROBLEM - puppet last run on ms-be1003 is CRITICAL: CRITICAL: Epic puppet fail [11:05:15] PROBLEM - puppet last run on mw1012 is CRITICAL: CRITICAL: Puppet has 57 failures [11:05:23] PROBLEM - puppet last run on db1053 is CRITICAL: CRITICAL: Puppet has 23 failures [11:05:23] PROBLEM - puppet last run on lvs4002 is CRITICAL: CRITICAL: Puppet has 18 failures [11:05:33] PROBLEM - puppet last run on db1073 is CRITICAL: CRITICAL: Epic puppet fail [11:05:33] PROBLEM - puppet last run on es1008 is CRITICAL: CRITICAL: Puppet has 21 failures [11:05:33] PROBLEM - puppet last run on gold is CRITICAL: CRITICAL: Epic puppet fail [11:05:33] PROBLEM - puppet last run on analytics1017 is CRITICAL: CRITICAL: Puppet has 20 failures [11:05:33] PROBLEM - puppet last run on db73 is CRITICAL: CRITICAL: Puppet has 18 failures [11:05:43] PROBLEM - puppet last run on elastic1001 is CRITICAL: CRITICAL: Puppet has 19 failures [11:05:43] PROBLEM - puppet last run on platinum is CRITICAL: CRITICAL: Puppet has 19 failures [11:05:43] PROBLEM - puppet last run on cp1047 is CRITICAL: CRITICAL: Puppet has 28 failures [11:05:44] PROBLEM - puppet last run on mw1060 is CRITICAL: CRITICAL: Epic puppet fail [11:05:44] PROBLEM - puppet last run on analytics1035 is CRITICAL: CRITICAL: Epic puppet fail [11:05:53] PROBLEM - puppet last run on analytics1040 is CRITICAL: CRITICAL: Puppet has 25 failures [11:05:53] PROBLEM - puppet last run on ssl1002 is CRITICAL: CRITICAL: Puppet has 25 failures [11:05:53] PROBLEM - puppet last run on potassium is CRITICAL: CRITICAL: Puppet has 24 failures [11:05:54] PROBLEM - puppet last run on mw1174 is CRITICAL: CRITICAL: Epic puppet fail [11:05:54] PROBLEM - puppet last run on mw1187 is CRITICAL: CRITICAL: Puppet has 70 failures [11:05:54] PROBLEM - puppet last run on analytics1041 is CRITICAL: CRITICAL: Epic puppet fail [11:05:54] PROBLEM - puppet last run on search1016 is CRITICAL: CRITICAL: Puppet has 51 failures [11:05:54] PROBLEM - puppet last run on cp1055 is CRITICAL: CRITICAL: Epic puppet fail [11:05:55] PROBLEM - puppet last run on mw1217 is CRITICAL: CRITICAL: Epic puppet fail [11:05:56] o_O [11:06:03] PROBLEM - puppet last run on rbf1002 is CRITICAL: CRITICAL: Puppet has 16 failures [11:06:03] PROBLEM - puppet last run on mw1153 is CRITICAL: CRITICAL: Epic puppet fail [11:06:03] PROBLEM - puppet last run on amssq49 is CRITICAL: CRITICAL: Puppet has 18 failures [11:06:03] PROBLEM - puppet last run on wtp1006 is CRITICAL: CRITICAL: Puppet has 19 failures [11:06:13] PROBLEM - puppet last run on mw1046 is CRITICAL: CRITICAL: Epic puppet fail [11:06:13] PROBLEM - puppet last run on db74 is CRITICAL: CRITICAL: Puppet has 15 failures [11:06:13] PROBLEM - puppet last run on mw1164 is CRITICAL: CRITICAL: Puppet has 68 failures [11:06:13] PROBLEM - puppet last run on cp1039 is CRITICAL: CRITICAL: Puppet has 21 failures [11:06:13] PROBLEM - puppet last run on mw1082 is CRITICAL: CRITICAL: Puppet has 65 failures [11:06:13] PROBLEM - puppet last run on mw1026 is CRITICAL: CRITICAL: Puppet has 65 failures [11:06:14] PROBLEM - puppet last run on amssq35 is CRITICAL: CRITICAL: Epic puppet fail [11:06:14] PROBLEM - puppet last run on mc1002 is CRITICAL: CRITICAL: Puppet has 16 failures [11:06:15] PROBLEM - puppet last run on mw1069 is CRITICAL: CRITICAL: Epic puppet fail [11:06:23] PROBLEM - puppet last run on lvs3001 is CRITICAL: CRITICAL: Puppet has 19 failures [11:06:23] PROBLEM - puppet last run on amssq32 is CRITICAL: CRITICAL: Puppet has 15 failures [11:06:23] PROBLEM - puppet last run on amssq53 is CRITICAL: CRITICAL: Puppet has 16 failures [11:06:23] PROBLEM - puppet last run on cp3016 is CRITICAL: CRITICAL: Epic puppet fail [11:06:33] PROBLEM - puppet last run on elastic1008 is CRITICAL: CRITICAL: Epic puppet fail [11:06:33] PROBLEM - puppet last run on ruthenium is CRITICAL: CRITICAL: Epic puppet fail [11:06:33] PROBLEM - puppet last run on elastic1012 is CRITICAL: CRITICAL: Epic puppet fail [11:06:33] PROBLEM - puppet last run on lvs1002 is CRITICAL: CRITICAL: Puppet has 23 failures [11:06:43] PROBLEM - puppet last run on lead is CRITICAL: CRITICAL: Puppet has 22 failures [11:06:43] PROBLEM - puppet last run on db1066 is CRITICAL: CRITICAL: Puppet has 18 failures [11:06:43] PROBLEM - puppet last run on wtp1016 is CRITICAL: CRITICAL: Epic puppet fail [11:06:44] PROBLEM - puppet last run on ms-fe1001 is CRITICAL: CRITICAL: Epic puppet fail [11:06:44] PROBLEM - puppet last run on mc1003 is CRITICAL: CRITICAL: Puppet has 20 failures [11:06:44] PROBLEM - puppet last run on db1022 is CRITICAL: CRITICAL: Puppet has 23 failures [11:06:53] PROBLEM - puppet last run on labsdb1003 is CRITICAL: CRITICAL: Epic puppet fail [11:06:54] PROBLEM - puppet last run on mw1042 is CRITICAL: CRITICAL: Epic puppet fail [11:06:54] PROBLEM - puppet last run on mw1205 is CRITICAL: CRITICAL: Puppet has 66 failures [11:06:54] PROBLEM - puppet last run on mw1189 is CRITICAL: CRITICAL: Puppet has 65 failures [11:06:54] PROBLEM - puppet last run on xenon is CRITICAL: CRITICAL: Puppet has 21 failures [11:06:54] PROBLEM - puppet last run on mw1003 is CRITICAL: CRITICAL: Puppet has 52 failures [11:06:54] PROBLEM - puppet last run on virt1006 is CRITICAL: CRITICAL: Epic puppet fail [11:06:54] PROBLEM - puppet last run on mw1176 is CRITICAL: CRITICAL: Puppet has 66 failures [11:07:03] PROBLEM - puppet last run on ms-fe1004 is CRITICAL: CRITICAL: Puppet has 19 failures [11:07:03] PROBLEM - puppet last run on mw1150 is CRITICAL: CRITICAL: Puppet has 54 failures [11:07:03] PROBLEM - puppet last run on cp1056 is CRITICAL: CRITICAL: Epic puppet fail [11:07:03] PROBLEM - puppet last run on search1010 is CRITICAL: CRITICAL: Puppet has 39 failures [11:07:03] PROBLEM - puppet last run on db1040 is CRITICAL: CRITICAL: Epic puppet fail [11:07:03] PROBLEM - puppet last run on cp3014 is CRITICAL: CRITICAL: Epic puppet fail [11:07:04] PROBLEM - puppet last run on mw1008 is CRITICAL: CRITICAL: Puppet has 49 failures [11:07:13] PROBLEM - puppet last run on mw1120 is CRITICAL: CRITICAL: Puppet has 68 failures [11:07:13] PROBLEM - puppet last run on iron is CRITICAL: CRITICAL: Epic puppet fail [11:07:13] PROBLEM - puppet last run on mw1025 is CRITICAL: CRITICAL: Epic puppet fail [11:07:14] PROBLEM - puppet last run on cp1061 is CRITICAL: CRITICAL: Epic puppet fail [11:07:14] PROBLEM - puppet last run on db1018 is CRITICAL: CRITICAL: Puppet has 22 failures [11:07:14] PROBLEM - puppet last run on mw1144 is CRITICAL: CRITICAL: Epic puppet fail [11:07:14] PROBLEM - puppet last run on db1015 is CRITICAL: CRITICAL: Puppet has 21 failures [11:07:14] PROBLEM - puppet last run on db1050 is CRITICAL: CRITICAL: Puppet has 19 failures [11:07:15] PROBLEM - puppet last run on lvs1005 is CRITICAL: CRITICAL: Puppet has 21 failures [11:07:15] PROBLEM - puppet last run on db1002 is CRITICAL: CRITICAL: Epic puppet fail [11:07:16] PROBLEM - puppet last run on mw1117 is CRITICAL: CRITICAL: Puppet has 65 failures [11:07:16] PROBLEM - puppet last run on mw1088 is CRITICAL: CRITICAL: Puppet has 54 failures [11:07:17] PROBLEM - puppet last run on mw1068 is CRITICAL: CRITICAL: Puppet has 67 failures [11:07:17] PROBLEM - puppet last run on mw1009 is CRITICAL: CRITICAL: Puppet has 47 failures [11:07:34] PROBLEM - puppet last run on mw1170 is CRITICAL: CRITICAL: Epic puppet fail [11:07:34] PROBLEM - puppet last run on db1059 is CRITICAL: CRITICAL: Puppet has 16 failures [11:07:34] PROBLEM - puppet last run on mw1099 is CRITICAL: CRITICAL: Puppet has 68 failures [11:07:34] PROBLEM - puppet last run on mw1092 is CRITICAL: CRITICAL: Puppet has 68 failures [11:07:44] PROBLEM - puppet last run on db1051 is CRITICAL: CRITICAL: Puppet has 27 failures [11:07:44] PROBLEM - puppet last run on mw1173 is CRITICAL: CRITICAL: Puppet has 72 failures [11:07:44] PROBLEM - puppet last run on mw1065 is CRITICAL: CRITICAL: Epic puppet fail [11:07:54] PROBLEM - puppet last run on mw1126 is CRITICAL: CRITICAL: Epic puppet fail [11:07:54] PROBLEM - puppet last run on mw1118 is CRITICAL: CRITICAL: Puppet has 55 failures [11:07:54] PROBLEM - puppet last run on holmium is CRITICAL: CRITICAL: Puppet has 31 failures [11:07:54] PROBLEM - puppet last run on db1067 is CRITICAL: CRITICAL: Epic puppet fail [11:07:54] PROBLEM - puppet last run on mw1211 is CRITICAL: CRITICAL: Epic puppet fail [11:07:54] PROBLEM - puppet last run on mw1166 is CRITICAL: CRITICAL: Puppet has 61 failures [11:08:03] PROBLEM - puppet last run on search1001 is CRITICAL: CRITICAL: Puppet has 43 failures [11:08:03] PROBLEM - puppet last run on db1046 is CRITICAL: CRITICAL: Puppet has 14 failures [11:08:03] PROBLEM - puppet last run on mw1119 is CRITICAL: CRITICAL: Puppet has 60 failures [11:08:03] PROBLEM - puppet last run on amssq46 is CRITICAL: CRITICAL: Epic puppet fail [11:08:03] PROBLEM - puppet last run on cp3003 is CRITICAL: CRITICAL: Puppet has 17 failures [11:08:03] PROBLEM - puppet last run on analytics1030 is CRITICAL: CRITICAL: Puppet has 20 failures [11:08:04] PROBLEM - puppet last run on db1042 is CRITICAL: CRITICAL: Epic puppet fail [11:08:04] PROBLEM - puppet last run on logstash1002 is CRITICAL: CRITICAL: Epic puppet fail [11:08:13] PROBLEM - puppet last run on amslvs1 is CRITICAL: CRITICAL: Epic puppet fail [11:08:13] PROBLEM - puppet last run on mw1061 is CRITICAL: CRITICAL: Puppet has 71 failures [11:08:13] PROBLEM - puppet last run on db1023 is CRITICAL: CRITICAL: Epic puppet fail [11:08:13] PROBLEM - puppet last run on mw1052 is CRITICAL: CRITICAL: Puppet has 60 failures [11:08:14] PROBLEM - puppet last run on search1018 is CRITICAL: CRITICAL: Puppet has 39 failures [11:08:23] PROBLEM - puppet last run on cp4003 is CRITICAL: CRITICAL: Puppet has 18 failures [11:08:23] PROBLEM - puppet last run on cp4004 is CRITICAL: CRITICAL: Epic puppet fail [11:08:23] PROBLEM - puppet last run on cp4008 is CRITICAL: CRITICAL: Puppet has 27 failures [11:08:33] PROBLEM - puppet last run on dbproxy1001 is CRITICAL: CRITICAL: Epic puppet fail [11:08:33] PROBLEM - puppet last run on mw1114 is CRITICAL: CRITICAL: Epic puppet fail [11:08:33] PROBLEM - puppet last run on mw1129 is CRITICAL: CRITICAL: Epic puppet fail [11:08:44] PROBLEM - puppet last run on mw1213 is CRITICAL: CRITICAL: Puppet has 68 failures [11:08:44] PROBLEM - puppet last run on mw1123 is CRITICAL: CRITICAL: Puppet has 73 failures [11:08:53] PROBLEM - puppet last run on analytics1010 is CRITICAL: CRITICAL: Epic puppet fail [11:08:53] PROBLEM - puppet last run on gallium is CRITICAL: CRITICAL: Puppet has 41 failures [11:08:54] PROBLEM - puppet last run on mw1177 is CRITICAL: CRITICAL: Puppet has 59 failures [11:08:54] PROBLEM - puppet last run on pc1002 is CRITICAL: CRITICAL: Epic puppet fail [11:08:54] PROBLEM - puppet last run on mw1206 is CRITICAL: CRITICAL: Epic puppet fail [11:08:54] PROBLEM - puppet last run on mw1172 is CRITICAL: CRITICAL: Puppet has 65 failures [11:08:54] PROBLEM - puppet last run on mc1012 is CRITICAL: CRITICAL: Puppet has 14 failures [11:08:54] PROBLEM - puppet last run on db1034 is CRITICAL: CRITICAL: Puppet has 20 failures [11:08:54] PROBLEM - puppet last run on mw1175 is CRITICAL: CRITICAL: Puppet has 82 failures [11:09:03] PROBLEM - puppet last run on mw1039 is CRITICAL: CRITICAL: Puppet has 54 failures [11:09:03] PROBLEM - puppet last run on mw1054 is CRITICAL: CRITICAL: Puppet has 66 failures [11:09:03] PROBLEM - puppet last run on search1007 is CRITICAL: CRITICAL: Puppet has 55 failures [11:09:03] PROBLEM - puppet last run on cp4014 is CRITICAL: CRITICAL: Epic puppet fail [11:09:03] PROBLEM - puppet last run on db1016 is CRITICAL: CRITICAL: Epic puppet fail [11:09:03] PROBLEM - puppet last run on db1003 is CRITICAL: CRITICAL: Epic puppet fail [11:09:13] PROBLEM - puppet last run on amssq47 is CRITICAL: CRITICAL: Puppet has 16 failures [11:09:13] PROBLEM - puppet last run on cp1058 is CRITICAL: CRITICAL: Epic puppet fail [11:09:13] PROBLEM - puppet last run on mw1149 is CRITICAL: CRITICAL: Epic puppet fail [11:09:13] PROBLEM - puppet last run on analytics1038 is CRITICAL: CRITICAL: Epic puppet fail [11:09:14] PROBLEM - puppet last run on es1007 is CRITICAL: CRITICAL: Puppet has 22 failures [11:09:14] PROBLEM - puppet last run on amssq55 is CRITICAL: CRITICAL: Puppet has 18 failures [11:09:14] PROBLEM - puppet last run on amssq34 is CRITICAL: CRITICAL: Epic puppet fail [11:09:15] PROBLEM - puppet last run on db1021 is CRITICAL: CRITICAL: Puppet has 14 failures [11:09:15] PROBLEM - puppet last run on labstore1001 is CRITICAL: CRITICAL: Puppet has 16 failures [11:09:15] PROBLEM - puppet last run on db1028 is CRITICAL: CRITICAL: Puppet has 21 failures [11:09:16] PROBLEM - puppet last run on mw1002 is CRITICAL: CRITICAL: Puppet has 53 failures [11:09:16] PROBLEM - puppet last run on tin is CRITICAL: CRITICAL: Puppet has 60 failures [11:09:16] PROBLEM - puppet last run on mw1011 is CRITICAL: CRITICAL: Puppet has 56 failures [11:09:17] PROBLEM - puppet last run on mw1208 is CRITICAL: CRITICAL: Epic puppet fail [11:09:23] PROBLEM - puppet last run on cp4019 is CRITICAL: CRITICAL: Epic puppet fail [11:09:23] PROBLEM - puppet last run on amssq60 is CRITICAL: CRITICAL: Puppet has 15 failures [11:09:23] PROBLEM - puppet last run on ms-be3001 is CRITICAL: CRITICAL: Epic puppet fail [11:09:23] PROBLEM - puppet last run on amssq48 is CRITICAL: CRITICAL: Puppet has 24 failures [11:09:33] PROBLEM - puppet last run on polonium is CRITICAL: CRITICAL: Puppet has 22 failures [11:09:33] PROBLEM - puppet last run on wtp1012 is CRITICAL: CRITICAL: Epic puppet fail [11:09:43] PROBLEM - puppet last run on db1052 is CRITICAL: CRITICAL: Puppet has 21 failures [11:09:43] PROBLEM - puppet last run on db1060 is CRITICAL: CRITICAL: Epic puppet fail [11:09:43] PROBLEM - puppet last run on mw1190 is CRITICAL: CRITICAL: Epic puppet fail [11:09:53] PROBLEM - puppet last run on wtp1005 is CRITICAL: CRITICAL: Epic puppet fail [11:09:53] PROBLEM - puppet last run on mc1014 is CRITICAL: CRITICAL: Epic puppet fail [11:09:54] PROBLEM - puppet last run on analytics1013 is CRITICAL: CRITICAL: Epic puppet fail [11:09:54] PROBLEM - puppet last run on mw1162 is CRITICAL: CRITICAL: Puppet has 65 failures [11:09:54] PROBLEM - puppet last run on labnet1001 is CRITICAL: CRITICAL: Puppet has 21 failures [11:09:54] PROBLEM - puppet last run on cp1046 is CRITICAL: CRITICAL: Puppet has 23 failures [11:10:03] PROBLEM - puppet last run on mw1180 is CRITICAL: CRITICAL: Epic puppet fail [11:10:03] PROBLEM - puppet last run on install2001 is CRITICAL: CRITICAL: Puppet has 17 failures [11:10:03] PROBLEM - puppet last run on db1036 is CRITICAL: CRITICAL: Epic puppet fail [11:10:03] PROBLEM - puppet last run on silver is CRITICAL: CRITICAL: Puppet has 31 failures [11:10:03] PROBLEM - puppet last run on db1043 is CRITICAL: CRITICAL: Puppet has 22 failures [11:10:03] PROBLEM - puppet last run on antimony is CRITICAL: CRITICAL: Puppet has 31 failures [11:10:03] PROBLEM - puppet last run on snapshot1001 is CRITICAL: CRITICAL: Puppet has 63 failures [11:10:04] PROBLEM - puppet last run on mw1076 is CRITICAL: CRITICAL: Puppet has 59 failures [11:10:04] PROBLEM - puppet last run on analytics1016 is CRITICAL: CRITICAL: Puppet has 15 failures [11:10:05] PROBLEM - puppet last run on analytics1026 is CRITICAL: CRITICAL: Epic puppet fail [11:10:05] PROBLEM - puppet last run on mw1195 is CRITICAL: CRITICAL: Puppet has 66 failures [11:10:13] PROBLEM - puppet last run on ms-be3002 is CRITICAL: CRITICAL: Puppet has 21 failures [11:10:13] PROBLEM - puppet last run on mw1098 is CRITICAL: CRITICAL: Epic puppet fail [11:10:13] PROBLEM - puppet last run on snapshot1002 is CRITICAL: CRITICAL: Epic puppet fail [11:10:13] PROBLEM - puppet last run on lvs4003 is CRITICAL: CRITICAL: Epic puppet fail [11:10:13] PROBLEM - puppet last run on search1002 is CRITICAL: CRITICAL: Puppet has 45 failures [11:10:14] PROBLEM - puppet last run on search1005 is CRITICAL: CRITICAL: Epic puppet fail [11:10:14] PROBLEM - puppet last run on mw1051 is CRITICAL: CRITICAL: Epic puppet fail [11:10:14] PROBLEM - puppet last run on db1039 is CRITICAL: CRITICAL: Epic puppet fail [11:10:14] PROBLEM - puppet last run on mw1202 is CRITICAL: CRITICAL: Epic puppet fail [11:10:15] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [11:10:15] PROBLEM - puppet last run on mw1055 is CRITICAL: CRITICAL: Puppet has 61 failures [11:10:23] PROBLEM - puppet last run on bast4001 is CRITICAL: CRITICAL: Epic puppet fail [11:10:23] PROBLEM - puppet last run on cp4001 is CRITICAL: CRITICAL: Puppet has 30 failures [11:10:23] PROBLEM - puppet last run on cp4005 is CRITICAL: CRITICAL: Epic puppet fail [11:10:23] PROBLEM - puppet last run on cp4018 is CRITICAL: CRITICAL: Epic puppet fail [11:10:24] PROBLEM - puppet last run on cp3010 is CRITICAL: CRITICAL: Puppet has 19 failures [11:10:24] PROBLEM - puppet last run on hooft is CRITICAL: CRITICAL: Epic puppet fail [11:10:33] PROBLEM - puppet last run on mw1044 is CRITICAL: CRITICAL: Puppet has 70 failures [11:10:33] PROBLEM - puppet last run on db1048 is CRITICAL: CRITICAL: Puppet has 14 failures [11:10:33] PROBLEM - puppet last run on mw1151 is CRITICAL: CRITICAL: Puppet has 72 failures [11:10:34] PROBLEM - puppet last run on ssl1005 is CRITICAL: CRITICAL: Puppet has 19 failures [11:10:34] PROBLEM - puppet last run on mw1125 is CRITICAL: CRITICAL: Epic puppet fail [11:10:34] PROBLEM - puppet last run on cp1050 is CRITICAL: CRITICAL: Epic puppet fail [11:10:34] PROBLEM - puppet last run on db1026 is CRITICAL: CRITICAL: Puppet has 18 failures [11:10:43] PROBLEM - puppet last run on cp1063 is CRITICAL: CRITICAL: Epic puppet fail [11:10:43] PROBLEM - puppet last run on db69 is CRITICAL: CRITICAL: Epic puppet fail [11:10:43] PROBLEM - puppet last run on mw1030 is CRITICAL: CRITICAL: Epic puppet fail [11:10:44] PROBLEM - puppet last run on db1069 is CRITICAL: CRITICAL: Epic puppet fail [11:10:54] PROBLEM - puppet last run on search1017 is CRITICAL: CRITICAL: Epic puppet fail [11:10:54] PROBLEM - puppet last run on db1071 is CRITICAL: CRITICAL: Epic puppet fail [11:10:54] PROBLEM - puppet last run on wtp1018 is CRITICAL: CRITICAL: Epic puppet fail [11:10:54] PROBLEM - puppet last run on virt1004 is CRITICAL: CRITICAL: Puppet has 20 failures [11:10:54] PROBLEM - puppet last run on mw1168 is CRITICAL: CRITICAL: Puppet has 53 failures [11:10:54] PROBLEM - puppet last run on mw1156 is CRITICAL: CRITICAL: Epic puppet fail [11:10:55] PROBLEM - puppet last run on mc1005 is CRITICAL: CRITICAL: Puppet has 21 failures [11:10:55] PROBLEM - puppet last run on mw1014 is CRITICAL: CRITICAL: Puppet has 46 failures [11:10:56] PROBLEM - puppet last run on labsdb1006 is CRITICAL: CRITICAL: Epic puppet fail [11:10:56] PROBLEM - puppet last run on mw1183 is CRITICAL: CRITICAL: Epic puppet fail [11:11:03] PROBLEM - puppet last run on rubidium is CRITICAL: CRITICAL: Epic puppet fail [11:11:03] PROBLEM - puppet last run on mw1111 is CRITICAL: CRITICAL: Puppet has 60 failures [11:11:03] PROBLEM - puppet last run on gadolinium is CRITICAL: CRITICAL: Epic puppet fail [11:11:03] PROBLEM - puppet last run on rdb1001 is CRITICAL: CRITICAL: Epic puppet fail [11:11:03] PROBLEM - puppet last run on elastic1015 is CRITICAL: CRITICAL: Puppet has 22 failures [11:11:03] PROBLEM - puppet last run on stat1002 is CRITICAL: CRITICAL: Epic puppet fail [11:11:04] PROBLEM - puppet last run on mw1049 is CRITICAL: CRITICAL: Puppet has 62 failures [11:11:04] PROBLEM - puppet last run on labmon1001 is CRITICAL: CRITICAL: Puppet has 22 failures [11:11:05] PROBLEM - puppet last run on mw1133 is CRITICAL: CRITICAL: Puppet has 59 failures [11:11:13] PROBLEM - puppet last run on lvs3004 is CRITICAL: CRITICAL: Puppet has 19 failures [11:11:13] PROBLEM - puppet last run on ms-fe3002 is CRITICAL: CRITICAL: Epic puppet fail [11:11:13] PROBLEM - puppet last run on amssq51 is CRITICAL: CRITICAL: Puppet has 24 failures [11:11:13] PROBLEM - puppet last run on virt1001 is CRITICAL: CRITICAL: Puppet has 20 failures [11:11:13] PROBLEM - puppet last run on amssq36 is CRITICAL: CRITICAL: Puppet has 19 failures [11:11:13] PROBLEM - puppet last run on virt1003 is CRITICAL: CRITICAL: Puppet has 31 failures [11:11:13] PROBLEM - puppet last run on mw1079 is CRITICAL: CRITICAL: Puppet has 49 failures [11:11:14] PROBLEM - puppet last run on ssl1009 is CRITICAL: CRITICAL: Epic puppet fail [11:11:14] PROBLEM - puppet last run on rhenium is CRITICAL: CRITICAL: Puppet has 22 failures [11:11:15] PROBLEM - puppet last run on cp1048 is CRITICAL: CRITICAL: Epic puppet fail [11:11:16] PROBLEM - puppet last run on elastic1006 is CRITICAL: CRITICAL: Puppet has 25 failures [11:11:16] PROBLEM - puppet last run on mw1146 is CRITICAL: CRITICAL: Epic puppet fail [11:11:17] PROBLEM - puppet last run on mw1050 is CRITICAL: CRITICAL: Epic puppet fail [11:11:17] PROBLEM - puppet last run on mw1084 is CRITICAL: CRITICAL: Puppet has 73 failures [11:11:17] PROBLEM - puppet last run on ms-be1008 is CRITICAL: CRITICAL: Epic puppet fail [11:11:19] PROBLEM - puppet last run on mw1034 is CRITICAL: CRITICAL: Epic puppet fail [11:11:19] PROBLEM - puppet last run on analytics1022 is CRITICAL: CRITICAL: Puppet has 23 failures [11:11:23] PROBLEM - puppet last run on amssq40 is CRITICAL: CRITICAL: Puppet has 28 failures [11:11:24] PROBLEM - puppet last run on ssl3002 is CRITICAL: CRITICAL: Epic puppet fail [11:11:33] PROBLEM - puppet last run on hafnium is CRITICAL: CRITICAL: Puppet has 23 failures [11:11:33] PROBLEM - puppet last run on wtp1023 is CRITICAL: CRITICAL: Epic puppet fail [11:11:33] PROBLEM - puppet last run on mw1165 is CRITICAL: CRITICAL: Puppet has 56 failures [11:11:33] PROBLEM - puppet last run on mw1181 is CRITICAL: CRITICAL: Epic puppet fail [11:11:34] PROBLEM - puppet last run on argon is CRITICAL: CRITICAL: Puppet has 27 failures [11:11:43] PROBLEM - puppet last run on virt1007 is CRITICAL: CRITICAL: Epic puppet fail [11:11:43] PROBLEM - puppet last run on cp1062 is CRITICAL: CRITICAL: Puppet has 21 failures [11:11:43] PROBLEM - puppet last run on tungsten is CRITICAL: CRITICAL: Epic puppet fail [11:11:44] PROBLEM - puppet last run on wtp1004 is CRITICAL: CRITICAL: Puppet has 13 failures [11:11:44] PROBLEM - puppet last run on analytics1023 is CRITICAL: CRITICAL: Puppet has 20 failures [11:11:44] PROBLEM - puppet last run on mw1056 is CRITICAL: CRITICAL: Puppet has 64 failures [11:11:44] PROBLEM - puppet last run on mw1081 is CRITICAL: CRITICAL: Epic puppet fail [11:11:53] PROBLEM - puppet last run on oxygen is CRITICAL: CRITICAL: Epic puppet fail [11:11:53] PROBLEM - puppet last run on analytics1037 is CRITICAL: CRITICAL: Puppet has 21 failures [11:11:53] PROBLEM - puppet last run on lvs1001 is CRITICAL: CRITICAL: Epic puppet fail [11:11:54] PROBLEM - puppet last run on mw1116 is CRITICAL: CRITICAL: Epic puppet fail [11:11:54] PROBLEM - puppet last run on mw1198 is CRITICAL: CRITICAL: Epic puppet fail [11:11:54] PROBLEM - puppet last run on thallium is CRITICAL: CRITICAL: Puppet has 16 failures [11:11:54] PROBLEM - puppet last run on db1055 is CRITICAL: CRITICAL: Puppet has 21 failures [11:12:03] PROBLEM - puppet last run on analytics1032 is CRITICAL: CRITICAL: Puppet has 17 failures [11:12:03] PROBLEM - puppet last run on mw1057 is CRITICAL: CRITICAL: Puppet has 67 failures [11:12:03] PROBLEM - puppet last run on db1004 is CRITICAL: CRITICAL: Puppet has 21 failures [11:12:03] PROBLEM - puppet last run on ms-be1007 is CRITICAL: CRITICAL: Puppet has 22 failures [11:12:03] PROBLEM - puppet last run on mc1001 is CRITICAL: CRITICAL: Epic puppet fail [11:12:03] PROBLEM - puppet last run on ms-be1012 is CRITICAL: CRITICAL: Puppet has 23 failures [11:12:03] PROBLEM - puppet last run on amssq56 is CRITICAL: CRITICAL: Puppet has 23 failures [11:12:04] PROBLEM - puppet last run on db1020 is CRITICAL: CRITICAL: Epic puppet fail [11:12:05] PROBLEM - puppet last run on wtp1002 is CRITICAL: CRITICAL: Epic puppet fail [11:12:13] PROBLEM - puppet last run on mw1212 is CRITICAL: CRITICAL: Puppet has 64 failures [11:12:13] PROBLEM - puppet last run on mw1074 is CRITICAL: CRITICAL: Epic puppet fail [11:12:14] PROBLEM - puppet last run on elastic1011 is CRITICAL: CRITICAL: Puppet has 15 failures [11:12:14] PROBLEM - puppet last run on db1001 is CRITICAL: CRITICAL: Epic puppet fail [11:12:14] PROBLEM - puppet last run on elastic1014 is CRITICAL: CRITICAL: Epic puppet fail [11:12:14] PROBLEM - puppet last run on mw1004 is CRITICAL: CRITICAL: Puppet has 48 failures [11:12:23] PROBLEM - puppet last run on amssq41 is CRITICAL: CRITICAL: Puppet has 19 failures [11:12:33] PROBLEM - puppet last run on wtp1011 is CRITICAL: CRITICAL: Epic puppet fail [11:12:33] PROBLEM - puppet last run on snapshot1004 is CRITICAL: CRITICAL: Puppet has 59 failures [11:12:33] PROBLEM - puppet last run on db1062 is CRITICAL: CRITICAL: Puppet has 23 failures [11:12:43] PROBLEM - puppet last run on db72 is CRITICAL: CRITICAL: Puppet has 19 failures [11:12:44] PROBLEM - puppet last run on mc1013 is CRITICAL: CRITICAL: Puppet has 21 failures [11:12:53] PROBLEM - puppet last run on wtp1022 is CRITICAL: CRITICAL: Puppet has 17 failures [11:12:53] PROBLEM - puppet last run on db1057 is CRITICAL: CRITICAL: Epic puppet fail [11:12:53] PROBLEM - puppet last run on ms-be1009 is CRITICAL: CRITICAL: Puppet has 21 failures [11:12:53] PROBLEM - puppet last run on mw1171 is CRITICAL: CRITICAL: Puppet has 51 failures [11:12:54] PROBLEM - puppet last run on mw1210 is CRITICAL: CRITICAL: Puppet has 71 failures [11:12:54] PROBLEM - puppet last run on titanium is CRITICAL: CRITICAL: Puppet has 23 failures [11:12:54] PROBLEM - puppet last run on cp1060 is CRITICAL: CRITICAL: Epic puppet fail [11:12:54] PROBLEM - puppet last run on mw1188 is CRITICAL: CRITICAL: Puppet has 68 failures [11:13:03] PROBLEM - puppet last run on es1002 is CRITICAL: CRITICAL: Puppet has 22 failures [11:13:03] PROBLEM - puppet last run on rdb1002 is CRITICAL: CRITICAL: Puppet has 18 failures [11:13:03] PROBLEM - puppet last run on cp1038 is CRITICAL: CRITICAL: Puppet has 17 failures [11:13:03] PROBLEM - puppet last run on mw1097 is CRITICAL: CRITICAL: Epic puppet fail [11:13:03] PROBLEM - puppet last run on mw1159 is CRITICAL: CRITICAL: Puppet has 69 failures [11:13:03] PROBLEM - puppet last run on mc1007 is CRITICAL: CRITICAL: Epic puppet fail [11:13:04] PROBLEM - puppet last run on mw1023 is CRITICAL: CRITICAL: Puppet has 76 failures [11:13:04] PROBLEM - puppet last run on mw1029 is CRITICAL: CRITICAL: Puppet has 60 failures [11:13:04] PROBLEM - puppet last run on amslvs3 is CRITICAL: CRITICAL: Epic puppet fail [11:13:05] PROBLEM - puppet last run on amssq42 is CRITICAL: CRITICAL: Puppet has 19 failures [11:13:05] PROBLEM - puppet last run on analytics1014 is CRITICAL: CRITICAL: Puppet has 19 failures [11:13:06] PROBLEM - puppet last run on db1054 is CRITICAL: CRITICAL: Epic puppet fail [11:13:17] PROBLEM - puppet last run on search1024 is CRITICAL: CRITICAL: Puppet has 38 failures [11:13:17] PROBLEM - puppet last run on search1023 is CRITICAL: CRITICAL: Puppet has 49 failures [11:13:17] PROBLEM - puppet last run on protactinium is CRITICAL: CRITICAL: Puppet has 16 failures [11:13:17] PROBLEM - puppet last run on elastic1005 is CRITICAL: CRITICAL: Puppet has 22 failures [11:13:17] PROBLEM - puppet last run on search1015 is CRITICAL: CRITICAL: Epic puppet fail [11:13:17] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.093 second response time [11:13:17] PROBLEM - puppet last run on mw1087 is CRITICAL: CRITICAL: Puppet has 59 failures [11:13:24] PROBLEM - puppet last run on cp3012 is CRITICAL: CRITICAL: Puppet has 21 failures [11:13:24] PROBLEM - puppet last run on amssq62 is CRITICAL: CRITICAL: Puppet has 16 failures [11:13:24] PROBLEM - puppet last run on cp3009 is CRITICAL: CRITICAL: Epic puppet fail [11:13:34] PROBLEM - puppet last run on labsdb1004 is CRITICAL: CRITICAL: Puppet has 16 failures [11:13:34] PROBLEM - puppet last run on db1063 is CRITICAL: CRITICAL: Epic puppet fail [11:13:43] PROBLEM - puppet last run on db1070 is CRITICAL: CRITICAL: Puppet has 22 failures [11:13:43] PROBLEM - puppet last run on ssl1008 is CRITICAL: CRITICAL: Puppet has 16 failures [11:13:44] PROBLEM - puppet last run on db1064 is CRITICAL: CRITICAL: Epic puppet fail [11:13:44] PROBLEM - puppet last run on wtp1015 is CRITICAL: CRITICAL: Puppet has 21 failures [11:13:44] PROBLEM - puppet last run on rcs1001 is CRITICAL: CRITICAL: Puppet has 24 failures [11:13:53] PROBLEM - puppet last run on elastic1002 is CRITICAL: CRITICAL: Epic puppet fail [11:13:53] PROBLEM - puppet last run on ssl1007 is CRITICAL: CRITICAL: Epic puppet fail [11:13:54] PROBLEM - puppet last run on wtp1013 is CRITICAL: CRITICAL: Puppet has 19 failures [11:13:54] PROBLEM - puppet last run on nitrogen is CRITICAL: CRITICAL: Epic puppet fail [11:13:54] PROBLEM - puppet last run on mw1186 is CRITICAL: CRITICAL: Epic puppet fail [11:13:54] PROBLEM - puppet last run on mw1001 is CRITICAL: CRITICAL: Epic puppet fail [11:13:54] PROBLEM - puppet last run on mw1167 is CRITICAL: CRITICAL: Epic puppet fail [11:14:03] PROBLEM - puppet last run on wtp1003 is CRITICAL: CRITICAL: Puppet has 26 failures [11:14:03] PROBLEM - puppet last run on rdb1003 is CRITICAL: CRITICAL: Epic puppet fail [11:14:03] PROBLEM - puppet last run on mw1022 is CRITICAL: CRITICAL: Epic puppet fail [11:14:03] PROBLEM - puppet last run on analytics1011 is CRITICAL: CRITICAL: Puppet has 23 failures [11:14:13] PROBLEM - puppet last run on wtp1007 is CRITICAL: CRITICAL: Epic puppet fail [11:14:13] PROBLEM - puppet last run on mw1032 is CRITICAL: CRITICAL: Puppet has 70 failures [11:14:13] PROBLEM - puppet last run on mw1148 is CRITICAL: CRITICAL: Puppet has 68 failures [11:14:13] PROBLEM - puppet last run on cp3004 is CRITICAL: CRITICAL: Epic puppet fail [11:14:13] PROBLEM - puppet last run on db1044 is CRITICAL: CRITICAL: Puppet has 19 failures [11:14:13] PROBLEM - puppet last run on ms-fe3001 is CRITICAL: CRITICAL: Epic puppet fail [11:14:14] PROBLEM - puppet last run on mw1121 is CRITICAL: CRITICAL: Puppet has 60 failures [11:14:14] PROBLEM - puppet last run on mw1043 is CRITICAL: CRITICAL: Epic puppet fail [11:14:15] PROBLEM - puppet last run on ocg1003 is CRITICAL: CRITICAL: Epic puppet fail [11:14:15] PROBLEM - puppet last run on rcs1002 is CRITICAL: CRITICAL: Puppet has 29 failures [11:14:16] PROBLEM - puppet last run on db1011 is CRITICAL: CRITICAL: Epic puppet fail [11:14:23] PROBLEM - puppet last run on sanger is CRITICAL: CRITICAL: Epic puppet fail [11:14:33] PROBLEM - puppet last run on mw1201 is CRITICAL: CRITICAL: Puppet has 65 failures [11:14:44] PROBLEM - puppet last run on mw1185 is CRITICAL: CRITICAL: Puppet has 78 failures [11:14:44] PROBLEM - puppet last run on mw1219 is CRITICAL: CRITICAL: Epic puppet fail [11:14:53] PROBLEM - puppet last run on ssl1001 is CRITICAL: CRITICAL: Epic puppet fail [11:14:54] PROBLEM - puppet last run on cp1037 is CRITICAL: CRITICAL: Epic puppet fail [11:14:54] PROBLEM - puppet last run on elastic1017 is CRITICAL: CRITICAL: Epic puppet fail [11:15:03] PROBLEM - puppet last run on pc1003 is CRITICAL: CRITICAL: Puppet has 30 failures [11:15:03] PROBLEM - puppet last run on cp1052 is CRITICAL: CRITICAL: Epic puppet fail [11:15:03] PROBLEM - puppet last run on db1030 is CRITICAL: CRITICAL: Puppet has 20 failures [11:15:03] PROBLEM - puppet last run on mw1024 is CRITICAL: CRITICAL: Puppet has 69 failures [11:15:03] PROBLEM - puppet last run on search1013 is CRITICAL: CRITICAL: Epic puppet fail [11:15:03] PROBLEM - puppet last run on db1033 is CRITICAL: CRITICAL: Epic puppet fail [11:15:04] PROBLEM - puppet last run on virt1000 is CRITICAL: CRITICAL: Puppet has 45 failures [11:15:04] PROBLEM - puppet last run on es1010 is CRITICAL: CRITICAL: Epic puppet fail [11:15:05] PROBLEM - puppet last run on mercury is CRITICAL: CRITICAL: Epic puppet fail [11:15:13] PROBLEM - puppet last run on mw1122 is CRITICAL: CRITICAL: Puppet has 56 failures [11:15:13] PROBLEM - puppet last run on amssq38 is CRITICAL: CRITICAL: Puppet has 20 failures [11:15:13] PROBLEM - puppet last run on mw1033 is CRITICAL: CRITICAL: Puppet has 55 failures [11:15:13] PROBLEM - puppet last run on db1006 is CRITICAL: CRITICAL: Puppet has 23 failures [11:15:13] PROBLEM - puppet last run on ms-be1011 is CRITICAL: CRITICAL: Epic puppet fail [11:15:13] PROBLEM - puppet last run on db1038 is CRITICAL: CRITICAL: Epic puppet fail [11:15:14] PROBLEM - puppet last run on mw1077 is CRITICAL: CRITICAL: Puppet has 72 failures [11:15:14] PROBLEM - puppet last run on mw1108 is CRITICAL: CRITICAL: Puppet has 69 failures [11:15:14] PROBLEM - puppet last run on stat1003 is CRITICAL: CRITICAL: Puppet has 48 failures [11:15:33] PROBLEM - puppet last run on mw1209 is CRITICAL: CRITICAL: Puppet has 63 failures [11:15:33] PROBLEM - puppet last run on mw1091 is CRITICAL: CRITICAL: Puppet has 57 failures [11:15:33] PROBLEM - puppet last run on search1006 is CRITICAL: CRITICAL: Epic puppet fail [11:15:33] PROBLEM - puppet last run on dbstore1002 is CRITICAL: CRITICAL: Puppet has 18 failures [11:15:34] PROBLEM - puppet last run on calcium is CRITICAL: CRITICAL: Puppet has 21 failures [11:15:43] PROBLEM - puppet last run on analytics1027 is CRITICAL: CRITICAL: Puppet has 17 failures [11:15:43] PROBLEM - puppet last run on db1061 is CRITICAL: CRITICAL: Epic puppet fail [11:15:44] PROBLEM - puppet last run on ssl1006 is CRITICAL: CRITICAL: Puppet has 16 failures [11:15:44] PROBLEM - puppet last run on mw1105 is CRITICAL: CRITICAL: Puppet has 65 failures [11:15:44] PROBLEM - puppet last run on analytics1028 is CRITICAL: CRITICAL: Epic puppet fail [11:15:53] PROBLEM - puppet last run on analytics1004 is CRITICAL: CRITICAL: Puppet has 28 failures [11:15:54] PROBLEM - puppet last run on fluorine is CRITICAL: CRITICAL: Puppet has 69 failures [11:16:13] PROBLEM - puppet last run on mw1139 is CRITICAL: CRITICAL: Puppet has 75 failures [11:16:13] PROBLEM - puppet last run on db1047 is CRITICAL: CRITICAL: Puppet has 20 failures [11:16:14] PROBLEM - puppet last run on search1011 is CRITICAL: CRITICAL: Puppet has 54 failures [11:22:13] RECOVERY - puppet last run on ms1001 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [11:24:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [11:24:53] PROBLEM - puppet last run on tridge is CRITICAL: CRITICAL: Epic puppet fail [11:25:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.071 second response time [11:26:33] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: Epic puppet fail [11:29:13] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: Epic puppet fail [11:34:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [11:36:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.043 second response time [11:40:13] PROBLEM - HTTP error ratio anomaly detection on labmon1001 is CRITICAL: CRITICAL: Anomaly detected: 10 data above and 0 below the confidence bounds [11:40:24] PROBLEM - HTTP error ratio anomaly detection on tungsten is CRITICAL: CRITICAL: Anomaly detected: 10 data above and 0 below the confidence bounds [11:41:23] PROBLEM - puppet last run on es4 is CRITICAL: CRITICAL: Epic puppet fail [11:43:13] PROBLEM - puppet last run on ms1001 is CRITICAL: CRITICAL: Epic puppet fail [11:44:33] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [11:48:13] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [11:50:44] PROBLEM - puppet last run on nfs1 is CRITICAL: CRITICAL: Epic puppet fail [11:54:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [12:00:13] PROBLEM - puppet last run on nickel is CRITICAL: CRITICAL: Epic puppet fail [12:01:13] RECOVERY - puppet last run on ms1001 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [12:03:53] RECOVERY - puppet last run on tridge is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [12:05:33] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: Epic puppet fail [12:09:13] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: Epic puppet fail [12:09:14] PROBLEM - puppet last run on sodium is CRITICAL: CRITICAL: Epic puppet fail [12:13:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [12:15:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.071 second response time [12:18:13] RECOVERY - puppet last run on nickel is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [12:18:43] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:18:04 UTC [12:23:13] PROBLEM - puppet last run on ms1001 is CRITICAL: CRITICAL: Epic puppet fail [12:24:53] PROBLEM - puppet last run on tridge is CRITICAL: CRITICAL: Epic puppet fail [12:25:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [12:25:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [12:26:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.099 second response time [12:28:13] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [12:30:14] RECOVERY - puppet last run on sodium is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [12:30:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [12:32:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.091 second response time [12:32:23] RECOVERY - puppet last run on sanger is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [12:59:40] RECOVERY - puppet last run on es4 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [12:59:41] PROBLEM - Puppet freshness on mw1138 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:39:27 UTC [12:59:41] RECOVERY - puppet last run on ms1001 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [12:59:41] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [12:59:41] RECOVERY - puppet last run on tridge is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [12:59:41] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.042 second response time [12:59:41] PROBLEM - Puppet freshness on analytics1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:45:42 UTC [12:59:41] RECOVERY - puppet last run on nfs1 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [12:59:41] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: Epic puppet fail [12:59:41] PROBLEM - Puppet freshness on ms-be1008 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:49:25 UTC [12:59:41] PROBLEM - Puppet freshness on amssq37 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:54:39 UTC [13:00:13] PROBLEM - puppet last run on nickel is CRITICAL: CRITICAL: Epic puppet fail [13:00:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [13:01:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.065 second response time [13:01:23] PROBLEM - puppet last run on es4 is CRITICAL: CRITICAL: Epic puppet fail [13:03:43] PROBLEM - Puppet freshness on ssl1002 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:03:08 UTC [13:11:38] RECOVERY - Puppet freshness on analytics1010 is OK: puppet ran at Sun Aug 31 13:05:33 UTC 2014 [13:11:38] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [13:11:38] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [13:11:38] PROBLEM - Puppet freshness on lvs3004 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:07:45 UTC [13:11:38] RECOVERY - Puppet freshness on ms-be1008 is OK: puppet ran at Sun Aug 31 13:09:15 UTC 2014 [13:12:43] PROBLEM - puppet last run on sodium is CRITICAL: CRITICAL: Epic puppet fail [13:14:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.038 second response time [13:14:23] PROBLEM - puppet last run on sanger is CRITICAL: CRITICAL: Epic puppet fail [13:14:44] RECOVERY - Puppet freshness on amssq37 is OK: puppet ran at Sun Aug 31 13:14:42 UTC 2014 [13:15:43] PROBLEM - Puppet freshness on db1037 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:15:29 UTC [13:16:53] PROBLEM - puppet last run on linne is CRITICAL: CRITICAL: Epic puppet fail [13:17:14] RECOVERY - HTTP error ratio anomaly detection on labmon1001 is OK: OK: No anomaly detected [13:17:23] RECOVERY - HTTP error ratio anomaly detection on tungsten is OK: OK: No anomaly detected [13:19:33] RECOVERY - Puppet freshness on mw1138 is OK: puppet ran at Sun Aug 31 13:19:28 UTC 2014 [13:21:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [13:22:43] PROBLEM - Puppet freshness on db1065 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:21:41 UTC [13:23:43] PROBLEM - Puppet freshness on snapshot1003 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:22:52 UTC [13:24:33] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [13:27:13] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.104 second response time [13:28:43] PROBLEM - Puppet freshness on oxygen is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:28:29 UTC [13:29:13] RECOVERY - Puppet freshness on oxygen is OK: puppet ran at Sun Aug 31 13:29:07 UTC 2014 [13:29:43] PROBLEM - Puppet freshness on mw1030 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:28:49 UTC [13:29:43] PROBLEM - puppet last run on nfs1 is CRITICAL: CRITICAL: Epic puppet fail [13:33:43] PROBLEM - Puppet freshness on mw1152 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:33:11 UTC [13:33:46] RECOVERY - Puppet freshness on mw1152 is OK: puppet ran at Sun Aug 31 13:33:39 UTC 2014 [13:34:53] RECOVERY - puppet last run on linne is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [13:36:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [13:37:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.128 second response time [13:41:33] RECOVERY - Puppet freshness on db1065 is OK: puppet ran at Sun Aug 31 13:41:27 UTC 2014 [13:42:14] PROBLEM - puppetmaster https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8140: HTTP/1.1 500 Internal Server Error [13:42:43] PROBLEM - Puppet freshness on mw1059 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:41:55 UTC [13:42:53] RECOVERY - Puppet freshness on snapshot1003 is OK: puppet ran at Sun Aug 31 13:42:43 UTC 2014 [13:43:43] PROBLEM - Puppet freshness on elastic1001 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:43:00 UTC [13:43:43] PROBLEM - Puppet freshness on analytics1040 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:43:20 UTC [13:44:14] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.051 second response time [13:44:53] PROBLEM - puppet last run on tridge is CRITICAL: CRITICAL: Epic puppet fail [13:45:33] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: Epic puppet fail [13:47:43] PROBLEM - Puppet freshness on amssq34 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:47:12 UTC [13:48:43] PROBLEM - Puppet freshness on amssq56 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:48:28 UTC [13:48:43] PROBLEM - Puppet freshness on install2001 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:47:42 UTC [13:48:43] RECOVERY - puppet last run on nfs1 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [13:49:13] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: Epic puppet fail [13:49:23] RECOVERY - Puppet freshness on mw1030 is OK: puppet ran at Sun Aug 31 13:49:15 UTC 2014 [13:52:43] PROBLEM - Puppet freshness on mw1077 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:51:54 UTC [13:53:23] RECOVERY - puppet last run on sanger is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [13:53:43] PROBLEM - Puppet freshness on cp1037 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:53:30 UTC [13:53:43] PROBLEM - Puppet freshness on dbstore1002 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:53:10 UTC [13:55:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [13:56:43] PROBLEM - Puppet freshness on bast2001 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 11:55:51 UTC [13:59:23] RECOVERY - puppet last run on es4 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:03:33] RECOVERY - Puppet freshness on analytics1040 is OK: puppet ran at Sun Aug 31 14:03:26 UTC 2014 [14:04:34] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:04:43] PROBLEM - Puppet freshness on mw1026 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:03:39 UTC [14:07:13] RECOVERY - Puppet freshness on install2001 is OK: puppet ran at Sun Aug 31 14:07:03 UTC 2014 [14:07:43] PROBLEM - Puppet freshness on pc1002 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:07:18 UTC [14:09:43] PROBLEM - puppet last run on nfs1 is CRITICAL: CRITICAL: Epic puppet fail [14:10:14] RECOVERY - puppet last run on sodium is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:12:13] RECOVERY - Puppet freshness on mw1077 is OK: puppet ran at Sun Aug 31 14:12:05 UTC 2014 [14:13:03] RECOVERY - Puppet freshness on dbstore1002 is OK: puppet ran at Sun Aug 31 14:13:00 UTC 2014 [14:14:43] PROBLEM - Puppet freshness on amssq39 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:14:01 UTC [14:14:43] RECOVERY - Puppet freshness on amssq39 is OK: puppet ran at Sun Aug 31 14:14:36 UTC 2014 [14:15:13] RECOVERY - Puppet freshness on db1037 is OK: puppet ran at Sun Aug 31 14:15:06 UTC 2014 [14:18:13] RECOVERY - puppet last run on nickel is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:19:43] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:18:04 UTC [14:21:43] PROBLEM - Puppet freshness on amssq59 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:21:29 UTC [14:21:53] RECOVERY - Puppet freshness on mw1059 is OK: puppet ran at Sun Aug 31 14:21:49 UTC 2014 [14:22:18] so this isn't the first chunk of these this weekend ^ [14:22:25] wtf is going on? [14:22:43] PROBLEM - Puppet freshness on db1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:21:34 UTC [14:23:13] PROBLEM - puppet last run on ms1001 is CRITICAL: CRITICAL: Epic puppet fail [14:23:23] RECOVERY - Puppet freshness on mw1026 is OK: puppet ran at Sun Aug 31 14:23:20 UTC 2014 [14:23:28] bblack: puppet is likely having a bad weekend :p [14:23:43] PROBLEM - Puppet freshness on mw1160 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:23:25 UTC [14:23:53] RECOVERY - puppet last run on tridge is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:24:37] it's annoying and spammy [14:25:33] we need to refresh our puppets [14:25:34] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: Epic puppet fail [14:25:41] bblack: in that case; wait for freenode to kline icinga-wm with the reason 'spam is offtopic on freenode' ;) but in all seriousness - yeah. Puppet seems to be a bit iffy this weekend. [14:26:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [14:26:43] RECOVERY - Puppet freshness on pc1002 is OK: puppet ran at Sun Aug 31 14:26:36 UTC 2014 [14:27:06] tunsten is oom and swapping is the issue [14:27:15] *tungsten [14:27:24] RECOVERY - Puppet freshness on amssq34 is OK: puppet ran at Sun Aug 31 14:27:22 UTC 2014 [14:27:32] prbably the maxreqs bump was too much for it, given ruby's leak rate :( [14:27:43] RECOVERY - Puppet freshness on lvs3004 is OK: puppet ran at Sun Aug 31 14:27:37 UTC 2014 [14:28:13] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:28:43] RECOVERY - Puppet freshness on amssq56 is OK: puppet ran at Sun Aug 31 14:28:33 UTC 2014 [14:28:46] wait tungsten does graphite/gdash/etc as well? [14:28:49] is that new? [14:32:24] PROBLEM - gdash.wikimedia.org on tungsten is CRITICAL: Connection refused [14:32:33] PROBLEM - graphite.wikimedia.org on tungsten is CRITICAL: Connection refused [14:33:14] PROBLEM - Number of mediawiki jobs queued on tungsten is CRITICAL: CRITICAL: Anomaly detected: 41 data above and 0 below the confidence bounds [14:33:14] PROBLEM - Number of mediawiki jobs running on tungsten is CRITICAL: CRITICAL: Anomaly detected: 41 data above and 0 below the confidence bounds [14:33:23] RECOVERY - gdash.wikimedia.org on tungsten is OK: HTTP OK: HTTP/1.1 200 OK - 9055 bytes in 0.037 second response time [14:33:33] RECOVERY - graphite.wikimedia.org on tungsten is OK: HTTP OK: HTTP/1.1 200 OK - 1607 bytes in 0.016 second response time [14:34:09] !log restarted apache on tungsten, machine is overloaded [14:34:16] Logged the message, Master [14:34:23] PROBLEM - puppet last run on sanger is CRITICAL: CRITICAL: Epic puppet fail [14:34:43] PROBLEM - Puppet freshness on db1035 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:34:30 UTC [14:34:43] PROBLEM - Puppet freshness on ssl3001 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:34:05 UTC [14:35:43] PROBLEM - Puppet freshness on cp3018 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 12:34:40 UTC [14:36:53] PROBLEM - puppet last run on linne is CRITICAL: CRITICAL: Epic puppet fail [14:37:04] RECOVERY - puppet last run on db1068 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:37:04] RECOVERY - puppet last run on labsdb1002 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [14:37:23] RECOVERY - puppetmaster backend https on strontium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 1.050 second response time [14:37:43] RECOVERY - puppet last run on hydrogen is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:37:54] RECOVERY - puppet last run on mw1020 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:38:03] RECOVERY - puppet last run on mw1179 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:38:03] RECOVERY - puppet last run on mw1070 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:38:03] RECOVERY - puppet last run on mw1085 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:38:03] RECOVERY - puppet last run on mw1101 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:38:03] RECOVERY - puppet last run on ms-be1014 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:38:03] RECOVERY - puppet last run on mw1157 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:38:04] RECOVERY - puppet last run on elastic1013 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:38:04] RECOVERY - puppet last run on ms-be3004 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:38:05] RECOVERY - puppet last run on cp1064 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:38:05] RECOVERY - puppet last run on db1009 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:38:06] RECOVERY - puppet last run on virt0 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:38:13] RECOVERY - puppet last run on lvs3002 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:38:13] RECOVERY - puppet last run on elastic1009 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:38:13] RECOVERY - puppet last run on lanthanum is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:38:13] RECOVERY - puppet last run on mw1075 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:38:13] RECOVERY - puppet last run on cp3007 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:38:13] RECOVERY - puppet last run on db1005 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:38:14] RECOVERY - puppet last run on db1049 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [14:38:14] RECOVERY - puppet last run on erbium is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:38:14] RECOVERY - puppet last run on mw1102 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:38:15] RECOVERY - puppet last run on mw1015 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:38:16] RECOVERY - puppet last run on mw1017 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:38:16] RECOVERY - puppet last run on mw1199 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:38:23] RECOVERY - puppet last run on lvs4001 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:38:23] RECOVERY - puppet last run on cp4015 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:38:24] RECOVERY - puppet last run on amssq45 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:38:24] RECOVERY - puppet last run on amssq52 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:38:33] RECOVERY - puppet last run on wtp1014 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:38:33] RECOVERY - puppet last run on ocg1002 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:38:33] RECOVERY - puppet last run on mw1058 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:38:33] RECOVERY - puppet last run on lvs1006 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:38:43] RECOVERY - puppet last run on analytics1024 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:38:45] !log restarted apache on strontium [14:38:51] Logged the message, Master [14:38:53] RECOVERY - puppet last run on mw1019 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:38:54] RECOVERY - puppet last run on mw1169 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:38:54] RECOVERY - puppet last run on ssl1004 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:38:54] RECOVERY - puppet last run on mw1214 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:38:54] RECOVERY - puppet last run on praseodymium is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:38:54] RECOVERY - puppet last run on elastic1016 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:39:03] RECOVERY - puppet last run on mw1184 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:39:03] RECOVERY - puppet last run on es1005 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:39:03] RECOVERY - puppet last run on search1021 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:39:03] RECOVERY - puppet last run on tmh1002 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:39:03] RECOVERY - puppet last run on mw1095 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:39:13] RECOVERY - puppet last run on db1058 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:39:13] RECOVERY - puppet last run on es1003 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:39:13] RECOVERY - puppet last run on mw1127 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:39:13] RECOVERY - puppet last run on mw1182 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:39:13] RECOVERY - puppet last run on labsdb1007 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:39:13] RECOVERY - puppet last run on analytics1029 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:39:14] RECOVERY - puppet last run on cp1057 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:39:14] RECOVERY - puppet last run on search1009 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:39:14] RECOVERY - puppet last run on analytics1019 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:39:15] RECOVERY - puppet last run on db1019 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:39:15] RECOVERY - puppet last run on mc1008 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:39:16] RECOVERY - puppet last run on mw1083 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:39:23] RECOVERY - puppet last run on mw1191 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:39:23] RECOVERY - puppet last run on cp4017 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:39:34] RECOVERY - puppet last run on ms-be1005 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:39:34] RECOVERY - puppet last run on cp1051 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:39:34] RECOVERY - puppet last run on mw1136 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:39:34] RECOVERY - puppet last run on mw1094 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:39:43] RECOVERY - puppet last run on cp4013 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:39:43] RECOVERY - puppet last run on cp1069 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:39:53] RECOVERY - puppet last run on analytics1036 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:39:54] RECOVERY - puppet last run on analytics1034 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:40:03] RECOVERY - puppet last run on search1014 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:40:03] RECOVERY - puppet last run on db1024 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:40:03] RECOVERY - puppet last run on cp1065 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:40:03] RECOVERY - puppet last run on db1041 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:40:03] RECOVERY - puppet last run on zirconium is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:40:03] RECOVERY - puppet last run on amslvs4 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:40:04] RECOVERY - puppet last run on es10 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:40:04] RECOVERY - puppet last run on es7 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:40:13] RECOVERY - puppet last run on mw1096 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:40:13] RECOVERY - puppet last run on amssq57 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:40:13] RECOVERY - puppet last run on mw1196 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:40:14] RECOVERY - puppet last run on db1007 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:40:14] RECOVERY - puppet last run on mw1138 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:40:14] RECOVERY - puppet last run on mw1013 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:40:23] RECOVERY - puppet last run on tarin is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:40:34] RECOVERY - puppet last run on cp1043 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:40:34] RECOVERY - puppet last run on neon is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:40:43] RECOVERY - Puppet freshness on amssq59 is OK: puppet ran at Sun Aug 31 14:40:34 UTC 2014 [14:40:43] RECOVERY - puppet last run on mw1035 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:40:53] RECOVERY - puppet last run on mw1040 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on wtp1024 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on virt1002 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on wtp1021 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on mc1010 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on mw1161 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on mw1132 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:40:54] RECOVERY - puppet last run on analytics1015 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:41:03] RECOVERY - puppet last run on mw1109 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:41:03] RECOVERY - puppet last run on mw1218 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:41:03] RECOVERY - puppet last run on es1009 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:41:03] RECOVERY - puppet last run on ms-be1001 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:41:03] RECOVERY - puppet last run on cp3022 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:41:03] RECOVERY - puppet last run on ytterbium is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:41:13] RECOVERY - puppet last run on analytics1039 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:41:13] RECOVERY - puppet last run on mw1216 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:41:13] RECOVERY - puppet last run on mw1036 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:41:13] RECOVERY - puppet last run on es1006 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:41:13] RECOVERY - puppet last run on mw1062 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:41:13] RECOVERY - puppet last run on db1010 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:41:14] RECOVERY - puppet last run on amssq58 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:41:14] RECOVERY - puppet last run on mw1130 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:41:15] RECOVERY - puppet last run on mw1124 is OK: OK: Puppet is currently enabled, last run 60 seconds ago with 0 failures [14:41:15] RECOVERY - puppet last run on mw1147 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:41:23] RECOVERY - puppet last run on cp4007 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:41:33] RECOVERY - puppet last run on logstash1003 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:41:44] RECOVERY - Puppet freshness on db1053 is OK: puppet ran at Sun Aug 31 14:41:40 UTC 2014 [14:41:44] RECOVERY - puppet last run on db1065 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [14:41:44] RECOVERY - puppet last run on wtp1019 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:41:44] RECOVERY - puppet last run on wtp1017 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:41:53] RECOVERY - puppet last run on mw1134 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:41:53] RECOVERY - puppet last run on ocg1001 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:41:54] RECOVERY - puppet last run on vanadium is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:41:54] RECOVERY - puppet last run on analytics1033 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [14:41:54] RECOVERY - puppet last run on labsdb1001 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:41:54] RECOVERY - puppet last run on ms-fe1003 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on cp1059 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on mc1011 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on pc1001 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on mw1080 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on mw1067 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on cp1049 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:42:03] RECOVERY - puppet last run on cp3013 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:42:04] RECOVERY - puppet last run on mc1004 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:42:04] RECOVERY - puppet last run on magnesium is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on ssl3003 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on mw1115 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on mw1005 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on ms-be1013 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on mc1009 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on rdb1004 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:42:13] RECOVERY - puppet last run on ms1001 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:42:14] RECOVERY - puppet last run on dbstore1001 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:42:15] RECOVERY - puppet last run on search1020 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:42:15] RECOVERY - puppet last run on dbproxy1002 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:42:16] RECOVERY - puppet last run on db1029 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:42:16] RECOVERY - puppet last run on mw1048 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:42:16] RECOVERY - puppet last run on cp3006 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:42:17] RECOVERY - puppet last run on amssq43 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:42:17] RECOVERY - puppet last run on amssq59 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:42:18] RECOVERY - puppet last run on cp3015 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:42:18] RECOVERY - puppet last run on mw1038 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:42:19] RECOVERY - puppet last run on mw1031 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:42:19] RECOVERY - puppet last run on mw1141 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:42:20] RECOVERY - puppet last run on mw1072 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:42:23] RECOVERY - puppet last run on db1053 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:42:23] RECOVERY - puppet last run on lvs4002 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:42:23] RECOVERY - puppet last run on amslvs2 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:42:23] RECOVERY - puppet last run on amssq44 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:42:33] RECOVERY - puppet last run on mc1016 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:42:33] RECOVERY - puppet last run on analytics1017 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:42:44] RECOVERY - puppet last run on wtp1009 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:42:44] RECOVERY - puppet last run on es1001 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:42:53] RECOVERY - puppet last run on analytics1025 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:42:54] RECOVERY - puppet last run on logstash1001 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:42:54] RECOVERY - puppet last run on netmon1001 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:43:03] RECOVERY - puppet last run on db1017 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:43:03] RECOVERY - puppet last run on rbf1002 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:43:03] RECOVERY - puppet last run on mw1089 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:43:03] RECOVERY - puppet last run on mw1063 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:43:03] RECOVERY - puppet last run on amssq49 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:43:03] RECOVERY - puppet last run on mw1028 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:43:04] RECOVERY - puppet last run on mw1007 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:43:04] RECOVERY - Puppet freshness on elastic1001 is OK: puppet ran at Sun Aug 31 14:43:01 UTC 2014 [14:43:05] RECOVERY - puppet last run on carbon is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on mw1145 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on caesium is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on mw1140 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on mw1045 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on db74 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on mw1197 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:43:13] RECOVERY - puppet last run on cp1039 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:43:14] RECOVERY - puppet last run on cp1070 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:43:15] RECOVERY - puppet last run on db1031 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:43:15] RECOVERY - puppet last run on mc1006 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:43:16] RECOVERY - puppet last run on mw1041 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:43:16] RECOVERY - puppet last run on cp3008 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:43:17] RECOVERY - puppet last run on mw1059 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:43:17] RECOVERY - puppet last run on mw1012 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:43:18] RECOVERY - puppet last run on mw1106 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:43:18] RECOVERY - puppet last run on ms-be1004 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:43:18] RECOVERY - puppet last run on mw1006 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:43:23] RECOVERY - Puppet freshness on mw1160 is OK: puppet ran at Sun Aug 31 14:43:16 UTC 2014 [14:43:23] RECOVERY - puppet last run on cp4006 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:43:24] RECOVERY - puppet last run on cp3020 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:43:33] RECOVERY - puppet last run on db1073 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:43:33] RECOVERY - puppet last run on es1008 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:43:33] RECOVERY - puppet last run on gold is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:43:33] RECOVERY - puppet last run on db73 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:43:34] RECOVERY - Puppet freshness on ssl1002 is OK: puppet ran at Sun Aug 31 14:43:31 UTC 2014 [14:43:43] RECOVERY - puppet last run on cp1047 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:43:43] RECOVERY - puppet last run on elastic1001 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:43:43] RECOVERY - puppet last run on platinum is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:43:53] RECOVERY - puppet last run on analytics1040 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:43:53] RECOVERY - puppet last run on wtp1020 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:43:54] RECOVERY - puppet last run on ssl1002 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:43:54] RECOVERY - puppet last run on potassium is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:43:54] RECOVERY - puppet last run on mw1187 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:43:54] RECOVERY - puppet last run on analytics1041 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:43:54] RECOVERY - puppet last run on cp1055 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:43:55] RECOVERY - puppet last run on search1016 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:43:55] RECOVERY - puppet last run on elastic1004 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:44:03] RECOVERY - puppet last run on searchidx1001 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:44:03] RECOVERY - puppet last run on ms-be1006 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:44:03] RECOVERY - puppet last run on mw1160 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:44:03] RECOVERY - puppet last run on snapshot1003 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:44:03] RECOVERY - puppet last run on cerium is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:44:04] RECOVERY - puppet last run on analytics1020 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:44:04] RECOVERY - puppet last run on wtp1006 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:44:13] RECOVERY - puppet last run on mw1082 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:44:14] RECOVERY - puppet last run on amssq54 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:44:14] RECOVERY - puppet last run on amssq61 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:44:14] RECOVERY - puppet last run on ms-be1003 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:44:23] RECOVERY - puppet last run on amssq32 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:44:24] RECOVERY - puppet last run on amssq53 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:44:33] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:44:33] RECOVERY - puppet last run on elastic1008 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:44:33] RECOVERY - puppet last run on lvs1002 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:44:33] RECOVERY - puppet last run on helium is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:44:43] RECOVERY - puppet last run on lead is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:44:43] RECOVERY - puppet last run on db1066 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:44:44] RECOVERY - puppet last run on mw1173 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:44:44] RECOVERY - puppet last run on wtp1016 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:44:44] RECOVERY - puppet last run on ms-fe1001 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:44:44] RECOVERY - puppet last run on mc1003 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:44:44] RECOVERY - puppet last run on db1022 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:44:45] RECOVERY - puppet last run on analytics1035 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:44:54] RECOVERY - puppet last run on mw1174 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:44:54] RECOVERY - puppet last run on mw1176 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:44:54] RECOVERY - puppet last run on mw1217 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:44:54] RECOVERY - puppet last run on xenon is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:44:54] RECOVERY - puppet last run on mw1189 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:45:03] RECOVERY - puppet last run on mw1153 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:45:03] RECOVERY - puppet last run on search1010 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:45:03] RECOVERY - puppet last run on cp3003 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:45:13] RECOVERY - puppet last run on mw1046 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:45:13] RECOVERY - puppet last run on mw1120 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:45:13] RECOVERY - puppet last run on mw1164 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:45:13] RECOVERY - puppet last run on mw1100 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:45:13] RECOVERY - puppet last run on mw1026 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:45:13] RECOVERY - puppet last run on db1015 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:45:14] RECOVERY - puppet last run on amssq35 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:45:14] RECOVERY - puppet last run on mc1002 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:45:14] RECOVERY - puppet last run on mw1069 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:45:15] RECOVERY - puppet last run on lvs1005 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:45:15] RECOVERY - puppet last run on db1050 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:45:16] RECOVERY - puppet last run on mw1088 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:45:16] RECOVERY - puppet last run on mw1009 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:45:24] RECOVERY - puppet last run on lvs3001 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:45:33] RECOVERY - puppet last run on elastic1012 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:45:33] RECOVERY - puppet last run on mw1099 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:45:33] RECOVERY - puppet last run on db1059 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:45:43] RECOVERY - puppet last run on mw1060 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:45:44] RECOVERY - puppet last run on mw1123 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:45:44] RECOVERY - puppet last run on mw1065 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:45:53] RECOVERY - puppet last run on labsdb1003 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:45:54] RECOVERY - puppet last run on db1067 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:45:54] RECOVERY - puppet last run on mw1166 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:45:54] RECOVERY - puppet last run on mw1118 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:45:54] RECOVERY - puppet last run on mw1205 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:45:54] RECOVERY - puppet last run on holmium is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:45:54] RECOVERY - puppet last run on mw1003 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:45:55] RECOVERY - puppet last run on mw1192 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:46:03] RECOVERY - puppet last run on search1001 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:46:03] RECOVERY - puppet last run on mw1150 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:46:03] RECOVERY - puppet last run on ms-fe1004 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:46:03] RECOVERY - puppet last run on db1046 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:46:03] RECOVERY - puppet last run on cp1056 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:46:03] RECOVERY - puppet last run on mw1119 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:46:04] RECOVERY - puppet last run on db1040 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:46:04] RECOVERY - puppet last run on db1042 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:46:04] RECOVERY - puppet last run on analytics1030 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:46:05] RECOVERY - puppet last run on mw1008 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:46:13] RECOVERY - puppet last run on iron is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:46:13] RECOVERY - puppet last run on cp1061 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:46:13] RECOVERY - puppet last run on mw1025 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:46:13] RECOVERY - puppet last run on mw1061 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:46:13] RECOVERY - puppet last run on db1018 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:46:13] RECOVERY - puppet last run on db1023 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:46:14] RECOVERY - puppet last run on mw1052 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:46:14] RECOVERY - puppet last run on mw1144 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:46:14] RECOVERY - puppet last run on search1018 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:46:15] RECOVERY - puppet last run on db1002 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:46:16] RECOVERY - puppet last run on mw1117 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:46:16] RECOVERY - puppet last run on mw1068 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:46:16] RECOVERY - puppet last run on mw1200 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:46:23] RECOVERY - puppet last run on cp4008 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:46:23] RECOVERY - puppet last run on cp4003 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:46:24] RECOVERY - puppet last run on cp3016 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:46:33] RECOVERY - puppet last run on dbproxy1001 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:46:33] RECOVERY - puppet last run on mw1170 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:46:33] RECOVERY - puppet last run on mw1092 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:46:43] RECOVERY - puppet last run on db1051 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:46:43] RECOVERY - puppet last run on db1052 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:46:44] RECOVERY - puppet last run on mw1213 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:46:53] RECOVERY - puppet last run on gallium is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:46:54] RECOVERY - puppet last run on analytics1010 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:46:54] RECOVERY - puppet last run on mw1177 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:46:54] RECOVERY - puppet last run on mw1126 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:46:54] RECOVERY - puppet last run on mw1042 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:46:54] RECOVERY - puppet last run on mw1172 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:46:54] RECOVERY - puppet last run on mw1175 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:46:55] RECOVERY - puppet last run on virt1006 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:46:55] RECOVERY - puppet last run on db1034 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on mw1039 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on search1007 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on mw1054 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on db1003 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on db1043 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on amssq46 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:47:03] RECOVERY - puppet last run on cp3014 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:47:04] RECOVERY - puppet last run on logstash1002 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:47:13] RECOVERY - puppet last run on amslvs1 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:47:13] RECOVERY - puppet last run on cp1058 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:47:13] RECOVERY - puppet last run on amssq55 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:47:14] RECOVERY - puppet last run on db1021 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:47:14] RECOVERY - puppet last run on db1028 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:47:14] RECOVERY - puppet last run on mw1011 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:47:23] RECOVERY - puppet last run on cp4004 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:47:24] RECOVERY - puppet last run on amssq48 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:47:24] RECOVERY - puppet last run on amssq60 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:47:33] RECOVERY - puppet last run on ruthenium is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:47:33] RECOVERY - puppet last run on mw1114 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:47:33] RECOVERY - puppet last run on mw1129 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:47:33] RECOVERY - puppet last run on polonium is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:47:34] RECOVERY - puppet last run on wtp1012 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:47:53] RECOVERY - puppet last run on pc1002 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:47:54] RECOVERY - puppet last run on wtp1005 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:47:54] RECOVERY - puppet last run on mc1012 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:47:54] RECOVERY - puppet last run on mw1206 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:47:54] RECOVERY - puppet last run on mw1211 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:47:54] RECOVERY - puppet last run on labnet1001 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on install2001 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on cp4014 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on snapshot1001 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on silver is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on db1016 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on mw1076 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:48:03] RECOVERY - puppet last run on antimony is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:48:04] RECOVERY - puppet last run on analytics1016 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:48:05] RECOVERY - puppet last run on analytics1026 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:48:05] RECOVERY - puppet last run on mw1195 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:48:13] RECOVERY - puppet last run on lvs3004 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:48:13] RECOVERY - puppet last run on ms-be3002 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:48:13] RECOVERY - puppet last run on analytics1038 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:48:13] RECOVERY - puppet last run on mw1149 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:48:13] RECOVERY - puppet last run on es1007 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:48:13] RECOVERY - puppet last run on search1005 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:48:14] RECOVERY - puppet last run on amssq47 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:48:14] RECOVERY - puppet last run on amssq34 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [14:48:15] RECOVERY - puppet last run on elastic1006 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:48:15] RECOVERY - puppet last run on labstore1001 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:48:16] RECOVERY - puppet last run on mw1055 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:48:16] RECOVERY - puppet last run on mw1002 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:48:17] RECOVERY - puppet last run on mw1208 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:48:17] RECOVERY - puppet last run on tin is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:48:23] RECOVERY - puppet last run on cp4001 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:48:23] RECOVERY - puppet last run on cp4019 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:48:24] RECOVERY - puppet last run on cp3010 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:48:33] RECOVERY - puppet last run on mw1044 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:48:33] RECOVERY - puppet last run on db1048 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:48:33] RECOVERY - puppet last run on mw1125 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:48:33] RECOVERY - puppet last run on cp1050 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:48:33] RECOVERY - puppet last run on db1026 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:48:34] RECOVERY - puppet last run on argon is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:48:43] RECOVERY - puppet last run on nfs1 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:48:43] RECOVERY - puppet last run on db1060 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:48:44] RECOVERY - puppet last run on db1069 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:48:54] RECOVERY - puppet last run on virt1004 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:48:54] RECOVERY - puppet last run on db1071 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:48:54] RECOVERY - puppet last run on mc1014 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:48:54] RECOVERY - puppet last run on mc1005 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:48:54] RECOVERY - puppet last run on mw1162 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:48:54] RECOVERY - puppet last run on cp1046 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:48:55] RECOVERY - puppet last run on labsdb1006 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:48:55] RECOVERY - puppet last run on thallium is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:48:55] RECOVERY - puppet last run on analytics1013 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:48:56] RECOVERY - puppet last run on mw1014 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on mw1180 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on gadolinium is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on mw1111 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on db1036 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on elastic1015 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on ms-be1012 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:49:03] RECOVERY - puppet last run on amssq56 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:49:04] RECOVERY - puppet last run on labmon1001 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:49:04] RECOVERY - puppet last run on mw1133 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on ms-fe3002 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on mw1098 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on snapshot1002 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on lvs4003 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on amssq51 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on virt1001 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:49:13] RECOVERY - puppet last run on virt1003 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:49:14] RECOVERY - puppet last run on search1002 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:49:14] RECOVERY - puppet last run on ssl1009 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:49:15] RECOVERY - puppet last run on rhenium is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:49:16] RECOVERY - puppet last run on mw1079 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:49:16] RECOVERY - puppet last run on mw1051 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:49:16] RECOVERY - puppet last run on amssq36 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:49:17] RECOVERY - puppet last run on mw1202 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:49:17] RECOVERY - puppet last run on db1039 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:49:18] RECOVERY - puppet last run on ms-be1008 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:49:19] RECOVERY - puppet last run on mw1084 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:49:19] RECOVERY - puppet last run on analytics1022 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:49:23] RECOVERY - puppet last run on bast4001 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:49:23] RECOVERY - puppet last run on cp4005 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:49:24] RECOVERY - puppet last run on ms-be3001 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:49:24] RECOVERY - puppet last run on amssq40 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:49:33] RECOVERY - puppet last run on hafnium is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:49:33] RECOVERY - puppet last run on ssl1005 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:49:33] RECOVERY - puppet last run on snapshot1004 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:49:33] RECOVERY - puppet last run on mw1151 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:49:34] RECOVERY - puppet last run on db1062 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:49:43] RECOVERY - puppet last run on cp1062 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:49:43] RECOVERY - puppet last run on cp1063 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:49:43] RECOVERY - puppet last run on db72 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:49:44] RECOVERY - puppet last run on mw1030 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:49:44] RECOVERY - puppet last run on mw1190 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:49:44] RECOVERY - puppet last run on analytics1023 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:49:44] RECOVERY - puppet last run on mw1081 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:49:44] RECOVERY - puppet last run on mw1056 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:49:53] RECOVERY - puppet last run on oxygen is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:49:54] RECOVERY - puppet last run on search1017 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:49:54] RECOVERY - puppet last run on wtp1018 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:49:54] RECOVERY - puppet last run on mw1168 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:49:54] RECOVERY - puppet last run on mw1183 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on rubidium is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on rdb1001 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on mw1057 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on db1004 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on mw1159 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on mc1001 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:50:03] RECOVERY - puppet last run on amssq42 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:50:04] RECOVERY - puppet last run on stat1002 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:50:04] RECOVERY - puppet last run on db1020 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:50:05] RECOVERY - puppet last run on mw1049 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [14:50:13] RECOVERY - puppet last run on elastic1011 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:50:13] RECOVERY - puppet last run on cp1048 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:50:13] RECOVERY - puppet last run on mw1146 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:50:14] RECOVERY - puppet last run on elastic1014 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:50:14] RECOVERY - puppet last run on mw1050 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:50:14] RECOVERY - puppet last run on mw1034 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:50:14] RECOVERY - puppet last run on mw1004 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:50:23] RECOVERY - puppet last run on cp4018 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:50:24] RECOVERY - puppet last run on amssq41 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:50:24] RECOVERY - puppet last run on ssl3002 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:50:34] RECOVERY - puppet last run on wtp1023 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:50:34] RECOVERY - puppet last run on mw1165 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:50:34] RECOVERY - puppet last run on mw1181 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:50:43] RECOVERY - puppet last run on tungsten is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:50:43] RECOVERY - puppet last run on virt1007 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:50:43] RECOVERY - puppet last run on db69 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:50:44] RECOVERY - puppet last run on wtp1004 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:50:53] RECOVERY - puppet last run on wtp1022 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:50:54] RECOVERY - puppet last run on lvs1001 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:50:54] RECOVERY - puppet last run on analytics1037 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:50:54] RECOVERY - puppet last run on mw1198 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:50:54] RECOVERY - puppet last run on mw1116 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:50:54] RECOVERY - puppet last run on ms-be1009 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:50:54] RECOVERY - puppet last run on mw1156 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:50:55] RECOVERY - puppet last run on mw1210 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:50:56] RECOVERY - puppet last run on titanium is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:50:56] RECOVERY - puppet last run on mw1188 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [14:50:56] RECOVERY - puppet last run on db1055 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:51:03] RECOVERY - puppet last run on analytics1032 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:51:03] RECOVERY - puppet last run on cp1038 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:51:03] RECOVERY - puppet last run on mw1097 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:51:03] RECOVERY - puppet last run on mw1023 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:51:03] RECOVERY - puppet last run on ms-be1007 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:51:03] RECOVERY - puppet last run on analytics1011 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:51:04] RECOVERY - puppet last run on wtp1002 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:51:04] RECOVERY - puppet last run on db1054 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:51:13] RECOVERY - puppet last run on mw1212 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:51:13] RECOVERY - puppet last run on search1024 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:51:13] RECOVERY - puppet last run on search1023 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:51:13] RECOVERY - puppet last run on mw1074 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:51:13] RECOVERY - puppet last run on protactinium is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:51:14] RECOVERY - puppet last run on mw1087 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:51:23] RECOVERY - puppet last run on hooft is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:51:23] RECOVERY - puppet last run on amssq62 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:51:33] RECOVERY - puppet last run on wtp1011 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:51:33] RECOVERY - puppet last run on labsdb1004 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:51:43] RECOVERY - puppet last run on ssl1008 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:51:43] RECOVERY - puppet last run on db1070 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:51:43] RECOVERY - puppet last run on db1064 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:51:43] RECOVERY - puppet last run on wtp1015 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:51:43] RECOVERY - puppet last run on mc1013 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [14:51:53] RECOVERY - puppet last run on elastic1002 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:51:53] RECOVERY - puppet last run on rcs1001 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:51:53] RECOVERY - puppet last run on wtp1013 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:51:53] RECOVERY - puppet last run on db1057 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:51:53] RECOVERY - puppet last run on nitrogen is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:51:54] RECOVERY - puppet last run on mw1171 is OK: OK: Puppet is currently enabled, last run 60 seconds ago with 0 failures [14:51:54] RECOVERY - puppet last run on cp1060 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:52:03] RECOVERY - puppet last run on rdb1002 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:52:03] RECOVERY - puppet last run on es1002 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:52:03] RECOVERY - puppet last run on mw1029 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:52:03] RECOVERY - puppet last run on mc1007 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [14:52:03] RECOVERY - puppet last run on amslvs3 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:52:03] RECOVERY - puppet last run on analytics1014 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:52:13] RECOVERY - puppet last run on wtp1007 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:52:13] RECOVERY - puppet last run on mw1032 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:52:13] RECOVERY - puppet last run on mw1148 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:52:14] RECOVERY - puppet last run on db1044 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [14:52:14] RECOVERY - puppet last run on search1015 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:52:14] RECOVERY - puppet last run on elastic1005 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:52:14] RECOVERY - puppet last run on db1001 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:52:14] RECOVERY - puppet last run on mw1108 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:52:14] RECOVERY - puppet last run on ocg1003 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:52:15] RECOVERY - puppet last run on rcs1002 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:52:24] RECOVERY - puppet last run on cp3012 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:52:24] RECOVERY - puppet last run on cp3009 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:52:33] RECOVERY - puppet last run on mw1201 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:52:34] RECOVERY - puppet last run on db1063 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:52:43] RECOVERY - puppet last run on db1061 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:52:53] RECOVERY - Puppet freshness on cp1037 is OK: puppet ran at Sun Aug 31 14:52:44 UTC 2014 [14:52:53] RECOVERY - puppet last run on ssl1007 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [14:52:54] RECOVERY - puppet last run on ssl1001 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:52:54] RECOVERY - puppet last run on analytics1004 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:52:54] RECOVERY - puppet last run on mw1186 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:52:54] RECOVERY - puppet last run on mw1167 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:52:54] RECOVERY - puppet last run on elastic1017 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:53:03] RECOVERY - puppet last run on wtp1003 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:53:03] RECOVERY - puppet last run on pc1003 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:53:03] RECOVERY - puppet last run on db1030 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:53:03] RECOVERY - puppet last run on mw1024 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:53:03] RECOVERY - puppet last run on rdb1003 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:53:03] RECOVERY - puppet last run on search1013 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:53:04] RECOVERY - puppet last run on mw1022 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:53:04] RECOVERY - puppet last run on db1033 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:53:05] RECOVERY - puppet last run on es1010 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:53:05] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:53:13] RECOVERY - puppet last run on mw1122 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:53:13] RECOVERY - puppet last run on amssq38 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [14:53:13] RECOVERY - puppet last run on cp3004 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:53:13] RECOVERY - puppet last run on mw1033 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:53:13] RECOVERY - puppet last run on db1047 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:53:13] RECOVERY - puppet last run on ms-fe3001 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:53:14] RECOVERY - puppet last run on mw1121 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:53:14] RECOVERY - puppet last run on mw1077 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:53:14] RECOVERY - puppet last run on mw1043 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:53:23] RECOVERY - puppet last run on sanger is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:53:33] RECOVERY - puppet last run on iodine is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:53:33] RECOVERY - puppet last run on dbstore1002 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:53:33] RECOVERY - puppet last run on calcium is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:53:43] RECOVERY - puppet last run on analytics1027 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [14:53:44] RECOVERY - Puppet freshness on ssl3001 is OK: puppet ran at Sun Aug 31 14:53:40 UTC 2014 [14:53:44] RECOVERY - puppet last run on ssl1006 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:53:44] RECOVERY - puppet last run on mw1219 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:53:44] RECOVERY - puppet last run on mw1185 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:53:44] RECOVERY - puppet last run on analytics1028 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [14:53:44] RECOVERY - puppet last run on copper is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:53:45] RECOVERY - puppet last run on mw1105 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:53:53] RECOVERY - puppet last run on mw1010 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:53:53] RECOVERY - puppet last run on mw1001 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:53:54] RECOVERY - puppet last run on fluorine is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:53:54] RECOVERY - puppet last run on mw1142 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:53:54] RECOVERY - puppet last run on cp1037 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [14:54:03] RECOVERY - puppet last run on cp1052 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [14:54:03] RECOVERY - puppet last run on mercury is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:54:03] RECOVERY - puppet last run on wtp1010 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [14:54:13] RECOVERY - puppet last run on amssq31 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [14:54:13] RECOVERY - puppet last run on mw1093 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:54:13] RECOVERY - puppet last run on db1006 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:54:13] RECOVERY - puppet last run on mw1139 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:54:13] RECOVERY - puppet last run on mw1193 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:54:13] RECOVERY - puppet last run on rbf1001 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:54:14] RECOVERY - puppet last run on db1038 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:54:14] RECOVERY - puppet last run on search1011 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:54:14] RECOVERY - puppet last run on ms-be1011 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:54:15] RECOVERY - puppet last run on search1022 is OK: OK: Puppet is currently enabled, last run 60 seconds ago with 0 failures [14:54:15] RECOVERY - puppet last run on stat1003 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:54:16] RECOVERY - puppet last run on db1011 is OK: OK: Puppet is currently enabled, last run 60 seconds ago with 0 failures [14:54:17] RECOVERY - puppet last run on mw1016 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:54:23] RECOVERY - Puppet freshness on cp3018 is OK: puppet ran at Sun Aug 31 14:54:15 UTC 2014 [14:54:23] RECOVERY - puppet last run on cp4020 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:54:23] RECOVERY - puppet last run on lvs3003 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:54:33] RECOVERY - puppet last run on mw1209 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:54:33] RECOVERY - puppet last run on search1006 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [14:54:33] RECOVERY - puppet last run on cp1067 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:54:33] RECOVERY - puppet last run on mw1091 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:54:43] RECOVERY - puppet last run on cp1040 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:54:44] RECOVERY - puppet last run on db1072 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:54:53] RECOVERY - puppet last run on db60 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:54:54] RECOVERY - puppet last run on wtp1001 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:54:54] RECOVERY - puppet last run on cp1044 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:54:54] RECOVERY - puppet last run on mw1203 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [14:55:03] RECOVERY - puppet last run on mw1220 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:55:03] RECOVERY - puppet last run on terbium is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [14:55:03] RECOVERY - puppet last run on strontium is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:55:03] RECOVERY - puppet last run on mw1152 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:55:03] RECOVERY - puppet last run on search1004 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [14:55:03] RECOVERY - puppet last run on mw1064 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:55:13] RECOVERY - puppet last run on mw1112 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:55:13] RECOVERY - puppet last run on ms-be1002 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:55:13] RECOVERY - puppet last run on osm-cp1001 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:55:13] RECOVERY - puppet last run on mw1107 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:55:14] RECOVERY - puppet last run on cp1068 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [14:55:14] RECOVERY - puppet last run on elastic1003 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:55:14] RECOVERY - puppet last run on dysprosium is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:55:14] RECOVERY - puppet last run on db1037 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:55:15] RECOVERY - puppet last run on db1045 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [14:55:15] RECOVERY - puppet last run on ssl3001 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:55:15] RECOVERY - puppet last run on cp3018 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:55:16] RECOVERY - puppet last run on search1012 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:55:17] RECOVERY - puppet last run on lvs1004 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:55:17] RECOVERY - puppet last run on mw1086 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [14:55:17] RECOVERY - puppet last run on mw1143 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [14:55:18] RECOVERY - puppet last run on mw1090 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [14:55:19] RECOVERY - puppet last run on mw1071 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:55:19] RECOVERY - puppet last run on mw1027 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:55:19] RECOVERY - puppet last run on mw1204 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:55:20] RECOVERY - puppet last run on analytics1018 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:55:23] RECOVERY - puppet last run on cp4012 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:55:23] RECOVERY - puppet last run on cp4009 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [14:55:23] RECOVERY - puppet last run on cp4002 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:55:24] RECOVERY - puppet last run on amssq39 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:55:34] RECOVERY - Puppet freshness on db1035 is OK: puppet ran at Sun Aug 31 14:55:26 UTC 2014 [14:55:34] RECOVERY - puppet last run on bast1001 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:55:43] RECOVERY - puppet last run on db1035 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:55:43] RECOVERY - puppet last run on wtp1008 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [14:55:53] RECOVERY - puppet last run on linne is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:55:54] RECOVERY - puppet last run on mw1215 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:55:54] RECOVERY - puppet last run on cp1045 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:55:54] RECOVERY - puppet last run on virt1008 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:55:54] RECOVERY - puppet last run on mw1113 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [14:55:54] RECOVERY - puppet last run on chromium is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [14:55:54] RECOVERY - puppet last run on mw1110 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [14:55:55] RECOVERY - Puppet freshness on bast2001 is OK: puppet ran at Sun Aug 31 14:55:51 UTC 2014 [14:56:03] RECOVERY - puppet last run on ms-be1015 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [14:56:03] RECOVERY - puppet last run on cp1053 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:56:03] RECOVERY - puppet last run on mw1155 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:56:03] RECOVERY - puppet last run on mw1066 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [14:56:03] RECOVERY - puppet last run on mw1021 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:56:04] RECOVERY - puppet last run on db71 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [14:56:04] RECOVERY - puppet last run on mw1037 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on cp3011 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on mc1015 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on ms-fe1002 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on mw1158 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on cp1054 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on mw1104 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [14:56:13] RECOVERY - puppet last run on es1004 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:56:14] RECOVERY - puppet last run on mw1154 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:56:14] RECOVERY - puppet last run on mw1131 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:56:15] RECOVERY - puppet last run on eeden is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:56:15] RECOVERY - puppet last run on amssq37 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:56:16] RECOVERY - puppet last run on mw1135 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [14:56:16] RECOVERY - puppet last run on db1027 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:56:17] RECOVERY - puppet last run on lvs1003 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:56:17] RECOVERY - puppet last run on mw1207 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:56:18] RECOVERY - puppet last run on analytics1021 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [14:56:23] RECOVERY - puppet last run on lvs4004 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:56:24] RECOVERY - puppet last run on cp3005 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [14:56:33] RECOVERY - puppet last run on search1003 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [14:56:33] RECOVERY - puppet last run on db1056 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:56:44] RECOVERY - puppet last run on mw1073 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [14:56:53] RECOVERY - puppet last run on analytics1012 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [14:56:53] RECOVERY - puppet last run on mexia is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [14:56:53] RECOVERY - puppet last run on ssl1003 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:56:53] RECOVERY - puppet last run on analytics1031 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [14:57:03] RECOVERY - puppet last run on bast2001 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [14:57:03] RECOVERY - puppet last run on cp1066 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [14:57:03] RECOVERY - puppet last run on cp3021 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [14:57:13] RECOVERY - puppet last run on tmh1001 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:57:13] RECOVERY - puppet last run on amssq50 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:57:13] RECOVERY - puppet last run on mw1194 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [14:57:13] RECOVERY - puppet last run on palladium is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:57:13] RECOVERY - puppet last run on elastic1010 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [14:57:13] RECOVERY - puppet last run on labsdb1005 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [14:57:14] RECOVERY - puppet last run on cp3017 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:57:14] RECOVERY - puppet last run on mw1103 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [14:57:23] RECOVERY - puppet last run on fenari is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [14:57:23] RECOVERY - puppet last run on cp4011 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [14:57:23] RECOVERY - puppet last run on cp4010 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:57:23] RECOVERY - puppet last run on cp4016 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [14:57:23] RECOVERY - puppet last run on cp3019 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [14:57:33] RECOVERY - puppet last run on mw1128 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [14:57:33] RECOVERY - puppet last run on mw1018 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [14:57:53] RECOVERY - puppet last run on mw1047 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [14:57:54] RECOVERY - puppet last run on zinc is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [14:57:54] RECOVERY - puppet last run on search1008 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [14:57:54] RECOVERY - puppet last run on virt1005 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [14:57:54] RECOVERY - puppet last run on virt1009 is OK: OK: Puppet is currently enabled, last run 1 seconds ago with 0 failures [14:58:13] RECOVERY - puppet last run on mw1078 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [14:58:14] RECOVERY - puppet last run on mw1137 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [14:58:30] that should be approximately the end of the spam [14:58:34] RECOVERY - puppet last run on search1019 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [15:56:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [16:20:43] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:18:04 UTC [16:27:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [17:50:53] PROBLEM - mailman_qrunner on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/qrunner [17:51:13] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [17:51:53] RECOVERY - mailman_qrunner on sodium is OK: PROCS OK: 8 processes with UID = 38 (list), regex args /mailman/bin/qrunner [17:52:13] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [17:57:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [18:10:53] PROBLEM - mailman_qrunner on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/qrunner [18:11:13] PROBLEM - mailman_ctl on sodium is CRITICAL: PROCS CRITICAL: 0 processes with UID = 38 (list), regex args /mailman/bin/mailmanctl [18:11:53] RECOVERY - mailman_qrunner on sodium is OK: PROCS OK: 8 processes with UID = 38 (list), regex args /mailman/bin/qrunner [18:12:13] RECOVERY - mailman_ctl on sodium is OK: PROCS OK: 1 process with UID = 38 (list), regex args /mailman/bin/mailmanctl [18:21:43] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:18:04 UTC [18:28:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [18:56:28] chasemp: ori sigh, just repackaged the deb from current precise for trusty, still no dice. lsfof tells me txstatsd is listening on 8125, but no data is coming in through it, and nmap doesn't find it, and telnet can't connect... [18:56:44] it's not a network config issue since I tried running a SimpleHTTPServer on 8125 and could connect to it [18:58:21] ah, interesting [18:58:22] nc works [18:59:14] hmm [18:59:19] so txstatsd seems to be working fine [18:59:33] * YuviPanda investigates [19:07:23] brrr, this is inconsistent and stupid [19:30:52] ok [19:31:01] it looks like UDP packets from labs to labmon are dropped [19:31:05] while TCP is sent through [19:31:08] * YuviPanda reopens RT [19:56:03] !log Jenkins updated HHVM to (3.3-dev+20140728+wmf5) over (3.3-dev+20140728+wmf4) [19:56:10] Logged the message, Master [19:57:04] regular unscheduled apt-get upgrade on the jenkins slaves :D [19:58:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [20:22:43] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:18:04 UTC [20:29:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC [20:47:15] (03PS1) 10Tim Landscheidt: labmon: Collect metrics from Toolsbeta [puppet] - 10https://gerrit.wikimedia.org/r/157620 [21:59:43] PROBLEM - Puppet freshness on mw1053 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 01:50:18 UTC [22:18:01] chasemp: ori found the root cause, was completely unrelated to txstatsd. https://rt.wikimedia.org/Ticket/Display.html?id=8163 updated [22:18:03] * YuviPanda goes to sleep [22:23:43] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 10:18:04 UTC [22:30:43] PROBLEM - Puppet freshness on elastic1007 is CRITICAL: Last successful Puppet run was Sun 31 Aug 2014 06:23:11 UTC