[00:00:25] exception handling weirdeness? [00:00:45] > var_dump( GWToolset\Config::$mediafile_job_queue_max ); [00:00:45] int(1000) [00:00:46] right [00:01:00] I recall there was some change to exception handling recently [00:01:32] for the GWT codebase itself this is the only change that could be the cause, based on timing: [00:01:35] https://github.com/wikimedia/mediawiki-extensions-GWToolset/commit/6608c10677666516b5f83a543de85b9d5b65da57 [00:01:53] and this seems harmless [00:02:20] tgr, I don't think it's that try {} catch () {} block around recreateMetadataJob is that's what you mean, it's supposed to return unconditionally after that is run... [00:03:12] yeah looks irrelevant [00:04:53] no I mean there was some sort of change from MWException to Exception (? I think) recently in core, and GWT does complicated things with custom exception types, maybe that's involved somehow [00:05:38] ah. [00:05:39] or could be a bug that went unnoticed so far, of course [00:06:07] but I don't see any relevant changes to GWT code or config [00:06:12] ah, no hang on [00:06:22] recreateMetadataJob throws MWException [00:06:42] Exception is caught.... which should be OK actually, I think [00:07:08] that can't happen, it wouldn't recreate itself then [00:07:27] yeah and it would error out [00:07:28] ok [00:08:44] tgr, your command to dump job details did not work for me [00:08:55] ( https://phabricator.wikimedia.org/T87040#984019 ) [00:09:27] you have to get lucky with the timing, just try a few times [00:09:53] the job is thrashing, sometimes it's in the unclaimed list, sometimes in the queued list [00:10:45] anyway if I just clear the GWT lists in redis, that should kill it, right? [00:11:03] assuming I manage to do it in a moment when the job is not actually running [00:11:53] (error) ERR unknown command 'rdb1003' [00:13:05] it's a redis command [00:13:16] give me a sec, I wanted to update the docs anyway [00:13:36] Do I need any special access beyond deployment? [00:13:58] no [00:19:17] alright well it didn't work [00:19:28] those users are on about 6,500 log entries each just within the past 24 hours [00:19:53] actually much more now compared to when I sent that message ^ [00:19:58] https://wikitech.wikimedia.org/wiki/Redis [00:20:28] something like 10 entries per sec, last I checked [00:22:41] alright, let's try randomly deleting stuff in redis [00:22:52] ("what harm could it do?") [00:23:46] ah okay I had to manually put the pass in, I assumed it was actually set as $REDISPWD from your message [00:30:17] tgr, did you d oit? [00:30:20] do it* [00:30:34] nope, it started again [00:31:35] I popped a key from l-unclaimed bit it doesn't seem to have any effect [00:37:51] killed it for good, I think [00:42:50] tgr, alright so now we need to work out how to prevent it happening again [00:53:08] Disable the job queue [00:53:51] tgr, $result = $this->processMetadata() seems weird considering that function returns string|array but we expect bool [00:56:47] there is throttling if you return false there, it backs off [00:59:35] I still don't understand what happened in the first place [00:59:48] it can't be the metadata job rescheduling itself [01:00:01] I agree on that, the attempts param would be going up like crazy if that was happening [01:00:16] that would set a 5 min waiting time every time, plus doesn't even happen unless there are 1000 upload jobs queued [01:19:16] tgr, did you take a peek into fluorine:/a/mw-log/runJobs.log ? [01:22:45] each time it was the same uniqid() value in the title [01:23:17] sorry, no it wasn't, it changed *slightly* [01:24:34] pff - I looked at the first few characters - but "Gets a prefixed unique identifier based on the current time in microseconds." [01:51:39] tgr, so UploadMetadataJob::processMetadata is what should be run, which just goes through to MetadataMappingHandler::processRequest, which will call processMetadata in our case (from the job runner), which can potentially start new jobs. [01:53:01] although, I'm not sure it's new metadata jobs... [01:55:53] no, those are the upload jobs [01:55:58] UploadMediafileJob [01:57:07] basically GWT has a master job (UpoloadMetadataJob) which fetches an XML from GLAM site, iterates through it and spawns an UploadMediafileJob for every file included [01:58:30] PROBLEM - puppet last run on radon is CRITICAL: CRITICAL: Puppet has 14 failures [01:58:31] ok. I'm going to stop looking at this now, hopefully it can be fixed monday [01:58:45] in the mean time we have a command to end flooding if/when it happens [01:58:49] PROBLEM - puppet last run on analytics1012 is CRITICAL: CRITICAL: puppet fail [01:58:49] PROBLEM - puppet last run on analytics1021 is CRITICAL: CRITICAL: Puppet has 22 failures [01:58:49] PROBLEM - puppet last run on ms-be1010 is CRITICAL: CRITICAL: Puppet has 7 failures [01:58:49] PROBLEM - puppet last run on tmh1001 is CRITICAL: CRITICAL: Puppet has 40 failures [01:58:49] PROBLEM - puppet last run on mw1018 is CRITICAL: CRITICAL: puppet fail [01:58:50] hm, on a closer look, you seem to be right [01:58:59] PROBLEM - puppet last run on es1004 is CRITICAL: CRITICAL: Puppet has 18 failures [01:59:00] really? [01:59:00] PROBLEM - puppet last run on es2006 is CRITICAL: CRITICAL: puppet fail [01:59:00] PROBLEM - puppetmaster backend https on palladium is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 8141: HTTP/1.1 500 Internal Server Error [01:59:01] PROBLEM - puppet last run on palladium is CRITICAL: CRITICAL: Puppet has 37 failures [01:59:05] it does create an UploadMetadataJob [01:59:09] PROBLEM - puppet last run on mw1019 is CRITICAL: CRITICAL: puppet fail [01:59:10] PROBLEM - puppet last run on cp4016 is CRITICAL: CRITICAL: Puppet has 15 failures [01:59:11] haha oh dear. [01:59:20] PROBLEM - puppet last run on mw1128 is CRITICAL: CRITICAL: Puppet has 36 failures [01:59:29] PROBLEM - puppet last run on cp4010 is CRITICAL: CRITICAL: Puppet has 28 failures [01:59:29] PROBLEM - puppet last run on mw1085 is CRITICAL: CRITICAL: puppet fail [01:59:30] PROBLEM - puppet last run on cp1066 is CRITICAL: CRITICAL: Puppet has 41 failures [01:59:30] PROBLEM - puppet last run on mw1199 is CRITICAL: CRITICAL: Puppet has 34 failures [01:59:30] PROBLEM - puppet last run on cp3019 is CRITICAL: CRITICAL: Puppet has 17 failures [01:59:30] PROBLEM - puppet last run on cp3021 is CRITICAL: CRITICAL: Puppet has 21 failures [01:59:30] PROBLEM - puppet last run on amssq37 is CRITICAL: CRITICAL: Puppet has 12 failures [01:59:34] ah, I remembere, that's a sort of throttling [01:59:39] PROBLEM - puppet last run on ms-be1014 is CRITICAL: CRITICAL: puppet fail [01:59:39] PROBLEM - puppet last run on mw1073 is CRITICAL: CRITICAL: Puppet has 42 failures [01:59:39] PROBLEM - puppet last run on elastic1010 is CRITICAL: CRITICAL: puppet fail [01:59:39] PROBLEM - puppet last run on mw1047 is CRITICAL: CRITICAL: puppet fail [01:59:49] PROBLEM - puppet last run on mw1179 is CRITICAL: CRITICAL: Puppet has 39 failures [01:59:49] PROBLEM - puppet last run on elastic1009 is CRITICAL: CRITICAL: puppet fail [01:59:49] PROBLEM - puppet last run on mw1103 is CRITICAL: CRITICAL: Puppet has 34 failures [01:59:50] PROBLEM - puppet last run on hydrogen is CRITICAL: CRITICAL: puppet fail [01:59:50] PROBLEM - puppet last run on db1009 is CRITICAL: CRITICAL: Puppet has 8 failures [01:59:50] PROBLEM - puppet last run on db1005 is CRITICAL: CRITICAL: puppet fail [01:59:50] PROBLEM - puppet last run on mw1194 is CRITICAL: CRITICAL: Puppet has 79 failures [01:59:50] PROBLEM - puppet last run on mw1020 is CRITICAL: CRITICAL: puppet fail [01:59:59] PROBLEM - puppet last run on labsdb1002 is CRITICAL: CRITICAL: puppet fail [01:59:59] PROBLEM - puppet last run on elastic1013 is CRITICAL: CRITICAL: puppet fail [01:59:59] PROBLEM - puppet last run on pollux is CRITICAL: CRITICAL: puppet fail [02:00:00] PROBLEM - puppet last run on analytics1024 is CRITICAL: CRITICAL: puppet fail [02:00:00] PROBLEM - puppet last run on db1068 is CRITICAL: CRITICAL: Puppet has 9 failures [02:00:00] PROBLEM - puppet last run on amssq52 is CRITICAL: CRITICAL: puppet fail [02:00:00] PROBLEM - puppet last run on cp3007 is CRITICAL: CRITICAL: puppet fail [02:00:00] PROBLEM - puppet last run on cp3017 is CRITICAL: CRITICAL: Puppet has 10 failures [02:00:09] PROBLEM - puppet last run on cp1064 is CRITICAL: CRITICAL: puppet fail [02:00:09] PROBLEM - puppet last run on db1049 is CRITICAL: CRITICAL: puppet fail [02:00:09] PROBLEM - puppet last run on virt1009 is CRITICAL: CRITICAL: puppet fail [02:00:10] PROBLEM - puppet last run on lvs2002 is CRITICAL: CRITICAL: Puppet has 14 failures [02:00:10] PROBLEM - puppet last run on mw1017 is CRITICAL: CRITICAL: puppet fail [02:00:11] PROBLEM - puppet last run on elastic1016 is CRITICAL: CRITICAL: puppet fail [02:00:11] PROBLEM - puppet last run on mw1182 is CRITICAL: CRITICAL: puppet fail [02:00:15] process N records, spawn a clone of self with some delay which continues from the next record [02:00:19] PROBLEM - puppet last run on es1005 is CRITICAL: CRITICAL: puppet fail [02:00:19] PROBLEM - puppet last run on ms-be2009 is CRITICAL: CRITICAL: puppet fail [02:00:19] PROBLEM - puppet last run on db2010 is CRITICAL: CRITICAL: Puppet has 7 failures [02:00:19] PROBLEM - puppet last run on ms-be1005 is CRITICAL: CRITICAL: puppet fail [02:00:19] PROBLEM - puppet last run on bast2001 is CRITICAL: CRITICAL: Puppet has 12 failures [02:00:20] PROBLEM - puppet last run on mw1157 is CRITICAL: CRITICAL: Puppet has 30 failures [02:00:20] PROBLEM - puppet last run on mw1137 is CRITICAL: CRITICAL: Puppet has 71 failures [02:00:20] PROBLEM - puppet last run on mw1075 is CRITICAL: CRITICAL: Puppet has 75 failures [02:00:21] PROBLEM - puppet last run on mw1078 is CRITICAL: CRITICAL: puppet fail [02:00:21] PROBLEM - puppet last run on labsdb1007 is CRITICAL: CRITICAL: puppet fail [02:00:21] PROBLEM - puppet last run on praseodymium is CRITICAL: CRITICAL: puppet fail [02:00:29] PROBLEM - puppet last run on cp4017 is CRITICAL: CRITICAL: puppet fail [02:00:29] PROBLEM - puppet last run on cp4015 is CRITICAL: CRITICAL: Puppet has 14 failures [02:00:29] PROBLEM - puppet last run on cp4011 is CRITICAL: CRITICAL: Puppet has 40 failures [02:00:29] PROBLEM - puppet last run on lanthanum is CRITICAL: CRITICAL: Puppet has 17 failures [02:00:29] PROBLEM - puppet last run on ocg1002 is CRITICAL: CRITICAL: puppet fail [02:00:30] PROBLEM - puppet last run on mw1058 is CRITICAL: CRITICAL: Puppet has 33 failures [02:00:30] PROBLEM - puppet last run on mw1101 is CRITICAL: CRITICAL: Puppet has 69 failures [02:00:30] PROBLEM - puppet last run on mw1230 is CRITICAL: CRITICAL: Puppet has 74 failures [02:00:39] PROBLEM - puppet last run on mw1102 is CRITICAL: CRITICAL: puppet fail [02:00:40] PROBLEM - puppet last run on mw1184 is CRITICAL: CRITICAL: puppet fail [02:00:49] PROBLEM - puppet last run on lvs3002 is CRITICAL: CRITICAL: Puppet has 20 failures [02:00:49] PROBLEM - puppet last run on amssq50 is CRITICAL: CRITICAL: Puppet has 16 failures [02:00:49] PROBLEM - puppet last run on mw1127 is CRITICAL: CRITICAL: puppet fail [02:00:50] PROBLEM - puppet last run on es1003 is CRITICAL: CRITICAL: Puppet has 15 failures [02:00:59] PROBLEM - puppet last run on erbium is CRITICAL: CRITICAL: Puppet has 21 failures [02:00:59] PROBLEM - puppet last run on cp1057 is CRITICAL: CRITICAL: puppet fail [02:00:59] PROBLEM - puppet last run on mw1070 is CRITICAL: CRITICAL: Puppet has 64 failures [02:01:00] PROBLEM - puppet last run on analytics1029 is CRITICAL: CRITICAL: Puppet has 20 failures [02:01:00] PROBLEM - puppet last run on mw1191 is CRITICAL: CRITICAL: puppet fail [02:01:07] the fun thing is that GWT is basically using global state for everything, except it's not truly global but passed from function to function as an array [02:01:09] PROBLEM - puppet last run on lvs2005 is CRITICAL: CRITICAL: Puppet has 25 failures [02:01:09] PROBLEM - puppet last run on mw1015 is CRITICAL: CRITICAL: Puppet has 70 failures [02:01:10] PROBLEM - puppet last run on mw1138 is CRITICAL: CRITICAL: puppet fail [02:01:10] PROBLEM - puppet last run on tmh1002 is CRITICAL: CRITICAL: puppet fail [02:01:10] PROBLEM - puppet last run on db1041 is CRITICAL: CRITICAL: puppet fail [02:01:10] PROBLEM - puppet last run on amslvs4 is CRITICAL: CRITICAL: puppet fail [02:01:10] PROBLEM - puppet last run on ms-be3004 is CRITICAL: CRITICAL: Puppet has 19 failures [02:01:10] PROBLEM - puppet last run on amssq45 is CRITICAL: CRITICAL: Puppet has 19 failures [02:01:19] PROBLEM - puppet last run on wtp1014 is CRITICAL: CRITICAL: Puppet has 19 failures [02:01:19] PROBLEM - puppet last run on mw1094 is CRITICAL: CRITICAL: Puppet has 31 failures [02:01:19] PROBLEM - puppet last run on mw1136 is CRITICAL: CRITICAL: puppet fail [02:01:19] PROBLEM - puppet last run on mw1095 is CRITICAL: CRITICAL: Puppet has 77 failures [02:01:20] PROBLEM - puppet last run on mw1196 is CRITICAL: CRITICAL: puppet fail [02:01:29] PROBLEM - puppet last run on db2041 is CRITICAL: CRITICAL: Puppet has 12 failures [02:01:29] PROBLEM - puppet last run on ms-be2015 is CRITICAL: CRITICAL: puppet fail [02:01:29] PROBLEM - puppet last run on lvs1006 is CRITICAL: CRITICAL: Puppet has 12 failures [02:01:30] PROBLEM - puppet last run on mw1232 is CRITICAL: CRITICAL: Puppet has 34 failures [02:01:30] PROBLEM - puppet last run on analytics1019 is CRITICAL: CRITICAL: Puppet has 12 failures [02:01:30] PROBLEM - puppet last run on cp1069 is CRITICAL: CRITICAL: puppet fail [02:01:30] PROBLEM - puppet last run on db1058 is CRITICAL: CRITICAL: Puppet has 20 failures [02:01:30] PROBLEM - puppet last run on cp1065 is CRITICAL: CRITICAL: puppet fail [02:01:30] PROBLEM - puppet last run on db1019 is CRITICAL: CRITICAL: Puppet has 21 failures [02:01:31] PROBLEM - puppet last run on lvs4001 is CRITICAL: CRITICAL: puppet fail [02:01:38] all methods read and write the option array [02:01:39] PROBLEM - puppet last run on cp4013 is CRITICAL: CRITICAL: Puppet has 31 failures [02:01:40] PROBLEM - puppet last run on mw1083 is CRITICAL: CRITICAL: Puppet has 73 failures [02:01:49] PROBLEM - puppet last run on mc1008 is CRITICAL: CRITICAL: Puppet has 23 failures [02:01:50] PROBLEM - puppet last run on mw1169 is CRITICAL: CRITICAL: Puppet has 74 failures [02:01:51] PROBLEM - puppet last run on mw1246 is CRITICAL: CRITICAL: puppet fail [02:01:59] urgh :( [02:01:59] PROBLEM - puppet last run on mw1214 is CRITICAL: CRITICAL: Puppet has 34 failures [02:01:59] PROBLEM - puppet last run on db1024 is CRITICAL: CRITICAL: puppet fail [02:02:00] PROBLEM - puppet last run on amssq58 is CRITICAL: CRITICAL: puppet fail [02:02:00] PROBLEM - puppet last run on stat1001 is CRITICAL: CRITICAL: puppet fail [02:02:09] PROBLEM - puppet last run on mw1257 is CRITICAL: CRITICAL: puppet fail [02:02:09] PROBLEM - puppet last run on mw1252 is CRITICAL: CRITICAL: puppet fail [02:02:09] PROBLEM - puppet last run on analytics1034 is CRITICAL: CRITICAL: puppet fail [02:02:09] PROBLEM - puppet last run on zirconium is CRITICAL: CRITICAL: Puppet has 39 failures [02:02:09] PROBLEM - puppet last run on mw1234 is CRITICAL: CRITICAL: Puppet has 78 failures [02:02:09] PROBLEM - puppet last run on cp1051 is CRITICAL: CRITICAL: Puppet has 13 failures [02:02:09] PROBLEM - puppet last run on virt1002 is CRITICAL: CRITICAL: puppet fail [02:02:12] PROBLEM - puppet last run on wtp1024 is CRITICAL: CRITICAL: puppet fail [02:02:17] so if there is some subtle bug in the state handling logic, that's going to be fun to figure out [02:02:19] PROBLEM - puppet last run on mw1036 is CRITICAL: CRITICAL: puppet fail [02:02:19] PROBLEM - puppet last run on mw1109 is CRITICAL: CRITICAL: puppet fail [02:02:29] PROBLEM - puppet last run on amssq57 is CRITICAL: CRITICAL: puppet fail [02:02:29] PROBLEM - puppet last run on mw1245 is CRITICAL: CRITICAL: puppet fail [02:02:30] PROBLEM - puppet last run on mw1013 is CRITICAL: CRITICAL: puppet fail [02:02:39] PROBLEM - puppet last run on db1007 is CRITICAL: CRITICAL: puppet fail [02:02:39] PROBLEM - puppet last run on analytics1039 is CRITICAL: CRITICAL: puppet fail [02:02:40] PROBLEM - puppet last run on wtp1021 is CRITICAL: CRITICAL: puppet fail [02:02:40] PROBLEM - puppet last run on virt1012 is CRITICAL: CRITICAL: puppet fail [02:02:40] PROBLEM - puppet last run on mw1040 is CRITICAL: CRITICAL: puppet fail [02:02:40] PROBLEM - puppet last run on ms-be2010 is CRITICAL: CRITICAL: Puppet has 29 failures [02:02:41] PROBLEM - puppet last run on cp1059 is CRITICAL: CRITICAL: puppet fail [02:02:49] PROBLEM - puppet last run on mw1218 is CRITICAL: CRITICAL: puppet fail [02:02:49] PROBLEM - puppet last run on db1010 is CRITICAL: CRITICAL: Puppet has 11 failures [02:02:49] PROBLEM - puppet last run on mw1035 is CRITICAL: CRITICAL: Puppet has 73 failures [02:02:49] PROBLEM - puppet last run on elastic1026 is CRITICAL: CRITICAL: Puppet has 24 failures [02:02:50] PROBLEM - puppet last run on cp4007 is CRITICAL: CRITICAL: puppet fail [02:02:59] PROBLEM - puppet last run on es1006 is CRITICAL: CRITICAL: Puppet has 18 failures [02:02:59] PROBLEM - puppet last run on mw1244 is CRITICAL: CRITICAL: Puppet has 33 failures [02:03:10] PROBLEM - puppet last run on cp1043 is CRITICAL: CRITICAL: puppet fail [02:03:10] PROBLEM - puppet last run on mw1089 is CRITICAL: CRITICAL: puppet fail [02:03:10] PROBLEM - puppet last run on mw1130 is CRITICAL: CRITICAL: puppet fail [02:03:10] PROBLEM - puppet last run on mw1216 is CRITICAL: CRITICAL: puppet fail [02:03:10] PROBLEM - puppet last run on amssq43 is CRITICAL: CRITICAL: puppet fail [02:03:10] PROBLEM - puppet last run on amssq44 is CRITICAL: CRITICAL: puppet fail [02:03:11] PROBLEM - puppet last run on ms-be1013 is CRITICAL: CRITICAL: puppet fail [02:03:11] PROBLEM - puppet last run on ytterbium is CRITICAL: CRITICAL: Puppet has 20 failures [02:03:12] PROBLEM - puppet last run on labsdb1001 is CRITICAL: CRITICAL: Puppet has 22 failures [02:03:15] anyway, this is not really urgent at this point, we can wait to see if it reoccurs (which would suggest some recent code change is involved) [02:03:19] PROBLEM - puppet last run on mc1011 is CRITICAL: CRITICAL: Puppet has 17 failures [02:03:19] PROBLEM - puppet last run on mw1161 is CRITICAL: CRITICAL: Puppet has 38 failures [02:03:20] PROBLEM - puppet last run on mw1096 is CRITICAL: CRITICAL: Puppet has 68 failures [02:03:20] PROBLEM - puppet last run on mc1004 is CRITICAL: CRITICAL: puppet fail [02:03:30] PROBLEM - puppet last run on analytics1036 is CRITICAL: CRITICAL: Puppet has 28 failures [02:03:30] PROBLEM - puppet last run on analytics1015 is CRITICAL: CRITICAL: puppet fail [02:03:30] PROBLEM - puppet last run on mw1080 is CRITICAL: CRITICAL: Puppet has 33 failures [02:03:31] PROBLEM - puppet last run on ms-fe1003 is CRITICAL: CRITICAL: puppet fail [02:03:31] PROBLEM - puppet last run on mw1031 is CRITICAL: CRITICAL: puppet fail [02:03:31] PROBLEM - puppet last run on wtp1019 is CRITICAL: CRITICAL: Puppet has 9 failures [02:03:31] PROBLEM - puppet last run on es1009 is CRITICAL: CRITICAL: Puppet has 20 failures [02:03:31] PROBLEM - puppet last run on mc1010 is CRITICAL: CRITICAL: Puppet has 9 failures [02:03:39] PROBLEM - puppet last run on db2035 is CRITICAL: CRITICAL: puppet fail [02:03:40] PROBLEM - puppet last run on mw1240 is CRITICAL: CRITICAL: puppet fail [02:03:40] PROBLEM - puppet last run on cp3022 is CRITICAL: CRITICAL: Puppet has 20 failures [02:03:40] PROBLEM - puppet last run on cp3013 is CRITICAL: CRITICAL: Puppet has 30 failures [02:03:40] PROBLEM - puppet last run on mw1005 is CRITICAL: CRITICAL: puppet fail [02:03:49] PROBLEM - puppet last run on mw1147 is CRITICAL: CRITICAL: Puppet has 76 failures [02:03:50] PROBLEM - puppet last run on elastic1028 is CRITICAL: CRITICAL: Puppet has 30 failures [02:03:50] PROBLEM - puppet last run on mw1132 is CRITICAL: CRITICAL: Puppet has 72 failures [02:03:50] PROBLEM - puppet last run on wtp1017 is CRITICAL: CRITICAL: Puppet has 13 failures [02:03:50] PROBLEM - puppet last run on ms-be1001 is CRITICAL: CRITICAL: puppet fail [02:03:50] PROBLEM - puppet last run on rdb1004 is CRITICAL: CRITICAL: Puppet has 23 failures [02:03:50] PROBLEM - puppet last run on mw1028 is CRITICAL: CRITICAL: puppet fail [02:03:51] PROBLEM - puppet last run on mw1221 is CRITICAL: CRITICAL: Puppet has 76 failures [02:03:51] PROBLEM - puppet last run on mw1072 is CRITICAL: CRITICAL: Puppet has 30 failures [02:03:51] PROBLEM - puppet last run on elastic1031 is CRITICAL: CRITICAL: puppet fail [02:03:53] PROBLEM - puppet last run on ms-be2013 is CRITICAL: CRITICAL: Puppet has 17 failures [02:03:53] PROBLEM - puppet last run on mw1048 is CRITICAL: CRITICAL: puppet fail [02:03:53] PROBLEM - puppet last run on es2003 is CRITICAL: CRITICAL: Puppet has 14 failures [02:03:59] PROBLEM - puppet last run on ms-be2002 is CRITICAL: CRITICAL: puppet fail [02:03:59] PROBLEM - puppet last run on vanadium is CRITICAL: CRITICAL: puppet fail [02:03:59] PROBLEM - puppet last run on uranium is CRITICAL: CRITICAL: Puppet has 17 failures [02:03:59] PROBLEM - puppet last run on db1053 is CRITICAL: CRITICAL: Puppet has 14 failures [02:03:59] PROBLEM - puppet last run on lvs4002 is CRITICAL: CRITICAL: puppet fail [02:04:00] PROBLEM - puppet last run on dbstore1001 is CRITICAL: CRITICAL: Puppet has 17 failures [02:04:00] PROBLEM - puppet last run on analytics1017 is CRITICAL: CRITICAL: puppet fail [02:04:09] PROBLEM - puppet last run on mc1009 is CRITICAL: CRITICAL: puppet fail [02:04:09] PROBLEM - puppet last run on magnesium is CRITICAL: CRITICAL: puppet fail [02:04:10] PROBLEM - puppet last run on wtp1009 is CRITICAL: CRITICAL: puppet fail [02:04:10] PROBLEM - puppet last run on mw1124 is CRITICAL: CRITICAL: Puppet has 65 failures [02:04:20] PROBLEM - puppet last run on mw1038 is CRITICAL: CRITICAL: Puppet has 81 failures [02:04:20] PROBLEM - puppet last run on pc1001 is CRITICAL: CRITICAL: puppet fail [02:04:20] PROBLEM - puppet last run on mw1178 is CRITICAL: CRITICAL: puppet fail [02:04:21] PROBLEM - puppet last run on logstash1003 is CRITICAL: CRITICAL: Puppet has 30 failures [02:04:21] PROBLEM - puppet last run on mw1197 is CRITICAL: CRITICAL: puppet fail [02:04:21] PROBLEM - puppet last run on amssq49 is CRITICAL: CRITICAL: puppet fail [02:04:21] PROBLEM - puppet last run on cp3006 is CRITICAL: CRITICAL: puppet fail [02:04:21] PROBLEM - puppet last run on cp3015 is CRITICAL: CRITICAL: Puppet has 33 failures [02:04:29] PROBLEM - puppet last run on ms-be1004 is CRITICAL: CRITICAL: puppet fail [02:04:29] PROBLEM - puppet last run on ocg1001 is CRITICAL: CRITICAL: Puppet has 12 failures [02:04:30] PROBLEM - puppet last run on mw1256 is CRITICAL: CRITICAL: Puppet has 66 failures [02:04:30] PROBLEM - puppet last run on mw1012 is CRITICAL: CRITICAL: puppet fail [02:04:39] PROBLEM - puppet last run on mw1200 is CRITICAL: CRITICAL: puppet fail [02:04:39] PROBLEM - puppet last run on analytics1033 is CRITICAL: CRITICAL: Puppet has 26 failures [02:04:40] PROBLEM - puppet last run on mw1233 is CRITICAL: CRITICAL: puppet fail [02:04:40] PROBLEM - puppet last run on es1001 is CRITICAL: CRITICAL: Puppet has 21 failures [02:04:40] PROBLEM - puppet last run on db1029 is CRITICAL: CRITICAL: Puppet has 25 failures [02:04:40] PROBLEM - puppet last run on cerium is CRITICAL: CRITICAL: puppet fail [02:04:40] PROBLEM - puppet last run on mw1140 is CRITICAL: CRITICAL: puppet fail [02:04:40] PROBLEM - puppet last run on mw1145 is CRITICAL: CRITICAL: puppet fail [02:04:41] PROBLEM - puppet last run on mw1059 is CRITICAL: CRITICAL: puppet fail [02:04:41] PROBLEM - puppet last run on cp1049 is CRITICAL: CRITICAL: Puppet has 28 failures [02:04:49] PROBLEM - puppet last run on carbon is CRITICAL: CRITICAL: Puppet has 30 failures [02:04:50] PROBLEM - puppet last run on mw1006 is CRITICAL: CRITICAL: puppet fail [02:04:50] PROBLEM - puppet last run on cp3020 is CRITICAL: CRITICAL: puppet fail [02:04:50] PROBLEM - puppet last run on amssq59 is CRITICAL: CRITICAL: Puppet has 17 failures [02:04:50] PROBLEM - puppet last run on neptunium is CRITICAL: CRITICAL: Puppet has 32 failures [02:04:51] tgr, the log comment shows that clearly something which should normally be shown to the user is actually being stuck elsewhere [02:04:59] PROBLEM - puppet last run on db1065 is CRITICAL: CRITICAL: Puppet has 11 failures [02:04:59] PROBLEM - puppet last run on mw1141 is CRITICAL: CRITICAL: puppet fail [02:04:59] PROBLEM - puppet last run on caesium is CRITICAL: CRITICAL: puppet fail [02:04:59] PROBLEM - puppet last run on mc1016 is CRITICAL: CRITICAL: puppet fail [02:04:59] PROBLEM - puppet last run on cp1070 is CRITICAL: CRITICAL: puppet fail [02:05:00] PROBLEM - puppet last run on labstore2001 is CRITICAL: CRITICAL: Puppet has 20 failures [02:05:00] PROBLEM - puppet last run on mw1106 is CRITICAL: CRITICAL: puppet fail [02:05:00] PROBLEM - puppet last run on es2005 is CRITICAL: CRITICAL: Puppet has 14 failures [02:05:00] PROBLEM - puppet last run on db2009 is CRITICAL: CRITICAL: puppet fail [02:05:01] PROBLEM - puppet last run on rbf1002 is CRITICAL: CRITICAL: puppet fail [02:05:01] PROBLEM - puppet last run on dbproxy1002 is CRITICAL: CRITICAL: Puppet has 13 failures [02:05:10] PROBLEM - puppet last run on mw1063 is CRITICAL: CRITICAL: Puppet has 28 failures [02:05:10] PROBLEM - puppet last run on mw1067 is CRITICAL: CRITICAL: Puppet has 35 failures [02:05:10] PROBLEM - puppet last run on searchidx1001 is CRITICAL: CRITICAL: puppet fail [02:05:10] PROBLEM - puppet last run on mw1187 is CRITICAL: CRITICAL: puppet fail [02:05:19] PROBLEM - puppet last run on mw1041 is CRITICAL: CRITICAL: puppet fail [02:05:20] PROBLEM - puppet last run on ms-be1003 is CRITICAL: CRITICAL: puppet fail [02:05:20] PROBLEM - puppet last run on xenon is CRITICAL: CRITICAL: Puppet has 21 failures [02:05:28] Doesn't strike me as an error that gets missed over a long time [02:05:30] PROBLEM - puppet last run on gold is CRITICAL: CRITICAL: puppet fail [02:05:30] PROBLEM - puppet last run on mw1007 is CRITICAL: CRITICAL: puppet fail [02:05:30] PROBLEM - puppet last run on mw1134 is CRITICAL: CRITICAL: Puppet has 80 failures [02:05:30] PROBLEM - puppet last run on mw1115 is CRITICAL: CRITICAL: Puppet has 32 failures [02:05:30] PROBLEM - puppet last run on potassium is CRITICAL: CRITICAL: puppet fail [02:05:39] PROBLEM - puppet last run on cp3008 is CRITICAL: CRITICAL: Puppet has 16 failures [02:05:39] PROBLEM - puppet last run on amslvs2 is CRITICAL: CRITICAL: Puppet has 10 failures [02:05:39] PROBLEM - puppet last run on amssq53 is CRITICAL: CRITICAL: puppet fail [02:05:39] PROBLEM - puppet last run on elastic1018 is CRITICAL: CRITICAL: puppet fail [02:05:49] PROBLEM - puppet last run on es1008 is CRITICAL: CRITICAL: Puppet has 16 failures [02:05:49] PROBLEM - puppet last run on wtp1006 is CRITICAL: CRITICAL: puppet fail [02:05:49] PROBLEM - puppet last run on mw1026 is CRITICAL: CRITICAL: puppet fail [02:05:50] PROBLEM - puppet last run on logstash1001 is CRITICAL: CRITICAL: Puppet has 18 failures [02:05:59] PROBLEM - puppet last run on ms-be1006 is CRITICAL: CRITICAL: puppet fail [02:05:59] PROBLEM - puppet last run on analytics1020 is CRITICAL: CRITICAL: Puppet has 11 failures [02:05:59] PROBLEM - puppet last run on analytics1040 is CRITICAL: CRITICAL: Puppet has 23 failures [02:06:00] PROBLEM - puppet last run on mw1224 is CRITICAL: CRITICAL: Puppet has 76 failures [02:06:00] PROBLEM - puppet last run on ms-fe2004 is CRITICAL: CRITICAL: Puppet has 20 failures [02:06:00] PROBLEM - puppet last run on dbstore2001 is CRITICAL: CRITICAL: Puppet has 8 failures [02:06:00] PROBLEM - puppet last run on db2034 is CRITICAL: CRITICAL: puppet fail [02:06:00] PROBLEM - puppet last run on db2039 is CRITICAL: CRITICAL: puppet fail [02:06:00] PROBLEM - puppet last run on amssq54 is CRITICAL: CRITICAL: Puppet has 44 failures [02:06:01] PROBLEM - puppet last run on amssq61 is CRITICAL: CRITICAL: puppet fail [02:06:02] PROBLEM - puppet last run on mw1045 is CRITICAL: CRITICAL: Puppet has 30 failures [02:06:09] PROBLEM - puppet last run on analytics1025 is CRITICAL: CRITICAL: Puppet has 16 failures [02:06:09] PROBLEM - puppet last run on mw1254 is CRITICAL: CRITICAL: puppet fail [02:06:09] PROBLEM - puppet last run on wtp1020 is CRITICAL: CRITICAL: puppet fail [02:06:09] PROBLEM - puppet last run on mw1176 is CRITICAL: CRITICAL: puppet fail [02:06:09] PROBLEM - puppet last run on mw1082 is CRITICAL: CRITICAL: puppet fail [02:06:19] PROBLEM - puppet last run on wtp1016 is CRITICAL: CRITICAL: puppet fail [02:06:19] PROBLEM - puppet last run on elastic1007 is CRITICAL: CRITICAL: Puppet has 15 failures [02:06:19] PROBLEM - puppet last run on labstore1003 is CRITICAL: CRITICAL: Puppet has 10 failures [02:06:19] PROBLEM - puppet last run on cp1039 is CRITICAL: CRITICAL: puppet fail [02:06:19] PROBLEM - puppet last run on es2009 is CRITICAL: CRITICAL: puppet fail [02:06:19] PROBLEM - puppet last run on heze is CRITICAL: CRITICAL: puppet fail [02:06:20] PROBLEM - puppet last run on es2002 is CRITICAL: CRITICAL: Puppet has 16 failures [02:06:20] PROBLEM - puppet last run on ms-be2004 is CRITICAL: CRITICAL: puppet fail [02:06:21] PROBLEM - puppet last run on es2008 is CRITICAL: CRITICAL: Puppet has 19 failures [02:06:21] PROBLEM - puppet last run on db2019 is CRITICAL: CRITICAL: puppet fail [02:06:21] PROBLEM - puppet last run on db2005 is CRITICAL: CRITICAL: Puppet has 13 failures [02:06:22] PROBLEM - puppet last run on ms-fe1001 is CRITICAL: CRITICAL: puppet fail [02:06:22] PROBLEM - puppet last run on mc1003 is CRITICAL: CRITICAL: Puppet has 9 failures [02:06:23] PROBLEM - puppet last run on ms-be2006 is CRITICAL: CRITICAL: puppet fail [02:06:23] PROBLEM - puppet last run on ms-be2003 is CRITICAL: CRITICAL: Puppet has 27 failures [02:06:24] PROBLEM - puppet last run on mw1100 is CRITICAL: CRITICAL: puppet fail [02:06:24] PROBLEM - puppet last run on db1050 is CRITICAL: CRITICAL: puppet fail [02:06:26] PROBLEM - puppet last run on analytics1035 is CRITICAL: CRITICAL: puppet fail [02:06:27] PROBLEM - puppet last run on db1031 is CRITICAL: CRITICAL: puppet fail [02:06:27] PROBLEM - puppet last run on cp1047 is CRITICAL: CRITICAL: Puppet has 29 failures [02:06:27] PROBLEM - puppet last run on elastic1004 is CRITICAL: CRITICAL: Puppet has 24 failures [02:06:29] PROBLEM - puppet last run on mw1242 is CRITICAL: CRITICAL: puppet fail [02:06:29] PROBLEM - puppet last run on cp1055 is CRITICAL: CRITICAL: Puppet has 17 failures [02:06:29] PROBLEM - puppet last run on db1073 is CRITICAL: CRITICAL: Puppet has 19 failures [02:06:29] PROBLEM - puppet last run on analytics1041 is CRITICAL: CRITICAL: Puppet has 22 failures [02:06:29] PROBLEM - puppet last run on cp4006 is CRITICAL: CRITICAL: Puppet has 26 failures [02:06:30] PROBLEM - puppet last run on helium is CRITICAL: CRITICAL: Puppet has 11 failures [02:06:39] PROBLEM - puppet last run on platinum is CRITICAL: CRITICAL: Puppet has 22 failures [02:06:40] PROBLEM - puppet last run on mw1226 is CRITICAL: CRITICAL: puppet fail [02:06:49] PROBLEM - puppet last run on mw1160 is CRITICAL: CRITICAL: Puppet has 40 failures [02:06:49] PROBLEM - puppet last run on lvs1002 is CRITICAL: CRITICAL: Puppet has 18 failures [02:06:49] PROBLEM - puppet last run on lvs3001 is CRITICAL: CRITICAL: Puppet has 25 failures [02:06:49] PROBLEM - puppet last run on amssq32 is CRITICAL: CRITICAL: Puppet has 12 failures [02:06:49] PROBLEM - puppet last run on mc1006 is CRITICAL: CRITICAL: Puppet has 11 failures [02:06:50] PROBLEM - puppet last run on snapshot1003 is CRITICAL: CRITICAL: Puppet has 26 failures [02:06:50] PROBLEM - puppet last run on mw1189 is CRITICAL: CRITICAL: puppet fail [02:06:50] PROBLEM - puppet last run on elastic1021 is CRITICAL: CRITICAL: puppet fail [02:06:59] PROBLEM - puppet last run on lead is CRITICAL: CRITICAL: Puppet has 26 failures [02:06:59] PROBLEM - puppet last run on elastic1012 is CRITICAL: CRITICAL: puppet fail [02:06:59] PROBLEM - puppet last run on mw1235 is CRITICAL: CRITICAL: puppet fail [02:06:59] PROBLEM - puppet last run on mc1002 is CRITICAL: CRITICAL: puppet fail [02:06:59] PROBLEM - puppet last run on mw1117 is CRITICAL: CRITICAL: puppet fail [02:06:59] PROBLEM - puppet last run on mw1222 is CRITICAL: CRITICAL: puppet fail [02:07:00] PROBLEM - puppet last run on mw1009 is CRITICAL: CRITICAL: puppet fail [02:07:00] PROBLEM - puppet last run on sca1002 is CRITICAL: CRITICAL: Puppet has 12 failures [02:07:01] PROBLEM - puppet last run on db1022 is CRITICAL: CRITICAL: Puppet has 13 failures [02:07:01] PROBLEM - puppet last run on mw1174 is CRITICAL: CRITICAL: Puppet has 67 failures [02:07:09] PROBLEM - puppet last run on mw1150 is CRITICAL: CRITICAL: puppet fail [02:07:09] PROBLEM - puppet last run on elastic1001 is CRITICAL: CRITICAL: Puppet has 26 failures [02:07:10] PROBLEM - puppet last run on mw1099 is CRITICAL: CRITICAL: puppet fail [02:07:11] PROBLEM - puppet last run on mw1173 is CRITICAL: CRITICAL: puppet fail [02:07:11] PROBLEM - puppet last run on mw1069 is CRITICAL: CRITICAL: Puppet has 69 failures [02:07:11] PROBLEM - puppet last run on ms-fe2001 is CRITICAL: CRITICAL: puppet fail [02:07:11] PROBLEM - puppet last run on mw1250 is CRITICAL: CRITICAL: Puppet has 35 failures [02:07:19] PROBLEM - puppet last run on db1066 is CRITICAL: CRITICAL: Puppet has 23 failures [02:07:19] PROBLEM - puppet last run on cp3016 is CRITICAL: CRITICAL: Puppet has 21 failures [02:07:19] PROBLEM - puppet last run on db1018 is CRITICAL: CRITICAL: puppet fail [02:07:19] PROBLEM - puppet last run on mw1217 is CRITICAL: CRITICAL: Puppet has 34 failures [02:07:19] PROBLEM - puppet last run on mw1119 is CRITICAL: CRITICAL: puppet fail [02:07:20] PROBLEM - puppet last run on iron is CRITICAL: CRITICAL: Puppet has 24 failures [02:07:29] PROBLEM - puppet last run on mw1008 is CRITICAL: CRITICAL: puppet fail [02:07:29] PROBLEM - puppet last run on mw1205 is CRITICAL: CRITICAL: Puppet has 64 failures [02:07:30] PROBLEM - puppet last run on mw1088 is CRITICAL: CRITICAL: Puppet has 30 failures [02:07:30] PROBLEM - puppet last run on capella is CRITICAL: CRITICAL: Puppet has 26 failures [02:07:30] PROBLEM - puppet last run on es2001 is CRITICAL: CRITICAL: Puppet has 21 failures [02:07:30] PROBLEM - puppet last run on db2018 is CRITICAL: CRITICAL: puppet fail [02:07:30] PROBLEM - puppet last run on db2002 is CRITICAL: CRITICAL: Puppet has 19 failures [02:07:31] PROBLEM - puppet last run on lvs1005 is CRITICAL: CRITICAL: Puppet has 13 failures [02:07:31] PROBLEM - puppet last run on mw1060 is CRITICAL: CRITICAL: puppet fail [02:07:39] PROBLEM - puppet last run on mw1061 is CRITICAL: CRITICAL: puppet fail [02:07:39] PROBLEM - puppet last run on mw1120 is CRITICAL: CRITICAL: Puppet has 76 failures [02:07:39] PROBLEM - puppet last run on cp1061 is CRITICAL: CRITICAL: puppet fail [02:07:39] PROBLEM - puppet last run on mw1153 is CRITICAL: CRITICAL: Puppet has 26 failures [02:07:39] PROBLEM - puppet last run on elastic1008 is CRITICAL: CRITICAL: Puppet has 22 failures [02:07:39] PROBLEM - puppet last run on mw1003 is CRITICAL: CRITICAL: Puppet has 69 failures [02:07:40] PROBLEM - puppet last run on db1015 is CRITICAL: CRITICAL: puppet fail [02:07:40] PROBLEM - puppet last run on cp4003 is CRITICAL: CRITICAL: puppet fail [02:07:40] PROBLEM - puppet last run on elastic1027 is CRITICAL: CRITICAL: puppet fail [02:07:41] PROBLEM - puppet last run on virt1006 is CRITICAL: CRITICAL: puppet fail [02:07:49] PROBLEM - puppet last run on mw1164 is CRITICAL: CRITICAL: Puppet has 30 failures [02:07:49] PROBLEM - puppet last run on analytics1010 is CRITICAL: CRITICAL: puppet fail [02:07:49] PROBLEM - puppet last run on mw1046 is CRITICAL: CRITICAL: Puppet has 42 failures [02:07:50] PROBLEM - puppet last run on cp4008 is CRITICAL: CRITICAL: puppet fail [02:07:59] PROBLEM - puppet last run on mw1065 is CRITICAL: CRITICAL: Puppet has 31 failures [02:08:00] PROBLEM - puppet last run on amssq35 is CRITICAL: CRITICAL: Puppet has 16 failures [02:08:00] PROBLEM - puppet last run on cp3014 is CRITICAL: CRITICAL: puppet fail [02:08:09] PROBLEM - puppet last run on mw1228 is CRITICAL: CRITICAL: Puppet has 73 failures [02:08:09] PROBLEM - puppet last run on mw1068 is CRITICAL: CRITICAL: Puppet has 77 failures [02:08:09] PROBLEM - puppet last run on db1059 is CRITICAL: CRITICAL: Puppet has 12 failures [02:08:09] PROBLEM - puppet last run on mw1144 is CRITICAL: CRITICAL: Puppet has 31 failures [02:08:10] PROBLEM - puppet last run on ms-fe1004 is CRITICAL: CRITICAL: Puppet has 28 failures [02:08:10] PROBLEM - puppet last run on mw1166 is CRITICAL: CRITICAL: Puppet has 69 failures [02:08:10] PROBLEM - puppet last run on db1040 is CRITICAL: CRITICAL: Puppet has 15 failures [02:08:19] PROBLEM - puppet last run on mw1114 is CRITICAL: CRITICAL: puppet fail [02:08:19] PROBLEM - puppet last run on db1002 is CRITICAL: CRITICAL: puppet fail [02:08:19] PROBLEM - puppet last run on mw1025 is CRITICAL: CRITICAL: puppet fail [02:08:20] PROBLEM - puppet last run on lvs2004 is CRITICAL: CRITICAL: puppet fail [02:08:20] PROBLEM - puppet last run on mw1211 is CRITICAL: CRITICAL: puppet fail [02:08:20] PROBLEM - puppet last run on dbproxy1001 is CRITICAL: CRITICAL: puppet fail [02:08:20] PROBLEM - puppet last run on mw1052 is CRITICAL: CRITICAL: Puppet has 65 failures [02:08:20] PROBLEM - puppet last run on db1046 is CRITICAL: CRITICAL: Puppet has 12 failures [02:08:29] PROBLEM - puppet last run on mw1092 is CRITICAL: CRITICAL: Puppet has 68 failures [02:08:29] PROBLEM - puppet last run on labcontrol2001 is CRITICAL: CRITICAL: puppet fail [02:08:29] PROBLEM - puppet last run on amssq47 is CRITICAL: CRITICAL: puppet fail [02:08:30] PROBLEM - puppet last run on amssq48 is CRITICAL: CRITICAL: puppet fail [02:08:30] PROBLEM - puppet last run on cp3003 is CRITICAL: CRITICAL: Puppet has 22 failures [02:08:30] PROBLEM - puppet last run on mw1177 is CRITICAL: CRITICAL: puppet fail [02:08:30] PROBLEM - puppet last run on mw1170 is CRITICAL: CRITICAL: Puppet has 78 failures [02:08:39] PROBLEM - puppet last run on ruthenium is CRITICAL: CRITICAL: Puppet has 20 failures [02:08:39] PROBLEM - puppet last run on analytics1030 is CRITICAL: CRITICAL: Puppet has 26 failures [02:08:39] PROBLEM - puppet last run on mw1011 is CRITICAL: CRITICAL: puppet fail [02:08:39] PROBLEM - puppet last run on cp1056 is CRITICAL: CRITICAL: Puppet has 18 failures [02:08:39] PROBLEM - puppet last run on labsdb1003 is CRITICAL: CRITICAL: Puppet has 11 failures [02:08:39] PROBLEM - puppet last run on db1023 is CRITICAL: CRITICAL: Puppet has 14 failures [02:08:40] PROBLEM - puppet last run on db1042 is CRITICAL: CRITICAL: puppet fail [02:08:40] PROBLEM - puppet last run on db2036 is CRITICAL: CRITICAL: Puppet has 9 failures [02:08:41] PROBLEM - puppet last run on db2040 is CRITICAL: CRITICAL: puppet fail [02:08:41] PROBLEM - puppet last run on elastic1022 is CRITICAL: CRITICAL: puppet fail [02:08:49] PROBLEM - puppet last run on gallium is CRITICAL: CRITICAL: puppet fail [02:08:49] PROBLEM - puppet last run on elastic1030 is CRITICAL: CRITICAL: puppet fail [02:08:49] PROBLEM - puppet last run on mw1175 is CRITICAL: CRITICAL: puppet fail [02:08:49] PROBLEM - puppet last run on mw1042 is CRITICAL: CRITICAL: Puppet has 78 failures [02:08:50] PROBLEM - puppet last run on db1028 is CRITICAL: CRITICAL: Puppet has 18 failures [02:08:50] PROBLEM - puppet last run on cp4014 is CRITICAL: CRITICAL: puppet fail [02:08:59] PROBLEM - puppet last run on db1067 is CRITICAL: CRITICAL: Puppet has 11 failures [02:08:59] PROBLEM - puppet last run on mw1126 is CRITICAL: CRITICAL: puppet fail [02:08:59] PROBLEM - puppet last run on cp1058 is CRITICAL: CRITICAL: puppet fail [02:08:59] PROBLEM - puppet last run on tin is CRITICAL: CRITICAL: puppet fail [02:09:00] PROBLEM - puppet last run on mw1213 is CRITICAL: CRITICAL: puppet fail [02:09:10] PROBLEM - puppet last run on mw1118 is CRITICAL: CRITICAL: Puppet has 74 failures [02:09:10] PROBLEM - puppet last run on amssq60 is CRITICAL: CRITICAL: puppet fail [02:09:10] PROBLEM - puppet last run on amslvs1 is CRITICAL: CRITICAL: Puppet has 10 failures [02:09:10] PROBLEM - puppet last run on amssq55 is CRITICAL: CRITICAL: Puppet has 13 failures [02:09:19] PROBLEM - puppet last run on db1021 is CRITICAL: CRITICAL: Puppet has 13 failures [02:09:19] PROBLEM - puppet last run on mw1251 is CRITICAL: CRITICAL: Puppet has 34 failures [02:09:20] PROBLEM - puppet last run on db1034 is CRITICAL: CRITICAL: Puppet has 14 failures [02:09:20] PROBLEM - puppet last run on mw1054 is CRITICAL: CRITICAL: puppet fail [02:09:20] PROBLEM - puppet last run on mw1129 is CRITICAL: CRITICAL: puppet fail [02:09:29] PROBLEM - puppet last run on mw1172 is CRITICAL: CRITICAL: puppet fail [02:09:29] PROBLEM - puppet last run on mw1055 is CRITICAL: CRITICAL: puppet fail [02:09:29] PROBLEM - puppet last run on db1051 is CRITICAL: CRITICAL: Puppet has 8 failures [02:09:30] PROBLEM - puppet last run on mw1123 is CRITICAL: CRITICAL: Puppet has 38 failures [02:09:30] PROBLEM - puppet last run on mw1249 is CRITICAL: CRITICAL: puppet fail [02:09:30] PROBLEM - puppet last run on mw1208 is CRITICAL: CRITICAL: puppet fail [02:09:30] PROBLEM - puppet last run on lvs2001 is CRITICAL: CRITICAL: puppet fail [02:09:30] PROBLEM - puppet last run on lithium is CRITICAL: CRITICAL: puppet fail [02:09:40] PROBLEM - puppet last run on mw1206 is CRITICAL: CRITICAL: Puppet has 36 failures [02:09:40] PROBLEM - puppet last run on mw1195 is CRITICAL: CRITICAL: puppet fail [02:09:40] PROBLEM - puppet last run on logstash1002 is CRITICAL: CRITICAL: puppet fail [02:09:40] PROBLEM - puppet last run on mw1076 is CRITICAL: CRITICAL: puppet fail [02:09:40] PROBLEM - puppet last run on db2042 is CRITICAL: CRITICAL: puppet fail [02:09:40] PROBLEM - puppet last run on amssq46 is CRITICAL: CRITICAL: puppet fail [02:09:40] PROBLEM - puppet last run on amssq34 is CRITICAL: CRITICAL: puppet fail [02:09:41] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: puppet fail [02:09:42] PROBLEM - puppet last run on analytics1016 is CRITICAL: CRITICAL: Puppet has 26 failures [02:09:49] PROBLEM - puppet last run on pc1002 is CRITICAL: CRITICAL: Puppet has 23 failures [02:09:50] PROBLEM - puppet last run on mw1039 is CRITICAL: CRITICAL: Puppet has 77 failures [02:09:50] PROBLEM - puppet last run on ms-fe2003 is CRITICAL: CRITICAL: Puppet has 15 failures [02:09:50] PROBLEM - puppet last run on mw1237 is CRITICAL: CRITICAL: Puppet has 77 failures [02:09:59] PROBLEM - puppet last run on db2038 is CRITICAL: CRITICAL: Puppet has 10 failures [02:09:59] PROBLEM - puppet last run on mc1012 is CRITICAL: CRITICAL: puppet fail [02:09:59] PROBLEM - puppet last run on ms-be2011 is CRITICAL: CRITICAL: puppet fail [02:09:59] PROBLEM - puppet last run on labnet1001 is CRITICAL: CRITICAL: puppet fail [02:09:59] PROBLEM - puppet last run on db2007 is CRITICAL: CRITICAL: puppet fail [02:09:59] PROBLEM - puppet last run on mw1133 is CRITICAL: CRITICAL: puppet fail [02:10:00] PROBLEM - puppet last run on mw1002 is CRITICAL: CRITICAL: Puppet has 57 failures [02:10:00] PROBLEM - puppet last run on cp1046 is CRITICAL: CRITICAL: puppet fail [02:10:00] PROBLEM - puppet last run on mw1044 is CRITICAL: CRITICAL: puppet fail [02:10:01] PROBLEM - puppet last run on db1043 is CRITICAL: CRITICAL: puppet fail [02:10:01] PROBLEM - puppet last run on analytics1038 is CRITICAL: CRITICAL: puppet fail [02:10:09] PROBLEM - puppet last run on db1052 is CRITICAL: CRITICAL: puppet fail [02:10:09] PROBLEM - puppet last run on wtp1012 is CRITICAL: CRITICAL: Puppet has 21 failures [02:10:09] PROBLEM - puppet last run on cp4018 is CRITICAL: CRITICAL: puppet fail [02:10:09] PROBLEM - puppet last run on virt1001 is CRITICAL: CRITICAL: puppet fail [02:10:09] PROBLEM - puppet last run on labstore1001 is CRITICAL: CRITICAL: Puppet has 19 failures [02:10:10] PROBLEM - puppet last run on virt1003 is CRITICAL: CRITICAL: puppet fail [02:10:10] PROBLEM - puppet last run on analytics1026 is CRITICAL: CRITICAL: puppet fail [02:10:10] PROBLEM - puppet last run on db1003 is CRITICAL: CRITICAL: puppet fail [02:10:14] !log l10nupdate Synchronized php-1.25wmf14/cache/l10n: (no message) (duration: 00m 02s) [02:10:18] !log LocalisationUpdate completed (1.25wmf14) at 2015-01-18 02:10:18+00:00 [02:10:19] PROBLEM - puppet last run on snapshot1002 is CRITICAL: CRITICAL: puppet fail [02:10:19] PROBLEM - puppet last run on cp4004 is CRITICAL: CRITICAL: Puppet has 26 failures [02:10:19] PROBLEM - puppet last run on cp4001 is CRITICAL: CRITICAL: Puppet has 18 failures [02:10:19] PROBLEM - puppet last run on cp4005 is CRITICAL: CRITICAL: puppet fail [02:10:19] PROBLEM - puppet last run on cp4019 is CRITICAL: CRITICAL: puppet fail [02:10:19] PROBLEM - puppet last run on db1048 is CRITICAL: CRITICAL: Puppet has 19 failures [02:10:20] PROBLEM - puppet last run on mw1049 is CRITICAL: CRITICAL: puppet fail [02:10:20] PROBLEM - puppet last run on db1016 is CRITICAL: CRITICAL: puppet fail [02:10:20] PROBLEM - puppet last run on mw1162 is CRITICAL: CRITICAL: Puppet has 29 failures [02:10:25] Logged the message, Master [02:10:29] PROBLEM - puppet last run on cp3010 is CRITICAL: CRITICAL: Puppet has 15 failures [02:10:29] PROBLEM - puppet last run on amssq56 is CRITICAL: CRITICAL: puppet fail [02:10:29] PROBLEM - puppet last run on elastic1006 is CRITICAL: CRITICAL: Puppet has 17 failures [02:10:30] PROBLEM - puppet last run on db1026 is CRITICAL: CRITICAL: Puppet has 14 failures [02:10:30] PROBLEM - puppet last run on stat1003 is CRITICAL: CRITICAL: Puppet has 11 failures [02:10:30] PROBLEM - puppet last run on wtp1005 is CRITICAL: CRITICAL: Puppet has 15 failures [02:10:30] PROBLEM - puppet last run on plutonium is CRITICAL: CRITICAL: Puppet has 18 failures [02:10:30] Logged the message, Master [02:10:31] PROBLEM - puppet last run on mc1014 is CRITICAL: CRITICAL: puppet fail [02:10:31] PROBLEM - puppet last run on polonium is CRITICAL: CRITICAL: puppet fail [02:10:31] PROBLEM - puppet last run on antimony is CRITICAL: CRITICAL: puppet fail [02:10:39] PROBLEM - puppet last run on snapshot1001 is CRITICAL: CRITICAL: Puppet has 61 failures [02:10:39] PROBLEM - puppet last run on elastic1019 is CRITICAL: CRITICAL: Puppet has 22 failures [02:10:40] PROBLEM - puppet last run on es1007 is CRITICAL: CRITICAL: Puppet has 23 failures [02:10:40] PROBLEM - puppet last run on mw1227 is CRITICAL: CRITICAL: puppet fail [02:10:40] PROBLEM - puppet last run on elastic1024 is CRITICAL: CRITICAL: Puppet has 21 failures [02:10:40] PROBLEM - puppet last run on lvs2006 is CRITICAL: CRITICAL: puppet fail [02:10:49] PROBLEM - puppet last run on db1069 is CRITICAL: CRITICAL: puppet fail [02:10:49] PROBLEM - puppet last run on dataset1001 is CRITICAL: CRITICAL: Puppet has 32 failures [02:10:50] PROBLEM - puppet last run on analytics1013 is CRITICAL: CRITICAL: Puppet has 13 failures [02:10:50] PROBLEM - puppet last run on mw1079 is CRITICAL: CRITICAL: puppet fail [02:10:50] PROBLEM - puppet last run on db1036 is CRITICAL: CRITICAL: puppet fail [02:10:50] PROBLEM - puppet last run on analytics1022 is CRITICAL: CRITICAL: puppet fail [02:10:50] PROBLEM - puppet last run on mw1125 is CRITICAL: CRITICAL: puppet fail [02:10:51] PROBLEM - puppet last run on lvs3004 is CRITICAL: CRITICAL: puppet fail [02:10:51] PROBLEM - puppet last run on ms-be3002 is CRITICAL: CRITICAL: Puppet has 18 failures [02:10:51] PROBLEM - puppet last run on ms-fe3002 is CRITICAL: CRITICAL: puppet fail [02:10:59] PROBLEM - puppet last run on sodium is CRITICAL: CRITICAL: puppet fail [02:10:59] PROBLEM - puppet last run on mw1180 is CRITICAL: CRITICAL: Puppet has 33 failures [02:10:59] PROBLEM - puppet last run on cp1050 is CRITICAL: CRITICAL: Puppet has 13 failures [02:10:59] PROBLEM - puppet last run on stat1002 is CRITICAL: CRITICAL: puppet fail [02:11:00] PROBLEM - puppet last run on mc1005 is CRITICAL: CRITICAL: puppet fail [02:11:09] PROBLEM - puppet last run on mw1149 is CRITICAL: CRITICAL: Puppet has 30 failures [02:11:09] PROBLEM - puppet last run on argon is CRITICAL: CRITICAL: puppet fail [02:11:09] PROBLEM - puppet last run on mw1081 is CRITICAL: CRITICAL: puppet fail [02:11:09] PROBLEM - puppet last run on db1039 is CRITICAL: CRITICAL: Puppet has 11 failures [02:11:09] PROBLEM - puppet last run on db2016 is CRITICAL: CRITICAL: Puppet has 12 failures [02:11:09] PROBLEM - puppet last run on mw1014 is CRITICAL: CRITICAL: puppet fail [02:11:09] PROBLEM - puppet last run on es2004 is CRITICAL: CRITICAL: puppet fail [02:11:10] PROBLEM - puppet last run on db2029 is CRITICAL: CRITICAL: Puppet has 10 failures [02:11:10] PROBLEM - puppet last run on nembus is CRITICAL: CRITICAL: Puppet has 23 failures [02:11:11] PROBLEM - puppet last run on install2001 is CRITICAL: CRITICAL: Puppet has 10 failures [02:11:11] PROBLEM - puppet last run on mw1168 is CRITICAL: CRITICAL: puppet fail [02:11:12] PROBLEM - puppet last run on osmium is CRITICAL: CRITICAL: puppet fail [02:11:12] PROBLEM - puppet last run on virt1004 is CRITICAL: CRITICAL: Puppet has 16 failures [02:11:13] PROBLEM - puppet last run on mw1111 is CRITICAL: CRITICAL: Puppet has 33 failures [02:11:14] PROBLEM - puppet last run on wtp1018 is CRITICAL: CRITICAL: puppet fail [02:11:14] PROBLEM - puppet last run on lvs4003 is CRITICAL: CRITICAL: Puppet has 11 failures [02:11:14] PROBLEM - puppet last run on db1060 is CRITICAL: CRITICAL: puppet fail [02:11:19] PROBLEM - puppet last run on ms-be1012 is CRITICAL: CRITICAL: puppet fail [02:11:19] PROBLEM - puppet last run on bast4001 is CRITICAL: CRITICAL: Puppet has 24 failures [02:11:19] PROBLEM - puppet last run on labmon1001 is CRITICAL: CRITICAL: Puppet has 26 failures [02:11:19] PROBLEM - puppet last run on mw1084 is CRITICAL: CRITICAL: Puppet has 65 failures [02:11:20] PROBLEM - puppet last run on mw1238 is CRITICAL: CRITICAL: Puppet has 38 failures [02:11:29] PROBLEM - puppet last run on mw1247 is CRITICAL: CRITICAL: Puppet has 42 failures [02:11:29] PROBLEM - puppet last run on thallium is CRITICAL: CRITICAL: puppet fail [02:11:30] PROBLEM - puppet last run on mw1151 is CRITICAL: CRITICAL: Puppet has 33 failures [02:11:30] PROBLEM - puppet last run on analytics1023 is CRITICAL: CRITICAL: Puppet has 23 failures [02:11:30] PROBLEM - puppet last run on mw1098 is CRITICAL: CRITICAL: puppet fail [02:11:39] PROBLEM - puppet last run on virt1010 is CRITICAL: CRITICAL: Puppet has 14 failures [02:11:40] PROBLEM - puppet last run on elastic1015 is CRITICAL: CRITICAL: puppet fail [02:11:40] PROBLEM - puppet last run on amssq40 is CRITICAL: CRITICAL: Puppet has 16 failures [02:11:40] PROBLEM - puppet last run on amssq51 is CRITICAL: CRITICAL: Puppet has 31 failures [02:11:40] PROBLEM - puppet last run on amssq36 is CRITICAL: CRITICAL: Puppet has 29 failures [02:11:40] PROBLEM - puppet last run on ms-be3001 is CRITICAL: CRITICAL: Puppet has 8 failures [02:11:40] PROBLEM - puppet last run on oxygen is CRITICAL: CRITICAL: Puppet has 29 failures [02:11:49] PROBLEM - puppet last run on cp1048 is CRITICAL: CRITICAL: Puppet has 17 failures [02:11:49] PROBLEM - puppet last run on cp1038 is CRITICAL: CRITICAL: puppet fail [02:11:50] PROBLEM - puppet last run on mw1190 is CRITICAL: CRITICAL: Puppet has 36 failures [02:11:50] PROBLEM - puppet last run on mw1057 is CRITICAL: CRITICAL: puppet fail [02:11:50] PROBLEM - puppet last run on snapshot1004 is CRITICAL: CRITICAL: puppet fail [02:11:50] PROBLEM - puppet last run on mw1181 is CRITICAL: CRITICAL: Puppet has 35 failures [02:11:59] PROBLEM - puppet last run on gadolinium is CRITICAL: CRITICAL: Puppet has 33 failures [02:11:59] PROBLEM - puppet last run on mw1051 is CRITICAL: CRITICAL: Puppet has 30 failures [02:11:59] PROBLEM - puppet last run on rdb1001 is CRITICAL: CRITICAL: puppet fail [02:11:59] PROBLEM - puppet last run on hafnium is CRITICAL: CRITICAL: Puppet has 30 failures [02:11:59] PROBLEM - puppet last run on cp1062 is CRITICAL: CRITICAL: Puppet has 28 failures [02:11:59] PROBLEM - puppet last run on mw1183 is CRITICAL: CRITICAL: puppet fail [02:12:00] PROBLEM - puppet last run on labsdb1006 is CRITICAL: CRITICAL: Puppet has 26 failures [02:12:00] PROBLEM - puppet last run on db1071 is CRITICAL: CRITICAL: Puppet has 23 failures [02:12:01] PROBLEM - puppet last run on mw1050 is CRITICAL: CRITICAL: puppet fail [02:12:01] PROBLEM - puppet last run on mw1165 is CRITICAL: CRITICAL: Puppet has 74 failures [02:12:01] PROBLEM - puppet last run on db2037 is CRITICAL: CRITICAL: puppet fail [02:12:09] PROBLEM - puppet last run on mw1156 is CRITICAL: CRITICAL: puppet fail [02:12:09] PROBLEM - puppet last run on mw1030 is CRITICAL: CRITICAL: puppet fail [02:12:09] PROBLEM - puppet last run on mw1258 is CRITICAL: CRITICAL: puppet fail [02:12:09] PROBLEM - puppet last run on hooft is CRITICAL: CRITICAL: puppet fail [02:12:10] PROBLEM - puppet last run on db1004 is CRITICAL: CRITICAL: puppet fail [02:12:10] PROBLEM - puppet last run on ms-be1008 is CRITICAL: CRITICAL: Puppet has 28 failures [02:12:10] PROBLEM - puppet last run on mw1202 is CRITICAL: CRITICAL: Puppet has 33 failures [02:12:20] PROBLEM - puppet last run on db1020 is CRITICAL: CRITICAL: Puppet has 10 failures [02:12:20] PROBLEM - puppet last run on es2007 is CRITICAL: CRITICAL: Puppet has 14 failures [02:12:20] PROBLEM - puppet last run on db2001 is CRITICAL: CRITICAL: puppet fail [02:12:20] PROBLEM - puppet last run on db2023 is CRITICAL: CRITICAL: Puppet has 11 failures [02:12:20] PROBLEM - puppet last run on rubidium is CRITICAL: CRITICAL: puppet fail [02:12:20] PROBLEM - puppet last run on mw1188 is CRITICAL: CRITICAL: puppet fail [02:12:20] PROBLEM - puppet last run on ms-be2001 is CRITICAL: CRITICAL: Puppet has 16 failures [02:12:21] PROBLEM - puppet last run on ms-be2012 is CRITICAL: CRITICAL: Puppet has 18 failures [02:12:22] PROBLEM - puppet last run on db2004 is CRITICAL: CRITICAL: puppet fail [02:12:22] PROBLEM - puppet last run on ms-be2005 is CRITICAL: CRITICAL: Puppet has 16 failures [02:12:22] PROBLEM - puppet last run on ms-be2008 is CRITICAL: CRITICAL: puppet fail [02:12:29] PROBLEM - puppet last run on mw1146 is CRITICAL: CRITICAL: Puppet has 39 failures [02:12:30] PROBLEM - puppet last run on mw1034 is CRITICAL: CRITICAL: puppet fail [02:12:30] PROBLEM - puppet last run on cp1063 is CRITICAL: CRITICAL: Puppet has 26 failures [02:12:30] PROBLEM - puppet last run on wtp1023 is CRITICAL: CRITICAL: Puppet has 18 failures [02:12:30] PROBLEM - puppet last run on tungsten is CRITICAL: CRITICAL: Puppet has 27 failures [02:12:30] PROBLEM - puppet last run on wtp1002 is CRITICAL: CRITICAL: puppet fail [02:12:31] PROBLEM - puppet last run on virt1007 is CRITICAL: CRITICAL: Puppet has 11 failures [02:12:40] PROBLEM - puppet last run on db1062 is CRITICAL: CRITICAL: puppet fail [02:12:49] PROBLEM - puppet last run on amssq41 is CRITICAL: CRITICAL: Puppet has 21 failures [02:12:50] PROBLEM - puppet last run on db1001 is CRITICAL: CRITICAL: puppet fail [02:12:50] PROBLEM - puppet last run on wtp1022 is CRITICAL: CRITICAL: Puppet has 25 failures [02:13:00] PROBLEM - puppet last run on db1054 is CRITICAL: CRITICAL: puppet fail [02:13:00] PROBLEM - puppet last run on mw1074 is CRITICAL: CRITICAL: puppet fail [02:13:00] PROBLEM - puppet last run on mw1097 is CRITICAL: CRITICAL: puppet fail [02:13:00] PROBLEM - puppet last run on elastic1014 is CRITICAL: CRITICAL: Puppet has 15 failures [02:13:00] PROBLEM - puppet last run on rcs1001 is CRITICAL: CRITICAL: puppet fail [02:13:00] PROBLEM - puppet last run on mw1029 is CRITICAL: CRITICAL: puppet fail [02:13:09] PROBLEM - puppet last run on analytics1032 is CRITICAL: CRITICAL: Puppet has 21 failures [02:13:09] PROBLEM - puppet last run on mw1056 is CRITICAL: CRITICAL: Puppet has 32 failures [02:13:09] PROBLEM - puppet last run on mw1053 is CRITICAL: CRITICAL: puppet fail [02:13:10] PROBLEM - puppet last run on mw1004 is CRITICAL: CRITICAL: Puppet has 24 failures [02:13:10] PROBLEM - puppet last run on analytics1037 is CRITICAL: CRITICAL: Puppet has 13 failures [02:13:10] PROBLEM - puppet last run on ms-be1007 is CRITICAL: CRITICAL: Puppet has 15 failures [02:13:10] PROBLEM - puppet last run on lvs1001 is CRITICAL: CRITICAL: Puppet has 13 failures [02:13:10] PROBLEM - puppet last run on mw1163 is CRITICAL: CRITICAL: puppet fail [02:13:19] PROBLEM - puppet last run on mc1001 is CRITICAL: CRITICAL: puppet fail [02:13:19] PROBLEM - puppet last run on db1055 is CRITICAL: CRITICAL: Puppet has 7 failures [02:13:20] PROBLEM - puppet last run on mw1210 is CRITICAL: CRITICAL: puppet fail [02:13:20] PROBLEM - puppet last run on amssq38 is CRITICAL: CRITICAL: puppet fail [02:13:20] PROBLEM - puppet last run on mw1148 is CRITICAL: CRITICAL: puppet fail [02:13:21] PROBLEM - puppet last run on mw1159 is CRITICAL: CRITICAL: Puppet has 33 failures [02:13:21] PROBLEM - puppet last run on elastic1011 is CRITICAL: CRITICAL: Puppet has 17 failures [02:13:21] PROBLEM - puppet last run on ms-be1009 is CRITICAL: CRITICAL: Puppet has 10 failures [02:13:29] PROBLEM - puppet last run on titanium is CRITICAL: CRITICAL: Puppet has 11 failures [02:13:29] PROBLEM - puppet last run on db1057 is CRITICAL: CRITICAL: puppet fail [02:13:29] PROBLEM - puppet last run on mw1243 is CRITICAL: CRITICAL: puppet fail [02:13:29] PROBLEM - puppet last run on mw1212 is CRITICAL: CRITICAL: Puppet has 36 failures [02:13:30] PROBLEM - puppet last run on elastic1002 is CRITICAL: CRITICAL: puppet fail [02:13:30] PROBLEM - puppet last run on wtp1011 is CRITICAL: CRITICAL: puppet fail [02:13:30] PROBLEM - puppet last run on db2003 is CRITICAL: CRITICAL: puppet fail [02:13:30] PROBLEM - puppet last run on haedus is CRITICAL: CRITICAL: puppet fail [02:13:30] PROBLEM - puppet last run on ms-be2007 is CRITICAL: CRITICAL: Puppet has 29 failures [02:13:31] PROBLEM - puppet last run on acamar is CRITICAL: CRITICAL: puppet fail [02:13:32] PROBLEM - puppet last run on mw1198 is CRITICAL: CRITICAL: Puppet has 34 failures [02:13:39] PROBLEM - puppet last run on labsdb1004 is CRITICAL: CRITICAL: Puppet has 16 failures [02:13:39] PROBLEM - puppet last run on analytics1014 is CRITICAL: CRITICAL: puppet fail [02:13:40] PROBLEM - puppet last run on mw1116 is CRITICAL: CRITICAL: Puppet has 81 failures [02:13:40] PROBLEM - puppet last run on protactinium is CRITICAL: CRITICAL: puppet fail [02:13:50] PROBLEM - puppet last run on cp1060 is CRITICAL: CRITICAL: Puppet has 11 failures [02:13:50] PROBLEM - puppet last run on wtp1004 is CRITICAL: CRITICAL: Puppet has 17 failures [02:13:50] PROBLEM - puppet last run on mc1007 is CRITICAL: CRITICAL: Puppet has 21 failures [02:13:50] PROBLEM - puppet last run on mw1171 is CRITICAL: CRITICAL: Puppet has 73 failures [02:13:59] PROBLEM - puppet last run on mw1032 is CRITICAL: CRITICAL: Puppet has 26 failures [02:13:59] PROBLEM - puppet last run on mw1023 is CRITICAL: CRITICAL: Puppet has 67 failures [02:13:59] PROBLEM - puppet last run on mw1248 is CRITICAL: CRITICAL: Puppet has 41 failures [02:14:00] PROBLEM - puppet last run on cp3012 is CRITICAL: CRITICAL: puppet fail [02:14:00] PROBLEM - puppet last run on amssq62 is CRITICAL: CRITICAL: Puppet has 23 failures [02:14:00] PROBLEM - puppet last run on cp3009 is CRITICAL: CRITICAL: Puppet has 17 failures [02:14:00] PROBLEM - puppet last run on rdb1002 is CRITICAL: CRITICAL: Puppet has 21 failures [02:14:09] PROBLEM - puppet last run on elastic1017 is CRITICAL: CRITICAL: puppet fail [02:14:10] PROBLEM - puppet last run on mw1087 is CRITICAL: CRITICAL: Puppet has 67 failures [02:14:10] PROBLEM - puppet last run on rcs1002 is CRITICAL: CRITICAL: Puppet has 14 failures [02:14:20] PROBLEM - puppet last run on elastic1005 is CRITICAL: CRITICAL: puppet fail [02:14:20] PROBLEM - puppet last run on analytics1011 is CRITICAL: CRITICAL: puppet fail [02:14:20] PROBLEM - puppet last run on rdb1003 is CRITICAL: CRITICAL: puppet fail [02:14:20] PROBLEM - puppet last run on wtp1007 is CRITICAL: CRITICAL: puppet fail [02:14:20] PROBLEM - puppet last run on mw1239 is CRITICAL: CRITICAL: Puppet has 79 failures [02:14:20] PROBLEM - puppet last run on wtp1015 is CRITICAL: CRITICAL: puppet fail [02:14:21] PROBLEM - puppet last run on lvs2003 is CRITICAL: CRITICAL: Puppet has 15 failures [02:14:21] PROBLEM - puppet last run on es1002 is CRITICAL: CRITICAL: Puppet has 10 failures [02:14:29] PROBLEM - puppet last run on mw1186 is CRITICAL: CRITICAL: puppet fail [02:14:29] PROBLEM - puppet last run on mc1013 is CRITICAL: CRITICAL: puppet fail [02:14:30] PROBLEM - puppet last run on amslvs3 is CRITICAL: CRITICAL: Puppet has 23 failures [02:14:39] PROBLEM - puppet last run on wtp1013 is CRITICAL: CRITICAL: Puppet has 24 failures [02:14:39] PROBLEM - puppet last run on db1064 is CRITICAL: CRITICAL: puppet fail [02:14:39] PROBLEM - puppet last run on mw1167 is CRITICAL: CRITICAL: puppet fail [02:14:39] PROBLEM - puppet last run on mw1108 is CRITICAL: CRITICAL: puppet fail [02:14:39] PROBLEM - puppet last run on mw1001 is CRITICAL: CRITICAL: puppet fail [02:14:39] PROBLEM - puppet last run on db1063 is CRITICAL: CRITICAL: Puppet has 20 failures [02:14:50] PROBLEM - puppet last run on db1030 is CRITICAL: CRITICAL: Puppet has 15 failures [02:14:50] PROBLEM - puppet last run on mw1225 is CRITICAL: CRITICAL: puppet fail [02:14:50] PROBLEM - puppet last run on mw1185 is CRITICAL: CRITICAL: puppet fail [02:14:50] PROBLEM - puppet last run on elastic1023 is CRITICAL: CRITICAL: Puppet has 23 failures [02:14:51] PROBLEM - puppet last run on nitrogen is CRITICAL: CRITICAL: puppet fail [02:14:59] PROBLEM - puppet last run on mw1043 is CRITICAL: CRITICAL: puppet fail [02:14:59] PROBLEM - puppet last run on mw1010 is CRITICAL: CRITICAL: puppet fail [02:15:10] PROBLEM - puppet last run on db1047 is CRITICAL: CRITICAL: puppet fail [02:15:10] PROBLEM - puppet last run on pc1003 is CRITICAL: CRITICAL: puppet fail [02:15:19] PROBLEM - puppet last run on d-i-test is CRITICAL: CRITICAL: puppet fail [02:15:19] PROBLEM - puppet last run on db1044 is CRITICAL: CRITICAL: puppet fail [02:15:20] PROBLEM - puppet last run on mw1223 is CRITICAL: CRITICAL: puppet fail [02:15:20] PROBLEM - puppet last run on db1070 is CRITICAL: CRITICAL: Puppet has 12 failures [02:15:20] PROBLEM - puppet last run on mw1024 is CRITICAL: CRITICAL: puppet fail [02:15:20] PROBLEM - puppet last run on ocg1003 is CRITICAL: CRITICAL: Puppet has 20 failures [02:15:29] PROBLEM - puppet last run on mw1229 is CRITICAL: CRITICAL: Puppet has 67 failures [02:15:29] PROBLEM - puppet last run on mw1033 is CRITICAL: CRITICAL: Puppet has 33 failures [02:15:30] PROBLEM - puppet last run on mw1077 is CRITICAL: CRITICAL: Puppet has 36 failures [02:15:30] PROBLEM - puppet last run on virt1000 is CRITICAL: CRITICAL: Puppet has 49 failures [02:15:30] PROBLEM - puppet last run on analytics1004 is CRITICAL: CRITICAL: puppet fail [02:15:30] PROBLEM - puppet last run on iodine is CRITICAL: CRITICAL: Puppet has 36 failures [02:15:30] PROBLEM - puppet last run on db1038 is CRITICAL: CRITICAL: puppet fail [02:15:30] PROBLEM - puppet last run on cp1052 is CRITICAL: CRITICAL: Puppet has 19 failures [02:15:31] PROBLEM - puppet last run on mw1022 is CRITICAL: CRITICAL: Puppet has 66 failures [02:15:31] PROBLEM - puppet last run on wtp1003 is CRITICAL: CRITICAL: puppet fail [02:15:32] PROBLEM - puppet last run on es1010 is CRITICAL: CRITICAL: puppet fail [02:15:40] PROBLEM - puppet last run on mw1121 is CRITICAL: CRITICAL: puppet fail [02:15:41] PROBLEM - puppet last run on ms-fe2002 is CRITICAL: CRITICAL: puppet fail [02:15:41] PROBLEM - puppet last run on db1006 is CRITICAL: CRITICAL: Puppet has 23 failures [02:15:41] PROBLEM - puppet last run on amssq31 is CRITICAL: CRITICAL: puppet fail [02:15:41] PROBLEM - puppet last run on cp3004 is CRITICAL: CRITICAL: Puppet has 24 failures [02:15:41] PROBLEM - puppet last run on analytics1027 is CRITICAL: CRITICAL: Puppet has 24 failures [02:15:41] PROBLEM - puppet last run on cp1037 is CRITICAL: CRITICAL: puppet fail [02:15:41] PROBLEM - puppet last run on ms-fe3001 is CRITICAL: CRITICAL: Puppet has 24 failures [02:15:49] PROBLEM - puppet last run on mw1105 is CRITICAL: CRITICAL: Puppet has 36 failures [02:15:49] PROBLEM - puppet last run on mw1139 is CRITICAL: CRITICAL: puppet fail [02:15:49] PROBLEM - puppet last run on calcium is CRITICAL: CRITICAL: Puppet has 13 failures [02:15:49] PROBLEM - puppet last run on mercury is CRITICAL: CRITICAL: puppet fail [02:15:50] PROBLEM - puppet last run on iridium is CRITICAL: CRITICAL: Puppet has 24 failures [02:15:59] PROBLEM - puppet last run on db2012 is CRITICAL: CRITICAL: Puppet has 8 failures [02:15:59] PROBLEM - puppet last run on db2011 is CRITICAL: CRITICAL: Puppet has 15 failures [02:15:59] PROBLEM - puppet last run on db2028 is CRITICAL: CRITICAL: Puppet has 8 failures [02:16:00] PROBLEM - puppet last run on mw1122 is CRITICAL: CRITICAL: Puppet has 37 failures [02:16:00] PROBLEM - puppet last run on analytics1028 is CRITICAL: CRITICAL: Puppet has 23 failures [02:16:00] PROBLEM - puppet last run on fluorine is CRITICAL: CRITICAL: Puppet has 68 failures [02:16:09] PROBLEM - puppet last run on mw1219 is CRITICAL: CRITICAL: puppet fail [02:16:09] PROBLEM - puppet last run on cp4020 is CRITICAL: CRITICAL: puppet fail [02:16:09] PROBLEM - puppet last run on mw1152 is CRITICAL: CRITICAL: Puppet has 40 failures [02:16:10] PROBLEM - puppet last run on mw1231 is CRITICAL: CRITICAL: puppet fail [02:16:19] PROBLEM - puppet last run on dbstore1002 is CRITICAL: CRITICAL: Puppet has 6 failures [02:16:19] PROBLEM - puppet last run on db1061 is CRITICAL: CRITICAL: puppet fail [02:16:19] PROBLEM - puppet last run on strontium is CRITICAL: CRITICAL: puppet fail [02:16:20] PROBLEM - puppet last run on db1011 is CRITICAL: CRITICAL: Puppet has 8 failures [02:16:29] PROBLEM - puppet last run on mw1220 is CRITICAL: CRITICAL: Puppet has 72 failures [02:16:29] PROBLEM - puppet last run on mw1016 is CRITICAL: CRITICAL: puppet fail [02:16:29] PROBLEM - puppet last run on mw1201 is CRITICAL: CRITICAL: Puppet has 37 failures [02:16:29] PROBLEM - puppet last run on db1033 is CRITICAL: CRITICAL: Puppet has 28 failures [02:16:29] PROBLEM - puppet last run on mw1091 is CRITICAL: CRITICAL: Puppet has 58 failures [02:16:29] PROBLEM - puppet last run on lvs3003 is CRITICAL: CRITICAL: puppet fail [02:16:30] PROBLEM - puppet last run on mw1209 is CRITICAL: CRITICAL: Puppet has 33 failures [02:16:39] PROBLEM - puppet last run on elastic1020 is CRITICAL: CRITICAL: Puppet has 14 failures [02:16:39] PROBLEM - puppet last run on mw1071 is CRITICAL: CRITICAL: puppet fail [02:16:39] PROBLEM - puppet last run on mw1093 is CRITICAL: CRITICAL: Puppet has 32 failures [02:16:39] PROBLEM - puppet last run on db1072 is CRITICAL: CRITICAL: puppet fail [02:16:39] PROBLEM - puppet last run on virt1008 is CRITICAL: CRITICAL: puppet fail [02:16:39] PROBLEM - puppet last run on mw1143 is CRITICAL: CRITICAL: puppet fail [02:16:40] PROBLEM - puppet last run on rbf1001 is CRITICAL: CRITICAL: Puppet has 20 failures [02:16:40] PROBLEM - puppet last run on mw1027 is CRITICAL: CRITICAL: puppet fail [02:16:41] PROBLEM - puppet last run on mw1090 is CRITICAL: CRITICAL: puppet fail [02:16:41] PROBLEM - puppet last run on cp1040 is CRITICAL: CRITICAL: puppet fail [02:16:49] PROBLEM - puppet last run on ms-be1011 is CRITICAL: CRITICAL: Puppet has 32 failures [02:16:50] PROBLEM - puppet last run on mw1236 is CRITICAL: CRITICAL: Puppet has 66 failures [02:16:50] PROBLEM - puppet last run on ms-be1002 is CRITICAL: CRITICAL: puppet fail [02:16:50] PROBLEM - puppet last run on mw1104 is CRITICAL: CRITICAL: puppet fail [02:16:59] PROBLEM - puppet last run on amssq39 is CRITICAL: CRITICAL: puppet fail [02:16:59] PROBLEM - puppet last run on mw1204 is CRITICAL: CRITICAL: puppet fail [02:17:00] PROBLEM - puppet last run on bast1001 is CRITICAL: CRITICAL: puppet fail [02:17:00] PROBLEM - puppet last run on mw1064 is CRITICAL: CRITICAL: puppet fail [02:17:00] PROBLEM - puppet last run on mw1142 is CRITICAL: CRITICAL: Puppet has 35 failures [02:17:01] PROBLEM - puppet last run on mw1203 is CRITICAL: CRITICAL: Puppet has 66 failures [02:17:01] PROBLEM - puppet last run on virt1011 is CRITICAL: CRITICAL: Puppet has 13 failures [02:17:10] PROBLEM - puppet last run on achernar is CRITICAL: CRITICAL: puppet fail [02:17:10] PROBLEM - puppet last run on baham is CRITICAL: CRITICAL: Puppet has 24 failures [02:17:10] PROBLEM - puppet last run on wtp1010 is CRITICAL: CRITICAL: puppet fail [02:17:11] PROBLEM - puppet last run on mw1193 is CRITICAL: CRITICAL: puppet fail [02:17:11] PROBLEM - puppet last run on elastic1003 is CRITICAL: CRITICAL: Puppet has 9 failures [02:17:11] PROBLEM - puppet last run on cp1044 is CRITICAL: CRITICAL: Puppet has 13 failures [02:17:11] PROBLEM - puppet last run on chromium is CRITICAL: CRITICAL: puppet fail [02:17:19] PROBLEM - puppet last run on cp4002 is CRITICAL: CRITICAL: puppet fail [02:17:20] PROBLEM - puppet last run on cp4009 is CRITICAL: CRITICAL: puppet fail [02:17:20] PROBLEM - puppet last run on sca1001 is CRITICAL: CRITICAL: puppet fail [02:17:20] PROBLEM - puppet last run on mw1241 is CRITICAL: CRITICAL: Puppet has 36 failures [02:17:20] PROBLEM - puppet last run on lvs1004 is CRITICAL: CRITICAL: puppet fail [02:17:30] PROBLEM - puppet last run on mw1066 is CRITICAL: CRITICAL: Puppet has 37 failures [02:17:30] PROBLEM - puppet last run on cp1067 is CRITICAL: CRITICAL: puppet fail [02:17:30] PROBLEM - puppet last run on analytics1018 is CRITICAL: CRITICAL: Puppet has 22 failures [02:17:30] PROBLEM - puppet last run on einsteinium is CRITICAL: CRITICAL: puppet fail [02:17:30] PROBLEM - puppet last run on mw1215 is CRITICAL: CRITICAL: Puppet has 35 failures [02:17:30] PROBLEM - puppet last run on ms-be1015 is CRITICAL: CRITICAL: Puppet has 21 failures [02:17:30] PROBLEM - puppet last run on db1035 is CRITICAL: CRITICAL: Puppet has 21 failures [02:17:31] PROBLEM - puppet last run on cp4012 is CRITICAL: CRITICAL: Puppet has 21 failures [02:17:31] PROBLEM - puppet last run on terbium is CRITICAL: CRITICAL: Puppet has 42 failures [02:17:40] PROBLEM - puppet last run on cp3011 is CRITICAL: CRITICAL: puppet fail [02:17:41] PROBLEM - puppet last run on cp1045 is CRITICAL: CRITICAL: puppet fail [02:17:50] PROBLEM - puppet last run on wtp1008 is CRITICAL: CRITICAL: Puppet has 11 failures [02:17:50] PROBLEM - puppet last run on radium is CRITICAL: CRITICAL: puppet fail [02:17:53] !log l10nupdate Synchronized php-1.25wmf15/cache/l10n: (no message) (duration: 00m 01s) [02:17:57] !log LocalisationUpdate completed (1.25wmf15) at 2015-01-18 02:17:57+00:00 [02:17:59] PROBLEM - puppet last run on mw1037 is CRITICAL: CRITICAL: Puppet has 42 failures [02:17:59] PROBLEM - puppet last run on copper is CRITICAL: CRITICAL: Puppet has 23 failures [02:17:59] PROBLEM - puppet last run on mw1155 is CRITICAL: CRITICAL: puppet fail [02:18:00] PROBLEM - puppet last run on mw1021 is CRITICAL: CRITICAL: Puppet has 33 failures [02:18:00] PROBLEM - puppet last run on mw1112 is CRITICAL: CRITICAL: Puppet has 36 failures [02:18:01] Logged the message, Master [02:18:05] Logged the message, Master [02:18:10] PROBLEM - puppet last run on dbstore2002 is CRITICAL: CRITICAL: Puppet has 14 failures [02:18:10] PROBLEM - puppet last run on osm-cp1001 is CRITICAL: CRITICAL: Puppet has 10 failures [02:18:10] PROBLEM - puppet last run on amssq33 is CRITICAL: CRITICAL: Puppet has 24 failures [02:18:10] PROBLEM - puppet last run on cp3018 is CRITICAL: CRITICAL: Puppet has 12 failures [02:18:11] PROBLEM - puppet last run on mw1158 is CRITICAL: CRITICAL: Puppet has 40 failures [02:18:11] PROBLEM - puppet last run on mw1255 is CRITICAL: CRITICAL: Puppet has 80 failures [02:18:11] PROBLEM - puppet last run on db1056 is CRITICAL: CRITICAL: Puppet has 22 failures [02:18:19] PROBLEM - puppet last run on mw1154 is CRITICAL: CRITICAL: puppet fail [02:18:20] PROBLEM - puppet last run on mw1107 is CRITICAL: CRITICAL: Puppet has 76 failures [02:18:20] PROBLEM - puppet last run on cp1054 is CRITICAL: CRITICAL: Puppet has 27 failures [02:18:20] PROBLEM - puppet last run on db1037 is CRITICAL: CRITICAL: Puppet has 24 failures [02:18:20] PROBLEM - puppet last run on lvs1003 is CRITICAL: CRITICAL: puppet fail [02:18:20] PROBLEM - puppet last run on mw1086 is CRITICAL: CRITICAL: Puppet has 40 failures [02:18:20] PROBLEM - puppet last run on mw1253 is CRITICAL: CRITICAL: Puppet has 32 failures [02:18:20] PROBLEM - puppet last run on es2010 is CRITICAL: CRITICAL: Puppet has 16 failures [02:18:20] PROBLEM - puppet last run on db1027 is CRITICAL: CRITICAL: puppet fail [02:18:21] PROBLEM - puppet last run on ms-fe1002 is CRITICAL: CRITICAL: Puppet has 23 failures [02:18:29] PROBLEM - puppet last run on mw1131 is CRITICAL: CRITICAL: Puppet has 36 failures [02:18:29] PROBLEM - puppet last run on cp1053 is CRITICAL: CRITICAL: Puppet has 21 failures [02:18:29] PROBLEM - puppet last run on dysprosium is CRITICAL: CRITICAL: Puppet has 9 failures [02:18:29] PROBLEM - puppet last run on lvs4004 is CRITICAL: CRITICAL: Puppet has 10 failures [02:18:30] PROBLEM - puppet last run on wtp1001 is CRITICAL: CRITICAL: Puppet has 23 failures [02:18:39] PROBLEM - puppet last run on elastic1025 is CRITICAL: CRITICAL: puppet fail [02:18:39] PROBLEM - puppet last run on db1045 is CRITICAL: CRITICAL: Puppet has 13 failures [02:18:40] PROBLEM - puppet last run on elastic1029 is CRITICAL: CRITICAL: puppet fail [02:18:40] PROBLEM - puppet last run on labsdb1005 is CRITICAL: CRITICAL: puppet fail [02:18:40] PROBLEM - puppet last run on mw1207 is CRITICAL: CRITICAL: puppet fail [02:18:50] PROBLEM - puppet last run on cp1068 is CRITICAL: CRITICAL: Puppet has 15 failures [02:18:50] PROBLEM - puppet last run on eeden is CRITICAL: CRITICAL: Puppet has 17 failures [02:18:59] PROBLEM - puppet last run on mw1110 is CRITICAL: CRITICAL: Puppet has 33 failures [02:18:59] PROBLEM - puppet last run on mc1015 is CRITICAL: CRITICAL: puppet fail [02:19:10] PROBLEM - puppet last run on virt1005 is CRITICAL: CRITICAL: Puppet has 21 failures [02:19:19] PROBLEM - puppet last run on analytics1031 is CRITICAL: CRITICAL: Puppet has 8 failures [02:19:20] PROBLEM - puppet last run on cp3005 is CRITICAL: CRITICAL: Puppet has 57 failures [02:19:20] 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 [02:19:29] PROBLEM - puppet last run on mw1135 is CRITICAL: CRITICAL: Puppet has 67 failures [02:19:30] PROBLEM - puppet last run on db2017 is CRITICAL: CRITICAL: Puppet has 6 failures [02:19:39] PROBLEM - puppet last run on mw1113 is CRITICAL: CRITICAL: Puppet has 71 failures [02:20:30] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.044 second response time [02:26:19] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: puppet fail [02:28:50] RECOVERY - puppet last run on sodium is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [02:41:49] 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 [02:43:00] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.056 second response time [02:44:00] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [02:48:59] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [02:51:10] 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 [02:52:29] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.026 second response time [03:06:39] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: puppet fail [03:10:20] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: puppet fail [03:30:29] PROBLEM - puppet last run on sodium is CRITICAL: CRITICAL: puppet fail [03:43:30] 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 [03:44:39] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [03:44:40] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.041 second response time [03:48:10] RECOVERY - puppet last run on sodium is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [03:48:29] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [04:03:04] !log LocalisationUpdate ResourceLoader cache refresh completed at Sun Jan 18 04:03:03 UTC 2015 (duration 3m 2s) [04:03:12] Logged the message, Master [04:03:39] 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 [04:04:49] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.035 second response time [04:06:00] PROBLEM - puppet last run on ms1004 is CRITICAL: CRITICAL: puppet fail [04:08:49] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: puppet fail [04:10:40] PROBLEM - puppet last run on sodium is CRITICAL: CRITICAL: puppet fail [04:13:09] 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 [04:15:29] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.021 second response time [04:27:40] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [04:29:40] RECOVERY - puppet last run on sodium is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [04:39:13] (03PS1) 10Mattflaschen: Add Flooders group on Officewiki [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185663 [04:40:04] (03PS2) 10Mattflaschen: Add Flooders group on Officewiki [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185663 (https://phabricator.wikimedia.org/T86237) [04:41:20] 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 [04:42:04] (03PS1) 10Tim Landscheidt: Tools: Install valgrind on bastions [puppet] - 10https://gerrit.wikimedia.org/r/185664 (https://phabricator.wikimedia.org/T87117) [04:42:30] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.033 second response time [04:48:59] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: puppet fail [04:49:50] PROBLEM - puppetmaster https on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:51:59] 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 [04:53:09] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.018 second response time [04:53:50] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [04:54:19] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:54:49] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [04:55:00] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [04:55:50] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [04:56:00] 3: Make Puppet repository pass lenient and strict lint checks - https://phabricator.wikimedia.org/T87132#984443 (10scfc) 3NEW [04:56:39] 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 [04:57:50] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.031 second response time [04:59:00] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 2.237 second response time [05:00:59] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:02:30] 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 [05:03:09] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:04:59] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.028 second response time [05:06:39] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:07:59] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:08:29] 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 [05:09:00] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [05:09:39] PROBLEM - Unmerged changes on repository puppet on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:09:40] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.024 second response time [05:10:10] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [05:10:40] RECOVERY - Unmerged changes on repository puppet on virt1000 is OK: No changes to merge. [05:11:00] PROBLEM - puppet last run on sodium is CRITICAL: CRITICAL: puppet fail [05:11:40] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [05:14:59] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:14:59] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:15:10] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:15:30] 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 [05:16:00] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [05:16:09] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [05:16:40] RECOVERY - puppetmaster https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.038 second response time [05:22:49] PROBLEM - Unmerged changes on repository puppet on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:24:00] RECOVERY - puppet last run on ms1004 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [05:28:10] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:29:29] PROBLEM - puppet last run on nescio is CRITICAL: CRITICAL: puppet fail [05:30:29] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [05:33:41] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:34:09] PROBLEM - DPKG on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:34:50] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 5.338 second response time [05:35:19] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:36:20] RECOVERY - DPKG on virt1000 is OK: All packages OK [05:36:20] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [05:40:10] PROBLEM - DPKG on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:42:32] RECOVERY - DPKG on virt1000 is OK: All packages OK [05:46:30] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [05:46:39] RECOVERY - Unmerged changes on repository puppet on virt1000 is OK: No changes to merge. [05:47:19] PROBLEM - DPKG on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:48:29] RECOVERY - DPKG on virt1000 is OK: All packages OK [05:48:30] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:49:30] !log restart apache2 on palladium, mod_passenger deadlock (known) [05:49:40] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [05:49:50] RECOVERY - puppet last run on cp1048 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [05:49:59] RECOVERY - puppet last run on ms-be2001 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [05:49:59] RECOVERY - puppet last run on ms-be2005 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:50:10] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:50:19] RECOVERY - puppetmaster backend https on palladium is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.118 second response time [05:50:20] RECOVERY - puppet last run on db1055 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:50:20] RECOVERY - puppet last run on elastic1011 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [05:50:30] RECOVERY - puppet last run on wtp1018 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [05:50:39] RECOVERY - puppet last run on ms-be1012 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:50:39] RECOVERY - puppet last run on wtp1023 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:50:40] RECOVERY - puppet last run on wtp1002 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [05:50:40] RECOVERY - puppet last run on wtp1004 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [05:50:40] RECOVERY - puppet last run on db1062 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [05:50:50] RECOVERY - puppet last run on mw1248 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [05:50:50] RECOVERY - puppet last run on mw1171 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:50:50] RECOVERY - puppet last run on db1054 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [05:50:50] RECOVERY - puppet last run on wtp1022 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [05:51:09] RECOVERY - puppet last run on mw1074 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [05:51:09] RECOVERY - puppet last run on mw1097 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:51:09] RECOVERY - puppet last run on es2007 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:51:10] RECOVERY - puppet last run on elastic1014 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:51:10] RECOVERY - puppet last run on haedus is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [05:51:10] RECOVERY - puppet last run on acamar is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [05:51:10] RECOVERY - puppet last run on ms-be2007 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:51:10] RECOVERY - puppet last run on es1002 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [05:51:10] RECOVERY - puppet last run on mw1029 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:51:19] RECOVERY - puppet last run on analytics1032 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [05:51:20] RECOVERY - puppet last run on ms-be1007 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:51:20] RECOVERY - puppet last run on mc1001 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [05:51:29] RECOVERY - puppet last run on analytics1037 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:51:29] RECOVERY - puppet last run on mw1163 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [05:51:29] RECOVERY - puppet last run on analytics1011 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [05:51:29] RECOVERY - puppet last run on mw1210 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:51:29] RECOVERY - puppet last run on mw1050 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:51:29] RECOVERY - puppet last run on titanium is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [05:51:30] RECOVERY - puppet last run on lvs1001 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:51:30] RECOVERY - puppet last run on wtp1013 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:51:30] RECOVERY - puppet last run on ms-be1009 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:51:31] RECOVERY - puppet last run on db1057 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [05:51:39] RECOVERY - puppet last run on wtp1011 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:51:39] RECOVERY - puppet last run on mw1212 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [05:51:40] RECOVERY - puppet last run on mw1188 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:51:49] RECOVERY - puppet last run on lvs2003 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:51:49] RECOVERY - puppet last run on labsdb1004 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [05:51:49] RECOVERY - puppet last run on elastic1002 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:51:49] RECOVERY - puppet last run on mw1198 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [05:51:50] RECOVERY - puppet last run on protactinium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:52:00] RECOVERY - puppet last run on mc1007 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:52:00] RECOVERY - puppet last run on mw1116 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [05:52:01] RECOVERY - puppet last run on pc1003 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [05:52:01] RECOVERY - puppet last run on db1001 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:52:01] RECOVERY - puppet last run on rdb1002 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:52:01] RECOVERY - puppet last run on mw1023 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:52:01] RECOVERY - puppet last run on analytics1014 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:52:02] RECOVERY - puppet last run on amslvs3 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:52:09] RECOVERY - puppet last run on cp1038 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [05:52:10] RECOVERY - puppet last run on elastic1017 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [05:52:19] RECOVERY - puppet last run on mw1087 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [05:52:19] RECOVERY - puppet last run on rdb1003 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [05:52:20] RECOVERY - puppet last run on db2003 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:52:20] RECOVERY - puppet last run on rcs1001 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:52:20] RECOVERY - puppet last run on rcs1002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:52:29] RECOVERY - puppet last run on elastic1005 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:52:29] RECOVERY - puppet last run on wtp1015 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:52:29] RECOVERY - puppet last run on mw1239 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [05:52:30] RECOVERY - puppet last run on mc1013 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:52:39] RECOVERY - puppet last run on mw1053 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:52:40] RECOVERY - puppet last run on db1063 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [05:52:40] RECOVERY - puppet last run on db1064 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [05:52:40] RECOVERY - puppet last run on mw1121 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [05:52:49] RECOVERY - puppet last run on mw1148 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:52:49] RECOVERY - puppet last run on mw1167 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:52:50] RECOVERY - puppet last run on mw1243 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:52:50] RECOVERY - puppet last run on db1030 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [05:52:50] RECOVERY - puppet last run on nitrogen is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:52:50] RECOVERY - puppet last run on cp3009 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [05:52:50] RECOVERY - puppet last run on mw1225 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:52:59] RECOVERY - puppet last run on elastic1023 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:53:00] RECOVERY - puppet last run on analytics1028 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [05:53:09] RECOVERY - puppet last run on cp1060 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:53:09] RECOVERY - puppet last run on db1061 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:53:10] RECOVERY - puppet last run on ms-fe2002 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [05:53:10] RECOVERY - puppet last run on db1011 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:53:10] RECOVERY - puppet last run on db1070 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [05:53:10] RECOVERY - puppet last run on db1033 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [05:53:19] RECOVERY - puppet last run on mw1032 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [05:53:19] RECOVERY - puppet last run on db1044 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [05:53:19] RECOVERY - puppet last run on mw1201 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [05:53:20] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:53:29] RECOVERY - puppet last run on ms-fe3001 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [05:53:29] RECOVERY - puppet last run on ocg1003 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:53:30] RECOVERY - puppet last run on d-i-test is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [05:53:30] RECOVERY - puppet last run on mw1024 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:53:30] RECOVERY - puppet last run on analytics1004 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:53:30] RECOVERY - puppet last run on mw1229 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:53:30] RECOVERY - puppet last run on db2011 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:53:30] RECOVERY - puppet last run on wtp1007 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [05:53:31] RECOVERY - puppet last run on db2012 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [05:53:39] RECOVERY - puppet last run on db1038 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [05:53:39] RECOVERY - puppet last run on iodine is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:53:40] RECOVERY - puppet last run on wtp1003 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:53:40] RECOVERY - puppet last run on mw1033 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:53:40] RECOVERY - puppet last run on ms-be1011 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [05:53:40] RECOVERY - puppet last run on mw1077 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:53:49] RECOVERY - puppet last run on db1006 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [05:53:49] RECOVERY - puppet last run on mw1022 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:53:49] RECOVERY - puppet last run on es1010 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:53:49] RECOVERY - puppet last run on calcium is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [05:53:50] RECOVERY - puppet last run on analytics1027 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [05:53:50] RECOVERY - puppet last run on mw1186 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:54:00] RECOVERY - puppet last run on mercury is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [05:54:00] RECOVERY - puppet last run on iridium is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [05:54:00] RECOVERY - puppet last run on mw1105 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [05:54:00] RECOVERY - puppet last run on mw1139 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:54:00] RECOVERY - puppet last run on mw1108 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [05:54:00] RECOVERY - puppet last run on mw1001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:54:01] RECOVERY - puppet last run on cp1044 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [05:54:01] RECOVERY - puppet last run on wtp1010 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [05:54:01] RECOVERY - puppet last run on cp3012 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [05:54:09] RECOVERY - puppet last run on amssq62 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [05:54:09] RECOVERY - puppet last run on fluorine is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [05:54:09] RECOVERY - puppet last run on mw1185 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:54:09] RECOVERY - puppet last run on mw1122 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [05:54:19] RECOVERY - puppet last run on elastic1003 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:54:19] RECOVERY - puppet last run on mw1219 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:54:20] RECOVERY - puppet last run on strontium is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [05:54:20] RECOVERY - puppet last run on dbstore1002 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:54:20] RECOVERY - puppet last run on mw1152 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [05:54:20] RECOVERY - puppet last run on mw1043 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:54:20] RECOVERY - puppet last run on mw1231 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:54:20] RECOVERY - puppet last run on dbstore2002 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [05:54:20] RECOVERY - puppet last run on mw1010 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:54:21] RECOVERY - puppet last run on db1047 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:54:21] RECOVERY - puppet last run on einsteinium is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [05:54:30] RECOVERY - puppet last run on analytics1018 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:54:30] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [05:54:30] RECOVERY - puppet last run on cp3004 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:54:30] RECOVERY - puppet last run on mw1016 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:54:30] RECOVERY - puppet last run on mw1091 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [05:54:30] RECOVERY - puppet last run on mw1223 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:54:30] RECOVERY - puppet last run on mw1209 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:54:40] RECOVERY - puppet last run on amssq38 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:54:40] RECOVERY - puppet last run on db1072 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [05:54:40] RECOVERY - puppet last run on elastic1020 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:54:40] RECOVERY - puppet last run on rbf1001 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:54:41] RECOVERY - puppet last run on achernar is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:54:49] RECOVERY - puppet last run on mw1093 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [05:54:49] RECOVERY - puppet last run on db2028 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:54:49] RECOVERY - puppet last run on cp1052 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:54:50] RECOVERY - puppet last run on copper is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:55:00] RECOVERY - puppet last run on ms-be1002 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [05:55:00] RECOVERY - puppet last run on cp1037 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:55:09] RECOVERY - puppet last run on db1056 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [05:55:10] RECOVERY - puppet last run on virt1011 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [05:55:10] RECOVERY - puppet last run on mw1107 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:55:11] RECOVERY - puppet last run on mw1203 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [05:55:11] RECOVERY - puppet last run on chromium is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [05:55:11] RECOVERY - puppet last run on mw1142 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [05:55:11] RECOVERY - puppet last run on lvs3003 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [05:55:19] RECOVERY - puppet last run on mw1086 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [05:55:29] RECOVERY - puppet last run on mw1241 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [05:55:30] RECOVERY - puppet last run on wtp1001 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [05:55:30] RECOVERY - puppet last run on ms-be1015 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [05:55:39] RECOVERY - puppet last run on db1035 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:55:39] RECOVERY - puppet last run on mw1215 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:55:39] RECOVERY - puppet last run on mw1066 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:55:40] RECOVERY - puppet last run on cp1045 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [05:55:40] RECOVERY - puppet last run on mc1015 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:55:49] RECOVERY - puppet last run on virt1008 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:55:49] RECOVERY - puppet last run on cp3018 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [05:55:50] RECOVERY - puppet last run on wtp1008 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [05:55:59] RECOVERY - puppet last run on mw1071 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [05:55:59] RECOVERY - puppet last run on baham is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [05:55:59] RECOVERY - puppet last run on cp1040 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [05:55:59] RECOVERY - puppet last run on es2010 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [05:56:00] RECOVERY - puppet last run on lvs4004 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [05:56:00] RECOVERY - puppet last run on mw1143 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [05:56:00] RECOVERY - puppet last run on mw1027 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [05:56:00] RECOVERY - puppet last run on radium is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [05:56:10] RECOVERY - puppet last run on osm-cp1001 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [05:56:10] RECOVERY - puppet last run on mw1090 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [05:56:10] RECOVERY - puppet last run on mw1236 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:56:10] RECOVERY - puppet last run on mw1037 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:56:19] RECOVERY - puppet last run on mw1021 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:56:19] RECOVERY - puppet last run on bast1001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:56:19] RECOVERY - puppet last run on mw1112 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [05:56:19] RECOVERY - puppet last run on analytics1031 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:56:19] RECOVERY - puppet last run on analytics1012 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [05:56:19] RECOVERY - puppet last run on mw1204 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:56:20] RECOVERY - puppet last run on mw1255 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [05:56:20] RECOVERY - puppet last run on mw1104 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:56:20] RECOVERY - puppet last run on lvs1003 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [05:56:29] RECOVERY - puppet last run on palladium is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:56:29] RECOVERY - puppet last run on ms-fe1002 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [05:56:29] RECOVERY - puppet last run on mw1064 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [05:56:29] RECOVERY - puppet last run on mw1253 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [05:56:29] RECOVERY - puppet last run on db1037 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:56:29] RECOVERY - puppet last run on dysprosium is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [05:56:39] RECOVERY - puppet last run on mw1193 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:56:39] RECOVERY - puppet last run on db1027 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [05:56:39] RECOVERY - puppet last run on mw1113 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:56:40] RECOVERY - puppet last run on sca1001 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [05:56:40] RECOVERY - puppet last run on lvs1004 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [05:56:40] RECOVERY - puppet last run on mw1131 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:56:40] RECOVERY - puppet last run on terbium is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:56:40] RECOVERY - puppet last run on db1045 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:56:49] RECOVERY - puppet last run on cp1067 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [05:56:50] RECOVERY - puppet last run on elastic1025 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [05:56:50] RECOVERY - puppet last run on labsdb1005 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:56:50] RECOVERY - puppet last run on cp1068 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [05:56:51] RECOVERY - puppet last run on elastic1029 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [05:56:51] RECOVERY - puppet last run on mw1207 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [05:56:51] RECOVERY - puppet last run on mw1220 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:56:59] RECOVERY - puppet last run on hydrogen is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [05:57:00] RECOVERY - puppet last run on cp3005 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:57:00] RECOVERY - puppet last run on amssq31 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [05:57:00] RECOVERY - puppet last run on amssq33 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [05:57:00] RECOVERY - puppet last run on lvs2002 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [05:57:09] RECOVERY - puppet last run on db1009 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:57:09] RECOVERY - puppet last run on mw1110 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [05:57:10] RECOVERY - puppet last run on db2017 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:57:10] RECOVERY - puppet last run on db2010 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:57:10] RECOVERY - puppet last run on es2006 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [05:57:10] RECOVERY - puppet last run on bast2001 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [05:57:10] RECOVERY - puppet last run on mw1103 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:57:10] RECOVERY - puppet last run on elastic1009 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [05:57:10] RECOVERY - puppet last run on radon is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [05:57:19] RECOVERY - puppet last run on mw1155 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [05:57:19] RECOVERY - puppet last run on cp4009 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [05:57:19] RECOVERY - puppet last run on virt1005 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [05:57:19] RECOVERY - puppet last run on cp4020 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [05:57:19] RECOVERY - puppet last run on labsdb1002 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [05:57:20] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [05:57:29] RECOVERY - puppet last run on ms-be1010 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:57:30] RECOVERY - puppet last run on virt1009 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [05:57:30] RECOVERY - puppet last run on mw1158 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [05:57:30] RECOVERY - puppet last run on es1004 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:57:30] RECOVERY - puppet last run on mw1154 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [05:57:40] RECOVERY - puppet last run on analytics1021 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:57:40] RECOVERY - puppet last run on cp1054 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [05:57:40] RECOVERY - puppet last run on mw1018 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [05:57:40] RECOVERY - puppet last run on db1049 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:57:41] RECOVERY - puppet last run on lvs3002 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [05:57:41] RECOVERY - puppet last run on eeden is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [05:57:41] RECOVERY - puppet last run on cp1053 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:57:49] RECOVERY - puppet last run on mw1135 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:57:50] RECOVERY - puppet last run on lvs2005 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:57:50] RECOVERY - puppet last run on mw1137 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [05:58:00] RECOVERY - puppet last run on mw1230 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [05:58:00] RECOVERY - puppet last run on pollux is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [05:58:00] RECOVERY - puppet last run on ms-be1014 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:00] RECOVERY - puppet last run on mw1128 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [05:58:00] RECOVERY - puppet last run on mw1199 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [05:58:09] RECOVERY - puppet last run on ms-be3004 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [05:58:19] RECOVERY - puppet last run on amssq39 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:19] RECOVERY - puppet last run on cp3007 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:58:19] RECOVERY - puppet last run on cp3017 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [05:58:19] RECOVERY - puppet last run on mw1179 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [05:58:19] RECOVERY - puppet last run on mw1047 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:58:19] RECOVERY - puppet last run on mw1073 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [05:58:20] RECOVERY - puppet last run on db1005 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:58:20] RECOVERY - puppet last run on elastic1010 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [05:58:21] RECOVERY - puppet last run on ms-be2009 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [05:58:29] RECOVERY - puppet last run on db1068 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:29] RECOVERY - puppet last run on mw1070 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [05:58:30] RECOVERY - puppet last run on analytics1029 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:58:30] RECOVERY - puppet last run on cp4002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:30] RECOVERY - puppet last run on cp4012 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [05:58:30] RECOVERY - puppet last run on mw1194 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:39] RECOVERY - puppet last run on mw1020 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [05:58:39] RECOVERY - puppet last run on analytics1024 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:58:39] RECOVERY - puppet last run on wtp1014 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:58:40] RECOVERY - puppet last run on cp1064 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [05:58:40] RECOVERY - puppet last run on tmh1001 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:58:40] RECOVERY - puppet last run on elastic1013 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:50] RECOVERY - puppet last run on db1058 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:58:50] RECOVERY - puppet last run on es1005 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [05:58:50] PROBLEM - Unmerged changes on repository puppet on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [05:58:50] RECOVERY - puppet last run on lvs1006 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [05:58:50] RECOVERY - puppet last run on mw1095 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:58:50] RECOVERY - puppet last run on ms-be1005 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:58:50] RECOVERY - puppet last run on db1019 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [05:58:51] RECOVERY - puppet last run on labsdb1007 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:58:51] RECOVERY - puppet last run on mw1017 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:58:52] RECOVERY - puppet last run on elastic1016 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [05:58:59] RECOVERY - puppet last run on amssq37 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [05:58:59] RECOVERY - puppet last run on cp3011 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [05:58:59] RECOVERY - puppet last run on cp3019 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [05:59:00] RECOVERY - puppetmaster https on virt1000 is OK: HTTP OK: Status line output matched 400 - 335 bytes in 3.414 second response time [05:59:09] RECOVERY - puppet last run on lanthanum is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [05:59:09] RECOVERY - puppet last run on mw1075 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [05:59:09] RECOVERY - puppet last run on mw1078 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [05:59:09] RECOVERY - puppet last run on ocg1002 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [05:59:10] RECOVERY - puppet last run on mw1083 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [05:59:10] RECOVERY - puppet last run on mw1169 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [05:59:10] RECOVERY - puppet last run on cp1066 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [05:59:10] RECOVERY - puppet last run on mw1058 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:59:10] RECOVERY - puppet last run on db1024 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [05:59:11] RECOVERY - puppet last run on praseodymium is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [05:59:11] RECOVERY - puppet last run on mw1101 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [05:59:12] RECOVERY - puppet last run on mw1102 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [05:59:19] RECOVERY - puppet last run on stat1001 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [05:59:19] RECOVERY - puppet last run on mw1214 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [05:59:19] RECOVERY - puppet last run on es1003 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [05:59:19] RECOVERY - puppet last run on mw1085 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [05:59:19] RECOVERY - puppet last run on mw1184 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [05:59:20] RECOVERY - puppet last run on mw1127 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [05:59:30] RECOVERY - puppet last run on analytics1034 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [05:59:30] RECOVERY - puppet last run on db2041 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [05:59:39] RECOVERY - puppet last run on ms-be2015 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [05:59:39] RECOVERY - puppet last run on ms-be2010 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:59:40] RECOVERY - puppet last run on lvs4001 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:59:40] RECOVERY - puppet last run on mw1191 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [05:59:40] RECOVERY - puppet last run on cp4013 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [05:59:40] RECOVERY - puppet last run on cp4015 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [05:59:40] RECOVERY - puppet last run on cp4016 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [05:59:40] RECOVERY - puppet last run on tmh1002 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [05:59:41] RECOVERY - puppet last run on cp4011 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [05:59:49] RECOVERY - puppet last run on cp4010 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [05:59:49] RECOVERY - puppet last run on db1041 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [05:59:59] RECOVERY - Unmerged changes on repository puppet on virt1000 is OK: No changes to merge. [05:59:59] RECOVERY - puppet last run on mw1015 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:00] RECOVERY - puppet last run on mw1094 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:00:00] RECOVERY - puppet last run on mw1136 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:00] RECOVERY - puppet last run on mw1013 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:00:00] RECOVERY - puppet last run on virt1012 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:00:00] RECOVERY - puppet last run on db1007 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:00:09] RECOVERY - puppet last run on mw1182 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:00:09] RECOVERY - puppet last run on mw1157 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:09] RECOVERY - puppet last run on cp3021 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:00:09] RECOVERY - puppet last run on amssq50 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:19] RECOVERY - puppet last run on mw1019 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:19] RECOVERY - puppet last run on db1010 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [06:00:19] RECOVERY - puppet last run on es1006 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:00:20] RECOVERY - puppet last run on mc1008 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:00:20] RECOVERY - puppet last run on analytics1019 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [06:00:20] RECOVERY - puppet last run on cp1043 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:00:20] RECOVERY - puppet last run on mw1246 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:00:20] RECOVERY - puppet last run on db2035 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [06:00:29] RECOVERY - puppet last run on labsdb1001 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:00:30] RECOVERY - puppet last run on cp1057 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [06:00:30] RECOVERY - puppet last run on erbium is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:00:30] RECOVERY - puppet last run on zirconium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:30] RECOVERY - puppet last run on amssq52 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [06:00:30] RECOVERY - puppet last run on cp1051 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:00:30] RECOVERY - puppet last run on mw1234 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [06:00:39] RECOVERY - puppet last run on wtp1024 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:00:39] RECOVERY - puppet last run on amslvs4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:40] RECOVERY - puppet last run on amssq45 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:00:49] RECOVERY - puppet last run on mw1096 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [06:00:50] RECOVERY - puppet last run on analytics1036 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:00:50] RECOVERY - puppet last run on mc1010 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:00:59] RECOVERY - puppet last run on es1009 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:01:00] RECOVERY - puppet last run on mw1036 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [06:01:00] RECOVERY - puppet last run on analytics1015 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:01:09] RECOVERY - puppet last run on mw1138 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:01:10] RECOVERY - puppet last run on rdb1004 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [06:01:10] RECOVERY - puppet last run on elastic1028 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:01:10] RECOVERY - puppet last run on mw1147 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [06:01:10] RECOVERY - puppet last run on wtp1021 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [06:01:10] RECOVERY - puppet last run on cp1069 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [06:01:10] RECOVERY - puppet last run on mw1196 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:01:10] RECOVERY - puppet last run on mw1221 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:01:10] RECOVERY - puppet last run on elastic1031 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:01:19] RECOVERY - puppet last run on mw1132 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:01:19] RECOVERY - puppet last run on cp1065 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [06:01:19] RECOVERY - puppet last run on mw1232 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:01:19] RECOVERY - puppet last run on analytics1039 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:01:20] RECOVERY - puppet last run on mw1218 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [06:01:20] RECOVERY - puppet last run on mw1040 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:01:20] RECOVERY - puppet last run on mc1009 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [06:01:29] RECOVERY - puppet last run on uranium is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [06:01:29] RECOVERY - puppet last run on mw1035 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:01:30] RECOVERY - puppet last run on elastic1026 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [06:01:30] RECOVERY - puppet last run on mw1244 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:01:30] RECOVERY - puppet last run on pc1001 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:01:40] RECOVERY - puppet last run on ytterbium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:01:40] RECOVERY - puppet last run on ms-be1013 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:01:40] RECOVERY - puppet last run on mc1011 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:01:41] RECOVERY - puppet last run on mw1124 is OK: OK: Puppet is currently enabled, last run 0 seconds ago with 0 failures [06:01:41] RECOVERY - puppet last run on mw1216 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:01:41] RECOVERY - puppet last run on logstash1003 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:01:41] RECOVERY - puppet last run on virt1002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:01:41] RECOVERY - puppet last run on mw1161 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [06:01:42] RECOVERY - puppet last run on mw1257 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:01:49] RECOVERY - puppet last run on ocg1001 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:01:49] RECOVERY - puppet last run on mw1130 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [06:01:49] RECOVERY - puppet last run on mw1252 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:01:49] RECOVERY - puppet last run on mc1004 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [06:01:49] RECOVERY - puppet last run on mw1256 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:01:50] RECOVERY - puppet last run on amssq57 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:01:59] RECOVERY - puppet last run on ms-be2013 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:01:59] RECOVERY - puppet last run on ms-fe1003 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:02:00] RECOVERY - puppet last run on mw1233 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:02:00] RECOVERY - puppet last run on es2003 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:02:00] RECOVERY - puppet last run on ms-be2002 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:02:09] RECOVERY - puppet last run on wtp1019 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:02:09] RECOVERY - puppet last run on cp4017 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [06:02:09] RECOVERY - puppet last run on cp4007 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:02:10] RECOVERY - puppet last run on db1065 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:02:10] RECOVERY - puppet last run on mw1109 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [06:02:19] RECOVERY - puppet last run on mw1080 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:02:19] RECOVERY - puppet last run on mw1245 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:02:19] RECOVERY - puppet last run on ms-be1001 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [06:02:19] RECOVERY - puppet last run on wtp1017 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:02:20] RECOVERY - puppet last run on neptunium is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [06:02:20] RECOVERY - puppet last run on dbproxy1002 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:02:29] RECOVERY - puppet last run on vanadium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:02:29] RECOVERY - puppet last run on db1053 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [06:02:29] RECOVERY - puppet last run on cp1059 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:02:30] RECOVERY - puppet last run on mw1072 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:02:30] RECOVERY - puppet last run on cp3006 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:02:30] RECOVERY - puppet last run on dbstore1001 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:02:39] RECOVERY - puppet last run on mw1048 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:02:39] RECOVERY - puppet last run on magnesium is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:02:40] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:40] RECOVERY - puppet last run on mw1067 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:02:49] RECOVERY - puppet last run on wtp1009 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:02:49] PROBLEM - puppetmaster https on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:02:50] RECOVERY - puppet last run on mw1178 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:02:51] RECOVERY - puppet last run on mw1038 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:02:51] RECOVERY - puppet last run on ms-be1004 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:02:51] RECOVERY - puppet last run on mw1089 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [06:02:51] RECOVERY - puppet last run on mw1134 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:02:59] RECOVERY - puppet last run on mw1115 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:02:59] RECOVERY - puppet last run on es1008 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:03:09] RECOVERY - puppet last run on mw1012 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:03:09] RECOVERY - puppet last run on heze is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:03:10] RECOVERY - puppet last run on db1029 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:10] RECOVERY - puppet last run on es1001 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [06:03:10] RECOVERY - puppet last run on mw1200 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [06:03:10] RECOVERY - puppet last run on db2009 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:03:10] RECOVERY - puppet last run on labstore2001 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [06:03:10] RECOVERY - puppet last run on es2005 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:11] RECOVERY - puppet last run on ms-be2003 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [06:03:12] RECOVERY - puppet last run on analytics1033 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:03:20] RECOVERY - puppet last run on carbon is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:03:20] RECOVERY - puppet last run on lvs4002 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:03:20] RECOVERY - puppet last run on cp1049 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:03:20] RECOVERY - puppet last run on logstash1001 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:03:20] RECOVERY - puppet last run on mw1140 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [06:03:29] RECOVERY - puppet last run on mw1031 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:29] RECOVERY - puppet last run on elastic1001 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:03:29] RECOVERY - puppet last run on mw1059 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:03:29] RECOVERY - puppet last run on mw1240 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:29] RECOVERY - puppet last run on mc1016 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:30] RECOVERY - puppet last run on mw1145 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:03:30] RECOVERY - puppet last run on wtp1020 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [06:03:30] RECOVERY - puppet last run on cerium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:30] RECOVERY - puppet last run on caesium is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:03:31] RECOVERY - puppet last run on mw1006 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:03:31] RECOVERY - puppet last run on mw1045 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:03:32] RECOVERY - puppet last run on mw1005 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:03:39] RECOVERY - puppet last run on analytics1020 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [06:03:39] RECOVERY - puppet last run on rbf1002 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:03:40] RECOVERY - puppet last run on mw1141 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:03:40] RECOVERY - puppet last run on mw1028 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:03:40] RECOVERY - puppet last run on db1031 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:03:40] RECOVERY - puppet last run on elastic1007 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:03:40] RECOVERY - puppet last run on amslvs2 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:03:40] RECOVERY - puppet last run on amssq58 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:41] RECOVERY - puppet last run on cp3015 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:41] RECOVERY - puppet last run on cp3008 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:03:50] RECOVERY - puppet last run on mw1106 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [06:03:51] RECOVERY - puppet last run on db1073 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:03:51] RECOVERY - puppet last run on helium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:51] RECOVERY - puppet last run on ms-be1003 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [06:03:51] RECOVERY - puppet last run on analytics1041 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:03:51] RECOVERY - puppet last run on mw1063 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:03:59] RECOVERY - puppet last run on elastic1008 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:03:59] RECOVERY - puppet last run on mw1187 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [06:03:59] RECOVERY - puppet last run on mw1041 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:03:59] RECOVERY - puppet last run on elastic1004 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [06:03:59] RECOVERY - puppet last run on potassium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:03:59] RECOVERY - puppet last run on platinum is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:00] RECOVERY - puppet last run on ms-fe2004 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:00] RECOVERY - puppet last run on db2039 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:04:00] RECOVERY - puppet last run on mc1006 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [06:04:01] RECOVERY - puppet last run on snapshot1003 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:04:01] RECOVERY - puppet last run on gold is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:04:02] RECOVERY - puppet last run on analytics1017 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:02] RECOVERY - puppet last run on dbstore2001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:03] RECOVERY - puppet last run on db2034 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:04:09] RECOVERY - puppet last run on xenon is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:04:09] RECOVERY - puppet last run on mw1197 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [06:04:09] RECOVERY - puppet last run on mw1007 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:10] RECOVERY - puppet last run on elastic1018 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [06:04:10] RECOVERY - puppet last run on searchidx1001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:10] RECOVERY - puppet last run on wtp1006 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:04:19] RECOVERY - puppet last run on cp3022 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:04:19] RECOVERY - puppet last run on cp3013 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:04:19] RECOVERY - puppet last run on elastic1012 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [06:04:20] RECOVERY - puppet last run on lvs1002 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:04:20] RECOVERY - puppet last run on db2005 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:20] RECOVERY - puppet last run on es2002 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:04:20] RECOVERY - puppet last run on es2008 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:20] RECOVERY - puppet last run on es2009 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:04:20] RECOVERY - puppet last run on db2019 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [06:04:29] RECOVERY - puppet last run on ms-be1006 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:29] RECOVERY - puppet last run on ms-be2006 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:04:29] RECOVERY - puppet last run on mw1174 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:04:29] RECOVERY - puppet last run on mw1026 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:04:30] RECOVERY - puppet last run on cp4006 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [06:04:30] RECOVERY - puppet last run on db1066 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [06:04:39] RECOVERY - puppet last run on mw1224 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:04:39] RECOVERY - puppet last run on mw1250 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [06:04:39] RECOVERY - puppet last run on analytics1025 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:39] RECOVERY - puppet last run on analytics1040 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:40] RECOVERY - puppet last run on cp1070 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:04:40] RECOVERY - puppet last run on mw1254 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on wtp1016 is OK: OK: Puppet is currently enabled, last run 4 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on cp1039 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on ms-fe1001 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on mc1003 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on mw1082 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on lvs1005 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:04:50] RECOVERY - puppet last run on labstore1003 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [06:04:51] RECOVERY - puppet last run on amssq44 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [06:04:51] RECOVERY - puppet last run on cp1047 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:04:52] RECOVERY - puppet last run on amssq43 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:04:59] RECOVERY - puppet last run on cp1055 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:04:59] RECOVERY - puppet last run on analytics1035 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:05:00] RECOVERY - puppet last run on db1050 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [06:05:10] RECOVERY - puppet last run on elastic1027 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:05:10] RECOVERY - puppet last run on db1015 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:05:10] RECOVERY - puppet last run on mw1226 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:05:19] RECOVERY - puppet last run on mc1002 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:05:19] RECOVERY - puppet last run on mw1228 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:05:19] RECOVERY - puppet last run on ms-fe1004 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [06:05:19] RECOVERY - puppet last run on lead is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:05:19] RECOVERY - puppet last run on cp3020 is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:05:19] RECOVERY - puppet last run on elastic1021 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:05:20] RECOVERY - puppet last run on db1022 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [06:05:20] RECOVERY - puppet last run on mw1222 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:05:29] RECOVERY - puppet last run on sca1002 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:05:29] RECOVERY - puppet last run on amssq59 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:05:29] RECOVERY - puppet last run on amssq54 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:05:29] RECOVERY - puppet last run on db1040 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:05:30] RECOVERY - puppet last run on mw1117 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [06:05:30] RECOVERY - puppet last run on db1002 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:05:30] RECOVERY - puppet last run on capella is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:05:39] RECOVERY - puppet last run on db2002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:05:39] RECOVERY - puppet last run on ms-be2004 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:05:39] RECOVERY - puppet last run on es2001 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:05:39] RECOVERY - puppet last run on db2018 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:05:39] RECOVERY - puppet last run on mw1009 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:05:49] RECOVERY - puppet last run on mw1150 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:05:49] RECOVERY - puppet last run on iron is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:05:49] RECOVERY - puppet last run on db1018 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:05:49] RECOVERY - puppet last run on mw1173 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:05:49] RECOVERY - puppet last run on mw1099 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:05:50] RECOVERY - puppet last run on db1046 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [06:05:50] RECOVERY - puppet last run on ruthenium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:05:59] RECOVERY - puppet last run on mw1069 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:05:59] RECOVERY - puppet last run on mw1217 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [06:05:59] RECOVERY - puppet last run on labsdb1003 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:05:59] RECOVERY - puppet last run on mw1176 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:00] RECOVERY - puppet last run on db1042 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:06:00] RECOVERY - puppet last run on analytics1030 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [06:06:00] RECOVERY - puppet last run on mw1205 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [06:06:09] RECOVERY - puppet last run on mw1008 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:06:09] RECOVERY - puppet last run on lvs3001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:09] RECOVERY - puppet last run on amssq32 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:06:09] RECOVERY - puppet last run on mw1088 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [06:06:09] RECOVERY - puppet last run on cp1061 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:06:09] RECOVERY - puppet last run on virt1006 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [06:06:10] RECOVERY - puppet last run on lvs2004 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:06:10] RECOVERY - puppet last run on db1067 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [06:06:10] RECOVERY - puppet last run on mw1242 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:06:11] RECOVERY - puppet last run on mw1100 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:11] RECOVERY - puppet last run on mw1060 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:19] RECOVERY - puppet last run on mw1120 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:06:20] RECOVERY - puppet last run on mw1003 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:20] RECOVERY - puppet last run on mw1164 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:06:20] RECOVERY - puppet last run on mw1160 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:20] RECOVERY - puppet last run on ms-fe2001 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [06:06:29] RECOVERY - puppet last run on mw1046 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:29] RECOVERY - puppet last run on db1034 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [06:06:30] RECOVERY - puppet last run on db1059 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:30] RECOVERY - puppet last run on mw1189 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [06:06:39] RECOVERY - puppet last run on cp3003 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:06:39] RECOVERY - puppet last run on amssq61 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:06:39] RECOVERY - puppet last run on cp3016 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:06:40] RECOVERY - puppet last run on mw1068 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:06:40] RECOVERY - puppet last run on mw1144 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:06:40] RECOVERY - puppet last run on ms-fe2003 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:06:49] RECOVERY - puppet last run on dbproxy1001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:07:00] RECOVERY - puppet last run on mw1123 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [06:07:00] RECOVERY - puppet last run on mw1052 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:07:09] RECOVERY - puppet last run on cp1056 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:07:09] RECOVERY - puppet last run on mw1092 is OK: OK: Puppet is currently enabled, last run 3 seconds ago with 0 failures [06:07:09] RECOVERY - puppet last run on mw1170 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:07:09] RECOVERY - puppet last run on db1023 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:07:10] RECOVERY - puppet last run on logstash1002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:07:19] RECOVERY - puppet last run on elastic1022 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:07:19] RECOVERY - puppet last run on mw1153 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:07:19] RECOVERY - puppet last run on db1043 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [06:07:19] RECOVERY - puppet last run on amslvs1 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:07:19] RECOVERY - puppet last run on amssq53 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:07:20] RECOVERY - puppet last run on elastic1030 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:07:20] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 0.132 second response time [06:07:29] RECOVERY - puppet last run on lvs2001 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:07:29] RECOVERY - puppet last run on db1028 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:07:29] RECOVERY - puppet last run on mw1061 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:07:29] RECOVERY - puppet last run on cp1058 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [06:07:29] RECOVERY - puppet last run on analytics1010 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:07:29] RECOVERY - puppet last run on db2042 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:07:30] RECOVERY - puppet last run on labstore1001 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [06:07:30] RECOVERY - puppet last run on mw1042 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [06:07:30] RECOVERY - puppet last run on analytics1038 is OK: OK: Puppet is currently enabled, last run 25 seconds ago with 0 failures [06:07:39] RECOVERY - puppet last run on db1016 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [06:07:39] RECOVERY - puppet last run on mw1118 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [06:07:40] RECOVERY - puppet last run on labcontrol2001 is OK: OK: Puppet is currently enabled, last run 24 seconds ago with 0 failures [06:07:40] RECOVERY - puppet last run on db1021 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [06:07:40] RECOVERY - puppet last run on wtp1005 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [06:07:40] RECOVERY - puppet last run on mw1065 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:07:49] RECOVERY - puppet last run on antimony is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:07:49] RECOVERY - puppet last run on mw1235 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on polonium is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on nescio is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on ms-be3002 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on mw1054 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on mw1129 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on mw1172 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:07:50] RECOVERY - puppet last run on mw1166 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:07:51] RECOVERY - puppet last run on es1007 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:07:51] RECOVERY - puppet last run on db2038 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:07:59] RECOVERY - puppet last run on db1051 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:07:59] RECOVERY - puppet last run on db2040 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:07:59] RECOVERY - puppet last run on db2036 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:07:59] RECOVERY - puppet last run on ms-be2011 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:07:59] RECOVERY - puppet last run on db2007 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:08:00] RECOVERY - puppet last run on nembus is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:08:00] RECOVERY - puppet last run on install2001 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:08:00] RECOVERY - puppet last run on lithium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:09] RECOVERY - puppet last run on cp4014 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [06:08:09] RECOVERY - puppet last run on mw1211 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [06:08:10] RECOVERY - puppet last run on mw1025 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:08:10] RECOVERY - puppet last run on mw1114 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:08:10] RECOVERY - puppet last run on pc1002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:10] RECOVERY - puppet last run on mw1206 is OK: OK: Puppet is currently enabled, last run 13 seconds ago with 0 failures [06:08:19] RECOVERY - puppet last run on mw1177 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:08:19] RECOVERY - puppet last run on mw1076 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:08:19] RECOVERY - puppet last run on mw1119 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:20] RECOVERY - puppet last run on analytics1013 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [06:08:20] RECOVERY - puppet last run on sodium is OK: OK: Puppet is currently enabled, last run 11 seconds ago with 0 failures [06:08:20] RECOVERY - puppet last run on dataset1001 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [06:08:20] RECOVERY - puppet last run on mc1012 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [06:08:20] RECOVERY - puppet last run on labnet1001 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:08:20] RECOVERY - puppet last run on gallium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:21] RECOVERY - puppet last run on mw1237 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [06:08:21] RECOVERY - puppet last run on virt1004 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [06:08:29] RECOVERY - puppet last run on mw1011 is OK: OK: Puppet is currently enabled, last run 21 seconds ago with 0 failures [06:08:29] RECOVERY - puppet last run on analytics1016 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:08:29] RECOVERY - puppet last run on mw1149 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:08:29] RECOVERY - puppet last run on mw1039 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:29] RECOVERY - puppet last run on cp3014 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [06:08:30] RECOVERY - puppet last run on amssq35 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:08:30] RECOVERY - puppet last run on db1052 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [06:08:30] RECOVERY - puppet last run on virt1001 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:08:31] RECOVERY - puppet last run on db1060 is OK: OK: Puppet is currently enabled, last run 5 seconds ago with 0 failures [06:08:31] RECOVERY - puppet last run on mw1175 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:39] RECOVERY - puppet last run on virt1003 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:39] RECOVERY - puppet last run on db1039 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:08:39] RECOVERY - puppet last run on wtp1012 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [06:08:39] RECOVERY - puppet last run on mw1002 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:08:39] RECOVERY - puppet last run on mw1044 is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [06:08:40] RECOVERY - puppet last run on db1003 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:40] RECOVERY - puppet last run on analytics1026 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:08:40] RECOVERY - puppet last run on db1048 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:08:49] RECOVERY - puppet last run on mw1126 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:08:49] RECOVERY - puppet last run on mw1213 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:08:51] RECOVERY - puppet last run on mw1162 is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [06:08:51] RECOVERY - puppet last run on lvs3004 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:08:51] RECOVERY - puppet last run on db1026 is OK: OK: Puppet is currently enabled, last run 38 seconds ago with 0 failures [06:08:51] RECOVERY - puppet last run on mc1014 is OK: OK: Puppet is currently enabled, last run 48 seconds ago with 0 failures [06:08:51] RECOVERY - puppet last run on mw1251 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:08:51] RECOVERY - puppet last run on stat1003 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [06:08:59] RECOVERY - puppet last run on snapshot1001 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:09:00] RECOVERY - puppet last run on ms-fe3002 is OK: OK: Puppet is currently enabled, last run 29 seconds ago with 0 failures [06:09:09] RECOVERY - puppet last run on elastic1006 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:09] RECOVERY - puppet last run on plutonium is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:09] RECOVERY - puppet last run on elastic1019 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:09:09] RECOVERY - puppet last run on db1069 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:09:09] RECOVERY - puppet last run on mw1055 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:10] RECOVERY - puppet last run on db2029 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:10] RECOVERY - puppet last run on es2004 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:10] RECOVERY - puppet last run on db2016 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:09:10] RECOVERY - puppet last run on mw1249 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:19] RECOVERY - puppet last run on elastic1024 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:09:19] RECOVERY - puppet last run on lvs4003 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:09:19] RECOVERY - puppet last run on cp4003 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:19] RECOVERY - puppet last run on db1036 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:09:19] RECOVERY - puppet last run on mw1208 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:09:19] RECOVERY - puppet last run on cp4008 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:20] RECOVERY - puppet last run on ms-be1008 is OK: OK: Puppet is currently enabled, last run 28 seconds ago with 0 failures [06:09:29] RECOVERY - puppet last run on mw1195 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:29] RECOVERY - puppet last run on analytics1022 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [06:09:30] RECOVERY - puppet last run on mc1005 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:30] RECOVERY - puppet last run on cp1050 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:30] RECOVERY - puppet last run on mw1180 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:09:40] RECOVERY - puppet last run on ms-be3001 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [06:09:40] RECOVERY - puppet last run on cp3010 is OK: OK: Puppet is currently enabled, last run 52 seconds ago with 0 failures [06:09:40] RECOVERY - puppet last run on amssq60 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [06:09:40] RECOVERY - puppet last run on amssq55 is OK: OK: Puppet is currently enabled, last run 34 seconds ago with 0 failures [06:09:40] RECOVERY - puppet last run on mw1168 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:09:49] RECOVERY - puppet last run on virt1007 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:09:49] RECOVERY - puppet last run on lvs2006 is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [06:09:50] RECOVERY - puppet last run on mw1014 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:09:50] RECOVERY - puppet last run on tin is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:09:50] RECOVERY - puppet last run on mw1238 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:09:59] RECOVERY - puppet last run on snapshot1002 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:00] RECOVERY - puppet last run on mw1247 is OK: OK: Puppet is currently enabled, last run 37 seconds ago with 0 failures [06:10:00] RECOVERY - puppet last run on thallium is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:10:00] RECOVERY - puppet last run on analytics1023 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [06:10:00] RECOVERY - puppet last run on mw1084 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [06:10:00] RECOVERY - puppet last run on labmon1001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:01] RECOVERY - puppet last run on mw1151 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:10:01] RECOVERY - puppet last run on db2037 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:01] RECOVERY - puppet last run on mw1049 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:10:02] RECOVERY - puppet last run on elastic1015 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:09] RECOVERY - puppet last run on snapshot1004 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:10:10] RECOVERY - puppet last run on amssq48 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:10:10] RECOVERY - puppet last run on amssq46 is OK: OK: Puppet is currently enabled, last run 54 seconds ago with 0 failures [06:10:10] RECOVERY - puppet last run on amssq47 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:19] RECOVERY - puppet last run on db1071 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:10:19] RECOVERY - puppet last run on gadolinium is OK: OK: Puppet is currently enabled, last run 20 seconds ago with 0 failures [06:10:19] RECOVERY - puppet last run on rdb1001 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:10:19] RECOVERY - puppet last run on labsdb1006 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [06:10:19] RECOVERY - puppet last run on hafnium is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [06:10:19] RECOVERY - puppet last run on mw1190 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:10:20] RECOVERY - puppet last run on db2023 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:10:20] RECOVERY - puppet last run on db2004 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:10:20] RECOVERY - puppet last run on db2001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:21] RECOVERY - puppet last run on ms-be2012 is OK: OK: Puppet is currently enabled, last run 42 seconds ago with 0 failures [06:10:21] RECOVERY - puppet last run on cp1062 is OK: OK: Puppet is currently enabled, last run 17 seconds ago with 0 failures [06:10:22] RECOVERY - puppet last run on mw1227 is OK: OK: Puppet is currently enabled, last run 49 seconds ago with 0 failures [06:10:22] RECOVERY - puppet last run on ms-be2008 is OK: OK: Puppet is currently enabled, last run 16 seconds ago with 0 failures [06:10:29] RECOVERY - puppet last run on bast4001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:29] RECOVERY - puppet last run on mw1183 is OK: OK: Puppet is currently enabled, last run 7 seconds ago with 0 failures [06:10:29] RECOVERY - puppet last run on mw1051 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [06:10:29] RECOVERY - puppet last run on cp4004 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:29] RECOVERY - puppet last run on cp4005 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:10:30] RECOVERY - puppet last run on mw1165 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures [06:10:39] RECOVERY - puppet last run on mw1258 is OK: OK: Puppet is currently enabled, last run 23 seconds ago with 0 failures [06:10:39] RECOVERY - puppet last run on mw1004 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [06:10:39] RECOVERY - puppet last run on mw1079 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:10:39] RECOVERY - puppet last run on mw1030 is OK: OK: Puppet is currently enabled, last run 15 seconds ago with 0 failures [06:10:39] RECOVERY - puppet last run on argon is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:39] RECOVERY - puppet last run on db1004 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:40] RECOVERY - puppet last run on mw1202 is OK: OK: Puppet is currently enabled, last run 39 seconds ago with 0 failures [06:10:40] RECOVERY - puppet last run on mw1125 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [06:10:41] RECOVERY - puppet last run on rubidium is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:10:49] RECOVERY - puppet last run on stat1002 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [06:10:50] RECOVERY - puppet last run on cp1046 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [06:10:50] RECOVERY - puppet last run on osmium is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:10:50] RECOVERY - puppet last run on db1020 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [06:10:50] RECOVERY - puppet last run on amssq40 is OK: OK: Puppet is currently enabled, last run 2 seconds ago with 0 failures [06:10:50] RECOVERY - puppet last run on mw1081 is OK: OK: Puppet is currently enabled, last run 43 seconds ago with 0 failures [06:10:59] RECOVERY - puppet last run on cp1063 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:10:59] RECOVERY - puppet last run on mw1133 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:00] RECOVERY - puppet last run on mw1111 is OK: OK: Puppet is currently enabled, last run 56 seconds ago with 0 failures [06:11:00] RECOVERY - puppet last run on tungsten is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:00] RECOVERY - puppet last run on mw1034 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:00] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:11:09] RECOVERY - puppet last run on mw1146 is OK: OK: Puppet is currently enabled, last run 46 seconds ago with 0 failures [06:11:09] RECOVERY - puppet last run on oxygen is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:09] RECOVERY - puppet last run on virt1010 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:10] RECOVERY - puppet last run on mw1098 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:20] RECOVERY - puppet last run on amssq34 is OK: OK: Puppet is currently enabled, last run 45 seconds ago with 0 failures [06:11:29] RECOVERY - puppet last run on mw1057 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:29] RECOVERY - puppet last run on mw1181 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:40] RECOVERY - puppet last run on cp4018 is OK: OK: Puppet is currently enabled, last run 10 seconds ago with 0 failures [06:11:40] RECOVERY - puppet last run on mw1056 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:41] RECOVERY - puppet last run on cp4019 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:41] RECOVERY - puppet last run on cp4001 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:41] RECOVERY - puppet last run on mw1156 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:11:49] RECOVERY - puppet last run on mw1159 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures [06:12:00] RECOVERY - puppet last run on amssq56 is OK: OK: Puppet is currently enabled, last run 26 seconds ago with 0 failures [06:12:00] RECOVERY - puppet last run on amssq36 is OK: OK: Puppet is currently enabled, last run 53 seconds ago with 0 failures [06:12:00] RECOVERY - puppet last run on amssq51 is OK: OK: Puppet is currently enabled, last run 59 seconds ago with 0 failures [06:12:39] RECOVERY - puppet last run on hooft is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:13:11] RECOVERY - puppet last run on amssq41 is OK: OK: Puppet is currently enabled, last run 50 seconds ago with 0 failures [06:14:29] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 57 seconds ago with 0 failures [06:22:19] PROBLEM - graphite.wikimedia.org on tungsten is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 525 bytes in 0.010 second response time [06:23:55] anyone else having problems accessing wikitech.wikimedia.org ? [06:24:01] RECOVERY - puppet last run on amssq49 is OK: OK: Puppet is currently enabled, last run 12 seconds ago with 0 failures [06:28:19] PROBLEM - puppet last run on cp3016 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:39] PROBLEM - puppet last run on cp1056 is CRITICAL: CRITICAL: Puppet has 1 failures [06:28:40] PROBLEM - puppet last run on mw1170 is CRITICAL: CRITICAL: Puppet has 1 failures [06:29:40] PROBLEM - puppet last run on cp4003 is CRITICAL: CRITICAL: Puppet has 1 failures [06:29:49] PROBLEM - puppet last run on mw1092 is CRITICAL: CRITICAL: Puppet has 3 failures [06:30:00] PROBLEM - puppet last run on cp3014 is CRITICAL: CRITICAL: Puppet has 1 failures [06:33:41] Um. [06:34:20] Did everything just explode? [06:36:30] RECOVERY - graphite.wikimedia.org on tungsten is OK: HTTP OK: HTTP/1.1 200 OK - 1607 bytes in 0.006 second response time [06:45:40] marktraceur, maybe puppetmaster died again? [06:45:43] Maybe [06:45:56] there were floods of puppet failures when that happened before [06:46:10] RECOVERY - puppet last run on cp3016 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [06:46:24] Risker|Busy, actually, yes [06:46:30] RECOVERY - puppet last run on cp4003 is OK: OK: Puppet is currently enabled, last run 14 seconds ago with 0 failures [06:46:30] RECOVERY - puppet last run on cp1056 is OK: OK: Puppet is currently enabled, last run 41 seconds ago with 0 failures [06:46:39] RECOVERY - puppet last run on mw1170 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:46:39] RECOVERY - puppet last run on mw1092 is OK: OK: Puppet is currently enabled, last run 51 seconds ago with 0 failures [06:46:40] Risker|Busy, use https://wikitech-static.wikimedia.org/wiki/Main_Page if it's important [06:46:50] RECOVERY - puppet last run on cp3014 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [06:46:53] Krenair, Ori is looking at it, I caught him -dev [06:46:53] Krenair, yep, it took an apache restart on palladium [07:15:59] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 0.010 second response time [07:15:59] RECOVERY - puppetmaster https on virt1000 is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.070 second response time [07:17:03] !log Restarted apache2 on virt1000 after user reports of wikitech being down. Process was hung. error.log has a Passenger-related crash: Exception Errno::EPIPE in Passenger RequestHandler (Broken pipe) from /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:109:in `write'. [07:17:28] where's morebots? [07:17:42] * ori sighs. [07:17:48] Risker|Busy: back up now. [07:18:07] thanks ori [07:19:20] morebots is such a piece of crap. I've known Windows 98 machines that stayed up longer. [07:20:03] isn't that just a simple IRC bot that logs stuff to wikitech? [07:20:20] ruby/1.8? no wonder it's crashy [07:20:29] isn't that EOL'd for like two years now? [07:21:06] it's in python [07:21:11] s/\/1.8// [07:21:17] in awful python, rather [07:21:21] and running in labs? [07:21:23] !log restarted morebots [07:21:40] lol [07:21:42] Krenair: yes. whenever anyone finds out, they gawk in disbelief, but never do anything about it. [07:21:49] !log Restarted apache2 on virt1000 after user reports of wikitech being down. Process was hung. error.log has a Passenger-related crash: Exception Errno::EPIPE in Passenger RequestHandler (Broken pipe) from /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:109:in `write'. [07:22:20] I (re)wrote logmsgbot. It stays up. :) [07:22:59] Could one of you archive the SAL? I think the size of the page is part of the problem. [07:23:07] I actually have to go [07:23:08] sorry [07:23:16] 'sokay [07:23:30] PROBLEM - puppetmaster https on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:23:39] oh, great. [07:24:02] it's down again. [07:24:42] Risker|Busy: don't uncork the champagne yet. It looks like it's flapping. The host wikitech is running on also runs another service and that other service is crashing repeatedly and take down wikitech with it. [07:24:54] *taking [07:25:49] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:25:51] well, I appreciate you working on it, ori. I'm sure there are more interesting things to do on a Saturday night in SF, even if it's just going down to the Golden Gate to watch the zipper truck do its thing.... [07:26:46] ori, just use the solution from http://thedailywtf.com/articles/Routers,-Routers,-Everywhere :P [07:26:49] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 1.244 second response time [07:27:02] reboot reboot reboot return to dell [07:27:04] Risker|Busy: hypnotic, no? :) Anyhow, I am compelled by pride to mention that this infrastructure isn't my responsibility. I wouldn't let it get so bad. [07:27:28] more like onthefloorbots [07:28:19] MaxSem: heh. [07:28:55] you know, ori, I was just talking to someone else about what a pleasure it is to watch people who love what they do and take pride in doing it well. There are a a few of you guys in this channel as I write. :) [07:29:40] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [07:30:10] PROBLEM - puppet last run on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [07:30:58] !log virt1000 was eaten by bears [07:34:59] PROBLEM - Unmerged changes on repository puppet on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [07:35:30] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [07:37:19] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 24 minutes ago with 0 failures [07:39:10] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [07:41:29] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [07:42:19] PROBLEM - puppet last run on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [07:46:09] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [07:48:16] mmm, that's a nice definition of ok [07:50:49] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:53:09] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [07:57:40] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 44 minutes ago with 0 failures [07:57:59] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:59:10] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [08:00:30] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:01:20] PROBLEM - puppet last run on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:01:40] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 9.188 second response time [08:01:40] PROBLEM - DPKG on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:02:29] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 49 minutes ago with 0 failures [08:02:50] RECOVERY - DPKG on virt1000 is OK: All packages OK [08:06:00] PROBLEM - puppet last run on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:06:20] PROBLEM - DPKG on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:09:59] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:10:49] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 58 minutes ago with 0 failures [08:14:40] RECOVERY - DPKG on virt1000 is OK: All packages OK [08:14:40] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [08:16:01] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [08:16:49] PROBLEM - puppet last run on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:19:50] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:23:29] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [08:30:19] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:30:30] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:31:20] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [08:32:20] PROBLEM - nutcracker process on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:32:40] PROBLEM - configured eth on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:32:40] PROBLEM - DPKG on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:34:09] PROBLEM - dhclient process on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:34:40] RECOVERY - nutcracker process on virt1000 is OK: PROCS OK: 1 process with UID = 122 (nutcracker), command name nutcracker [08:35:00] PROBLEM - HTTP on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:35:00] PROBLEM - SSH on virt1000 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:35:09] RECOVERY - dhclient process on virt1000 is OK: PROCS OK: 0 processes with command name dhclient [08:36:09] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 4.112 second response time [08:37:29] RECOVERY - SSH on virt1000 is OK: SSH OK - OpenSSH_5.9p1 Debian-5ubuntu1.4 (protocol 2.0) [08:37:29] PROBLEM - salt-minion processes on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:38:19] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 1 hour ago with 0 failures [08:38:19] RECOVERY - Unmerged changes on repository puppet on virt1000 is OK: No changes to merge. [08:38:30] RECOVERY - salt-minion processes on virt1000 is OK: PROCS OK: 1 process with regex args ^/usr/bin/python /usr/bin/salt-minion [08:38:30] RECOVERY - DPKG on virt1000 is OK: All packages OK [08:38:39] RECOVERY - configured eth on virt1000 is OK: NRPE: Unable to read output [08:38:50] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [08:39:09] PROBLEM - Memcached on virt1000 is CRITICAL: Connection refused [08:42:10] PROBLEM - puppet last run on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:42:40] PROBLEM - RAID on virt1000 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:43:20] RECOVERY - puppet last run on virt1000 is OK: OK: Puppet is currently enabled, last run 1 hour ago with 0 failures [08:43:49] RECOVERY - RAID on virt1000 is OK: RAID STATUS: OPTIMAL [08:46:59] PROBLEM - HTTP on virt1000 is CRITICAL: Connection refused [08:56:29] RECOVERY - HTTP on virt1000 is OK: HTTP OK: HTTP/1.1 302 Found - 457 bytes in 0.002 second response time [08:56:30] RECOVERY - puppetmaster https on virt1000 is OK: HTTP OK: Status line output matched 400 - 335 bytes in 0.716 second response time [08:56:49] RECOVERY - Memcached on virt1000 is OK: TCP OK - 0.000 second response time on port 11000 [10:06:05] (03PS1) 10Nikerabbit: Re-enable event logging for cx [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185667 [10:09:45] !log restarted Jenkins. beta cluster jobs were no more running due to a deadlock [10:11:05] bah [10:14:39] !log restarted Jenkins. beta cluster jobs were no more running due to a deadlock [10:16:12] !log restarted Jenkins. beta cluster jobs were no more running due to a deadlock [10:16:16] stupid logbot [10:41:43] Any sys admin online? [10:47:22] 3MediaWiki-File-management, operations, Multimedia: [REGRESSION] File comment with source information no longer added to thumbnails - https://phabricator.wikimedia.org/T44368#984567 (10Raymond) 5Open>3Resolved a:3Raymond I think this regression was fixed sometime in the past. For my new uploaded images it... [10:49:58] 3MediaWiki-File-management, operations, Multimedia: [REGRESSION] File comment with source information no longer added to thumbnails - https://phabricator.wikimedia.org/T44368#984570 (10Bawolff) >PNG thumbs are also lacking such a comment. Note, that Its a known issue that pngs processed by VIPS (which happens i... [11:26:40] PROBLEM - Disk space on dataset1001 is CRITICAL: DISK CRITICAL - free space: /data 1520784 MB (3% inode=99%): [11:34:29] PROBLEM - puppet last run on mw1074 is CRITICAL: CRITICAL: Puppet has 1 failures [11:52:20] RECOVERY - puppet last run on mw1074 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [13:37:20] 3Wikimedia-Site-requests, operations: Move the Nourmande Wikipedia from nrm to nrf - https://phabricator.wikimedia.org/T25216#984630 (10Amire80) [13:38:06] 3Wikimedia-Site-requests, operations: Move the Nourmande Wikipedia from nrm to nrf - https://phabricator.wikimedia.org/T25216#281394 (10Amire80) I updated the description to the newly approved code nrf. Congratulations to the people of Jersey and Guernsey :) [13:44:09] hello [13:44:13] I need some help [13:44:34] wikipedia pages are taking too much time to load [13:45:08] I have tried different browsers but the problem persists [13:45:34] my net connection also seems to be okay since other websites are running properly [13:45:45] what should I do?? [13:46:11] Guest86012: Do you have packet loss? [13:47:36] packet loss?? [13:48:21] yes [13:48:53] what is packet loss?? [13:49:13] https://en.wikipedia.org/wiki/Packet_loss [13:49:57] I can't load wikipedia pages [13:50:15] I thought they were only slow for you [13:50:28] https://webcache.googleusercontent.com/search?q=cache:6TQ76FUg4BQJ:en.wikipedia.org/wiki/Packet_loss+&cd=2&hl=de&ct=clnk&gl=de [13:52:26] I don't know if there's a packet loss, how can I check it?? [13:53:15] other websites are running smooth [13:55:03] ping en.wikipedia.org [13:55:13] run that [13:56:26] looading [13:56:44] still loading [13:58:03] still loading [14:02:01] still loading [14:02:06] --- en.wikipedia.org ping statistics --- 16 packets transmitted, 16 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 55.206/81.550/243.465/55.461 ms [14:02:25] just in case that can help anybody. [14:02:43] NotASpy: And you also can't access it? [14:02:57] no, I was helping Guest earlier [14:03:14] loads fine for me. [14:03:28] Ok, so a traceroute/ ping from you wont help :P [14:03:52] no, can't access, the page seems to be loading forever [14:05:36] should I use a proxy server?? [14:05:59] That will help [14:06:04] you can also eg. use Tor [14:06:40] how? [14:07:50] google it [15:31:50] PROBLEM - Varnishkafka Delivery Errors per minute on cp3015 is CRITICAL: CRITICAL: 22.22% of data above the critical threshold [20000.0] [15:36:27] (03CR) 10KartikMistry: [C: 031] Re-enable event logging for cx [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185667 (owner: 10Nikerabbit) [15:39:00] RECOVERY - Varnishkafka Delivery Errors per minute on cp3015 is OK: OK: Less than 1.00% above the threshold [0.0] [16:31:10] PROBLEM - Apache HTTP on mw1176 is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 50482 bytes in 0.040 second response time [16:31:50] PROBLEM - HHVM rendering on mw1176 is CRITICAL: HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 50482 bytes in 0.039 second response time [17:23:11] PROBLEM - puppet last run on mw1196 is CRITICAL: CRITICAL: Puppet has 1 failures [17:39:50] RECOVERY - puppet last run on mw1196 is OK: OK: Puppet is currently enabled, last run 35 seconds ago with 0 failures [18:21:04] (03PS1) 10Ori.livneh: xenon: tweak formatting of closures and file scope [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185687 [18:31:11] 3ops-requests: Make Puppet repository pass lenient and strict lint checks - https://phabricator.wikimedia.org/T87132#984899 (10Aklapper) [18:41:10] (03PS2) 10Ori.livneh: xenon: tweak formatting of closures and file scope [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185687 [19:40:19] (03PS1) 10Springle: depool db1054 [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185694 [19:41:23] (03CR) 10Springle: [C: 032] depool db1054 [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185694 (owner: 10Springle) [19:42:31] !log springle Synchronized wmf-config/db-eqiad.php: depool db1054 (duration: 00m 05s) [19:46:34] !log 19:39 <+logmsgbot> !log springle Synchronized wmf-config/db-eqiad.php: depool db1054 (duration: 00m 05s) [19:47:08] morebots: hi [19:47:08] I am a logbot running on tools-exec-04. [19:47:08] Messages are logged to wikitech.wikimedia.org/wiki/Server_Admin_Log. [19:47:08] To log a message, type !log . [19:59:57] (03CR) 10Aaron Schulz: [C: 031] xenon: tweak formatting of closures and file scope [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185687 (owner: 10Ori.livneh) [20:24:40] PROBLEM - puppet last run on amssq59 is CRITICAL: CRITICAL: puppet fail [20:31:20] PROBLEM - Varnishkafka Delivery Errors per minute on cp3015 is CRITICAL: CRITICAL: 37.50% of data above the critical threshold [20000.0] [20:31:40] (03PS1) 10Springle: upgrade db1054 to trusty and mariadb 10 [puppet] - 10https://gerrit.wikimedia.org/r/185698 [20:32:40] (03CR) 10Springle: [C: 032] upgrade db1054 to trusty and mariadb 10 [puppet] - 10https://gerrit.wikimedia.org/r/185698 (owner: 10Springle) [20:39:49] RECOVERY - Varnishkafka Delivery Errors per minute on cp3015 is OK: OK: Less than 1.00% above the threshold [0.0] [20:42:22] RECOVERY - puppet last run on amssq59 is OK: OK: Puppet is currently enabled, last run 22 seconds ago with 0 failures [20:52:46] !log springle Synchronized wmf-config/db-eqiad.php: test mw1167 (duration: 00m 07s) [21:22:11] PROBLEM - git.wikimedia.org on antimony is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:28:12] 3ops-codfw, ops-eqiad: ship blanking panels from eqiad to codfw - https://phabricator.wikimedia.org/T86082#984993 (10Papaul) 5Open>3Resolved Received 3 boxes of blanking panels [21:38:42] RECOVERY - git.wikimedia.org on antimony is OK: HTTP OK: HTTP/1.1 200 OK - 59701 bytes in 0.304 second response time [21:38:47] 3Beta-Cluster, operations: Renumber apache user/group to uid=48 - https://phabricator.wikimedia.org/T78076#984995 (10bd808) Consensus at this point seems to be that renumbering production is not feasible. Should we leave the patch applied only in beta for now, close this task and instead focus on eliminating sha... [22:33:59] 3operations: Static image files from en.m.wikipedia.org are served with cache-suppressing headers - https://phabricator.wikimedia.org/T86993#985038 (10tstarling) a:3mark [22:35:37] sorry, but mark is really the most relevant person there [22:36:20] and nobody else looked at it on Friday [23:07:15] (03PS3) 10Ori.livneh: xenon: tweak formatting of closures and file scope [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185687 [23:07:29] (03CR) 10Ori.livneh: [C: 032] xenon: tweak formatting of closures and file scope [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185687 (owner: 10Ori.livneh) [23:07:33] (03Merged) 10jenkins-bot: xenon: tweak formatting of closures and file scope [mediawiki-config] - 10https://gerrit.wikimedia.org/r/185687 (owner: 10Ori.livneh) [23:44:12] 3MediaWiki-extensions-CentralNotice, operations: Use the appropriate content models for CentralNotice scripts and CSS - https://phabricator.wikimedia.org/T86904#985096 (10Aklapper) p:5Triage>3Low