[09:26] <progre55> hi guys. when running an instance, I get these exceptions (http://pastie.org/1160744) on the node logs, and the instance instantly terminates. Any suggestions please?
[10:44] <progre55> anybody? after I restarted my nc, it's not discovered by the cc anymore.. in the cc logs I get this "could not be invoked (check NC host, port, and credentials)"
[10:44] <progre55> and also this "netInitTunnels(): in MANAGED-NOVLAN mode, priv interface 'eth0' must be a bridge, tunneling disabled"
[10:44] <progre55> any suggestions, please?
[13:22] <duxbuz> hello.... waht is ubuntu cloud
[13:44] <smoser> progre55, do your node controllers have hvm support ?
[13:44] <smoser> you can check by 'kvm-ok' on them
[13:57] <progre55> smoser: hey man =) thanks for the reply, I've been able to fix it already..
[13:57] <progre55> but honestly, no idea how
[13:57] <progre55> it got fixed on its own somehow =)
[13:57] <smoser> hm.m.
[13:58] <progre55> I was restarting it several times, deattaching and re-attaching the node, etc
[13:58] <progre55> but now I have another problem =)
[13:58] <progre55> I'm running an instance, and it's getting a public IP 192.168.2.37
[13:59] <progre55> but actually, my local IP range in the office is 172.16.xx.xx
[13:59] <progre55> so I dont have access to the instance from anywhere, and the instance doesnt have connection to the internet =)
[14:00] <progre55> I can only ssh into it from the eucalyptus server machine
[14:01] <progre55> I'm guessing it's because I had VNET_PUBLICIPS="192.168.1.37-192.168.1.77" in the conf
[14:02] <progre55> but now I've changed it to 172.16.xx.xx-... and even restarted the cc machine after it, but the instances are still assigned 192.168.1.37
[14:02] <progre55> smoser: any suggestions, please?
[14:03] <smoser> hmm..
[14:03] <smoser> well, the instances get their address via dhcp
[14:03] <smoser> so if you have a dhcp server on that network, it can be a race
[14:04] <smoser> and you instance might not even have the ip address that euca says it has.
[14:04] <progre55> oh.. and how do I check the actual IP address?
[14:04] <smoser> i'm not sure
[14:05] <progre55> and the dhcp on the network would not assign 192.168, cause the invalid IP range in the network starts with 172.16
[14:51] <progre55> how do you download an EMI from a command line?
[14:51] <progre55> cause I had downloaded it from the web-UI, and now it says it's "Installed", but I had "disabled" it from the Images tab
[14:52] <progre55> and it's not there anymore
[16:06] <progre55> my instances are running and everything is okay, but they do not have internet connection, and cannot be reached from outside the cc machine..
[16:49] <TeTeT> progre55: you can grab an EMI from http://uec-images.ubuntu.com/ and then use uec-publish-tarball to upload it
[16:51] <progre55> TeTeT: yep, I've done that already =) thanks
[21:18] <veenenen> random bug
[21:18] <veenenen> http://paste.ubuntu.com/494924/
[21:18] <veenenen> when I launch an auto scaling group on ec2, the second one I launch goes down after 10 minutes
[21:19] <veenenen> and it's complete unreponsive
[21:19] <veenenen> the only indication the server gives is generating 2 ssh server keys
[21:31] <veenenen> oh yeah, and this is uec 32bit maverick running on ec2
[21:33] <smoser> veenenen, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/567334
[21:33] <smoser> if you reboot it might come back up
[21:35] <smoser> s/might/likely will/
[21:37] <veenenen> the instance is actually available at first
[21:38] <veenenen> but after 30 minutes the load drops to 0 suddenly
[21:39] <veenenen> i know I said 10 minutes before, but I just got around to checking the graph and it was actually 30 minutes. Well, 31 minutes to be exact.
[21:39] <smoser> well, its the same bug. those messages are not good.
[21:39] <veenenen> ok
[21:40] <smoser> i'd say it started after about 32 minutes of being up
[21:40] <smoser> to be more precise
[21:40] <smoser> 1920.220071 seconds
[21:41] <veenenen> haha, sorry.
[21:42] <veenenen> i just got back from a meeting to this
[21:52] <smoser> veenenen, what image were you booting ?
[21:52] <veenenen> the same one from yesterday
[21:52] <smoser> i'm being asked if you have console=hvc0. on /proc/cmdline.
[21:52] <smoser> so you probably dont
[21:53] <veenenen> how would I check that?
[21:53] <smoser> cat /proc/cmdline
[21:53] <smoser> but you wont have it
[21:53] <veenenen> ok, yeah
[21:54] <smoser> (you should add that if you want to maintain this image, add it in /boot/grub/menu.lst
[21:57] <veenenen> just add that anywhere?
[22:03] <smoser> ## additional options to use with the default boot option, but not with the
[22:03] <smoser> ## alternatives
[22:03] <smoser> ## e.g. defoptions=vga=791 resume=/dev/hda5
[22:03] <smoser> # defoptions=console=hvc0
[22:03] <smoser> yours probably has empty 'defoptions'
[22:03] <smoser> add that, then run 'sudo update-grub-legacy-ec2'
[22:08] <smoser> veenenen, ^
[22:11] <veenenen> is cloud-init uncommenting that line?
[22:12] <veenenen> Sorry if this is rudimentary. I haven't worked much with grub directly.