[00:15:43] New review: MZMcBride; "Limitations in Gerrit make it necessary to use Code-Review points to mark changes in this way. Comme..." [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/69982 [00:17:48] Krenair: http://www.buzzfeed.com/charliewarzel/meet-crapcha-the-impossible-captcha [00:18:34] sigh [00:19:01] because of course, someone telling you that you shouldn't use Gerrit for policy discussions means that you should use Gerrit to argue about what Gerrit is for [00:20:14] you can add custom fileds to gerrit [00:20:17] fields* [00:21:04] we should add a "MZMcBride annoying comment" field [00:21:20] "fill this here if you just want to annoy and demotivate people" [00:21:24] "verified" is pretty ambigious, and I wonder why "normal" can use it [00:21:35] cant [00:21:49] verified means the code is syntactically valid & passes tests [00:22:16] jenkins usually does this [00:22:29] and "code review" means it looks syntactically valid and looks like it passes tests? [00:22:33] but we have the capability to override it, in case something's wrong with jenkins and we need to push code immediately [00:22:54] code review means that the code is doing what it's supposed to, it's doing it the proper way etc. [00:23:05] Change abandoned: Krinkle; "Per email conversation. The repo shouldn't have gate-and-submit so instead of fixing the ability to ..." [operations/puppet/kafka] (refs/meta/config) - https://gerrit.wikimedia.org/r/69890 [00:23:20] for me I have always felt that "verified" means the commit does what it says it does, and "code review" is that the code looks fine [00:24:08] no [00:24:25] yes [00:24:28] for me [00:24:44] you can't change what I've have always felt [00:24:52] no that's not the case [00:25:01] AzaToth: Verified is only for bots and should only be set if any and all standard Jenkins tests have been run. Otherwise setting it manually may cause a nother unrelated change to be seen as a regression (e.g. if you set it to Verfied and merge, and jenkins would've disagreed , the next change will instead be the first brekage eventhrough it wasn't) [00:25:23] Gerrit’s default work-flow requires two checks before a change is accepted. Code-Review is someone looking at the code, ensuring it meets the project guidelines, intent etc. Verifying is checking that the code actually compiles, unit tests pass etc. Verification is usually done by an automated build server rather than a person [00:25:28] that's from the fine manual [00:26:07] With the exception of repositories that do not yet have unit tests. In that case Verified +2 is for humans only. There may be a linting job by jenkins for Verified+1 but it'll still need +2 for full testing. [00:26:15] paravoid: Thanks! /me copies into snippet manager [00:27:00] paravoid: normal people cant even find the gerrit manual, and less can actually read that document [00:27:14] so what do you suggest? [00:27:54] people can still google "gerrit verified code review" and click on the first result [00:27:57] paravoid: hoverinfo [00:29:37] Sometimes -2 is used to mark code as "do not merge." [00:30:01] The idea that Code-Review scoring always relates to pure code review is kind of silly. [00:30:47] Elsie: the logical assumption of Code-Review is code review [00:31:48] And yet. [00:32:02] New review: AzaToth; "I do not like "wmgEnableNewbieEditCaptcha", as it contains the colored "Newbie" word" [operations/mediawiki-config] (master) C: -1; - https://gerrit.wikimedia.org/r/69982 [00:32:18] Heh. [00:32:24] That's code review? [00:32:32] it's a variable name [00:32:37] :-P [00:33:03] Elsie: can you please take it elsewhere? [00:35:03] paravoid: Hmm, try /ignore. [00:36:00] PROBLEM - RAID on ms-be10 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [00:36:38] I'm sure you'll find other ways to become trollish and annoying, like, I don't know, abuse our code review system [00:37:01] You seem to burden yourself with worry about me. ;-) [00:38:24] please stop using gerrit and irc channels outside of their scope [00:41:28] Hmmm. [01:01:28] it seems no worse than then the "shellpolicy" and apprioate votes that have been used in the past [01:01:38] and it is a form of code review really [01:32:23] RECOVERY - NTP on ssl3002 is OK: NTP OK: Offset -0.003455042839 secs [01:45:05] New review: Alex Monk; "Do you have any better ideas? We considered 'Anon' as well but it applies to unconfirmed users, so..." [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/69982 [02:01:18] RECOVERY - NTP on ssl3003 is OK: NTP OK: Offset -0.004040241241 secs [02:05:29] !log LocalisationUpdate completed (1.22wmf7) at Sun Jun 23 02:05:29 UTC 2013 [02:05:46] Logged the message, Master [02:09:09] !log LocalisationUpdate completed (1.22wmf8) at Sun Jun 23 02:09:09 UTC 2013 [02:09:19] Logged the message, Master [02:10:35] RECOVERY - search indices - check lucene status page on search18 is OK: HTTP OK: HTTP/1.1 200 OK - 55880 bytes in 0.114 second response time [02:16:43] !log LocalisationUpdate ResourceLoader cache refresh completed at Sun Jun 23 02:16:43 UTC 2013 [02:16:51] Logged the message, Master [02:52:20] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:53:10] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.126 second response time [03:01:40] PROBLEM - Puppet freshness on manutius is CRITICAL: No successful Puppet run in the last 10 hours [03:27:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:28:17] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.126 second response time [03:32:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:36:19] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.127 second response time [03:40:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:43:24] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 9.169 second response time [03:46:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:48:14] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.144 second response time [03:52:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:53:14] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.127 second response time [03:56:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:58:14] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.152 second response time [04:09:22] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:10:12] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.127 second response time [04:15:19] New patchset: Ori.livneh; "Enable logging to Twitter via Twitter API v1.1" [operations/debs/adminbot] (master) - https://gerrit.wikimedia.org/r/70032 [04:21:03] PROBLEM - Puppet freshness on ms-be1001 is CRITICAL: No successful Puppet run in the last 10 hours [04:24:15] hey ori-l [04:29:49] hey paravoid [04:30:00] thanks for the package [04:31:40] New review: Faidon; "What happens if the message is > 140 chars? The identi.ca code trims it, but yours doesn't. I checke..." [operations/debs/adminbot] (master) C: -1; - https://gerrit.wikimedia.org/r/70032 [04:32:44] ori-l: ^ :) [04:32:51] d'oh [04:32:53] let's see [04:33:46] twitter.TwitterError: [{u'message': u'Status is over 140 characters', u'code': 186}] [04:33:54] good catch [04:34:06] there's PostUpdates [04:34:18] which segments the message into multiple tweets [04:34:26] I'm not sure what's more appropriate here [04:34:36] I think the former, for simplicity / consistency [04:34:39] i.e., truncating [04:34:57] ok [04:35:12] updating the patch.. [04:39:27] New patchset: Ori.livneh; "Enable logging to Twitter via Twitter API v1.1" [operations/debs/adminbot] (master) - https://gerrit.wikimedia.org/r/70032 [04:40:29] spaces! [04:40:35] l;kjhsd;oahjsdf[0qihf [04:40:52] haha [04:41:31] just in config.py, right? [04:41:44] oh no, in adminlog.py too [04:42:26] New patchset: Ori.livneh; "Enable logging to Twitter via Twitter API v1.1" [operations/debs/adminbot] (master) - https://gerrit.wikimedia.org/r/70032 [04:43:07] i can't believe i almost desecrated this monument to the beauty and elegance programming [04:43:37] hahahaa [04:44:07] Change merged: jenkins-bot; [operations/debs/adminbot] (master) - https://gerrit.wikimedia.org/r/70032 [04:44:15] danke [04:44:16] * ori-l will bbiab [04:48:07] New patchset: Faidon; "Release 1.7.4" [operations/debs/adminbot] (master) - https://gerrit.wikimedia.org/r/70033 [04:58:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [04:59:17] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.137 second response time [05:28:36] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:29:26] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.133 second response time [05:42:29] PROBLEM - NTP on ssl3003 is CRITICAL: NTP CRITICAL: No response from NTP server [05:45:29] PROBLEM - NTP on ssl3002 is CRITICAL: NTP CRITICAL: No response from NTP server [05:58:40] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [05:59:29] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.164 second response time [06:26:55] !log krinkle Started syncing Wikimedia installation... : Update VisualEditor I7f875f48ce2d [06:27:04] Logged the message, Master [06:27:39] !log Aborted scap due to php fatal errors Narayam.i18n.php, WebFonts.i18n.php and WebFonts.alias.php in 1.22wmf8 [06:27:47] Logged the message, Master [06:31:39] !log Made ExtensionMessages-1.22wmf8.php group-writeable [06:31:48] Logged the message, Mr. Obvious [06:32:59] PROBLEM - RAID on searchidx1001 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [06:33:49] RECOVERY - RAID on searchidx1001 is OK: OK: State is Optimal, checked 4 logical device(s) [06:38:01] !log krinkle Started syncing Wikimedia installation... : Update VisualEditor I7f875f48ce2d [06:38:09] Logged the message, Master [06:52:37] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:53:23] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.124 second response time [06:55:03] New review: Krinkle; "This change triggered a pipeline in Zuul with 0 build steps in it (http://cl.ly/image/110t2u0b3F05)." [operations/debs/adminbot] (master) - https://gerrit.wikimedia.org/r/70033 [07:01:33] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:03:24] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.131 second response time [07:05:34] !log krinkle Finished syncing Wikimedia installation... : Update VisualEditor I7f875f48ce2d [07:05:42] Logged the message, Master [07:09:30] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:10:24] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.124 second response time [07:40:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [07:41:27] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.122 second response time [07:54:37] PROBLEM - Puppet freshness on erzurumi is CRITICAL: No successful Puppet run in the last 10 hours [07:54:37] PROBLEM - Puppet freshness on lvs1006 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:37] PROBLEM - Puppet freshness on lvs1004 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:37] PROBLEM - Puppet freshness on lvs1005 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:37] PROBLEM - Puppet freshness on mc15 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:37] PROBLEM - Puppet freshness on ms-fe3001 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:38] PROBLEM - Puppet freshness on spence is CRITICAL: No successful Puppet run in the last 10 hours [07:54:38] PROBLEM - Puppet freshness on virt3 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:39] PROBLEM - Puppet freshness on virt1 is CRITICAL: No successful Puppet run in the last 10 hours [07:54:39] PROBLEM - Puppet freshness on virt4 is CRITICAL: No successful Puppet run in the last 10 hours [08:01:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:02:18] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.140 second response time [08:22:52] PROBLEM - Puppet freshness on sodium is CRITICAL: No successful Puppet run in the last 10 hours [08:27:51] PROBLEM - Puppet freshness on magnesium is CRITICAL: No successful Puppet run in the last 10 hours [08:32:11] RECOVERY - NTP on ssl3003 is OK: NTP OK: Offset 0.002150654793 secs [08:33:11] RECOVERY - NTP on ssl3002 is OK: NTP OK: Offset 0.001660466194 secs [08:57:42] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:58:31] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.128 second response time [09:01:41] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [09:02:31] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.124 second response time [10:23:23] PROBLEM - Puppet freshness on tin is CRITICAL: No successful Puppet run in the last 10 hours [11:44:41] New review: Helder.wiki; "Some options for the variable name:" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/69982 [11:45:33] New review: Helder.wiki; "(1 comment)" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/69982 [12:18:11] New review: AzaToth; "Could call it then wmgEnableUnconfirmedEditCaptcha" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/69982 [12:30:56] PROBLEM - Disk space on mc15 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [12:32:46] RECOVERY - Disk space on mc15 is OK: DISK OK [12:36:45] New patchset: ArielGlenn; "wikiretriever now gets page titles for log events of given type" [operations/dumps] (ariel) - https://gerrit.wikimedia.org/r/70042 [12:40:53] Change merged: ArielGlenn; [operations/dumps] (ariel) - https://gerrit.wikimedia.org/r/70042 [13:01:46] PROBLEM - Puppet freshness on manutius is CRITICAL: No successful Puppet run in the last 10 hours [13:07:44] New patchset: ArielGlenn; "wikiretriever, cleanup usage message and calls to it" [operations/dumps] (ariel) - https://gerrit.wikimedia.org/r/70043 [13:08:30] Change merged: ArielGlenn; [operations/dumps] (ariel) - https://gerrit.wikimedia.org/r/70043 [14:21:59] PROBLEM - Puppet freshness on ms-be1001 is CRITICAL: No successful Puppet run in the last 10 hours [14:53:35] New patchset: Alex Monk; "Re-enable captcha on ptwiki per overwhelming community consensus" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/69982 [15:36:24] RD: any news regarding the otrs thingi? [16:09:56] New review: Alex Monk; "Some things that definitely should not be in this commit, and this needs a rebase." [operations/mediawiki-config] (master) C: -1; - https://gerrit.wikimedia.org/r/65860 [17:54:47] PROBLEM - Puppet freshness on lvs1006 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:48] PROBLEM - Puppet freshness on erzurumi is CRITICAL: No successful Puppet run in the last 10 hours [17:54:48] PROBLEM - Puppet freshness on spence is CRITICAL: No successful Puppet run in the last 10 hours [17:54:48] PROBLEM - Puppet freshness on ms-fe3001 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:48] PROBLEM - Puppet freshness on virt4 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:48] PROBLEM - Puppet freshness on virt1 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:49] PROBLEM - Puppet freshness on lvs1004 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:49] PROBLEM - Puppet freshness on mc15 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:50] PROBLEM - Puppet freshness on lvs1005 is CRITICAL: No successful Puppet run in the last 10 hours [17:54:51] PROBLEM - Puppet freshness on virt3 is CRITICAL: No successful Puppet run in the last 10 hours [18:23:21] PROBLEM - Puppet freshness on sodium is CRITICAL: No successful Puppet run in the last 10 hours [18:28:21] PROBLEM - Puppet freshness on magnesium is CRITICAL: No successful Puppet run in the last 10 hours [20:03:33] New patchset: Yuvipanda; "Add support for renaming Redis commands to the redis class" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [20:05:00] New review: Yuvipanda; "Hello! Trying to setup Puppet for tools-redis (Tools Labs redis instance), where we want to disable ..." [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [20:05:15] * YuviPanda eyes ori-l with https://gerrit.wikimedia.org/r/#/c/70064/ [20:06:10] hmm, actually not. needs patching [20:09:34] New patchset: Yuvipanda; "Add support for renaming Redis commands to the redis class" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [20:22:25] New review: Asher; "(1 comment)" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [20:23:24] PROBLEM - Puppet freshness on tin is CRITICAL: No successful Puppet run in the last 10 hours [20:46:38] New patchset: Yuvipanda; "Add support for renaming Redis commands to the redis class" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [20:52:55] RD: ping [20:56:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [20:57:14] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.135 second response time [21:03:36] New patchset: Yuvipanda; "Remove unused, empty memcached-sasl class" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70103 [21:06:17] New patchset: Yuvipanda; "Remove unused, empty memcached-sasl class" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70103 [21:06:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:07:16] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.138 second response time [21:31:26] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:32:06] New review: Ori.livneh; "(1 comment)" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [21:32:17] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.124 second response time [21:33:30] New review: Yuvipanda; "(1 comment)" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [21:43:18] New review: Ori.livneh; "(1 comment)" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [21:46:18] New review: Yuvipanda; "(1 comment)" [operations/puppet] (production) - https://gerrit.wikimedia.org/r/70064 [21:46:37] ori-l: do you have some way of testing your puppet patches to operations/puppet locally? [21:46:50] i cloned it, setup vagrant to point to it, but is complaining about missing private repos [21:46:55] YuviPanda: i usually do the work in vagrant first [21:47:45] I think you can clone the labs version of the private puppet repo [21:47:55] oh? [21:47:56] * YuviPanda looks [21:47:58] IIRC it is kept in-sync with production [21:48:10] meaning any password that is defined in one should also be defined in the other (with the different value, obviously) [21:48:47] right, dummy value but same structure [21:48:55] do you remember the repo name? [21:48:57] * YuviPanda searches [21:49:15] YuviPanda: https://gerrit.wikimedia.org/r/#/admin/projects/labs/private [21:49:21] ty [21:49:33] * YuviPanda clones [21:49:42] 'YuviPandaPanda' [21:49:55] shouldn't that be YuviPandaYuviPanda [21:49:58] if it were a proper clone? [21:50:08] or was the clone conjoined? [21:50:25] You usually replace 'Yuvi' with the state description [21:50:34] hence 'SadPanda' rather than 'SadYuviPanda', etc. [21:50:40] heh [21:50:44] :D [21:50:49] true. [21:51:05] * ori-l smacks YuviPanda with a ruler [21:51:08] get your grammar straight! [21:51:24] grammer? :P [21:52:00] what did I get wrong? [21:52:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:52:54] the morphology and syntax of state-indicators in YuviPanda [21:53:19] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.263 second response time [21:53:22] under the grammar of 'IRC Nicks' it is fairly accurate, considering the constraints involved [21:57:27] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:58:19] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.150 second response time [22:01:59] hmm, time to sleep [22:02:04] nite folks. [22:26:31] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:27:20] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK: Status line output matched 400 - 336 bytes in 0.183 second response time [22:45:30] PROBLEM - NTP on ssl3003 is CRITICAL: NTP CRITICAL: No response from NTP server [23:02:10] PROBLEM - Puppet freshness on manutius is CRITICAL: No successful Puppet run in the last 10 hours [23:09:16] PROBLEM - NTP on ssl3002 is CRITICAL: NTP CRITICAL: No response from NTP server