[00:00:06] it should work, but I can't guarantee anything as I haven't got it running myself either yet [00:00:25] your bot I mean - my bots work fine on python [00:02:15] Thehelpfulone: how much Java do you know? [00:02:40] Good luck getting things working, Sven_Manguard ... IIRC there are other folks around who know Java, including in the #mediawiki channel. I think Beau_ there knows Java [00:02:52] not much sorry [00:03:11] I'm looking into this x-forwarding [00:03:14] I know none [00:03:14] petan: am I right in remembering that you know some Java? [00:03:25] Thehelpfulone: x-forwarding is a pretty useful trick, I hear from the people who do it! [00:03:39] petan|wk: ^ (re Java) [00:05:03] thehelpfulone@bots-3:~$ The program 'xeyes' is currently not installed. To run 'xeyes' please ask your administrator to install the package 'x11-apps' [00:05:23] do I need that Reedy? ^ [00:05:35] probably [00:06:00] might as well give it to me too... [00:06:24] Sven_Manguard: it will be installed on the server to be accessible by all [00:06:59] petan: petan|wk ^^ something for you to have a look at please: thehelpfulone@bots-3:~$ The program 'xeyes' is currently not installed. To run 'xeyes' please ask your administrator to install the package 'x11-apps [00:12:37] night, all [01:34:10] PROBLEM Puppet freshness is now: CRITICAL on hugglewiki i-000000aa output: Puppet has not run in last 20 hours [01:35:10] PROBLEM Puppet freshness is now: CRITICAL on wikistream-1 i-0000016e output: Puppet has not run in last 20 hours [01:43:50] PROBLEM Free ram is now: WARNING on bots-2 i-0000009c output: Warning: 19% free memory [01:46:10] PROBLEM Puppet freshness is now: CRITICAL on migration1 i-00000261 output: Puppet has not run in last 20 hours [01:58:49] RECOVERY Free ram is now: OK on bots-2 i-0000009c output: OK: 20% free memory [02:00:14] PROBLEM Puppet freshness is now: CRITICAL on memcache-puppet i-00000153 output: Puppet has not run in last 20 hours [02:04:14] PROBLEM Puppet freshness is now: CRITICAL on jenkins2 i-00000102 output: Puppet has not run in last 20 hours [02:04:14] PROBLEM Puppet freshness is now: CRITICAL on publicdata-administration i-0000019e output: Puppet has not run in last 20 hours [02:04:14] PROBLEM Puppet freshness is now: CRITICAL on resourceloader2-apache i-000001d7 output: Puppet has not run in last 20 hours [02:05:14] PROBLEM Puppet freshness is now: CRITICAL on dumps-6 i-00000266 output: Puppet has not run in last 20 hours [02:05:14] PROBLEM Puppet freshness is now: CRITICAL on labs-nfs1 i-0000005d output: Puppet has not run in last 20 hours [02:05:14] PROBLEM Puppet freshness is now: CRITICAL on mailman-01 i-00000235 output: Puppet has not run in last 20 hours [02:05:14] PROBLEM Puppet freshness is now: CRITICAL on swift-be3 i-000001c9 output: Puppet has not run in last 20 hours [02:05:14] PROBLEM Puppet freshness is now: CRITICAL on wikidata-dev-3 i-00000225 output: Puppet has not run in last 20 hours [02:06:14] PROBLEM Puppet freshness is now: CRITICAL on wep i-000000c2 output: Puppet has not run in last 20 hours [02:07:24] PROBLEM Puppet freshness is now: CRITICAL on deployment-thumbproxy i-0000026b output: Puppet has not run in last 20 hours [02:07:24] PROBLEM Puppet freshness is now: CRITICAL on gerrit i-000000ff output: Puppet has not run in last 20 hours [02:07:24] PROBLEM Puppet freshness is now: CRITICAL on gluster-devstack i-00000274 output: Puppet has not run in last 20 hours [02:07:24] PROBLEM Puppet freshness is now: CRITICAL on shop-analytics-main i-000001e6 output: Puppet has not run in last 20 hours [02:07:24] PROBLEM Puppet freshness is now: CRITICAL on wikistats-01 i-00000042 output: Puppet has not run in last 20 hours [02:07:24] PROBLEM Puppet freshness is now: CRITICAL on worker1 i-00000208 output: Puppet has not run in last 20 hours [02:08:14] PROBLEM Puppet freshness is now: CRITICAL on bots-apache1 i-000000b0 output: Puppet has not run in last 20 hours [02:08:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-web3 i-00000219 output: Puppet has not run in last 20 hours [02:08:14] PROBLEM Puppet freshness is now: CRITICAL on dumps-2 i-00000257 output: Puppet has not run in last 20 hours [02:08:14] PROBLEM Puppet freshness is now: CRITICAL on precise-test i-00000231 output: Puppet has not run in last 20 hours [02:09:14] PROBLEM Puppet freshness is now: CRITICAL on swift-be2 i-000001c8 output: Puppet has not run in last 20 hours [02:10:14] PROBLEM Puppet freshness is now: CRITICAL on building i-0000014d output: Puppet has not run in last 20 hours [02:10:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-backup i-000000f8 output: Puppet has not run in last 20 hours [02:12:14] PROBLEM Puppet freshness is now: CRITICAL on aggregator-test2 i-0000024e output: Puppet has not run in last 20 hours [02:12:14] PROBLEM Puppet freshness is now: CRITICAL on reportcard2 i-000001ea output: Puppet has not run in last 20 hours [02:13:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache22 i-0000026f output: Puppet has not run in last 20 hours [02:13:14] PROBLEM Puppet freshness is now: CRITICAL on dumps-1 i-00000170 output: Puppet has not run in last 20 hours [02:13:14] PROBLEM Puppet freshness is now: CRITICAL on webserver-lcarr i-00000134 output: Puppet has not run in last 20 hours [02:15:14] PROBLEM Puppet freshness is now: CRITICAL on bots-4 i-000000e8 output: Puppet has not run in last 20 hours [02:15:14] PROBLEM Puppet freshness is now: CRITICAL on bots-cb i-0000009e output: Puppet has not run in last 20 hours [02:15:14] PROBLEM Puppet freshness is now: CRITICAL on ganglia-collector i-000000b7 output: Puppet has not run in last 20 hours [02:15:14] PROBLEM Puppet freshness is now: CRITICAL on hugglewa-db i-00000188 output: Puppet has not run in last 20 hours [02:15:14] PROBLEM Puppet freshness is now: CRITICAL on swift-be4 i-000001ca output: Puppet has not run in last 20 hours [02:15:14] PROBLEM Puppet freshness is now: CRITICAL on wikisource-web i-000000fe output: Puppet has not run in last 20 hours [02:16:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache20 i-0000026c output: Puppet has not run in last 20 hours [02:16:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-transcoding i-00000105 output: Puppet has not run in last 20 hours [02:16:14] PROBLEM Puppet freshness is now: CRITICAL on incubator-bot1 i-00000251 output: Puppet has not run in last 20 hours [02:17:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-cache-upload i-00000263 output: Puppet has not run in last 20 hours [02:17:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-dbdump i-000000d2 output: Puppet has not run in last 20 hours [02:17:14] PROBLEM Puppet freshness is now: CRITICAL on php5builds i-00000192 output: Puppet has not run in last 20 hours [02:18:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-feed i-00000118 output: Puppet has not run in last 20 hours [02:18:14] PROBLEM Puppet freshness is now: CRITICAL on incubator-bot2 i-00000252 output: Puppet has not run in last 20 hours [02:18:14] PROBLEM Puppet freshness is now: CRITICAL on robh2 i-000001a2 output: Puppet has not run in last 20 hours [02:18:14] PROBLEM Puppet freshness is now: CRITICAL on wikidata-dev-1 i-0000020c output: Puppet has not run in last 20 hours [02:19:14] PROBLEM Puppet freshness is now: CRITICAL on bots-sql1 i-000000b5 output: Puppet has not run in last 20 hours [02:19:14] PROBLEM Puppet freshness is now: CRITICAL on cn-wiki-db-lucid i-00000241 output: Puppet has not run in last 20 hours [02:19:14] PROBLEM Puppet freshness is now: CRITICAL on firstinstance i-0000013e output: Puppet has not run in last 20 hours [02:19:14] PROBLEM Puppet freshness is now: CRITICAL on kripke i-00000268 output: Puppet has not run in last 20 hours [02:19:14] PROBLEM Puppet freshness is now: CRITICAL on localpuppet1 i-0000020b output: Puppet has not run in last 20 hours [02:20:14] PROBLEM Puppet freshness is now: CRITICAL on bots-sql2 i-000000af output: Puppet has not run in last 20 hours [02:20:14] PROBLEM Puppet freshness is now: CRITICAL on mobile-testing i-00000271 output: Puppet has not run in last 20 hours [02:20:14] PROBLEM Puppet freshness is now: CRITICAL on swift-fe1 i-000001d2 output: Puppet has not run in last 20 hours [02:22:14] PROBLEM Puppet freshness is now: CRITICAL on ganglia-test2 i-00000250 output: Puppet has not run in last 20 hours [02:22:14] PROBLEM Puppet freshness is now: CRITICAL on nginx-dev1 i-000000f0 output: Puppet has not run in last 20 hours [02:22:14] PROBLEM Puppet freshness is now: CRITICAL on secondinstance i-0000015b output: Puppet has not run in last 20 hours [02:22:14] PROBLEM Puppet freshness is now: CRITICAL on test2 i-0000013c output: Puppet has not run in last 20 hours [02:23:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache23 i-00000270 output: Puppet has not run in last 20 hours [02:24:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-webs1 i-0000012a output: Puppet has not run in last 20 hours [02:25:14] PROBLEM Puppet freshness is now: CRITICAL on bastion1 i-000000ba output: Puppet has not run in last 20 hours [02:26:14] PROBLEM Puppet freshness is now: CRITICAL on venus i-000000ea output: Puppet has not run in last 20 hours [02:27:22] PROBLEM Puppet freshness is now: CRITICAL on demo-deployment1 i-00000276 output: Puppet has not run in last 20 hours [02:30:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-cache-bits i-00000264 output: Puppet has not run in last 20 hours [02:30:14] PROBLEM Puppet freshness is now: CRITICAL on feeds i-000000fa output: Puppet has not run in last 20 hours [02:30:14] PROBLEM Puppet freshness is now: CRITICAL on fundraising-civicrm i-00000169 output: Puppet has not run in last 20 hours [02:31:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-nfs-memc i-000000d7 output: Puppet has not run in last 20 hours [02:31:14] PROBLEM Puppet freshness is now: CRITICAL on grail i-0000021e output: Puppet has not run in last 20 hours [02:31:14] PROBLEM Puppet freshness is now: CRITICAL on labs-relay i-00000103 output: Puppet has not run in last 20 hours [02:31:14] PROBLEM Puppet freshness is now: CRITICAL on nova-production1 i-0000007b output: Puppet has not run in last 20 hours [02:31:14] PROBLEM Puppet freshness is now: CRITICAL on udp-filter i-000001df output: Puppet has not run in last 20 hours [02:32:14] PROBLEM Puppet freshness is now: CRITICAL on bastion-restricted1 i-0000019b output: Puppet has not run in last 20 hours [02:32:14] PROBLEM Puppet freshness is now: CRITICAL on bots-2 i-0000009c output: Puppet has not run in last 20 hours [02:32:14] PROBLEM Puppet freshness is now: CRITICAL on demo-mysql1 i-00000256 output: Puppet has not run in last 20 hours [02:32:14] PROBLEM Puppet freshness is now: CRITICAL on demo-web1 i-00000255 output: Puppet has not run in last 20 hours [02:32:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-imagescaler01 i-0000025a output: Puppet has not run in last 20 hours [02:32:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-mc i-0000021b output: Puppet has not run in last 20 hours [02:32:15] PROBLEM Puppet freshness is now: CRITICAL on ee-prototype i-0000013d output: Puppet has not run in last 20 hours [02:32:15] PROBLEM Puppet freshness is now: CRITICAL on fr-wiki-db-precise i-0000023e output: Puppet has not run in last 20 hours [02:32:16] PROBLEM Puppet freshness is now: CRITICAL on swift-aux1 i-0000024b output: Puppet has not run in last 20 hours [02:33:14] PROBLEM Puppet freshness is now: CRITICAL on build-precise1 i-00000273 output: Puppet has not run in last 20 hours [02:34:14] PROBLEM Puppet freshness is now: CRITICAL on fundraising-db i-0000015c output: Puppet has not run in last 20 hours [02:34:14] PROBLEM Puppet freshness is now: CRITICAL on rds i-00000207 output: Puppet has not run in last 20 hours [02:34:14] PROBLEM Puppet freshness is now: CRITICAL on upload-wizard i-0000021c output: Puppet has not run in last 20 hours [02:35:14] PROBLEM Puppet freshness is now: CRITICAL on asher1 i-0000003a output: Puppet has not run in last 20 hours [02:35:14] PROBLEM Puppet freshness is now: CRITICAL on bots-1 i-000000a9 output: Puppet has not run in last 20 hours [02:35:14] PROBLEM Puppet freshness is now: CRITICAL on dumps-7 i-00000267 output: Puppet has not run in last 20 hours [02:36:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-web i-00000217 output: Puppet has not run in last 20 hours [02:36:14] PROBLEM Puppet freshness is now: CRITICAL on dumps-5 i-00000258 output: Puppet has not run in last 20 hours [02:36:14] PROBLEM Puppet freshness is now: CRITICAL on pageviews i-000000b2 output: Puppet has not run in last 20 hours [02:36:14] PROBLEM Puppet freshness is now: CRITICAL on pediapress-ocg1 i-00000233 output: Puppet has not run in last 20 hours [02:39:58] PROBLEM Puppet freshness is now: CRITICAL on aggregator-test i-0000024d output: Puppet has not run in last 20 hours [02:39:58] PROBLEM Puppet freshness is now: CRITICAL on bots-labs i-0000015e output: Puppet has not run in last 20 hours [02:39:58] PROBLEM Puppet freshness is now: CRITICAL on deployment-wmsearch i-000000e1 output: Puppet has not run in last 20 hours [02:39:58] PROBLEM Puppet freshness is now: CRITICAL on embed-sandbox i-000000d1 output: Puppet has not run in last 20 hours [02:39:58] PROBLEM Puppet freshness is now: CRITICAL on en-wiki-db-lucid i-0000023b output: Puppet has not run in last 20 hours [02:39:58] PROBLEM Puppet freshness is now: CRITICAL on opengrok-web i-000001e1 output: Puppet has not run in last 20 hours [02:39:59] PROBLEM Puppet freshness is now: CRITICAL on p-b i-000000ae output: Puppet has not run in last 20 hours [02:39:59] PROBLEM Puppet freshness is now: CRITICAL on testing-groupchange i-00000205 output: Puppet has not run in last 20 hours [02:40:00] PROBLEM Puppet freshness is now: CRITICAL on ve-nodejs i-00000245 output: Puppet has not run in last 20 hours [02:40:21] PROBLEM Puppet freshness is now: CRITICAL on catsort-pub i-000001cc output: Puppet has not run in last 20 hours [02:40:21] PROBLEM Puppet freshness is now: CRITICAL on incubator-common i-00000254 output: Puppet has not run in last 20 hours [02:40:21] PROBLEM Puppet freshness is now: CRITICAL on otrs-jgreen i-0000015a output: Puppet has not run in last 20 hours [02:40:21] PROBLEM Puppet freshness is now: CRITICAL on outreacheval i-0000012e output: Puppet has not run in last 20 hours [02:40:21] PROBLEM Puppet freshness is now: CRITICAL on patchtest i-000000f1 output: Puppet has not run in last 20 hours [02:40:21] PROBLEM Puppet freshness is now: CRITICAL on ubuntu1-pgehres i-000000fb output: Puppet has not run in last 20 hours [02:42:04] PROBLEM Free ram is now: WARNING on bots-2 i-0000009c output: Warning: 18% free memory [02:42:14] PROBLEM Puppet freshness is now: CRITICAL on bots-dev i-00000190 output: Puppet has not run in last 20 hours [02:42:14] PROBLEM Puppet freshness is now: CRITICAL on dev-solr i-00000152 output: Puppet has not run in last 20 hours [02:42:14] PROBLEM Puppet freshness is now: CRITICAL on en-wiki-db-precise i-0000023c output: Puppet has not run in last 20 hours [02:42:14] PROBLEM Puppet freshness is now: CRITICAL on maps-test2 i-00000253 output: Puppet has not run in last 20 hours [02:42:14] PROBLEM Puppet freshness is now: CRITICAL on nova-dev3 i-000000e9 output: Puppet has not run in last 20 hours [02:43:04] PROBLEM Current Load is now: WARNING on nagios 127.0.0.1 output: WARNING - load average: 1.56, 4.57, 2.61 [02:43:14] PROBLEM Puppet freshness is now: CRITICAL on log1 i-00000239 output: Puppet has not run in last 20 hours [02:43:14] PROBLEM Puppet freshness is now: CRITICAL on vumi i-000001e5 output: Puppet has not run in last 20 hours [02:44:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-web4 i-00000214 output: Puppet has not run in last 20 hours [02:44:14] PROBLEM Puppet freshness is now: CRITICAL on ganglia-test3 i-0000025b output: Puppet has not run in last 20 hours [02:48:04] RECOVERY Current Load is now: OK on nagios 127.0.0.1 output: OK - load average: 0.46, 1.85, 1.95 [02:50:14] PROBLEM Puppet freshness is now: CRITICAL on aggregator1 i-0000010c output: Puppet has not run in last 20 hours [02:50:14] PROBLEM Puppet freshness is now: CRITICAL on bots-3 i-000000e5 output: Puppet has not run in last 20 hours [02:50:14] PROBLEM Puppet freshness is now: CRITICAL on deployment-web5 i-00000213 output: Puppet has not run in last 20 hours [02:50:14] PROBLEM Puppet freshness is now: CRITICAL on exim-test i-00000265 output: Puppet has not run in last 20 hours [02:50:14] PROBLEM Puppet freshness is now: CRITICAL on nova-essex-test i-000001f9 output: Puppet has not run in last 20 hours [02:50:14] PROBLEM Puppet freshness is now: CRITICAL on nova-ldap2 i-00000238 output: Puppet has not run in last 20 hours [02:50:15] PROBLEM Puppet freshness is now: CRITICAL on nova-precise1 i-00000236 output: Puppet has not run in last 20 hours [02:50:15] PROBLEM Puppet freshness is now: CRITICAL on scribunto i-0000022c output: Puppet has not run in last 20 hours [02:50:16] PROBLEM Puppet freshness is now: CRITICAL on swift-aux2 i-0000024c output: Puppet has not run in last 20 hours [02:50:16] PROBLEM Puppet freshness is now: CRITICAL on varnish i-000001ac output: Puppet has not run in last 20 hours [02:51:12] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache21 i-0000026d output: Puppet has not run in last 20 hours [02:53:12] PROBLEM Puppet freshness is now: CRITICAL on deployment-sql i-000000d0 output: Puppet has not run in last 20 hours [02:53:12] PROBLEM Puppet freshness is now: CRITICAL on hugglewa-1 i-000001e0 output: Puppet has not run in last 20 hours [02:53:12] PROBLEM Puppet freshness is now: CRITICAL on master i-0000007a output: Puppet has not run in last 20 hours [02:53:12] PROBLEM Puppet freshness is now: CRITICAL on nginx-ffuqua-doom1-3 i-00000196 output: Puppet has not run in last 20 hours [02:53:12] PROBLEM Puppet freshness is now: CRITICAL on simplewikt i-00000149 output: Puppet has not run in last 20 hours [02:53:12] PROBLEM Puppet freshness is now: CRITICAL on vumi-gw1 i-0000008f output: Puppet has not run in last 20 hours [02:54:43] PROBLEM Puppet freshness is now: CRITICAL on labs-realserver i-00000104 output: Puppet has not run in last 20 hours [02:59:20] 05/17/2012 - 02:59:19 - Updating keys for laner at /export/home/deployment-prep/laner [02:59:24] PROBLEM Puppet freshness is now: CRITICAL on bob i-0000012d output: Puppet has not run in last 20 hours [02:59:24] PROBLEM Puppet freshness is now: CRITICAL on bots-nfs i-000000b1 output: Puppet has not run in last 20 hours [02:59:24] PROBLEM Puppet freshness is now: CRITICAL on bots-sql3 i-000000b4 output: Puppet has not run in last 20 hours [02:59:24] PROBLEM Puppet freshness is now: CRITICAL on deployment-squid i-000000dc output: Puppet has not run in last 20 hours [02:59:24] PROBLEM Puppet freshness is now: CRITICAL on dumps-3 i-0000017c output: Puppet has not run in last 20 hours [02:59:24] PROBLEM Puppet freshness is now: CRITICAL on dumps-8 i-0000026e output: Puppet has not run in last 20 hours [02:59:25] PROBLEM Puppet freshness is now: CRITICAL on labs-build1 i-0000006b output: Puppet has not run in last 20 hours [02:59:25] PROBLEM Puppet freshness is now: CRITICAL on pediapress-ocg2 i-00000234 output: Puppet has not run in last 20 hours [02:59:26] PROBLEM Puppet freshness is now: CRITICAL on pediapress-packager i-000001e4 output: Puppet has not run in last 20 hours [02:59:26] PROBLEM Puppet freshness is now: CRITICAL on translation-memory-1 i-0000013a output: Puppet has not run in last 20 hours [02:59:27] PROBLEM Puppet freshness is now: CRITICAL on vivek-puppet i-000000ca output: Puppet has not run in last 20 hours [03:00:15] PROBLEM Puppet freshness is now: CRITICAL on dumps-4 i-0000017d output: Puppet has not run in last 20 hours [03:00:15] PROBLEM Puppet freshness is now: CRITICAL on incubator-apache i-00000211 output: Puppet has not run in last 20 hours [03:11:57] PROBLEM Current Load is now: WARNING on nagios 127.0.0.1 output: WARNING - load average: 5.63, 5.47, 3.36 [03:21:31] 05/17/2012 - 03:21:31 - Updating keys for laner at /export/home/deployment-prep/laner [03:35:30] Ryan_Lane: how often do you update your keys? [03:35:35] or is this a bug [03:35:40] it's a bug [03:35:51] why only for you ? [03:35:55] not sure [03:36:02] need to figure it out [03:36:14] I'm wondering if it has something to do with OATHAuth [03:36:23] though I can't imagine it does [03:36:36] wgOSMRandomlyNagAboutUpdateKeysWhenUserJoinsIrc = array( 'laner' ); ? [03:36:48] heh [03:36:59] it was right before you joined [03:37:03] 05/17/2012 - 03:21:31 - Updating keys for laner at /export/home/deployment-prep/laner [03:37:15] and an hour before that as well [03:39:47] there must be something screwed up with my account in ldap [03:42:12] or with the script [03:42:18] I could be computing timestamps poorly [03:42:59] PROBLEM Free ram is now: WARNING on test-oneiric i-00000187 output: Warning: 14% free memory [03:43:14] still weird that it's only happening to me [03:43:20] 05/17/2012 - 03:43:19 - Updating keys for laner at /export/home/deployment-prep/laner [03:43:57] -_- [03:57:58] PROBLEM Free ram is now: CRITICAL on test-oneiric i-00000187 output: Critical: 5% free memory [04:00:29] PROBLEM Free ram is now: WARNING on utils-abogott i-00000131 output: Warning: 15% free memory [04:02:59] RECOVERY Free ram is now: OK on test-oneiric i-00000187 output: OK: 97% free memory [04:08:09] PROBLEM Free ram is now: WARNING on orgcharts-dev i-0000018f output: Warning: 14% free memory [04:10:29] PROBLEM Free ram is now: WARNING on nova-daas-1 i-000000e7 output: Warning: 15% free memory [04:20:39] PROBLEM Free ram is now: CRITICAL on utils-abogott i-00000131 output: Critical: 3% free memory [04:22:40] PROBLEM dpkg-check is now: CRITICAL on nova-daas-1 i-000000e7 output: CHECK_NRPE: Socket timeout after 10 seconds. [04:25:32] RECOVERY Free ram is now: OK on utils-abogott i-00000131 output: OK: 96% free memory [04:27:35] RECOVERY dpkg-check is now: OK on nova-daas-1 i-000000e7 output: All packages OK [04:28:15] PROBLEM Free ram is now: CRITICAL on orgcharts-dev i-0000018f output: Critical: 4% free memory [04:33:12] RECOVERY Free ram is now: OK on orgcharts-dev i-0000018f output: OK: 95% free memory [04:35:31] PROBLEM Free ram is now: CRITICAL on nova-daas-1 i-000000e7 output: Critical: 5% free memory [04:45:31] RECOVERY Free ram is now: OK on nova-daas-1 i-000000e7 output: OK: 94% free memory [04:49:16] PROBLEM Puppet freshness is now: CRITICAL on deployment-syslog i-00000269 output: Puppet has not run in last 20 hours [05:38:51] MySQL error: 1146: Table 'enwiki.pagetriage_page' doesn't exist (deployment-sql) [05:38:52] oh yeah [05:38:53] ;) [06:05:34] PROBLEM Disk Space is now: WARNING on nova-production1 i-0000007b output: DISK WARNING - free space: / 573 MB (5% inode=80%): [06:43:13] RECOVERY Disk Space is now: OK on nova-production1 i-0000007b output: DISK OK [06:47:21] !log labs died ;-D Veryyyy high I/O latency [06:47:21] labs is not a valid project. [06:47:24] !log [06:47:27] !help log [06:47:28] !documentation for labs !wm-bot for bot [06:47:38] !wm-bot [06:47:38] http://meta.wikimedia.org/wiki/WM-Bot [06:47:49] !help [06:47:49] !documentation for labs !wm-bot for bot [06:49:04] yeah, labs died [06:49:17] I did a :wq on a vi of mine and I'm waiting for like 10 minutes now [06:49:38] 06:49:28 up 16 days, 5:43, 2 users, load average: 482.89, 353.14, 203.70 [06:49:42] "yay" [06:52:34] PROBLEM Current Load is now: CRITICAL on nagios 127.0.0.1 output: CRITICAL - load average: 13.00, 12.54, 7.83 [06:53:35] PROBLEM Free ram is now: CRITICAL on bots-2 i-0000009c output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:00] PROBLEM dpkg-check is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:20] PROBLEM Disk Space is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:20] PROBLEM Total Processes is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:25] PROBLEM dpkg-check is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:25] PROBLEM Current Load is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:26] PROBLEM Total Processes is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:30] PROBLEM Free ram is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:31] PROBLEM Free ram is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:31] PROBLEM dpkg-check is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:32] PROBLEM Current Load is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:32] PROBLEM Current Users is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:54:32] PROBLEM Free ram is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:56:50] PROBLEM Current Load is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:56:50] PROBLEM Current Users is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:56:50] PROBLEM Disk Space is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:56:50] PROBLEM Total Processes is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:56:55] PROBLEM Disk Space is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:23] PROBLEM Current Load is now: WARNING on rds i-00000207 output: WARNING - load average: 4.77, 7.40, 5.26 [06:57:24] PROBLEM Disk Space is now: CRITICAL on labs-lvs1 i-00000057 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:24] PROBLEM Disk Space is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:24] PROBLEM Free ram is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:24] PROBLEM Current Load is now: CRITICAL on labs-lvs1 i-00000057 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:24] PROBLEM Total Processes is now: CRITICAL on labs-lvs1 i-00000057 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:34] PROBLEM Free ram is now: CRITICAL on labs-lvs1 i-00000057 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:34] PROBLEM dpkg-check is now: CRITICAL on labs-lvs1 i-00000057 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:57:34] PROBLEM Current Users is now: CRITICAL on labs-lvs1 i-00000057 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:58:15] PROBLEM Free ram is now: WARNING on bots-2 i-0000009c output: Warning: 17% free memory [06:58:45] PROBLEM Current Users is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [06:59:10] RECOVERY Disk Space is now: OK on precise-test i-00000231 output: DISK OK [06:59:10] RECOVERY Total Processes is now: OK on precise-test i-00000231 output: PROCS OK: 82 processes [06:59:15] PROBLEM Current Load is now: WARNING on incubator-bot1 i-00000251 output: WARNING - load average: 7.32, 8.45, 6.45 [06:59:15] RECOVERY dpkg-check is now: OK on precise-test i-00000231 output: All packages OK [06:59:15] RECOVERY Free ram is now: OK on precise-test i-00000231 output: OK: 86% free memory [06:59:15] RECOVERY Current Load is now: OK on precise-test i-00000231 output: OK - load average: 3.57, 5.10, 4.19 [07:01:44] PROBLEM Current Load is now: WARNING on mobile-testing i-00000271 output: WARNING - load average: 9.16, 8.23, 5.91 [07:01:59] RECOVERY Disk Space is now: OK on labs-lvs1 i-00000057 output: DISK OK [07:01:59] RECOVERY Free ram is now: OK on incubator-bot1 i-00000251 output: OK: 69% free memory [07:01:59] RECOVERY Current Load is now: OK on labs-lvs1 i-00000057 output: OK - load average: 2.23, 4.23, 3.56 [07:01:59] RECOVERY Total Processes is now: OK on labs-lvs1 i-00000057 output: PROCS OK: 78 processes [07:02:04] RECOVERY Disk Space is now: OK on incubator-bot1 i-00000251 output: DISK OK [07:02:04] RECOVERY Free ram is now: OK on labs-lvs1 i-00000057 output: OK: 91% free memory [07:02:05] RECOVERY Current Users is now: OK on labs-lvs1 i-00000057 output: USERS OK - 0 users currently logged in [07:02:05] RECOVERY dpkg-check is now: OK on labs-lvs1 i-00000057 output: All packages OK [07:02:09] PROBLEM Current Load is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:07:33] RECOVERY dpkg-check is now: OK on migration1 i-00000261 output: All packages OK [07:07:33] RECOVERY Free ram is now: OK on migration1 i-00000261 output: OK: 84% free memory [07:07:33] RECOVERY Total Processes is now: OK on rds i-00000207 output: PROCS OK: 76 processes [07:07:38] RECOVERY Current Users is now: OK on rds i-00000207 output: USERS OK - 0 users currently logged in [07:07:38] RECOVERY Free ram is now: OK on rds i-00000207 output: OK: 94% free memory [07:07:43] PROBLEM Current Load is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:08:30] PROBLEM HTTP is now: CRITICAL on deployment-web3 i-00000219 output: CRITICAL - Socket timeout after 10 seconds [07:08:31] RECOVERY Disk Space is now: OK on rds i-00000207 output: DISK OK [07:08:31] PROBLEM Current Load is now: WARNING on rds i-00000207 output: WARNING - load average: 0.88, 4.66, 5.37 [07:08:31] RECOVERY Current Load is now: OK on migration1 i-00000261 output: OK - load average: 0.27, 1.91, 3.30 [07:08:31] RECOVERY Current Users is now: OK on migration1 i-00000261 output: USERS OK - 0 users currently logged in [07:08:31] RECOVERY Disk Space is now: OK on migration1 i-00000261 output: DISK OK [07:08:31] RECOVERY Total Processes is now: OK on migration1 i-00000261 output: PROCS OK: 83 processes [07:08:36] PROBLEM Current Load is now: CRITICAL on gluster-devstack i-00000274 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:08:36] PROBLEM dpkg-check is now: CRITICAL on gluster-devstack i-00000274 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:09:05] PROBLEM Current Users is now: CRITICAL on gluster-devstack i-00000274 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:10:29] PROBLEM Current Load is now: CRITICAL on mobile-testing i-00000271 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:11:19] PROBLEM HTTP is now: WARNING on deployment-web3 i-00000219 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.014 second response time [07:13:06] PROBLEM Total Processes is now: CRITICAL on worker1 i-00000208 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:13:11] PROBLEM Disk Space is now: CRITICAL on worker1 i-00000208 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:13:11] PROBLEM Current Users is now: CRITICAL on worker1 i-00000208 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:13:11] PROBLEM Current Load is now: CRITICAL on worker1 i-00000208 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:13:11] PROBLEM Free ram is now: CRITICAL on upload-wizard i-0000021c output: CHECK_NRPE: Socket timeout after 10 seconds. [07:13:11] PROBLEM Free ram is now: CRITICAL on worker1 i-00000208 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:14:15] PROBLEM Current Load is now: WARNING on deployment-transcoding i-00000105 output: WARNING - load average: 6.56, 10.05, 6.83 [07:15:44] PROBLEM Disk Space is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:16:05] PROBLEM Free ram is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:16:09] "fun" [07:18:12] RECOVERY Disk Space is now: OK on worker1 i-00000208 output: DISK OK [07:18:12] RECOVERY Total Processes is now: OK on worker1 i-00000208 output: PROCS OK: 76 processes [07:18:17] RECOVERY Current Users is now: OK on worker1 i-00000208 output: USERS OK - 0 users currently logged in [07:18:17] PROBLEM Current Load is now: WARNING on worker1 i-00000208 output: WARNING - load average: 3.64, 6.09, 6.11 [07:18:17] RECOVERY Free ram is now: OK on worker1 i-00000208 output: OK: 94% free memory [07:18:22] PROBLEM Current Load is now: CRITICAL on incubator-bot2 i-00000252 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:00] PROBLEM HTTP is now: CRITICAL on deployment-web4 i-00000214 output: CRITICAL - Socket timeout after 10 seconds [07:20:00] PROBLEM HTTP is now: CRITICAL on deployment-web5 i-00000213 output: CRITICAL - Socket timeout after 10 seconds [07:20:19] PROBLEM HTTP is now: CRITICAL on deployment-web i-00000217 output: CRITICAL - Socket timeout after 10 seconds [07:20:37] PROBLEM Current Users is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:37] PROBLEM Disk Space is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:37] PROBLEM Total Processes is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:42] PROBLEM dpkg-check is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:42] PROBLEM Current Load is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:42] PROBLEM Free ram is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:48] PROBLEM Current Users is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:48] PROBLEM Total Processes is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:20:48] PROBLEM Free ram is now: CRITICAL on rds i-00000207 output: CHECK_NRPE: Socket timeout after 10 seconds. [07:21:51] RECOVERY Current Users is now: OK on incubator-bot1 i-00000251 output: USERS OK - 0 users currently logged in [07:21:51] RECOVERY dpkg-check is now: OK on incubator-bot1 i-00000251 output: All packages OK [07:22:40] RECOVERY Current Load is now: OK on worker1 i-00000208 output: OK - load average: 0.08, 2.35, 4.48 [07:22:40] RECOVERY Current Load is now: OK on incubator-bot2 i-00000252 output: OK - load average: 0.42, 2.85, 4.02 [07:22:40] RECOVERY Free ram is now: OK on upload-wizard i-0000021c output: OK: 94% free memory [07:23:48] PROBLEM HTTP is now: WARNING on deployment-web4 i-00000214 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.017 second response time [07:23:48] PROBLEM HTTP is now: WARNING on deployment-web5 i-00000213 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.017 second response time [07:23:48] PROBLEM HTTP is now: WARNING on deployment-web i-00000217 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.017 second response time [07:25:25] RECOVERY Current Users is now: OK on precise-test i-00000231 output: USERS OK - 0 users currently logged in [07:28:47] RECOVERY Current Load is now: OK on deployment-transcoding i-00000105 output: OK - load average: 0.05, 1.33, 3.66 [07:29:35] PROBLEM Puppet freshness is now: CRITICAL on nova-ldap1 i-000000df output: Puppet has not run in last 20 hours [07:46:12] PROBLEM Current Load is now: WARNING on nagios 127.0.0.1 output: WARNING - load average: 0.71, 1.25, 3.93 [07:56:11] RECOVERY Current Load is now: OK on nagios 127.0.0.1 output: OK - load average: 0.87, 1.11, 2.53 [08:15:12] !log WMFLabs seems to have recovered now [08:15:13] WMFLabs is not a valid project. [08:25:12] o.o [08:25:21] morning hashar [08:25:24] :P [08:25:28] hello :) [08:26:21] hi petan|wk [08:26:26] which tz are you in anyway? [08:29:09] GMT [08:29:53] er, are you sure about that? :) [08:30:04] you probably aren't [08:33:46] paravoid: really? [08:33:55] where do you live? [08:33:58] europe [08:35:23] europe has many timezones [08:35:30] right this one has GMT+1 [08:35:33] that's like GMT [08:35:34] but very few countries are on GMT during summer time [08:35:46] ok right now I have 10:35 [08:35:47] right :-) [08:36:04] ok, so WEST [08:36:08] :-) [08:36:10] probably [08:36:32] I am in good tz to bother hashar whole day [08:36:59] 10:37 here [08:37:01] GMT + 2 [08:37:03] CET ? [08:37:09] oh, right, wo you're in CEST [08:37:11] not WEST [08:37:21] !hashar is [10:15:12] !log WMFLabs seems to have recovered now [08:37:25] Key was added! [08:37:26] you don't observe GMT even during winter [08:37:30] !ping [08:37:30] pong [08:37:52] WEST is probably portugal [08:38:04] yes [08:38:07] and WEST = BST [08:38:11] which is the UK too [09:11:46] PROBLEM Disk Space is now: WARNING on nova-production1 i-0000007b output: DISK WARNING - free space: / 573 MB (5% inode=80%): [09:29:02] !ping [09:29:02] pong [09:43:14] !log deployment-prep hashar: removed Draft extension for now. [09:43:16] Logged the message, Master [09:48:16] going to love that error [09:48:16] Exception thrown without a stack frame in Unknown on line 0 [09:48:18] \o/ [10:15:21] !log deployment-prep hashar: Fixed cluster which was giving blank page. Root cause was wmfUdp2logDest which must be (aka not use a hostname [10:15:22] Logged the message, Master [10:20:09] !log deployment-prep hashar: Fixed filerepo backend by using chown -R www-data:depops /mnt/export/upload6/wikibooks [10:20:10] Logged the message, Master [10:29:22] !log deployment-prep hashar: afterall, made /mnt/export/upload6 to be world writable "sudo chmod -R 777 *" [10:29:23] Logged the message, Master [10:48:51] RECOVERY Disk Space is now: OK on deployment-transcoding i-00000105 output: DISK OK [11:34:33] PROBLEM Puppet freshness is now: CRITICAL on hugglewiki i-000000aa output: Puppet has not run in last 20 hours [11:35:33] PROBLEM Puppet freshness is now: CRITICAL on wikistream-1 i-0000016e output: Puppet has not run in last 20 hours [11:46:42] PROBLEM Puppet freshness is now: CRITICAL on migration1 i-00000261 output: Puppet has not run in last 20 hours [12:00:36] PROBLEM Puppet freshness is now: CRITICAL on memcache-puppet i-00000153 output: Puppet has not run in last 20 hours [12:04:36] PROBLEM Puppet freshness is now: CRITICAL on jenkins2 i-00000102 output: Puppet has not run in last 20 hours [12:04:36] PROBLEM Puppet freshness is now: CRITICAL on publicdata-administration i-0000019e output: Puppet has not run in last 20 hours [12:04:36] PROBLEM Puppet freshness is now: CRITICAL on resourceloader2-apache i-000001d7 output: Puppet has not run in last 20 hours [12:05:36] PROBLEM Puppet freshness is now: CRITICAL on dumps-6 i-00000266 output: Puppet has not run in last 20 hours [12:05:36] PROBLEM Puppet freshness is now: CRITICAL on labs-nfs1 i-0000005d output: Puppet has not run in last 20 hours [12:05:36] PROBLEM Puppet freshness is now: CRITICAL on mailman-01 i-00000235 output: Puppet has not run in last 20 hours [12:05:36] PROBLEM Puppet freshness is now: CRITICAL on swift-be3 i-000001c9 output: Puppet has not run in last 20 hours [12:05:36] PROBLEM Puppet freshness is now: CRITICAL on wikidata-dev-3 i-00000225 output: Puppet has not run in last 20 hours [12:06:36] PROBLEM Puppet freshness is now: CRITICAL on wep i-000000c2 output: Puppet has not run in last 20 hours [12:07:41] PROBLEM Puppet freshness is now: CRITICAL on deployment-thumbproxy i-0000026b output: Puppet has not run in last 20 hours [12:07:41] PROBLEM Puppet freshness is now: CRITICAL on gerrit i-000000ff output: Puppet has not run in last 20 hours [12:07:41] PROBLEM Puppet freshness is now: CRITICAL on gluster-devstack i-00000274 output: Puppet has not run in last 20 hours [12:07:41] PROBLEM Puppet freshness is now: CRITICAL on shop-analytics-main i-000001e6 output: Puppet has not run in last 20 hours [12:07:41] PROBLEM Puppet freshness is now: CRITICAL on wikistats-01 i-00000042 output: Puppet has not run in last 20 hours [12:07:41] PROBLEM Puppet freshness is now: CRITICAL on worker1 i-00000208 output: Puppet has not run in last 20 hours [12:08:41] PROBLEM Puppet freshness is now: CRITICAL on bots-apache1 i-000000b0 output: Puppet has not run in last 20 hours [12:08:41] PROBLEM Puppet freshness is now: CRITICAL on deployment-web3 i-00000219 output: Puppet has not run in last 20 hours [12:08:41] PROBLEM Puppet freshness is now: CRITICAL on dumps-2 i-00000257 output: Puppet has not run in last 20 hours [12:08:41] PROBLEM Puppet freshness is now: CRITICAL on precise-test i-00000231 output: Puppet has not run in last 20 hours [12:09:41] PROBLEM Puppet freshness is now: CRITICAL on swift-be2 i-000001c8 output: Puppet has not run in last 20 hours [12:10:41] PROBLEM Puppet freshness is now: CRITICAL on building i-0000014d output: Puppet has not run in last 20 hours [12:10:41] PROBLEM Puppet freshness is now: CRITICAL on deployment-backup i-000000f8 output: Puppet has not run in last 20 hours [12:12:41] PROBLEM Puppet freshness is now: CRITICAL on aggregator-test2 i-0000024e output: Puppet has not run in last 20 hours [12:12:41] PROBLEM Puppet freshness is now: CRITICAL on reportcard2 i-000001ea output: Puppet has not run in last 20 hours [12:13:41] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache22 i-0000026f output: Puppet has not run in last 20 hours [12:13:41] PROBLEM Puppet freshness is now: CRITICAL on dumps-1 i-00000170 output: Puppet has not run in last 20 hours [12:13:41] PROBLEM Puppet freshness is now: CRITICAL on webserver-lcarr i-00000134 output: Puppet has not run in last 20 hours [12:15:11] RECOVERY Puppet freshness is now: OK on en-wiki-db-precise i-0000023c output: puppet ran at Thu May 17 12:14:51 UTC 2012 [12:15:21] RECOVERY Puppet freshness is now: OK on pediapress-ocg2 i-00000234 output: puppet ran at Thu May 17 12:15:14 UTC 2012 [12:15:21] RECOVERY Puppet freshness is now: OK on varnish i-000001ac output: puppet ran at Thu May 17 12:15:14 UTC 2012 [12:15:30] !log nagios - started snmptrapd [12:15:52] Logged the message, Master [12:15:58] RECOVERY Puppet freshness is now: OK on bots-1 i-000000a9 output: puppet ran at Thu May 17 12:15:24 UTC 2012 [12:15:58] RECOVERY Puppet freshness is now: OK on ve-nodejs i-00000245 output: puppet ran at Thu May 17 12:15:54 UTC 2012 [12:16:04] PROBLEM Puppet freshness is now: CRITICAL on bots-4 i-000000e8 output: Puppet has not run in last 20 hours [12:16:04] PROBLEM Puppet freshness is now: CRITICAL on bots-cb i-0000009e output: Puppet has not run in last 20 hours [12:16:04] PROBLEM Puppet freshness is now: CRITICAL on ganglia-collector i-000000b7 output: Puppet has not run in last 20 hours [12:16:04] PROBLEM Puppet freshness is now: CRITICAL on hugglewa-db i-00000188 output: Puppet has not run in last 20 hours [12:16:04] PROBLEM Puppet freshness is now: CRITICAL on swift-be4 i-000001ca output: Puppet has not run in last 20 hours [12:16:04] PROBLEM Puppet freshness is now: CRITICAL on wikisource-web i-000000fe output: Puppet has not run in last 20 hours [12:16:14] RECOVERY Puppet freshness is now: OK on venus i-000000ea output: puppet ran at Thu May 17 12:16:06 UTC 2012 [12:16:34] RECOVERY Puppet freshness is now: OK on maps-test2 i-00000253 output: puppet ran at Thu May 17 12:16:18 UTC 2012 [12:16:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache20 i-0000026c output: Puppet has not run in last 20 hours [12:16:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-transcoding i-00000105 output: Puppet has not run in last 20 hours [12:16:34] PROBLEM Puppet freshness is now: CRITICAL on incubator-bot1 i-00000251 output: Puppet has not run in last 20 hours [12:16:44] RECOVERY Puppet freshness is now: OK on kripke i-00000268 output: puppet ran at Thu May 17 12:16:34 UTC 2012 [12:16:44] RECOVERY Puppet freshness is now: OK on dumps-6 i-00000266 output: puppet ran at Thu May 17 12:16:40 UTC 2012 [12:17:04] RECOVERY Puppet freshness is now: OK on swift-be2 i-000001c8 output: puppet ran at Thu May 17 12:17:02 UTC 2012 [12:17:34] RECOVERY Puppet freshness is now: OK on deployment-webs1 i-0000012a output: puppet ran at Thu May 17 12:17:12 UTC 2012 [12:17:34] RECOVERY Puppet freshness is now: OK on deployment-backup i-000000f8 output: puppet ran at Thu May 17 12:17:15 UTC 2012 [12:17:34] RECOVERY Puppet freshness is now: OK on wikidata-dev-1 i-0000020c output: puppet ran at Thu May 17 12:17:18 UTC 2012 [12:17:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-cache-upload i-00000263 output: Puppet has not run in last 20 hours [12:17:34] PROBLEM Puppet freshness is now: CRITICAL on php5builds i-00000192 output: Puppet has not run in last 20 hours [12:17:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-dbdump i-000000d2 output: Puppet has not run in last 20 hours [12:17:44] RECOVERY Puppet freshness is now: OK on publicdata-administration i-0000019e output: puppet ran at Thu May 17 12:17:27 UTC 2012 [12:17:44] RECOVERY Puppet freshness is now: OK on ee-prototype i-0000013d output: puppet ran at Thu May 17 12:17:27 UTC 2012 [12:17:44] RECOVERY Puppet freshness is now: OK on bots-cb i-0000009e output: puppet ran at Thu May 17 12:17:30 UTC 2012 [12:17:44] RECOVERY Puppet freshness is now: OK on deployment-squid i-000000dc output: puppet ran at Thu May 17 12:17:31 UTC 2012 [12:17:44] RECOVERY Puppet freshness is now: OK on deployment-apache23 i-00000270 output: puppet ran at Thu May 17 12:17:35 UTC 2012 [12:18:14] RECOVERY Puppet freshness is now: OK on dev-solr i-00000152 output: puppet ran at Thu May 17 12:18:04 UTC 2012 [12:18:24] RECOVERY Puppet freshness is now: OK on demo-web1 i-00000255 output: puppet ran at Thu May 17 12:18:12 UTC 2012 [12:18:24] RECOVERY Puppet freshness is now: OK on deployment-web3 i-00000219 output: puppet ran at Thu May 17 12:18:12 UTC 2012 [12:18:26] hmm? [12:18:34] RECOVERY Puppet freshness is now: OK on dumps-1 i-00000170 output: puppet ran at Thu May 17 12:18:15 UTC 2012 [12:18:34] RECOVERY Puppet freshness is now: OK on dumps-4 i-0000017d output: puppet ran at Thu May 17 12:18:17 UTC 2012 [12:18:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-feed i-00000118 output: Puppet has not run in last 20 hours [12:18:34] PROBLEM Puppet freshness is now: CRITICAL on incubator-bot2 i-00000252 output: Puppet has not run in last 20 hours [12:18:34] PROBLEM Puppet freshness is now: CRITICAL on robh2 i-000001a2 output: Puppet has not run in last 20 hours [12:19:04] RECOVERY Puppet freshness is now: OK on dumps-3 i-0000017c output: puppet ran at Thu May 17 12:18:42 UTC 2012 [12:19:34] PROBLEM Puppet freshness is now: CRITICAL on bots-sql1 i-000000b5 output: Puppet has not run in last 20 hours [12:19:34] PROBLEM Puppet freshness is now: CRITICAL on cn-wiki-db-lucid i-00000241 output: Puppet has not run in last 20 hours [12:19:34] PROBLEM Puppet freshness is now: CRITICAL on firstinstance i-0000013e output: Puppet has not run in last 20 hours [12:19:34] PROBLEM Puppet freshness is now: CRITICAL on localpuppet1 i-0000020b output: Puppet has not run in last 20 hours [12:19:44] RECOVERY Puppet freshness is now: OK on demo-deployment1 i-00000276 output: puppet ran at Thu May 17 12:19:33 UTC 2012 [12:20:05] RECOVERY Puppet freshness is now: OK on bastion1 i-000000ba output: puppet ran at Thu May 17 12:19:52 UTC 2012 [12:20:18] RECOVERY Puppet freshness is now: OK on shop-analytics-main i-000001e6 output: puppet ran at Thu May 17 12:20:05 UTC 2012 [12:20:18] RECOVERY Puppet freshness is now: OK on ganglia-test2 i-00000250 output: puppet ran at Thu May 17 12:20:07 UTC 2012 [12:20:34] RECOVERY Puppet freshness is now: OK on resourceloader2-apache i-000001d7 output: puppet ran at Thu May 17 12:20:24 UTC 2012 [12:20:34] RECOVERY Puppet freshness is now: OK on nova-precise1 i-00000236 output: puppet ran at Thu May 17 12:20:24 UTC 2012 [12:20:34] PROBLEM Puppet freshness is now: CRITICAL on bots-sql2 i-000000af output: Puppet has not run in last 20 hours [12:20:34] PROBLEM Puppet freshness is now: CRITICAL on mobile-testing i-00000271 output: Puppet has not run in last 20 hours [12:20:34] PROBLEM Puppet freshness is now: CRITICAL on swift-fe1 i-000001d2 output: Puppet has not run in last 20 hours [12:21:04] RECOVERY Puppet freshness is now: OK on deployment-thumbproxy i-0000026b output: puppet ran at Thu May 17 12:20:44 UTC 2012 [12:21:04] RECOVERY Puppet freshness is now: OK on deployment-apache21 i-0000026d output: puppet ran at Thu May 17 12:20:50 UTC 2012 [12:21:04] RECOVERY Puppet freshness is now: OK on outreacheval i-0000012e output: puppet ran at Thu May 17 12:20:56 UTC 2012 [12:21:38] RECOVERY Puppet freshness is now: OK on swift-aux1 i-0000024b output: puppet ran at Thu May 17 12:21:22 UTC 2012 [12:22:14] RECOVERY Puppet freshness is now: OK on hugglewa-db i-00000188 output: puppet ran at Thu May 17 12:21:58 UTC 2012 [12:22:14] RECOVERY Puppet freshness is now: OK on swift-fe1 i-000001d2 output: puppet ran at Thu May 17 12:21:59 UTC 2012 [12:22:14] RECOVERY Puppet freshness is now: OK on cn-wiki-db-lucid i-00000241 output: puppet ran at Thu May 17 12:22:03 UTC 2012 [12:22:14] RECOVERY Puppet freshness is now: OK on swift-be4 i-000001ca output: puppet ran at Thu May 17 12:22:05 UTC 2012 [12:22:14] RECOVERY Puppet freshness is now: OK on deployment-apache20 i-0000026c output: puppet ran at Thu May 17 12:22:07 UTC 2012 [12:22:24] RECOVERY Puppet freshness is now: OK on incubator-bot1 i-00000251 output: puppet ran at Thu May 17 12:22:12 UTC 2012 [12:22:34] PROBLEM Puppet freshness is now: CRITICAL on nginx-dev1 i-000000f0 output: Puppet has not run in last 20 hours [12:22:34] PROBLEM Puppet freshness is now: CRITICAL on secondinstance i-0000015b output: Puppet has not run in last 20 hours [12:22:34] PROBLEM Puppet freshness is now: CRITICAL on test2 i-0000013c output: Puppet has not run in last 20 hours [12:22:44] RECOVERY Puppet freshness is now: OK on fundraising-db i-0000015c output: puppet ran at Thu May 17 12:22:28 UTC 2012 [12:22:50] found it [12:23:14] RECOVERY Puppet freshness is now: OK on bots-sql3 i-000000b4 output: puppet ran at Thu May 17 12:23:11 UTC 2012 [12:23:44] RECOVERY Puppet freshness is now: OK on upload-wizard i-0000021c output: puppet ran at Thu May 17 12:23:28 UTC 2012 [12:23:44] RECOVERY Puppet freshness is now: OK on mailman-01 i-00000235 output: puppet ran at Thu May 17 12:23:32 UTC 2012 [12:24:04] RECOVERY Puppet freshness is now: OK on swift-aux2 i-0000024c output: puppet ran at Thu May 17 12:23:54 UTC 2012 [12:24:14] RECOVERY Puppet freshness is now: OK on incubator-apache i-00000211 output: puppet ran at Thu May 17 12:23:57 UTC 2012 [12:24:14] RECOVERY Puppet freshness is now: OK on testing-groupchange i-00000205 output: puppet ran at Thu May 17 12:24:05 UTC 2012 [12:24:14] RECOVERY Puppet freshness is now: OK on bastion-restricted1 i-0000019b output: puppet ran at Thu May 17 12:24:05 UTC 2012 [12:24:14] RECOVERY Puppet freshness is now: OK on ganglia-test3 i-0000025b output: puppet ran at Thu May 17 12:24:09 UTC 2012 [12:24:54] RECOVERY Puppet freshness is now: OK on fundraising-civicrm i-00000169 output: puppet ran at Thu May 17 12:24:31 UTC 2012 [12:24:54] RECOVERY Puppet freshness is now: OK on labs-relay i-00000103 output: puppet ran at Thu May 17 12:24:52 UTC 2012 [12:24:54] RECOVERY Puppet freshness is now: OK on catsort-pub i-000001cc output: puppet ran at Thu May 17 12:24:53 UTC 2012 [12:25:34] RECOVERY Puppet freshness is now: OK on wikistats-01 i-00000042 output: puppet ran at Thu May 17 12:25:17 UTC 2012 [12:25:34] RECOVERY Puppet freshness is now: OK on memcache-puppet i-00000153 output: puppet ran at Thu May 17 12:25:22 UTC 2012 [12:25:44] RECOVERY Puppet freshness is now: OK on bots-sql1 i-000000b5 output: puppet ran at Thu May 17 12:25:31 UTC 2012 [12:25:59] New patchset: Faidon; "Fix a silly syntax error (dependency on a class)" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7853 [12:26:04] RECOVERY Puppet freshness is now: OK on reportcard2 i-000001ea output: puppet ran at Thu May 17 12:25:46 UTC 2012 [12:26:14] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/7853 [12:26:14] RECOVERY Puppet freshness is now: OK on deployment-web5 i-00000213 output: puppet ran at Thu May 17 12:25:58 UTC 2012 [12:26:14] RECOVERY Puppet freshness is now: OK on gluster-devstack i-00000274 output: puppet ran at Thu May 17 12:26:00 UTC 2012 [12:26:26] New review: Faidon; "(no comment)" [operations/puppet] (test); V: 0 C: 2; - https://gerrit.wikimedia.org/r/7853 [12:26:29] Change merged: Faidon; [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7853 [12:26:34] RECOVERY Puppet freshness is now: OK on aggregator-test i-0000024d output: puppet ran at Thu May 17 12:26:20 UTC 2012 [12:26:44] RECOVERY Puppet freshness is now: OK on nginx-ffuqua-doom1-3 i-00000196 output: puppet ran at Thu May 17 12:26:30 UTC 2012 [12:27:11] fix pusehd [12:27:14] pushed even [12:27:14] RECOVERY Puppet freshness is now: OK on pageviews i-000000b2 output: puppet ran at Thu May 17 12:26:57 UTC 2012 [12:27:35] RECOVERY Puppet freshness is now: OK on deployment-transcoding i-00000105 output: puppet ran at Thu May 17 12:27:26 UTC 2012 [12:27:44] RECOVERY Puppet freshness is now: OK on exim-test i-00000265 output: puppet ran at Thu May 17 12:27:29 UTC 2012 [12:27:44] RECOVERY Puppet freshness is now: OK on deployment-cache-bits i-00000264 output: puppet ran at Thu May 17 12:27:33 UTC 2012 [12:28:34] RECOVERY Puppet freshness is now: OK on bots-apache1 i-000000b0 output: puppet ran at Thu May 17 12:28:22 UTC 2012 [12:28:44] RECOVERY Puppet freshness is now: OK on precise-test i-00000231 output: puppet ran at Thu May 17 12:28:29 UTC 2012 [12:28:44] RECOVERY Puppet freshness is now: OK on dumps-8 i-0000026e output: puppet ran at Thu May 17 12:28:31 UTC 2012 [12:28:44] RECOVERY Puppet freshness is now: OK on embed-sandbox i-000000d1 output: puppet ran at Thu May 17 12:28:37 UTC 2012 [12:29:34] RECOVERY Puppet freshness is now: OK on vumi i-000001e5 output: puppet ran at Thu May 17 12:29:12 UTC 2012 [12:29:34] RECOVERY Puppet freshness is now: OK on secondinstance i-0000015b output: puppet ran at Thu May 17 12:29:22 UTC 2012 [12:29:34] RECOVERY Puppet freshness is now: OK on rds i-00000207 output: puppet ran at Thu May 17 12:29:25 UTC 2012 [12:29:44] RECOVERY Puppet freshness is now: OK on patchtest i-000000f1 output: puppet ran at Thu May 17 12:29:39 UTC 2012 [12:29:54] RECOVERY Puppet freshness is now: OK on robh2 i-000001a2 output: puppet ran at Thu May 17 12:29:42 UTC 2012 [12:30:11] RECOVERY Puppet freshness is now: OK on grail i-0000021e output: puppet ran at Thu May 17 12:29:48 UTC 2012 [12:30:14] RECOVERY Puppet freshness is now: OK on ganglia-collector i-000000b7 output: puppet ran at Thu May 17 12:29:57 UTC 2012 [12:30:14] RECOVERY Puppet freshness is now: OK on aggregator1 i-0000010c output: puppet ran at Thu May 17 12:30:10 UTC 2012 [12:30:34] RECOVERY Puppet freshness is now: OK on demo-mysql1 i-00000256 output: puppet ran at Thu May 17 12:30:26 UTC 2012 [12:30:34] PROBLEM Puppet freshness is now: CRITICAL on feeds i-000000fa output: Puppet has not run in last 20 hours [12:30:44] RECOVERY Puppet freshness is now: OK on localpuppet1 i-0000020b output: puppet ran at Thu May 17 12:30:30 UTC 2012 [12:30:44] RECOVERY Puppet freshness is now: OK on bots-sql2 i-000000af output: puppet ran at Thu May 17 12:30:31 UTC 2012 [12:31:04] RECOVERY Puppet freshness is now: OK on log1 i-00000239 output: puppet ran at Thu May 17 12:30:47 UTC 2012 [12:31:04] RECOVERY Puppet freshness is now: OK on labs-nfs1 i-0000005d output: puppet ran at Thu May 17 12:30:49 UTC 2012 [12:31:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-nfs-memc i-000000d7 output: Puppet has not run in last 20 hours [12:31:34] PROBLEM Puppet freshness is now: CRITICAL on nova-production1 i-0000007b output: Puppet has not run in last 20 hours [12:31:34] PROBLEM Puppet freshness is now: CRITICAL on udp-filter i-000001df output: Puppet has not run in last 20 hours [12:31:44] RECOVERY Puppet freshness is now: OK on jenkins2 i-00000102 output: puppet ran at Thu May 17 12:31:29 UTC 2012 [12:32:14] RECOVERY Puppet freshness is now: OK on deployment-dbdump i-000000d2 output: puppet ran at Thu May 17 12:32:08 UTC 2012 [12:32:14] RECOVERY Puppet freshness is now: OK on bots-dev i-00000190 output: puppet ran at Thu May 17 12:32:09 UTC 2012 [12:32:34] RECOVERY Puppet freshness is now: OK on migration1 i-00000261 output: puppet ran at Thu May 17 12:32:15 UTC 2012 [12:32:34] RECOVERY Puppet freshness is now: OK on mobile-testing i-00000271 output: puppet ran at Thu May 17 12:32:21 UTC 2012 [12:32:34] PROBLEM Puppet freshness is now: CRITICAL on bots-2 i-0000009c output: Puppet has not run in last 20 hours [12:32:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-imagescaler01 i-0000025a output: Puppet has not run in last 20 hours [12:32:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-mc i-0000021b output: Puppet has not run in last 20 hours [12:32:34] PROBLEM Puppet freshness is now: CRITICAL on fr-wiki-db-precise i-0000023e output: Puppet has not run in last 20 hours [12:32:44] RECOVERY Puppet freshness is now: OK on gerrit i-000000ff output: puppet ran at Thu May 17 12:32:34 UTC 2012 [12:32:44] RECOVERY Puppet freshness is now: OK on otrs-jgreen i-0000015a output: puppet ran at Thu May 17 12:32:39 UTC 2012 [12:33:14] RECOVERY Puppet freshness is now: OK on bots-nfs i-000000b1 output: puppet ran at Thu May 17 12:32:59 UTC 2012 [12:33:14] RECOVERY Puppet freshness is now: OK on building i-0000014d output: puppet ran at Thu May 17 12:33:11 UTC 2012 [12:33:34] PROBLEM Puppet freshness is now: CRITICAL on build-precise1 i-00000273 output: Puppet has not run in last 20 hours [12:33:44] RECOVERY Puppet freshness is now: OK on pediapress-ocg1 i-00000233 output: puppet ran at Thu May 17 12:33:38 UTC 2012 [12:34:04] RECOVERY Puppet freshness is now: OK on bots-3 i-000000e5 output: puppet ran at Thu May 17 12:33:47 UTC 2012 [12:34:34] RECOVERY Puppet freshness is now: OK on udp-filter i-000001df output: puppet ran at Thu May 17 12:34:24 UTC 2012 [12:34:44] RECOVERY Puppet freshness is now: OK on bob i-0000012d output: puppet ran at Thu May 17 12:34:28 UTC 2012 [12:34:44] RECOVERY Puppet freshness is now: OK on php5builds i-00000192 output: puppet ran at Thu May 17 12:34:29 UTC 2012 [12:35:14] RECOVERY Puppet freshness is now: OK on nova-production1 i-0000007b output: puppet ran at Thu May 17 12:35:03 UTC 2012 [12:35:24] RECOVERY Puppet freshness is now: OK on nova-ldap2 i-00000238 output: puppet ran at Thu May 17 12:35:13 UTC 2012 [12:35:34] PROBLEM Puppet freshness is now: CRITICAL on asher1 i-0000003a output: Puppet has not run in last 20 hours [12:35:34] PROBLEM Puppet freshness is now: CRITICAL on dumps-7 i-00000267 output: Puppet has not run in last 20 hours [12:36:04] RECOVERY Puppet freshness is now: OK on asher1 i-0000003a output: puppet ran at Thu May 17 12:35:53 UTC 2012 [12:36:04] RECOVERY Puppet freshness is now: OK on vivek-puppet i-000000ca output: puppet ran at Thu May 17 12:35:54 UTC 2012 [12:36:34] RECOVERY Puppet freshness is now: OK on bots-2 i-0000009c output: puppet ran at Thu May 17 12:36:20 UTC 2012 [12:36:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-web i-00000217 output: Puppet has not run in last 20 hours [12:36:34] PROBLEM Puppet freshness is now: CRITICAL on dumps-5 i-00000258 output: Puppet has not run in last 20 hours [12:37:14] RECOVERY Puppet freshness is now: OK on ubuntu1-pgehres i-000000fb output: puppet ran at Thu May 17 12:37:01 UTC 2012 [12:37:14] RECOVERY Puppet freshness is now: OK on fr-wiki-db-precise i-0000023e output: puppet ran at Thu May 17 12:37:04 UTC 2012 [12:37:44] RECOVERY Puppet freshness is now: OK on nova-essex-test i-000001f9 output: puppet ran at Thu May 17 12:37:30 UTC 2012 [12:37:44] RECOVERY Puppet freshness is now: OK on deployment-sql i-000000d0 output: puppet ran at Thu May 17 12:37:34 UTC 2012 [12:38:04] RECOVERY Puppet freshness is now: OK on bots-labs i-0000015e output: puppet ran at Thu May 17 12:37:53 UTC 2012 [12:38:14] RECOVERY Puppet freshness is now: OK on simplewikt i-00000149 output: puppet ran at Thu May 17 12:37:59 UTC 2012 [12:38:14] RECOVERY Puppet freshness is now: OK on hugglewiki i-000000aa output: puppet ran at Thu May 17 12:38:11 UTC 2012 [12:38:34] RECOVERY Puppet freshness is now: OK on wikistream-1 i-0000016e output: puppet ran at Thu May 17 12:38:16 UTC 2012 [12:38:35] RECOVERY Puppet freshness is now: OK on en-wiki-db-lucid i-0000023b output: puppet ran at Thu May 17 12:38:20 UTC 2012 [12:38:44] RECOVERY Puppet freshness is now: OK on deployment-web4 i-00000214 output: puppet ran at Thu May 17 12:38:30 UTC 2012 [12:38:44] RECOVERY Puppet freshness is now: OK on master i-0000007a output: puppet ran at Thu May 17 12:38:35 UTC 2012 [12:38:54] RECOVERY Puppet freshness is now: OK on test2 i-0000013c output: puppet ran at Thu May 17 12:38:42 UTC 2012 [12:39:04] RECOVERY Puppet freshness is now: OK on wikisource-web i-000000fe output: puppet ran at Thu May 17 12:38:44 UTC 2012 [12:39:04] RECOVERY Puppet freshness is now: OK on aggregator-test2 i-0000024e output: puppet ran at Thu May 17 12:38:44 UTC 2012 [12:39:14] RECOVERY Puppet freshness is now: OK on labs-build1 i-0000006b output: puppet ran at Thu May 17 12:38:57 UTC 2012 [12:39:14] RECOVERY Puppet freshness is now: OK on incubator-bot2 i-00000252 output: puppet ran at Thu May 17 12:39:02 UTC 2012 [12:39:14] RECOVERY Puppet freshness is now: OK on deployment-cache-upload i-00000263 output: puppet ran at Thu May 17 12:39:03 UTC 2012 [12:39:34] RECOVERY Puppet freshness is now: OK on nova-dev3 i-000000e9 output: puppet ran at Thu May 17 12:39:17 UTC 2012 [12:39:34] RECOVERY Puppet freshness is now: OK on build-precise1 i-00000273 output: puppet ran at Thu May 17 12:39:22 UTC 2012 [12:39:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-wmsearch i-000000e1 output: Puppet has not run in last 20 hours [12:39:34] PROBLEM Puppet freshness is now: CRITICAL on opengrok-web i-000001e1 output: Puppet has not run in last 20 hours [12:39:34] PROBLEM Puppet freshness is now: CRITICAL on p-b i-000000ae output: Puppet has not run in last 20 hours [12:40:11] RECOVERY Puppet freshness is now: OK on worker1 i-00000208 output: puppet ran at Thu May 17 12:39:53 UTC 2012 [12:40:34] RECOVERY Puppet freshness is now: OK on deployment-mc i-0000021b output: puppet ran at Thu May 17 12:40:26 UTC 2012 [12:40:34] PROBLEM Puppet freshness is now: CRITICAL on incubator-common i-00000254 output: Puppet has not run in last 20 hours [12:41:04] RECOVERY Puppet freshness is now: OK on vumi-gw1 i-0000008f output: puppet ran at Thu May 17 12:40:45 UTC 2012 [12:42:04] RECOVERY Puppet freshness is now: OK on nginx-dev1 i-000000f0 output: puppet ran at Thu May 17 12:41:49 UTC 2012 [12:42:04] RECOVERY Puppet freshness is now: OK on deployment-nfs-memc i-000000d7 output: puppet ran at Thu May 17 12:41:54 UTC 2012 [12:42:14] RECOVERY Puppet freshness is now: OK on dumps-7 i-00000267 output: puppet ran at Thu May 17 12:41:57 UTC 2012 [12:42:14] RECOVERY Puppet freshness is now: OK on firstinstance i-0000013e output: puppet ran at Thu May 17 12:42:01 UTC 2012 [12:42:14] RECOVERY Puppet freshness is now: OK on labs-realserver i-00000104 output: puppet ran at Thu May 17 12:42:10 UTC 2012 [12:42:24] RECOVERY Puppet freshness is now: OK on webserver-lcarr i-00000134 output: puppet ran at Thu May 17 12:42:12 UTC 2012 [12:42:34] RECOVERY Puppet freshness is now: OK on dumps-5 i-00000258 output: puppet ran at Thu May 17 12:42:18 UTC 2012 [12:42:44] RECOVERY Puppet freshness is now: OK on dumps-2 i-00000257 output: puppet ran at Thu May 17 12:42:27 UTC 2012 [12:43:04] RECOVERY Puppet freshness is now: OK on bots-4 i-000000e8 output: puppet ran at Thu May 17 12:42:45 UTC 2012 [12:43:34] RECOVERY Puppet freshness is now: OK on deployment-web i-00000217 output: puppet ran at Thu May 17 12:43:20 UTC 2012 [12:43:44] RECOVERY Puppet freshness is now: OK on translation-memory-1 i-0000013a output: puppet ran at Thu May 17 12:43:33 UTC 2012 [12:43:44] RECOVERY Puppet freshness is now: OK on pediapress-packager i-000001e4 output: puppet ran at Thu May 17 12:43:41 UTC 2012 [12:44:04] RECOVERY Puppet freshness is now: OK on swift-be3 i-000001c9 output: puppet ran at Thu May 17 12:43:52 UTC 2012 [12:44:04] RECOVERY Puppet freshness is now: OK on scribunto i-0000022c output: puppet ran at Thu May 17 12:43:53 UTC 2012 [12:44:44] RECOVERY Puppet freshness is now: OK on hugglewa-1 i-000001e0 output: puppet ran at Thu May 17 12:44:34 UTC 2012 [12:44:44] RECOVERY Puppet freshness is now: OK on p-b i-000000ae output: puppet ran at Thu May 17 12:44:35 UTC 2012 [12:44:44] RECOVERY Puppet freshness is now: OK on incubator-common i-00000254 output: puppet ran at Thu May 17 12:44:41 UTC 2012 [12:45:04] RECOVERY Puppet freshness is now: OK on wep i-000000c2 output: puppet ran at Thu May 17 12:44:50 UTC 2012 [12:45:34] RECOVERY Puppet freshness is now: OK on deployment-imagescaler01 i-0000025a output: puppet ran at Thu May 17 12:45:14 UTC 2012 [12:51:34] RECOVERY Puppet freshness is now: OK on wikidata-dev-3 i-00000225 output: puppet ran at Thu May 17 12:51:20 UTC 2012 [13:06:44] RECOVERY Puppet freshness is now: OK on deployment-wmsearch i-000000e1 output: puppet ran at Thu May 17 13:06:32 UTC 2012 [13:07:49] !accountreq [13:07:50] case you want to have an account on labs please read here: https://labsconsole.wikimedia.org/wiki/Help:Access#Access_FAQ [13:10:04] RECOVERY Puppet freshness is now: OK on opengrok-web i-000001e1 output: puppet ran at Thu May 17 13:09:56 UTC 2012 [13:10:14] RECOVERY Puppet freshness is now: OK on feeds i-000000fa output: puppet ran at Thu May 17 13:10:04 UTC 2012 [14:34:04] PROBLEM dpkg-check is now: CRITICAL on gluster-devstack i-00000274 output: DPKG CRITICAL dpkg reports broken packages [14:49:34] PROBLEM Puppet freshness is now: CRITICAL on deployment-syslog i-00000269 output: Puppet has not run in last 20 hours [14:58:05] New patchset: Faidon; "misc::mediawiki-logger needs nfs::home::wikipedia" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7858 [14:58:19] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/7858 [14:58:26] New review: Faidon; "(no comment)" [operations/puppet] (test); V: 0 C: 2; - https://gerrit.wikimedia.org/r/7858 [14:58:29] Change merged: Faidon; [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7858 [15:05:40] * Tanvir walks in. [15:05:52] Hi Tanvir - yes, I can create a Labs account for you [15:05:58] !accountreq [15:05:58] case you want to have an account on labs please read here: https://labsconsole.wikimedia.org/wiki/Help:Access#Access_FAQ [15:06:02] Nice Sumana! [15:06:03] !accountquestions [15:06:26] hmmmm [15:06:30] Oh aye, THO already guided me to that page. [15:06:44] yeah, I can create the account for you now if you would rather do that :) [15:06:48] just need the same answers [15:07:11] Okay, will do. [15:07:49] Tanvir: https://www.mediawiki.org/wiki/Developer_access has the 4 questions [15:09:16] 05/17/2012 - 15:09:15 - Creating a home directory for mshavlovsky at /export/home/bastion/mshavlovsky [15:09:46] 05/17/2012 - 15:09:46 - Creating a home directory for mshavlovsky at /export/home/blamemaps/mshavlovsky [15:10:15] 05/17/2012 - 15:10:14 - Updating keys for mshavlovsky at /export/home/bastion/mshavlovsky [15:10:43] 05/17/2012 - 15:10:43 - Updating keys for mshavlovsky at /export/home/blamemaps/mshavlovsky [15:34:45] @accountquestions [15:35:01] !accountquestions [15:35:04] !account-questions [15:35:04] I need the following info from you: 1. Your preferred wiki user name. This will also be your git username, so if you'd prefer this to be your real name, then provide your real name. 2. Your preferred email address. 3. Your SVN account name, or your preferred shell account name, if you do not have SVN access. [15:35:29] hi petan|wk [15:35:32] hey [15:35:33] did you see my ping yesterday? [15:35:35] no [15:35:48] it was to do with getting x-forwarding working on bots-3 [15:35:55] aha [15:36:06] what you need to do that [15:36:16] [00:05:03] thehelpfulone@bots-3:~$ The program 'xeyes' is currently not installed. To run 'xeyes' please ask your administrator to install the package 'x11-apps' [15:36:29] Thehelpfulone: sudo apt-get install xeyes [15:36:36] Thehelpfulone: sudo apt-get install x11-apps [15:36:52] xeyes is what? [15:36:55] oh interesting, I'll have a go :) [15:36:55] I don't even want to know why you need that for x forwarding but anyway [15:37:04] hehe [15:37:10] :D [15:37:17] Damianz: I was wondering as well [15:37:19] Damianz: I was following some guide and it told me to type something to do with that [15:37:20] xeyes IIRC is 2 "eyes" that bounce around [15:37:24] yeah [15:37:27] Thehelpfulone: yes [15:37:34] Thehelpfulone: xeyes is a game for kids [15:37:36] ssh -X WOW X FORWARDING [15:37:37] I guess [15:37:51] lol it's a game? [15:37:55] Thehelpfulone: it's running in graphical environment [15:37:56] xeyes? yes. [15:37:58] what guide was I reading 9_9 [15:38:00] :D [15:38:44] Is xeyes useful as a decoy/test, to check whether various X functionality is working right? [15:38:47] I'm just speculating [15:39:17] http://courses.cms.caltech.edu/cs11/misc/xwindows.html [15:39:22] I think it might have been yes sumanah [15:39:22] Not sure if the ssh configs are setup for x-forwarding as there is really no need to do it... and for bots you're just going to hand open the ssh session then the bot will die when your connection drops. [15:39:33] s/hand/hang/ [15:39:46] + it will be terribly slo [15:39:49] w [15:40:13] hmm Damianz the idea was that the bot would run from wmf labs, so why does it need x-forwarding? [15:40:21] I'm on about Sven's bot from yesterday [15:40:30] Because someone wrote the login window as a graphical thing. [15:40:36] Thehelpfulone: why does it even need xeyes to run? [15:40:44] what kind of bot is it [15:40:46] You could hack up the code somewhat and get it to work assuming that's the only graphical thing it does. [15:40:47] * sumanah leaves things to the experts [15:40:56] petan|wk: like sumanah said, I think that was just to test that x-forwarding works [15:41:10] Thehelpfulone: why do you need X? [15:41:11] it's a java bot petan, see /home/svenmanguard/bot/ on bots-3 [15:41:20] Thehelpfulone: java can run in terminal too [15:41:22] petan|wk: Damianz said it's because to login there's a GUI [15:41:27] oh [15:41:34] can the code be changed? [15:41:40] running X across the internet is a bad idea [15:41:41] It's a jar so should be. [15:41:46] k [15:41:50] sure, but I don't know how to change it ;) [15:41:55] running anything graphical on server is a bad idea [15:42:00] yep [15:42:11] *cough* windows *cough* [15:42:13] it's a waste of memory and cpu, at least [15:42:26] meh byte compiled java [15:42:32] Thehelpfulone: that's not an example that helps the case ;) [15:42:36] it eats a lot of resources, btw windows on server is one of these graphical stuffs I would never recommend you to install [15:42:45] Ryan_Lane: it was helping your case :D [15:42:49] heh [15:43:21] Totally don't have time to un-byte compile java and figure out wtf it's doing right now [15:43:37] so who knows java that would be able to tweak that stolen code to not use a GUI login? [15:43:46] Thehelpfulone: stolen code? [15:43:47] apparently it's stolen code, I didn't steal it. [15:44:00] stolen in the sense you can only run opensource stuff on labs? [15:44:02] Thehelpfulone: you know only open source should run on labs [15:44:15] XD [15:44:22] Damianz: I am quiet [15:44:23] The wikipedia api is a pile of wank, keeps dropping off every few hours :( [15:44:32] petan|wk: according to Sven, it belonged to Fastily, someone found it on the internet, copied it, and then Fastily went all RAGE or something [15:44:39] let me see what Sven said yesterday [15:44:40] ugh [15:44:48] Sounds dodgy [15:44:59] so, if it isn't open source, it shouldn't run on labs [15:45:04] [23:32:42] Damianz: I don't have the source code because Sigma found it on the internet and stole it so Fastily nuked everything [15:45:16] yeah, it shouldn't run on labs [15:45:19] Found it under ? [15:45:37] I'd prefer no lawsuits ;) [15:45:47] Meh you have a laywer [15:46:07] 24020 < seriously, so it managed to do 45k+ over night, yet it's failed to do 500 in the past 4hours :( [15:46:08] I'm pretty sure they'd prefer not to have one either [15:46:11] * Damianz kicks the api [15:46:41] so I should send them to the toolserver instead? ;) [15:46:51] doesn't toolserver have the same policy? [15:46:54] if not, then yes [15:47:31] I really should do this on the toolserver rather than make a few hundred thousand api requests but I'm not waiting a week for an account. [15:47:44] Thehelpfulone: maybe you shouldn't use it [15:47:48] Thehelpfulone: "In Windows Server 2008, Server Core installation does not include the traditional full graphical user interface (GUI)";) [15:48:19] mutante: really? [15:48:22] what an upgrade [15:48:26] petan|wk: yeah, I'll tell Sven [15:48:44] in newer versions of windows they aren't going to have a GUI at all [15:48:47] Thehelpfulone: whatever it is code your own version [15:48:51] Well it includes a gui to the point that the cmd runs in a GUI [15:48:52] *window server, that is [15:49:12] Ryan_Lane: in newer windows? so microsoft is going to learn people use terminal XD [15:49:20] heh [15:49:29] basically, yes [15:49:30] petan|wk: try on a windows: cmd.exe -> wmic [15:49:32] New patchset: Faidon; "Ensure File['/home/wikipedia'] exists on labs too" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7861 [15:49:32] windows 8 - terminal [15:49:47] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/7861 [15:49:51] mutante: I will try and if it break my pc I will find you [15:49:53] :P [15:50:10] petan|wk: basically the wmic shell lets you do everything that gui system settings can and a bit more [15:50:12] what's that mutante? [15:50:15] New review: Faidon; "(no comment)" [operations/puppet] (test); V: 0 C: 2; - https://gerrit.wikimedia.org/r/7861 [15:50:18] Change merged: Faidon; [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7861 [15:50:20] C:\Users\petr.bena>wmic [15:50:20] wmic:root\cli>ls [15:50:21] wmic:root\cli> [15:50:24] what is it [15:50:32] windows meta instrumentation cmdline or so [15:50:38] now type [15:50:39] PROCESS [15:50:56] what's with all of you running windows? [15:50:59] you're scaring me [15:51:07] ohhi ryan [15:51:09] Ryan_Lane: I have to [15:51:10] all of us? :P [15:51:10] in office [15:51:11] had a nice trip? [15:51:14] paravoid: howdy [15:51:23] well, I'm basically just getting here [15:51:25] flights were good [15:51:32] I've got far too many processes open mutante [15:51:32] the 1st had wifi [15:51:46] although chrome is 1/3rd of them [15:51:46] not running it :) just want to point out cmdline is possible in Windows as well, just nobody does it [15:52:06] I do [15:52:08] actually maybe about a 1/4 [15:52:12] http://s23.org/wiki/WmicAliase [15:52:19] works since XP [15:52:56] mutante: why not just use powershell? [15:53:08] Ryan_Lane: now you'r a windows guru? [15:53:09] :P [15:53:23] petan|wk: I did interoperability at my last job [15:53:26] Ryan_Lane: true, it did not come on-board back in XP though [15:53:37] yep [15:53:52] petan|wk: I can get a kerberos ticket from an AD using a smart card on linux ;) [15:54:12] or access a linux samba share using kerberos from a windows system [15:54:32] that doesn't really sound so complicated given that's a goal of samba [15:54:34] Keep your windows over **there** [15:55:07] heh. you'd think so [15:55:19] I run some pdc using samba [15:55:27] windows domain on linux [15:55:29] :) [15:55:43] yeah, that's an old-style domain though [15:55:46] everything works fine except for file permissions [15:55:55] no group policy and such [15:56:05] there are but very limited [15:56:24] I use to work in a setup where we used novell stuff, with an AD env mirrored then with a unix env mirroed.. yay for having 3 copies of everything out of sync. [15:56:33] heh [15:56:45] I still think you could do an awesome group policy style setup with selinux. [15:56:53] if you are running samba, make sure you have recent upgrades, btw [15:56:54] I don't [15:56:54] :D [15:57:02] mutante: how recent? [15:57:02] there was a pretty serious issue, remote access [15:57:15] mutante: there is firewall level access restriction from outside [15:57:18] If you are running samba NOT BEHIND A FIREWALL then you're an idiot [15:57:35] we I do [15:57:46] run behind it [15:57:53] :o [15:58:02] how are we talking about windows now? :( [15:58:41] :D [15:58:49] Windows sucks generally. [15:58:51] petan|wk: there it is http://www.h-online.com/open/news/item/Samba-fixes-critical-remote-code-execution-vulnerability-1518580.html [15:58:56] 11 April [15:58:59] oh [15:59:38] "complete access to a Samba server from an unauthenticated connection" :) [16:00:21] gtg [16:00:37] mutante: they are just keeping in spec with microsoft's implementation [16:00:39] Thehelpfulone: send me an email or ask Damianz if you needed any help [16:00:46] Ryan_Lane: hehee [16:01:17] Have you ever read the spec on the exchange protocol? That's some scary shit. [16:01:26] heh [16:01:39] ok. I need to switch locations. there's no proper place to sit here [16:01:51] Use the power of the hover board? :D [16:23:46] PROBLEM Current Load is now: CRITICAL on s1tiny i-00000277 output: CHECK_NRPE: Error - Could not complete SSL handshake. [16:24:26] PROBLEM Current Users is now: CRITICAL on s1tiny i-00000277 output: CHECK_NRPE: Error - Could not complete SSL handshake. [16:25:06] PROBLEM Disk Space is now: CRITICAL on s1tiny i-00000277 output: CHECK_NRPE: Error - Could not complete SSL handshake. [16:25:36] PROBLEM Free ram is now: CRITICAL on s1tiny i-00000277 output: CHECK_NRPE: Error - Could not complete SSL handshake. [16:26:56] PROBLEM Total Processes is now: CRITICAL on s1tiny i-00000277 output: CHECK_NRPE: Error - Could not complete SSL handshake. [16:27:36] PROBLEM dpkg-check is now: CRITICAL on s1tiny i-00000277 output: CHECK_NRPE: Error - Could not complete SSL handshake. [16:40:10] New patchset: Faidon; "Another silly syntax error" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7863 [16:40:24] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/7863 [16:40:37] New review: Faidon; "(no comment)" [operations/puppet] (test); V: 0 C: 2; - https://gerrit.wikimedia.org/r/7863 [16:40:40] Change merged: Faidon; [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7863 [16:40:43] I really need to get some serious sleep [16:41:45] paravoid: still jetlagged? [16:41:48] besides making all those terribly stupid mistakes [16:41:54] mistakes? [16:42:03] I just hit ctrl+alt+backspace instead of ctrl+alt+left arrow [16:42:06] and killed my X [16:42:08] hahaha [16:42:13] you don't have that disabled? [16:42:14] for the 2nd time today [16:42:21] yes, 2nd [16:42:28] I just disabled it [16:42:35] * Ryan_Lane nods [16:42:39] apparently I hadn't, and hadn't killed my X for months [16:42:40] I always disable that. I hate it [16:43:22] if I need to restart X I can go into a virtual terminal and restart it from there [16:43:22] mistakes as in typing "requires" instead of "require" [16:43:29] and commiting that [16:43:29] heh [16:46:23] RECOVERY Puppet freshness is now: OK on deployment-feed i-00000118 output: puppet ran at Thu May 17 16:46:05 UTC 2012 [16:46:25] at least I fixed puppet [16:46:28] for labs [16:46:39] that was apparently broken since yesterday [16:46:48] oh? [16:46:51] in which way? [16:47:19] yeah, hashar made a change that was a syntax error and I reviewed it and pushed it [16:47:27] ah [16:47:30] (not my best days obviously) [16:47:39] puppet-lint didn't catch it though [16:47:53] er, our lint, not /the/ puppet-lint [16:48:40] Ryan_Lane: btw, labs had another major hiccup today [16:48:44] oh? [16:48:45] I/O was blocked for several minutes [16:48:51] odd. why? [16:48:59] I had a vim open, typed :wq and waited for like 10 minutes [16:49:09] ganglia showed I/O wait [16:49:18] hashar also noticed that at the same time [16:49:33] and his instances were running on a different node than mine [16:49:44] didn't find anything weird on the logs [16:49:44] paravoid: oh, but all those Nagios puppet freshness warnings in labs, i didnt think it was you [16:49:56] paravoid: that was no snmtrapd on nagios instance , and i started it [16:50:07] tried gluster volume info (or status) etc. and everything seemed normal [16:50:51] so, really, no idea [16:51:04] everything returned to normal after a while [16:51:39] (while = ten minute or so) [16:56:53] annoying [16:56:59] we really need to get off of gluster [16:57:21] stupid hardware won't be available for about another two weeks [16:58:27] oh really? [16:58:28] that sucks [17:13:19] PROBLEM dpkg-check is now: CRITICAL on swift-be1 i-000001c7 output: DPKG CRITICAL dpkg reports broken packages [17:30:34] PROBLEM Puppet freshness is now: CRITICAL on nova-ldap1 i-000000df output: Puppet has not run in last 20 hours [17:38:18] RECOVERY dpkg-check is now: OK on swift-be1 i-000001c7 output: All packages OK [17:45:08] * sumanah looks for most up-to-date roadmap for Labs functionality [17:58:36] New patchset: Hashar; "ability to change thumbnail server name" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7255 [17:58:51] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/7255 [17:59:28] New review: Hashar; "Patchset 4 is a rebase on top of `test`" [operations/puppet] (test); V: 0 C: 0; - https://gerrit.wikimedia.org/r/7255 [18:00:18] New patchset: Hashar; "/home/wikipedia/logs on mediawiki-logger service" [operations/puppet] (test) - https://gerrit.wikimedia.org/r/7304 [18:00:33] New review: gerrit2; "Lint check passed." [operations/puppet] (test); V: 1 - https://gerrit.wikimedia.org/r/7304 [18:00:43] I think we have a Bugzilla bug open for the task of making Developer access (Labs) accounts self-serve. Ryan_Lane can you remind me of what it is? can't find it [18:00:56] New review: Hashar; "Patchset 3 is a rebase on top of `test`" [operations/puppet] (test); V: 0 C: 0; - https://gerrit.wikimedia.org/r/7304 [18:03:43] Ryan_Lane: looked on https://www.mediawiki.org/wiki/Wikimedia_Labs#Roadmap and didn't see it but I might have searched for the wrong terms [18:05:32] PROBLEM HTTP is now: CRITICAL on deployment-web3 i-00000219 output: CRITICAL - Socket timeout after 10 seconds [18:06:53] paravoid and andrewbogott_ perhaps you know something about this and can help answer? (re self-serve accounts) [18:07:12] PROBLEM HTTP is now: CRITICAL on deployment-web4 i-00000214 output: CRITICAL - Socket timeout after 10 seconds [18:11:12] PROBLEM Current Load is now: CRITICAL on nagios 127.0.0.1 output: CRITICAL - load average: 16.94, 13.78, 8.97 [18:12:29] hi channel -- I have policy/tech questions on a proposed Labs project that's different in scope from existing projects [18:12:48] PROBLEM Current Load is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:53] PROBLEM Current Users is now: CRITICAL on bots-cb i-0000009e output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:53] PROBLEM Disk Space is now: CRITICAL on bots-cb i-0000009e output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:54] PROBLEM Current Users is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:54] PROBLEM dpkg-check is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:54] PROBLEM Free ram is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:54] PROBLEM Disk Space is now: CRITICAL on incubator-bot1 i-00000251 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:12:54] PROBLEM SSH is now: CRITICAL on bots-cb i-0000009e output: CRITICAL - Socket timeout after 10 seconds [18:13:59] PROBLEM HTTP is now: CRITICAL on deployment-web i-00000217 output: CRITICAL - Socket timeout after 10 seconds [18:13:59] PROBLEM HTTP is now: CRITICAL on deployment-web5 i-00000213 output: CRITICAL - Socket timeout after 10 seconds [18:14:04] which is to say migration of OpenMeetings.org into Labs, and hopefully into a WMF project as the platform matures [18:15:10] PROBLEM HTTP is now: WARNING on deployment-web3 i-00000219 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 2.453 second response time [18:15:15] PROBLEM Current Users is now: CRITICAL on upload-wizard i-0000021c output: CHECK_NRPE: Socket timeout after 10 seconds. [18:15:15] PROBLEM Total Processes is now: CRITICAL on upload-wizard i-0000021c output: CHECK_NRPE: Socket timeout after 10 seconds. [18:15:23] PROBLEM Current Load is now: CRITICAL on upload-wizard i-0000021c output: CHECK_NRPE: Socket timeout after 10 seconds. [18:15:23] PROBLEM Disk Space is now: CRITICAL on upload-wizard i-0000021c output: CHECK_NRPE: Socket timeout after 10 seconds. [18:15:42] OpenMeetings.org is an older Mediawiki installation w/ the MetaVidWiki extension that "features full-length recordings of meetings that span a broad range of social issues" [18:16:08] PROBLEM HTTP is now: WARNING on deployment-web4 i-00000214 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.011 second response time [18:16:08] RECOVERY Current Users is now: OK on bots-cb i-0000009e output: USERS OK - 0 users currently logged in [18:16:08] RECOVERY Disk Space is now: OK on bots-cb i-0000009e output: DISK OK [18:16:08] RECOVERY SSH is now: OK on bots-cb i-0000009e output: SSH OK - OpenSSH_5.3p1 Debian-3ubuntu7 (protocol 2.0) [18:16:48] PROBLEM Current Load is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:16:49] PROBLEM Total Processes is now: CRITICAL on precise-test i-00000231 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:16:59] it also meets all Labs terms-of-use [18:17:18] PROBLEM Disk Space is now: CRITICAL on reportcard2 i-000001ea output: CHECK_NRPE: Socket timeout after 10 seconds. [18:17:18] PROBLEM Free ram is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:17:18] PROBLEM Current Users is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:17:18] PROBLEM dpkg-check is now: CRITICAL on migration1 i-00000261 output: CHECK_NRPE: Socket timeout after 10 seconds. [18:18:03] PROBLEM Current Load is now: WARNING on deployment-nfs-memc i-000000d7 output: WARNING - load average: 4.57, 6.72, 5.40 [18:18:08] PROBLEM HTTP is now: WARNING on deployment-web i-00000217 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.012 second response time [18:18:08] PROBLEM HTTP is now: WARNING on deployment-web5 i-00000213 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.014 second response time [18:18:08] PROBLEM Current Load is now: WARNING on bots-apache1 i-000000b0 output: WARNING - load average: 2.07, 11.14, 8.13 [18:18:50] GChriss: I suggest you email the Labs mailing list [18:19:55] hmm [18:19:55] RECOVERY Current Users is now: OK on upload-wizard i-0000021c output: USERS OK - 0 users currently logged in [18:19:55] RECOVERY Total Processes is now: OK on upload-wizard i-0000021c output: PROCS OK: 84 processes [18:20:03] petan: Is the nagios box a vm? [18:20:11] RECOVERY Current Load is now: OK on upload-wizard i-0000021c output: OK - load average: 0.63, 4.12, 3.56 [18:20:11] RECOVERY Disk Space is now: OK on upload-wizard i-0000021c output: DISK OK [18:20:23] PROBLEM HTTP is now: CRITICAL on deployment-web3 i-00000219 output: CRITICAL - Socket timeout after 10 seconds [18:20:26] GChriss: https://lists.wikimedia.org/mailman/listinfo/labs-l [18:20:27] I'm wondering if these random io latency spikes are hitting nagios checks and causing some of these spams of warnings. [18:21:15] RECOVERY Current Load is now: OK on incubator-bot1 i-00000251 output: OK - load average: 0.46, 3.18, 3.69 [18:21:15] RECOVERY Current Users is now: OK on incubator-bot1 i-00000251 output: USERS OK - 0 users currently logged in [18:21:15] RECOVERY Disk Space is now: OK on incubator-bot1 i-00000251 output: DISK OK [18:21:15] RECOVERY Free ram is now: OK on incubator-bot1 i-00000251 output: OK: 65% free memory [18:21:15] RECOVERY dpkg-check is now: OK on incubator-bot1 i-00000251 output: All packages OK [18:21:15] RECOVERY Current Load is now: OK on precise-test i-00000231 output: OK - load average: 0.43, 2.92, 2.45 [18:21:16] RECOVERY Total Processes is now: OK on precise-test i-00000231 output: PROCS OK: 83 processes [18:22:03] RECOVERY Disk Space is now: OK on reportcard2 i-000001ea output: DISK OK [18:22:03] RECOVERY Current Users is now: OK on migration1 i-00000261 output: USERS OK - 0 users currently logged in [18:22:03] RECOVERY Free ram is now: OK on migration1 i-00000261 output: OK: 83% free memory [18:22:03] RECOVERY dpkg-check is now: OK on migration1 i-00000261 output: All packages OK [18:22:53] PROBLEM Current Load is now: CRITICAL on bots-cb i-0000009e output: CRITICAL - load average: 0.38, 27.50, 50.73 [18:26:22] ok, will do. In comparison to the "Labs to host wikilovesmonuments.org?" thread, a OpenMeetings migration to Labs would not be for production use (or, if so, only lightly). there's a bunch of code cleanup/rewrites that need to happen, hopefully in a WMF-friendly environment [18:28:03] RECOVERY Current Load is now: OK on deployment-nfs-memc i-000000d7 output: OK - load average: 0.05, 2.13, 3.86 [18:28:03] RECOVERY Current Load is now: OK on bots-apache1 i-000000b0 output: OK - load average: 0.00, 1.55, 4.30 [18:29:46] Eloquence: are you in the middle of some TitleBlacklist-related sweep? [18:30:07] * Damianz yawns [18:31:13] PROBLEM Current Load is now: WARNING on nagios 127.0.0.1 output: WARNING - load average: 0.48, 0.87, 3.42 [18:31:30] sumanah: I don't know if there's a registered bug for it at the moment. I think the aim is to have gerrit accounts be self-serve but for labs staff to remain gatekeepers for actual labs accounts for the foreseeable future. [18:32:33] It's a shame gerrit doesn't use central auth [18:33:09] blame central auth for not using LDAP :-D [18:33:54] vvv, done for now [18:38:09] PROBLEM Current Load is now: WARNING on bots-cb i-0000009e output: WARNING - load average: 0.35, 1.68, 19.40 [18:38:16] ... [18:51:21] RECOVERY Current Load is now: OK on nagios 127.0.0.1 output: OK - load average: 1.91, 1.94, 2.61 [19:02:54] RECOVERY Current Load is now: OK on bots-cb i-0000009e output: OK - load average: 0.48, 0.84, 4.74 [19:45:21] well, I would answer sumanah on her question, but she never seems to stay online for long periods of time... [20:01:15] PROBLEM HTTP is now: WARNING on deployment-web3 i-00000219 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 4.217 second response time [21:01:54] PROBLEM HTTP is now: CRITICAL on deployment-web3 i-00000219 output: CRITICAL - Socket timeout after 10 seconds [21:02:04] PROBLEM HTTP is now: CRITICAL on deployment-web4 i-00000214 output: CRITICAL - Socket timeout after 10 seconds [21:06:44] PROBLEM HTTP is now: WARNING on deployment-web3 i-00000219 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.012 second response time [21:06:54] PROBLEM HTTP is now: WARNING on deployment-web4 i-00000214 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.010 second response time [22:02:26] Thehelpfulone: I have returned [22:02:40] and Roan has fled, apparently :P [22:08:13] * RoanKattouw is back [22:08:21] hey [22:08:30] hi Sven_Manguard [22:08:42] remember me from yesterday Thehelpfulone? You know, the doomed one? [22:08:57] I'm afraid I've got bad news for you :P [22:09:21] I don't think the bot can be run on labs - that's what Ryan Lane was saying earlier [22:09:33] on labs bot code needs to be open source [22:09:48] it didn't sound like Fastily's code was open source? [22:10:18] Well it isn't right now [22:10:22] but there are larger issues [22:10:24] http://imagr.eu/up/4fb5772a810af0_error_putty.png [22:10:29] ignore the name of the image, it [22:10:32] 's reused [22:11:11] as it says,it can't find rc.txt [22:11:23] Sven_Manguard: ^ What Reedy said :P [22:11:37] wonderful [22:12:00] it wasn't there [22:12:09] Java, sort like PHP, will throw up tons of error messages for 1 easy to undertsnad issue [22:12:25] it's not a tonne of error messages [22:12:29] it's one with a stack trace [22:12:41] Either way ;P [22:14:07] PROBLEM Puppet freshness is now: CRITICAL on deployment-apache22 i-0000026f output: Puppet has not run in last 20 hours [22:19:56] hmm [22:24:45] Reedy: Thehelpfulone: methecooldude: etc: if I get fastily to okay releasing it under open source, what *other* issues am I going to run into. It seems like there's been one every night now [22:25:05] you've only been at it for one night :) [22:25:24] two now [22:25:30] any technical issues you would usually be able to find someone to help you [22:31:52] methecooldude: Lies [22:31:55] It's called a stack *trace* for a reason [22:32:21] Sven_Manguard: Depends, if you're not grumpy, willing to disect issues and figure things out no so many. [22:32:53] Damianz: I have installed several pieces of software that I don't really know anything about on what is blind trust in Thehelpfulone [22:33:01] And yet things keep falling apart [22:33:17] Besides, I'm only grumpy around you. Shitty first impressions and all that :P [22:38:30] I'm sure methecooldude will testify that you'll be driven insane first. [22:38:49] Yep :P [22:39:26] If you had a nice opensource bot I'd just look at the code and try to 'fix' it but fuck you if you think I'm un-byte compiling java classes to run something that you 'stole' randomly in the first place while you complain :) [22:39:38] ^ see smilly face makes me look like a happy ass [23:02:40] PROBLEM HTTP is now: CRITICAL on deployment-web4 i-00000214 output: CRITICAL - Socket timeout after 10 seconds [23:02:50] PROBLEM HTTP is now: CRITICAL on deployment-web3 i-00000219 output: CRITICAL - Socket timeout after 10 seconds [23:04:20] PROBLEM HTTP is now: CRITICAL on deployment-web5 i-00000213 output: CRITICAL - Socket timeout after 10 seconds [23:04:20] PROBLEM HTTP is now: CRITICAL on deployment-web i-00000217 output: CRITICAL - Socket timeout after 10 seconds [23:07:35] RECOVERY Disk Space is now: OK on deployment-feed i-00000118 output: DISK OK [23:12:20] PROBLEM HTTP is now: WARNING on deployment-web3 i-00000219 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.007 second response time [23:12:30] PROBLEM HTTP is now: WARNING on deployment-web4 i-00000214 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.008 second response time [23:14:10] PROBLEM HTTP is now: WARNING on deployment-web5 i-00000213 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.010 second response time [23:14:10] PROBLEM HTTP is now: WARNING on deployment-web i-00000217 output: HTTP WARNING: HTTP/1.1 403 Forbidden - 366 bytes in 0.008 second response time [23:15:30] PROBLEM Disk Space is now: WARNING on deployment-feed i-00000118 output: DISK WARNING - free space: / 70 MB (5% inode=40%):