[08:57] <erichammond> smoser: ping
[08:58] <kim0> Morning everyone
[09:51] <koolhead11> afternoon everyone :)
[09:51] <koolhead11> hi kim0
[09:51] <kim0> koolhead11: hey man
[09:51] <kim0> It's morning for me .. but yeah :)
[09:51] <koolhead11> :D
[10:44] <koolhead11> kim0, ping
[10:48] <kim0> yes ?
[10:49] <koolhead11> kim0, issue resloved!! :D
[10:55] <kim0> koolhead11: what issue :)
[10:55] <koolhead11> kim0, had some confusion soren helped me
[10:56] <kim0> ah awesome :)
[10:56] <koolhead11> its typo day 4 me. doing mistakes :(
[13:09] <smoser> erichammond, here now.
[16:05] <TeTeT> smoser: I discovered lately that 'persistency' does not seem to be an English word at all - should I ask to rename the project to be 'uec-persistence'?
[16:05] <TeTeT> TREllis: ^ your thoughts would be interesting as well
[16:06] <kim0> lol :D
[16:06] <smoser> TeTeT, i have no strong feelings.
[16:19] <TREllis> TeTeT: sounds fine, I have no strong feelings
[16:21] <TeTeT> ok, so we leave it as is, hope we don't look like the fool that I am ;)
[17:30] <bhavesh> does anybody has worked on UEC 2.0 ?
[17:31] <bhavesh> hello ?
[17:35] <jero> hello
[17:38] <jero> I have been experiencing several and quite frequent lockups (machine becomes like frozen for 3-5 minutes, my statistics show one cpu stuck at 100% and load climbs at 40-50 while system is unloaded) with  EC2 "m1.large" instances those last weeks, with lucid ami-fa01f193
[17:39] <jero> s/unloaded/not much loaded/
[17:47] <jero> anyone experienced that ?
[17:50] <bhavesh>  does anybody has worked on UEC 2.0 ?
[18:10] <kim0> jero: I think there was some bug that did that .. smoser would know about it
[18:10] <jero> kim0: ah!
[18:11] <jero> is smoser around ?
[18:11] <kim0> just wait around
[18:11] <jero> thanks !
[18:11] <jero> this is giving me white hair :)
[18:12] <kim0> hehe
[18:15] <smoser> jero, please open a bug (use ubuntu-bug /boot/vmlinuz-$(uname -r) from inside an instance)
[18:16] <smoser> and describe anything anything you can do to trigger it
[18:16] <smoser> and see if console output shows anything of interest (or dmesg if you can get it)
[18:16] <kim0> oh so it's not a known issue .. okie
[18:16] <smoser> load in a ec2 instance might not be 100% useful
[18:16] <smoser> well, there are kernel bugs.
[18:18] <jero> I opened a case at aws too
[18:21] <smoser> http://tinyurl.com/ec2-bugs-linux and http://tinyurl.com/ec2-bugs-linux-ec2 have list of bugs that are open on 'linux' or 'linux-ec2' and are tagged ec2-images
[18:22] <jero> thanks
[18:23] <smoser> jero, but please do open a bug. you can subscribe 'smoser' and stefan-bader-canonical
[18:23] <jero> smolyn: I used m1.large instances some time ago with lucid (other AMIs), and didn't have that issue
[21:14] <gtaylor_laptop> Anyone else notice that Ubuntu EC2 instances take -forever- to restart? Or get stuck and don't restart until you restart them a second time through the EC2 management console?
[22:02] <erichammond> gtaylor_laptop: What do you mean by "restart"?  Reboot?  stop/start? terminate/run?
[22:02] <gtaylor_laptop> erichammond: Reboot via the management console
[22:02] <gtaylor_laptop> erichammond: Though, it's done the same thing via SSH and 'shutdown -r now'