[02:15:34] <whym>	 Hi, could anyone here take care of http://ja.wikipedia.beta.wmflabs.org?
[02:17:06] <Damianz>	 petan is your best bet but he will be in bed
[02:19:59] <whym>	 hmmmm, being in japan, nearly everyone goes bed when I wake up :(
[02:20:12] <whym>	 Damianz: thanks anyway
[02:21:42] <Damianz>	 If you email the mailing list someone will probably sort it soonish, I don't have access to that project I don't think.
[02:24:36] <whym>	 thanks, that's good to know, I wasn't aware of labs-l
[02:37:28] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on bots-sql3 bots-sql3 output: OK: 20% free memory
[02:40:08] <labs-nagios-wm>	 PROBLEM Free ram is now: WARNING on puppet-lucid puppet-lucid output: Warning: 12% free memory
[02:45:28] <labs-nagios-wm>	 PROBLEM Free ram is now: WARNING on bots-sql3 bots-sql3 output: Warning: 18% free memory
[03:10:08] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on puppet-lucid puppet-lucid output: Critical: 3% free memory
[03:30:08] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on puppet-lucid puppet-lucid output: OK: 20% free memory
[03:39:56] <jeremyb>	 whym: looking
[03:40:08] <jeremyb>	 whym: did it ever work?
[03:41:09] <whym>	 jeremyb: hi
[03:41:25] <whym>	 the test wiki of jawp generally is working well
[03:41:57] <whym>	 i just wanted to test with further customissation implemented in the MediaWiki namespace of the current jawp
[03:46:28] <whym>	 i would want to have them synced, either manually or automatically
[04:03:59] <jeremyb>	 whym: you want to have the MediaWiki NS wiped clean and reimported? or just specific pages?
[04:06:23] <whym>	 jeremyb: for now I want to test several localisations like MediaWiki:Talk, but there will be more to come, i think
[04:06:40] <whym>	 if it's easy to automatically import everything, that would be the best
[04:06:48] <jeremyb>	 what's MediaWiki:Talk?
[04:06:59] <jeremyb>	 you mean MediaWiki talk: ?
[04:07:04] <whym>	 jeremyb:  https://ja.wikipedia.org/wiki/MediaWiki:Talk
[04:07:41] <jeremyb>	 ahh
[04:07:48] <whym>	 since it affects all pages, it immediately came to my mind :)
[04:08:23] <jeremyb>	 but it's not just that page? or 5 pages?
[04:09:47] <whym>	 [[MediaWiki:Talk]] will be used as the name of the tab "Discussion", as well as a part of URL of all talk pages instead of "talk"
[04:10:12] <whym>	 wait, maybe URL will have a separate configuration
[04:10:16] <jeremyb>	 i don't think it will be used for the URL unless you change the actual config (not just the interface msg)
[04:10:40] <whym>	 yep
[04:10:42] <jeremyb>	 i can change the config pretty easily i think but idk the current best practice for new imports
[04:10:51] <jeremyb>	 you can just make the edit yourself though?
[04:11:04] <jeremyb>	 what should the config be? same as the interface msg?
[04:11:37] <whym>	 jeremyb: i don't seem to write access to MediaWiki namespace on http://ja.wikipedia.beta.wmflabs.org
[04:11:56] <whym>	 ^i don't seem to be have write access
[04:14:39] <jeremyb>	 ノート vs. 「ノート ?
[04:14:42] <jeremyb>	 whym: ^
[04:15:25] <whym>	 ノート should be substituted with 'talk' in URLs
[04:15:45] <jeremyb>	 what is 「?
[04:16:22] <whym>	 「 corresponds to left parenthesis
[04:16:32] <jeremyb>	 huh
[04:16:38] <jeremyb>	 why is it there? ;)
[04:17:00] <jeremyb>	 and を編集中 ?
[04:17:06] <whym>	 seems like an error in copy-and-paste?
[04:17:18] <jeremyb>	 google says "while editing the"
[04:17:48] <whym>	 "を編集中" is an incomplete sentence lacking a subject
[04:18:10] <whym>	 ^lacking an object
[04:18:16] <whym>	 it would read as "editing (something)"
[04:18:31] <Damianz>	 https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-ash4/407974_334538833244352_130810663617171_1118630_1115067198_n.jpg lol
[04:19:49] <jeremyb>	 do you have any firearms stowed in your server?
[04:20:00] <Damianz>	 That would be win
[04:20:08] <Damianz>	 The uk gun law is a little nazi though
[04:21:24] <jeremyb>	 whym: so, i think the URL was already correct on beta? just not the tab?
[04:21:44] <jeremyb>	 Damianz: you don't know beta do you?
[04:21:55] <jeremyb>	 and hex mode is idle
[04:22:19] <Damianz>	 Can't say I've ever logged into the servers tbh
[04:22:52] <whym>	 jeremyb: yes, i checked it again and the prolem is just the tab
[04:23:18] <Damianz>	 It also doesn't help that it's in Japanese :P
[04:23:27] <jeremyb>	 whym: k
[04:23:34] <jeremyb>	 whym: username?
[04:23:55] <whym>	 jeremyb: this name, "Whym"
[04:24:16] <jeremyb>	 whym: btw, you're not on the list @ http://labs.wikimedia.beta.wmflabs.org/ so we should get you fully imported when petan's around
[04:26:45] <whym>	 jeremyb: so, will I just can wait for that?
[04:27:05] <whym>	 ^can I just wait
[04:27:08] <jeremyb>	 whym: idk... i'm digging a little
[04:29:30] <Damianz>	 Don't dig too much, you'll end up in Japan.
[04:30:00] <whym>	 jeremyb: ok I'll ask petan when I can catch, and I'll appreciate if you do so when possible
[04:30:37] <jeremyb>	 whym: seen the other channel?
[04:30:41] <jeremyb>	 Damianz: ha. ha
[04:31:52] <whym>	 jeremyb: i'm on some others, wikimedia-tech, mediawiki-i18n, mostly listening
[04:32:29] <jeremyb>	 whym: i hilighted you in #mediawiki
[04:35:45] <jeremyb>	 hah, deployment-web has a scary warning to not run maint scripts ;P
[04:35:47] <jeremyb>	 there
[06:18:10] <j^>	 can someone svn up /usr/local/apache/common/live/extensions/TimedMediaHandler/ on deployment-web
[06:56:23] * jeremyb  sleeps

[07:04:55] <labs-nagios-wm>	 PROBLEM Disk Space is now: CRITICAL on deployment-webs1 deployment-webs1 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:04:55] <labs-nagios-wm>	 PROBLEM Total Processes is now: CRITICAL on deployment-webs1 deployment-webs1 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:05:00] <labs-nagios-wm>	 PROBLEM dpkg-check is now: CRITICAL on deployment-webs1 deployment-webs1 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:05:00] <labs-nagios-wm>	 PROBLEM Total Processes is now: CRITICAL on bots-cb bots-cb output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:05:52] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on nagios 127.0.0.1 output: CRITICAL - load average: 5.33, 7.36, 5.70
[07:05:52] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on bots-2 bots-2 output: WARNING - load average: 10.80, 11.59, 9.05
[07:05:52] <labs-nagios-wm>	 PROBLEM Free ram is now: WARNING on puppet-lucid puppet-lucid output: Warning: 18% free memory
[07:05:52] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on bots-sql3 bots-sql3 output: WARNING - load average: 9.94, 9.92, 7.41
[07:05:52] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on bots-cb bots-cb output: WARNING - load average: 15.95, 13.41, 9.55
[07:05:55] <labs-nagios-wm>	 PROBLEM Disk Space is now: CRITICAL on nova-dev2 nova-dev2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:06:39] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-webs1 deployment-webs1 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:06:39] <labs-nagios-wm>	 PROBLEM SSH is now: CRITICAL on bots-cb bots-cb output: CRITICAL - Socket timeout after 10 seconds
[07:06:39] <labs-nagios-wm>	 PROBLEM SSH is now: CRITICAL on deployment-webs1 deployment-webs1 output: CRITICAL - Socket timeout after 10 seconds
[07:06:48] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on labs-nfs1 labs-nfs1 output: WARNING - load average: 4.48, 5.79, 5.16
[07:06:48] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on nova-production1 nova-production1 output: WARNING - load average: 6.49, 9.32, 7.21
[07:06:48] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on gluster-devstack gluster-devstack output: WARNING - load average: 11.26, 12.83, 10.20
[07:07:00] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on nova-dev2 nova-dev2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:07:01] <labs-nagios-wm>	 PROBLEM Current Users is now: CRITICAL on nova-dev2 nova-dev2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:07:01] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on nova-dev2 nova-dev2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:07:01] <labs-nagios-wm>	 PROBLEM Total Processes is now: CRITICAL on nova-dev2 nova-dev2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:07:06] <labs-nagios-wm>	 PROBLEM dpkg-check is now: CRITICAL on nova-dev2 nova-dev2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[07:07:56] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on bots-3 bots-3 output: WARNING - load average: 8.86, 8.77, 6.20
[07:09:58] <labs-nagios-wm>	 RECOVERY Total Processes is now: OK on deployment-webs1 deployment-webs1 output: PROCS OK: 105 processes
[07:10:03] <labs-nagios-wm>	 RECOVERY Disk Space is now: OK on deployment-webs1 deployment-webs1 output: DISK OK
[07:10:03] <labs-nagios-wm>	 RECOVERY Total Processes is now: OK on bots-cb bots-cb output: PROCS OK: 110 processes
[07:10:08] <labs-nagios-wm>	 RECOVERY dpkg-check is now: OK on deployment-webs1 deployment-webs1 output: All packages OK
[07:10:38] <labs-nagios-wm>	 RECOVERY Disk Space is now: OK on nova-dev2 nova-dev2 output: DISK OK
[07:11:08] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on deployment-webs1 deployment-webs1 output: OK - load average: 1.40, 4.63, 4.18
[07:11:08] <labs-nagios-wm>	 RECOVERY SSH is now: OK on bots-cb bots-cb output: SSH OK - OpenSSH_5.3p1 Debian-3ubuntu7 (protocol 2.0)
[07:11:08] <labs-nagios-wm>	 RECOVERY SSH is now: OK on deployment-webs1 deployment-webs1 output: SSH OK - OpenSSH_5.3p1 Debian-3ubuntu7 (protocol 2.0)
[07:11:48] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on labs-nfs1 labs-nfs1 output: OK - load average: 0.65, 3.08, 4.21
[07:11:50] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on nova-dev2 nova-dev2 output: OK: 56% free memory
[07:11:50] <labs-nagios-wm>	 RECOVERY dpkg-check is now: OK on nova-dev2 nova-dev2 output: All packages OK
[07:11:50] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on nova-dev2 nova-dev2 output: OK - load average: 1.57, 4.14, 4.05
[07:11:50] <labs-nagios-wm>	 RECOVERY Current Users is now: OK on nova-dev2 nova-dev2 output: USERS OK - 0 users currently logged in
[07:11:50] <labs-nagios-wm>	 RECOVERY Total Processes is now: OK on nova-dev2 nova-dev2 output: PROCS OK: 122 processes
[07:15:28] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on puppet-lucid puppet-lucid output: OK: 20% free memory
[07:16:48] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on nova-production1 nova-production1 output: OK - load average: 0.00, 1.99, 4.51
[07:17:08] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on bots-3 bots-3 output: OK - load average: 2.86, 3.46, 4.54
[07:20:28] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on nagios 127.0.0.1 output: WARNING - load average: 0.35, 1.02, 3.10
[07:20:28] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on bots-cb bots-cb output: OK - load average: 0.18, 1.14, 4.32
[07:20:28] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on bots-sql3 bots-sql3 output: OK - load average: 0.15, 1.74, 4.53
[07:25:28] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on nagios 127.0.0.1 output: OK - load average: 0.24, 0.47, 2.27
[07:25:28] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on bots-2 bots-2 output: OK - load average: 1.66, 2.10, 4.36
[07:26:48] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on gluster-devstack gluster-devstack output: OK - load average: 0.00, 0.51, 3.88
[10:32:06] <zlato>	 can anyone help me with infoboxes please?
[10:51:18] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on deployment-web2 deployment-web2 output: Critical: 3% free memory
[10:51:28] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on deployment-web deployment-web output: Critical: 2% free memory
[10:52:18] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-web2 deployment-web2 output: CRITICAL - load average: 47.31, 26.48, 11.02
[10:52:28] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-web deployment-web output: CRITICAL - load average: 101.02, 69.43, 30.75
[10:53:28] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on deployment-webs1 deployment-webs1 output: Critical: 2% free memory
[10:54:08] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-webs1 deployment-webs1 output: CRITICAL - load average: 19.06, 26.77, 14.00
[10:56:18] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on deployment-web2 deployment-web2 output: OK: 47% free memory
[10:56:28] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on deployment-web deployment-web output: OK: 68% free memory
[10:57:18] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on deployment-web2 deployment-web2 output: WARNING - load average: 0.89, 12.75, 9.74
[10:58:28] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on deployment-webs1 deployment-webs1 output: OK: 42% free memory
[10:59:08] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on deployment-webs1 deployment-webs1 output: WARNING - load average: 0.20, 9.85, 10.15
[11:07:28] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on deployment-web deployment-web output: WARNING - load average: 0.04, 5.67, 16.21
[11:12:18] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on deployment-web2 deployment-web2 output: OK - load average: 0.04, 0.67, 3.73
[11:14:08] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on deployment-webs1 deployment-webs1 output: OK - load average: 0.03, 0.53, 3.86
[11:27:28] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on deployment-web deployment-web output: OK - load average: 0.00, 0.11, 4.45
[17:01:38] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on deployment-webs1 deployment-webs1 output: Critical: 3% free memory
[17:02:08] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-webs1 deployment-webs1 output: CRITICAL - load average: 43.98, 34.95, 15.45
[17:04:28] <labs-nagios-wm>	 PROBLEM Free ram is now: WARNING on deployment-web deployment-web output: Warning: 8% free memory
[17:04:38] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on deployment-web2 deployment-web2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[17:05:28] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-web deployment-web output: CRITICAL - load average: 38.05, 73.37, 41.29
[17:05:28] <labs-nagios-wm>	 PROBLEM Current Load is now: CRITICAL on deployment-web2 deployment-web2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[17:06:18] <labs-nagios-wm>	 PROBLEM HTTP is now: CRITICAL on deployment-web2 deployment-web2 output: CRITICAL - Socket timeout after 10 seconds
[17:06:28] <labs-nagios-wm>	 PROBLEM Current Users is now: CRITICAL on deployment-web2 deployment-web2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[17:06:38] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on deployment-webs1 deployment-webs1 output: OK: 44% free memory
[17:06:48] <labs-nagios-wm>	 PROBLEM Total Processes is now: CRITICAL on deployment-web2 deployment-web2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[17:06:53] <labs-nagios-wm>	 PROBLEM dpkg-check is now: CRITICAL on deployment-web2 deployment-web2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[17:07:08] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on deployment-webs1 deployment-webs1 output: WARNING - load average: 0.66, 14.08, 11.92
[17:07:48] <labs-nagios-wm>	 PROBLEM Disk Space is now: CRITICAL on deployment-web2 deployment-web2 output: CHECK_NRPE: Socket timeout after 10 seconds.
[17:07:48] <labs-nagios-wm>	 PROBLEM SSH is now: CRITICAL on deployment-web2 deployment-web2 output: CRITICAL - Socket timeout after 10 seconds
[17:09:28] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on deployment-web deployment-web output: OK: 73% free memory
[17:20:28] <labs-nagios-wm>	 PROBLEM Current Load is now: WARNING on deployment-web deployment-web output: WARNING - load average: 0.00, 3.66, 15.73
[17:22:08] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on deployment-webs1 deployment-webs1 output: OK - load average: 0.02, 0.73, 4.54
[17:23:58] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[17:40:28] <labs-nagios-wm>	 RECOVERY Current Load is now: OK on deployment-web deployment-web output: OK - load average: 0.01, 0.08, 4.31
[17:54:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[18:05:08] <labs-nagios-wm>	 RECOVERY dpkg-check is now: OK on gluster-devstack gluster-devstack output: All packages OK
[18:24:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[18:37:48] <labs-nagios-wm>	 PROBLEM Free ram is now: WARNING on bots-3 bots-3 output: Warning: 19% free memory
[18:49:08] <labs-nagios-wm>	 PROBLEM dpkg-check is now: CRITICAL on gluster-devstack gluster-devstack output: DPKG CRITICAL dpkg reports broken packages
[18:54:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[18:56:48] <labs-nagios-wm>	 PROBLEM host: driver-dev is DOWN address: driver-dev CRITICAL - Host Unreachable (driver-dev)
[18:59:38] <labs-nagios-wm>	 RECOVERY host: driver-dev is UP address: driver-dev PING OK - Packet loss = 0%, RTA = 2.89 ms
[19:04:28] <labs-nagios-wm>	 RECOVERY dpkg-check is now: OK on driver-dev driver-dev output: All packages OK
[19:24:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[19:27:48] <labs-nagios-wm>	 PROBLEM Free ram is now: CRITICAL on bots-3 bots-3 output: Critical: 5% free memory
[19:54:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[19:57:28] <labs-nagios-wm>	 PROBLEM dpkg-check is now: CRITICAL on driver-dev driver-dev output: DPKG CRITICAL dpkg reports broken packages
[19:57:48] <labs-nagios-wm>	 RECOVERY Free ram is now: OK on bots-3 bots-3 output: OK: 51% free memory
[20:24:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[20:54:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[21:04:18] <Tpt>	 Hello, I'm admin of the Frensh wikisource and I would like to use the http://wikisource-dev.wmflabs.org in order to test the configuaration of some extensions before installation in Wikisource. Zaran has say me to ask here.
[21:04:30] <Tpt>	 What I've to do ?
[21:24:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[21:54:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[22:12:28] <labs-nagios-wm>	 RECOVERY dpkg-check is now: OK on driver-dev driver-dev output: All packages OK
[22:18:27] <Ryan_Lane>	 andrewbogott: you don't get the emails about sudo failures, eh?
[22:18:33] <Ryan_Lane>	 andrewbogott: your instance is throwing sudo errors
[22:18:42] <andrewbogott>	 Only as of 10 minutes ago, right?
[22:18:46] <Ryan_Lane>	 yep
[22:19:05] <Ryan_Lane>	 thought it might be good to let you know, since it is likely causing things to break for you :)
[22:19:18] <andrewbogott>	 If I ctrl-C at just the right time during devstack, it corrupts the sudoers file.  I can not for the life of me train myself not to do that.
[22:19:20] <Ryan_Lane>	 did you get an invite to the openstack design summit, btw?
[22:19:26] <Ryan_Lane>	 ah. hah
[22:19:33] <Ryan_Lane>	 that's kind of funny
[22:19:38] <andrewbogott>	 I presume that puppet will replace sudoers during a periodic update if I wait?
[22:20:02] <Ryan_Lane>	  /etc/sudoers?
[22:20:03] <Ryan_Lane>	 yeah
[22:20:06] <andrewbogott>	 It is funny -- also, funny how useless a system is without sudo :(
[22:20:14] <Ryan_Lane>	 why would it write there, rather than dropping a file into /etc/sudoers.d?
[22:20:24] <andrewbogott>	 I can't imagine.
[22:20:35] <Ryan_Lane>	 likely because they want cross-distro compatibility
[22:20:46] <Ryan_Lane>	 should likely open a bug with them for ubuntu
[22:20:47] <andrewbogott>	 I did get an invite.  Are you planning to go to the conference or just to the summit?
[22:20:51] <Ryan_Lane>	 both
[22:21:02] <Ryan_Lane>	 you should likely register for both too
[22:21:23] <Ryan_Lane>	 it gives more time to talk with people and try to get help from them
[22:21:25] <andrewbogott>	 Sure.  I wasn't sure if the conference was for developers or just for vendors.
[22:21:38] <Ryan_Lane>	 well, it's free to go to the conference, if you are a dev
[22:21:50] <andrewbogott>	 True.
[22:21:53] <Ryan_Lane>	 so most people also go to the conference
[22:22:00] <Ryan_Lane>	 also, many of the devs talk at the conference
[22:22:09] <andrewbogott>	 ok, that's good to know.
[22:22:10] <Ryan_Lane>	 I've talked at each of them so far
[22:22:14] <andrewbogott>	 Not just suits then.
[22:22:25] <Ryan_Lane>	 yep
[22:22:30] <Ryan_Lane>	 there's a lot of them too
[22:22:46] <Ryan_Lane>	 the panel I moderated last time was suit city. it pained me a little
[22:22:54] <Ryan_Lane>	 was fun though. heh
[22:24:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[22:24:50] <andrewbogott>	 And for travel/hotel... will Laura do all that, or should I make my own arrangements and expense them?
[22:25:13] <Ryan_Lane>	 I believe Laura will handle that
[22:25:25] <Ryan_Lane>	 I'll need to talk to CT about this Monday
[22:25:31] <andrewbogott>	 ok
[22:25:48] <Ryan_Lane>	 but since you are doing the openstack dev, I think it's a really good idea for you to go :)
[22:26:11] <Ryan_Lane>	 thinking of that, I really need to finish that bug I started fixing a few weeks ago
[22:26:58] <Ryan_Lane>	 either that, or defer the bug. I think it's more extensive than I originally thought it was
[22:27:58] <andrewbogott>	 ok, registered.
[22:28:41] <andrewbogott>	 sorry about flooding you with sudo emails, btw.  I kind of wish I could mark a labs instance as 'silent' so it doesn't spam you and/or IRC.
[22:28:53] <Ryan_Lane>	 nah. it's no big deal
[22:29:02] <Ryan_Lane>	 they all get grouped into one thread
[22:29:21] <Ryan_Lane>	 I just didn't know if you knew or not, and wanted to make sure it wasn't blocking your work
[22:29:32] <Ryan_Lane>	 we should likely get you added to some of the aliases and lists
[22:30:04] <Ryan_Lane>	 want me to run puppet on your instance?
[22:30:20] <andrewbogott>	 Sure.
[22:30:30] <andrewbogott>	 Otherwise I'll just do a load of laundry and wait for the cron to do it :)
[22:30:34] <Ryan_Lane>	 heh
[22:30:49] <Ryan_Lane>	 bah. I just tried to ssh into it and sudo
[22:30:56] <andrewbogott>	 Yeah, that doesn't work.
[22:30:59] <Ryan_Lane>	 :)
[22:31:00] <Ryan_Lane>	 yep
[22:31:07] <Ryan_Lane>	 I can ssh directly in as root, though
[22:31:30] <Ryan_Lane>	 ok. should be fixed
[22:31:33] <andrewbogott>	 Really?  I thought that ubuntu basically prevented all logins as root not via sudo.
[22:31:50] <Ryan_Lane>	 we have it enabled.
[22:31:59] <Ryan_Lane>	 via ssh keys
[22:32:11] <andrewbogott>	 Yep, sudo is fixed.  thanks.
[22:32:14] <Ryan_Lane>	 yw
[22:32:25] <Ryan_Lane>	 only ops gets to do that :)
[22:32:28] <andrewbogott>	 Ah, but of course puppet also reinstalled ganglia which I have to uninstall to make devstack work...
[22:32:35] <andrewbogott>	 It's the cycle of life.
[22:32:41] <Ryan_Lane>	 otherwise we have no way to fix things if they *really* get jacked up
[22:32:47] <Ryan_Lane>	 ah
[22:32:55] <Ryan_Lane>	 for ganglia you can install a system user for it
[22:32:58] <Ryan_Lane>	 then it stops breaking
[22:33:18] <andrewbogott>	 OK, next time it comes back I'll try that.
[22:33:36] <Ryan_Lane>	 adduser --system --ingroup ganglia --home /var/lib/ganglia ganglia
[22:33:51] <Ryan_Lane>	 hopefully they switch devstack to precise soon
[22:33:55] <andrewbogott>	 Does KVM not provide some equivalent to a physical console?  When I break sudo in VirtualBox I can just boot into recovery mode.
[22:34:02] <Ryan_Lane>	 it does, yes
[22:34:03] <Ryan_Lane>	 but...
[22:34:06] <andrewbogott>	 I mean, not to say that root-by-ssh isn't better.
[22:34:10] <Ryan_Lane>	 we don't set root passwords
[22:34:14] <Ryan_Lane>	 well, we do
[22:34:21] <Ryan_Lane>	 to some long, random thing
[22:34:54] <Ryan_Lane>	 maybe we could set a project specific root password. I don't know how we'd let people know what it was, though
[22:35:30] <Ryan_Lane>	 I really don't want people logging in directly as root, either, though
[22:38:00] <andrewbogott>	 Well... having puppet revert sudoers periodically fixes the only case I can think of that matters.
[22:38:23] <andrewbogott>	 Um... unless puppet is broken :D
[22:39:04] <Ryan_Lane>	 heh
[22:39:23] <Ryan_Lane>	 yeah. we've broken puppet a few times too
[22:39:40] <Ryan_Lane>	 when I switched the puppet master I broke it on every single instance
[22:40:05] <Ryan_Lane>	 I had to run a script to re-join the new puppet master
[22:40:34] <Ryan_Lane>	 I may break every node soon when we switch home directories from NFS to gluster
[22:40:42] <Ryan_Lane>	 s/node/instance/
[22:54:28] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[23:01:28] <labs-nagios-wm>	 PROBLEM dpkg-check is now: CRITICAL on driver-dev driver-dev output: DPKG CRITICAL dpkg reports broken packages
[23:19:13] <andrewbogott>	 ok... how do I add a ganglia system user?
[23:21:28] <labs-nagios-wm>	 RECOVERY dpkg-check is now: OK on driver-dev driver-dev output: All packages OK
[23:23:28] <methecooldude>	 andrewbogott: "[22:33:36] <Ryan_Lane> adduser --system --ingroup ganglia --home /var/lib/ganglia ganglia"
[23:23:49] <andrewbogott>	 thx
[23:24:38] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)
[23:54:38] <labs-nagios-wm>	 PROBLEM host: deployment-web2 is DOWN address: deployment-web2 CRITICAL - Host Unreachable (deployment-web2)