[00:24:14] PROBLEM Current Load is now: WARNING on bots-cb i-0000009e output: WARNING - load average: 10.10, 15.89, 7.85 [00:34:14] RECOVERY Current Load is now: OK on bots-cb i-0000009e output: OK - load average: 0.22, 2.45, 4.31 [00:41:27] Ryan_Lane: Do we have database replication of any kind in labs yet? [01:23:54] PROBLEM Disk Space is now: CRITICAL on deployment-transcoding i-00000105 output: DISK CRITICAL - free space: / 37 MB (2% inode=53%): [01:28:54] PROBLEM Disk Space is now: WARNING on deployment-transcoding i-00000105 output: DISK WARNING - free space: / 48 MB (3% inode=53%): [01:31:14] PROBLEM Puppet freshness is now: CRITICAL on wikidata-dev-2 i-0000020a output: Puppet has not run in last 20 hours [02:47:27] RECOVERY Total Processes is now: OK on wikidata-dev-3 i-00000222 output: PROCS OK: 110 processes [02:47:57] RECOVERY dpkg-check is now: OK on wikidata-dev-3 i-00000222 output: All packages OK [02:49:07] RECOVERY Current Load is now: OK on wikidata-dev-3 i-00000222 output: OK - load average: 0.44, 0.89, 0.42 [02:49:27] RECOVERY Current Users is now: OK on wikidata-dev-3 i-00000222 output: USERS OK - 0 users currently logged in [02:50:47] RECOVERY Disk Space is now: OK on wikidata-dev-3 i-00000222 output: DISK OK [02:50:47] RECOVERY Free ram is now: OK on wikidata-dev-3 i-00000222 output: OK: 90% free memory [03:27:09] PROBLEM Puppet freshness is now: CRITICAL on nginx-dev1 i-000000f0 output: Puppet has not run in last 20 hours [03:35:39] PROBLEM Free ram is now: WARNING on nova-daas-1 i-000000e7 output: Warning: 13% free memory [03:55:39] PROBLEM Free ram is now: CRITICAL on nova-daas-1 i-000000e7 output: Critical: 5% free memory [03:57:29] PROBLEM Free ram is now: WARNING on utils-abogott i-00000131 output: Warning: 14% free memory [03:57:49] PROBLEM Free ram is now: WARNING on test-oneiric i-00000187 output: Warning: 17% free memory [04:04:09] PROBLEM Free ram is now: WARNING on orgcharts-dev i-0000018f output: Warning: 17% free memory [04:05:39] RECOVERY Free ram is now: OK on nova-daas-1 i-000000e7 output: OK: 93% free memory [04:12:29] PROBLEM Free ram is now: CRITICAL on utils-abogott i-00000131 output: Critical: 5% free memory [04:21:06] PROBLEM Free ram is now: CRITICAL on test-oneiric i-00000187 output: Critical: 2% free memory [04:21:06] RECOVERY Free ram is now: OK on utils-abogott i-00000131 output: OK: 96% free memory [04:24:18] PROBLEM Current Load is now: WARNING on nagios 127.0.0.1 output: WARNING - load average: 1.24, 5.29, 3.42 [04:26:31] RECOVERY Free ram is now: OK on test-oneiric i-00000187 output: OK: 96% free memory [04:29:02] PROBLEM Current Load is now: WARNING on bots-sql3 i-000000b4 output: WARNING - load average: 5.18, 6.82, 5.68 [04:31:42] PROBLEM Free ram is now: CRITICAL on orgcharts-dev i-0000018f output: Critical: 4% free memory [04:34:02] RECOVERY Current Load is now: OK on bots-sql3 i-000000b4 output: OK - load average: 1.14, 4.26, 4.97 [04:34:22] RECOVERY Current Load is now: OK on nagios 127.0.0.1 output: OK - load average: 0.31, 1.82, 2.60 [04:36:42] RECOVERY Free ram is now: OK on orgcharts-dev i-0000018f output: OK: 95% free memory [05:04:02] PROBLEM Free ram is now: WARNING on test3 i-00000093 output: Warning: 6% free memory [05:09:02] PROBLEM Free ram is now: CRITICAL on test3 i-00000093 output: Critical: 5% free memory [05:59:02] RECOVERY Free ram is now: OK on test3 i-00000093 output: OK: 96% free memory [06:06:02] PROBLEM Disk Space is now: CRITICAL on bz-dev i-000001db output: DISK CRITICAL - free space: / 21 MB (1% inode=43%): [06:11:02] PROBLEM Disk Space is now: WARNING on bz-dev i-000001db output: DISK WARNING - free space: / 54 MB (4% inode=43%): [07:07:00] PROBLEM Puppet freshness is now: CRITICAL on nova-production1 i-0000007b output: Puppet has not run in last 20 hours [07:11:00] PROBLEM Puppet freshness is now: CRITICAL on nova-gsoc1 i-000001de output: Puppet has not run in last 20 hours [08:51:45] hellllooo [08:52:49] goodbyyyyyyyyyyyyyyyye [09:12:05] hashar: hey [09:12:20] what's the status of your update :-) [09:16:34] which update ? [09:18:32] you changed configuration of apaches or not? [09:19:41] we needed to install some cache or something like that like Reedy said, I don't remember what is that [09:31:11] I have only changed deployment-web instance to use the production puppet class [09:31:30] why is there 7 apaches instances anyway? Is there any specific differences between them ? [09:31:46] I am going to switch all the webXX boxes this morning [09:34:17] there is 5 of them and 1 is being set up [09:34:28] and there is so many of them because they are overloaded most of time [09:34:51] Ryan said I should create some more, we had 2 in past [09:35:08] Ryan_Lane hi :O [09:35:20] hashar: I can do that if you tell me what to change [09:36:05] so which one is being used right ? :D [09:36:44] all we have to do is probably to use the apaches::service class instead of web server::php5 [09:37:18] hashar: all of them are being used [09:37:29] traffic is split to apaches [09:37:40] btw reloging to irc brb [09:37:42] by a LVS box or is that done at squid login? [09:37:47] squid [09:46:39] bak [09:46:41] :O [09:57:29] petan|wk: back. Where is the squid conf / doc ? :-] [09:58:00] ./etc/squid [09:58:05] there is no doc [09:58:11] \o/ [09:58:32] I don't understand squid I was hoping that Ryan give us the prod config few months ago [09:58:44] this is a workaround only what we use now [09:58:47] don't spend anytime on squid anyway [09:58:55] why [09:58:57] I think it is going to be dropped in favor of Varnish anyway [09:59:02] hm [09:59:12] but right now we use it [09:59:15] on prod [09:59:18] yes [09:59:36] but by the time we figure out how to configure it on labs, prod will probably have dropped it :-] [09:59:40] anyway it is not a big issue [09:59:48] ok [09:59:59] we just need it to split the load between the apaches and cache some statics files [10:00:06] I guess everything else should hit the apaches [10:01:06] ok [10:02:30] !log deployment-req adding generic::packages::git-core on deployment-squid so we can track changes being made in /etc/ [10:02:32] deployment-req is not a valid project. [10:03:13] AHHHH [10:03:25] !log deployment-prep adding generic::packages::git-core on deployment-squid so we can track [10:03:28] Logged the message, Master [10:03:47] !depprep [10:03:52] :-P [10:04:44] today is deadmau5 day , one hour long mix http://www.youtube.com/watch?v=_9IBbMW2o_o [10:04:45] \o/ [10:07:46] ahh [10:07:58] we can't rename an instance through labsconsole :D [10:11:08] !log deployment-prep made /etc/ a git repository on deployment-squid and committed existing /etc/squid/ [10:11:10] Logged the message, Master [10:12:26] o.0 [10:12:30] That's rather insane [10:12:53] what is insane? [10:13:02] Making /etc/ a git repo [10:13:18] that is the first thing I do on all my machine [10:13:29] Then you're insane [10:13:36] I even know someone who has / under git [10:13:51] that let you easily track any modification made to your system [10:13:58] and revert to a previous know state :] [10:14:03] I am not sure that is all insane [10:14:11] As git doesn't track changes unless you make commits then you have to specifically commit on changes so you should know what changes have been made and you should then use a config management system [10:14:50] XD [10:14:53] it's insane [10:14:53] I do review change in /etc regular and do the commit manually [10:15:02] but I don't care unless it's not my server [10:15:33] like commiting /etc/shadow is a bad idea [10:15:58] you would need to commit as root also [10:16:05] that's another bad thing you should avoid [10:16:42] making a repo of rootfs is a most insane thing I can imagine :D [10:16:53] like commiting stuff in /tmp [10:17:05] Lets just make /etc a ramfs :D [10:17:08] hehe [10:17:17] live cd does it [10:17:32] is beta.wmflabs.org deprecated in favor of deployment.wikimedia.beta.wmflabs.org ? [10:17:38] squid still references the first [10:17:47] hashar: I don't understand squid [10:17:52] ok :-) [10:17:54] will update it so [10:17:54] I did what I thought it's correct and it works [10:18:27] I thought that beta.wmflabs.org would tell to squid use cache for *beta.wmflabs.org [10:18:35] because I didn't want to define all domains we have [10:18:52] Nah [10:18:55] It's special like that [10:18:56] <3 varnish [10:43:19] petan|wk: is deployment-webs1 an Apache too ? [10:47:15] !log deployment-prep Cleaning out squid peers list [10:47:17] Logged the message, Master [10:53:58] IIRC yes [10:54:04] Dunno why it's called webs not web though [10:54:27] ahhso I will have to add it too [10:54:36] cause there is only 4 apaches in squid right now :-) [10:54:38] but [10:54:43] I need a coffee first [10:55:58] Squid is horrible to configure imo [11:02:46] !log deployment-prep migrate web{3,4,5} from webserver::php5 to apaches::service [11:02:47] Logged the message, Master [11:07:45] puppet takes sooo long :( [11:09:53] It does? [11:12:35] PROBLEM dpkg-check is now: CRITICAL on deployment-web3 i-00000219 output: DPKG CRITICAL dpkg reports broken packages [11:14:25] PROBLEM dpkg-check is now: CRITICAL on deployment-web4 i-00000214 output: DPKG CRITICAL dpkg reports broken packages [11:14:45] PROBLEM dpkg-check is now: CRITICAL on deployment-web5 i-00000213 output: DPKG CRITICAL dpkg reports broken packages [11:19:21] !log deployment-prep changed squid visible name to squid001.beta.wmflabs.org [11:19:23] Logged the message, Master [11:19:25] RECOVERY dpkg-check is now: OK on deployment-web4 i-00000214 output: All packages OK [11:19:36] RECOVERY dpkg-check is now: OK on deployment-web5 i-00000213 output: All packages OK [11:20:03] hashar: that's https version [11:20:38] beta ? [11:20:55] so should I name it squid001.deployment.wmflabs.org instead? [11:21:04] no [11:21:06] webs1 [11:21:11] ohh [11:21:14] don't insert it to squid [11:21:17] it doesn't work [11:21:35] squid only has web web3 web4 and web5 for now [11:21:39] web - web5 are apaches [11:21:42] ok [11:21:48] web2 should be up soon [11:22:17] !log deployment-prep puppet finished migration of web{3,4,5} to apache::service [11:22:19] Logged the message, Master [11:22:29] can you install that cache [11:22:34] we talked about it [11:22:35] RECOVERY dpkg-check is now: OK on deployment-web3 i-00000219 output: All packages OK [11:23:11] APC [11:23:12] that one [11:23:26] what are 'beta' and 'deployment' sub domains for ? [11:23:33] it used to be deployment in past [11:23:34] yeah APC is being installed right now. Need to check it works [11:23:37] then we renamed it [11:23:56] great [11:24:19] could you bless me with `netadmin` role on deployment-prep project? [11:24:25] would need it to maintain dns entries :-] [11:26:35] yes [11:27:41] done [11:27:46] danke [11:27:54] just don't remove the deployment dns it should still work [11:28:49] just wanted to set an entry for squid001.beta.wmflabs.org [11:28:56] ok [11:29:30] so APC should be enabled now [11:29:41] ok [11:29:44] that magically happens when installing apache::service [11:30:00] which somehow makes puppet install the php-apc package [11:30:05] which is, AFAIK, enabled by default [11:31:15] PROBLEM Puppet freshness is now: CRITICAL on wikidata-dev-2 i-0000020a output: Puppet has not run in last 20 hours [11:31:34] there is problem with log [11:32:41] when I open any page on wiki there is no debug log [11:32:43] $wgDebugLogFile [11:35:52] where is that set ? [11:36:41] in CommonSettings.php [11:36:59] it used to work today [11:37:07] last entry is-rw-r--r-- 1 www-data www-data 289522903 2012-04-25 11:19 [11:37:14] just like when someone die, he used to live yesterday :-] [11:37:17] few minutes ago it worked [11:37:17] lets see [11:39:13] !deployment-prep manually purged debian package `ack`, installed `ack-grep` [11:39:13] deployment-prep is a project to test mediawiki at beta.wmflabs.org before putting it to prod [11:39:22] !log deployment-prep manually purged debian package `ack`, installed `ack-grep` [11:39:23] Logged the message, Master [11:56:01] hashar: did you find why logging stopped working? [11:56:04] is there a way to debug it [11:56:34] there must be one [11:56:39] sorry was distracted by something else [11:56:41] resuming now [12:16:22] New patchset: Hashar; "classes for deployment preparation project (beta)" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/5790 [12:16:36] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/5790 [12:16:40] New review: Hashar; "(no comment)" [operations/puppet] (test); V: 1 C: 2; - https://gerrit.wikimedia.org/r/5790 [12:22:18] ahhhh [12:23:02] I should have applied to an op position :-] [12:23:09] to get root access on the machine that actually matter [12:23:59] !log deployment-prep added a basic puppet skeleton in manifests/labs/beta/ with https://gerrit.wikimedia.org/r/5790 (test branch) [12:24:01] Logged the message, Master [12:27:48] mutante: do you know how we could use the various passwords::* puppets classes on labs? [12:27:56] I thought we had a dummy repository [12:29:04] hashar: there is labs/private [12:29:12] ohh forgot about that one [12:29:18] going to add some dummy classes there so [12:30:18] yeah, guess so, and then replace passwords in public classes with variables reading from private [12:31:14] eh, public puppet templates of config files i should say [12:31:37] I try to enable misc::scripts on labs but it requires the misc::passwordsScripts class which indeed uses assignments such as : [12:31:40] $cachemgr_pass = $passwords::misc::scripts::cachemgr_pass [12:32:35] hashar: that logging is really fucked [12:32:44] now it does work for commons but nothing else [12:33:15] hashar: sry, not really time to look at that closer right now, but how about we merge your mysql change, because installing these servers will eat more time [12:33:20] is it needed to enable any other variable than wgDebugLogFile [12:34:44] mutante: follow up on #wikimedia-operations [12:37:06] petan|wk: so is the variable set in CommonSettings ? [12:37:11] what does it log ? Everything ? [12:37:13] or just errors? [12:41:48] New patchset: Hashar; "dummy misc::passwordScript" [labs/private] (master) - https://gerrit.wikimedia.org/r/5792 [12:42:31] o.0 [12:43:10] hashar: it used to log some stuff, not really sure what exactly [12:43:27] how do you run maintenance script on labs? [12:43:28] but it was logging surely some lines for each execution of page [12:43:32] I guess from deployment-dbdump ? [12:43:33] hashar: there is a folder bin [12:43:37] hashar: yes [12:43:37] I would like to run the eval.php script [12:43:42] ok do it on dbdump [12:43:45] or webs1 [12:43:49] depends on load [12:43:53] both of them can do that [12:44:04] webs1 is not being used for apache so far so it's good for that as well [12:44:19] I will probably request to have dbdump renamed as bastion [12:44:20] :-D [12:44:40] so we get everything installed there and use that machine as the main working server [12:45:53] oh [12:46:22] got a prompt form: /usr/local/apache/common/live/maintenance/eval.php --wiki enwiki [12:59:33] hashar: works? [12:59:58] been fixing some syntax errors in a ruby template :-D [13:00:04] trying to log stuff right now [13:00:13] if you really need to rename it you could just create a new server [13:00:27] don't forget you can type log in shell [13:00:44] !log deployment-prep petrb: test [13:00:46] Logged the message, Master [13:00:51] see? [13:01:02] ohhh there is a web service !!! [13:01:04] \o/ [13:01:05] yes [13:01:13] it works on some projects where people want it :-) [13:01:24] !log deployment-prep hashar: I am a hero [13:01:25] Logged the message, Master [13:02:14] I use only that [13:02:17] too lazy [13:02:36] I have a similar command on production [13:02:46] thanks! [13:04:37] still logging doesn't work [13:04:57] only for commons [13:06:06] hmm $wgDebug is inexistent somehow [13:07:13] weird [13:07:19] is it needed for anything? [13:07:35] for some reason it's logging stuff on commons wiki, but not on any other [13:07:43] :/ [13:07:48] don't understand why [13:08:07] it's using both same config [13:15:47] well I can not write to files in /usr/local/apache/common/wmf-config -( [13:23:54] hashar: that's weird [13:24:00] sec [13:25:20] hashar: try now [13:25:26] logout before [13:25:31] then log back [13:25:37] o.0 why is apache in /usr/local/ anyway? [13:25:50] Damianz: because that's the way they have it on prod [13:25:56] we just mirror it [13:26:05] mw does have some bizzare choices [13:26:10] indeed [13:26:13] mw not [13:26:17] wmf maybe :P [13:26:28] Same diff :P [13:26:34] Damianz: cause production has/had its own apache compilation installed using the /usr/local/ prefix [13:26:36] Some of the mw choices are as bizzare as wmf's [13:26:46] heh [13:26:46] since that path is hardcoded everywhere it is safer to keep using it :-]]] [13:26:48] hashar: Can not haz packages? [13:27:11] back in 2002 none knew about how to write a .rpm :-D [13:27:14] Hmm really need to test my gil theory on why py2.7 sucks and try it with 3 [13:27:23] so no l33t p4ck4g3s !!! [13:28:14] PROBLEM Puppet freshness is now: CRITICAL on nginx-dev1 i-000000f0 output: Puppet has not run in last 20 hours [13:28:16] hashar: you said you want to kill nfs [13:28:17] why [13:28:25] nfs sucks [13:28:28] cause I can't write to the common path ? :D [13:28:31] and overall NFS sucks [13:28:32] scap sucks [13:28:48] but it makes stuff so easy :D [13:28:56] ok what is your alternative to that [13:29:10] scap :-D [13:29:16] before you decide to use something experimental like gluster, keep in mind it's buggy a lot [13:29:17] seriously I have no idea right now [13:29:19] NFS is fine for now [13:29:49] in the end the safe way is to have files modified on a bastion then deployed on the other hosts using rsync / git / whatever file copy [13:29:57] for example right now I moved all logs to gluster and since then I have a lot of troubles with that [13:29:59] you could even tar | nc ;-] [13:30:05] also the whole auto mount is broken [13:30:20] maybe it's not gluster what sucks but actually the way it's mounted [13:30:25] might be [13:30:34] like when I do ls /data/project [13:30:40] shell stuck [13:30:43] for 20 seconds [13:30:53] that's what I hate [13:31:01] touch: cannot touch `/usr/local/apache/foo': Permission denied [13:31:01] [13:31:03] ;-D [13:31:14] althgouth the dir is drwxrwxr-x 5 mah depops [13:31:25] and I am a member of depops [13:31:30] yes so am I [13:31:36] no idea why it doesn't work for you [13:31:40] everyone else is fine [13:31:49] try sudo su mah [13:31:51] :P [13:31:56] that will fix it hehe [13:32:30] maybe we could just create a new user "op" :D [13:32:35] and switch to it [13:32:58] we wouldn't need group at all [13:33:15] <^demon> If you're trying to be more like the actual deployment, you should make the user called mwdeploy and have all deployment scripts sudo to it. [13:33:26] aha [13:33:39] right [13:34:21] ^demon: where is $HOME [13:34:35] <^demon> /home/wikipedia? [13:34:58] ^demon: going to have misc::scripts installed on the bastion [13:35:58] ok done [13:36:08] hashar: try sudo su mwdeploy [13:36:10] <^demon> Heh, so it turns out httpd.maxThreads is set to 25, but database.poolLimit is set to 8. Doesn't this mean anyone beyond the first 8 users is likely to hit a database connection limit error? [13:36:20] <^demon> (these are defaults) [13:36:57] hmm at least I can write to deployment-nfs-memc:/mnt/export/apache/ [13:37:58] it magically solved!! [13:38:01] * hashar hates NFS [13:39:08] what solved [13:39:16] just use mwdeploy since now [13:39:17] :D [13:39:21] it works [14:13:45] PROBLEM Current Load is now: CRITICAL on twmysqlconf i-00000223 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:14:25] PROBLEM Current Users is now: CRITICAL on twmysqlconf i-00000223 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:15:05] PROBLEM Disk Space is now: CRITICAL on twmysqlconf i-00000223 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:15:45] PROBLEM Free ram is now: CRITICAL on twmysqlconf i-00000223 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:16:15] ^^^ that twmysqlconf is a new instance [14:16:20] yeh [14:16:29] that's why so many problems hehe [14:16:40] puppet is slower than my c++ parser XD [14:16:54] which creates the nagios confs [14:16:55] PROBLEM Total Processes is now: CRITICAL on twmysqlconf i-00000223 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:17:35] PROBLEM dpkg-check is now: CRITICAL on twmysqlconf i-00000223 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:33:38] and I can't log on that new instance [14:33:48] the "testwarm" project is f*** beyond repair [14:35:25] Change abandoned: Demon; "Was part of a test that's already merged, so abandoning. Feel free to restore if it's necessary." [operations/puppet] (test) - https://gerrit.wikimedia.org/r/4144 [14:41:00] hashar: what is on log? [14:41:05] !console [14:41:05] in case you want to see what is happening on terminal of your vm, check console output [14:42:59] !log deployment-prep Creating temporary instance to test a MySQL puppet snippet [14:43:02] Logged the message, Master [14:43:19] hashar: can you prefix all instances with deployment [14:43:22] petan|wk: problem solved. I am deleting the project and already deleted all instances. [14:43:29] petan|wk: that one is a temp one [14:43:30] which project? [14:43:34] I will delete it in an hour or so [14:43:57] the delete project is 'testswarm' . I have opened a bug request to have it deleted. : https://bugzilla.wikimedia.org/36241 [14:44:00] ah ok [14:44:04] never worked :D [14:44:07] well it did [14:44:11] right [14:44:17] but then stopped working once labs started requesting ssh keys [14:44:20] and we never figured out why [14:44:23] ok [14:44:24] It did work, I worked on it a lot. but no longer needed [14:44:36] ohh [14:44:37] I can login still [14:44:45] Krinkle: I never managed to log in it :-D [14:45:12] petan|wk: testswarmmysqlconf will be deleted as soon as I finish my mess with it [14:46:45] PROBLEM host: swarm-specialpage is DOWN address: i-0000017b check_ping: Invalid hostname/address - i-0000017b [14:46:53] hashar: I logged my progress on https://labsconsole.wikimedia.org/w/index.php?title=Nova_Resource:I-0000017b#Config (which is now deleted) [14:48:05] PROBLEM host: twmysqlconf is DOWN address: i-00000223 check_ping: Invalid hostname/address - i-00000223 [14:49:35] PROBLEM host: miniswarm is DOWN address: i-0000010a check_ping: Invalid hostname/address - i-0000010a [14:49:54] Krinkle: there should be some people who can undelete pages or just have generic sysop rights [14:50:09] I don't understand why Ryan didn't make nova admin a user rights [14:50:11] right [14:50:14] I'd like to have sysop on labsconsolewiki [14:50:18] instead of giving it to sysop by default [14:50:46] current permissions on console are strange [14:53:44] PROBLEM Current Load is now: CRITICAL on testswarmmysqlconf i-00000224 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:54:17] https://bugzilla.wikimedia.org/show_bug.cgi?id=36243 [14:54:24] PROBLEM Current Users is now: CRITICAL on testswarmmysqlconf i-00000224 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:55:04] PROBLEM Disk Space is now: CRITICAL on testswarmmysqlconf i-00000224 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:55:44] PROBLEM Free ram is now: CRITICAL on testswarmmysqlconf i-00000224 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:56:54] PROBLEM Total Processes is now: CRITICAL on testswarmmysqlconf i-00000224 output: CHECK_NRPE: Error - Could not complete SSL handshake. [14:57:34] PROBLEM dpkg-check is now: CRITICAL on testswarmmysqlconf i-00000224 output: CHECK_NRPE: Error - Could not complete SSL handshake. [15:03:27]