=== zz_natorious is now known as natorious === natorious is now known as zz_natorious [13:40] Odd_Bloke, i think "use sectors". [13:41] smoser: Cool, that was my plan. :) [13:41] the one annoyance is that i'm not 100% certain that sectors is always 512 bytes [13:53] smoser: It looks like the reporting changes have broken the MAAS DataSource: https://launchpadlibrarian.net/215516689/cloud-init.log [13:53] smoser: That's attached to https://bugs.launchpad.net/cloud-init/+bug/1488507 [13:54] Odd_Bloke, right . looking at that now. [13:55] fudge [13:55] thats a packaging thing [13:55] i think === zz_natorious is now known as natorious === natorious is now known as zz_natorious === zz_natorious is now known as natorious [18:40] hi guys. How can I tell in the main system log if cloud-init ran? [18:40] or can I? [18:42] 'main'? usually you will want to check something like /var/log/cloud-init.log [18:42] and we're not all 'guys' ;-) [18:44] kwadronaut: ok, but what if I can't access /var/log/cloud-* ?? Are there indicators in the main syslog to at least indicate cloud-init's ran? [18:44] kwadronaut: The context is aws ec2 instances. Getting the console log is easy. Nothing else is. [18:46] boot log might have something, haven't looked at ec2 in a long time. stick around, someone else might know. [18:47] tks [20:02] gamename, "main system log" [20:02] systemctl ? [20:02] or upstart [20:03] smoser: ok [20:03] i'm asking. [20:03] which were you using ? [20:04] smoser: neither. I have an aws ec2 instance which I think may not have run the cloud init code. But, I can only get access to the console log of the aws instance. Nothing more. I'm locked out. Was looking for hints as to how I can start debugging. [20:05] smoser: One option on aws is to get the console log. That works. Was hoping for some indication in it ... [20:06] can you post the console log ? [20:06] if its ubuntu you should see cloud-init writing things to it. [20:06] smoser: yes. Standby ... [20:06] smoser: No, its CentOS 7 [20:08] i dont have a lot of experience there, testing a quick [20:08] heres a centos 6.6 with cloud-init: http://paste.ubuntu.com/12194874/ [20:08] see cloud-init in that log [20:09] smoser: Here's the log https://gist.github.com/gamename/0407dccb5af2d35c6061 [20:09] and heres a 7 http://paste.ubuntu.com/12194878/ [20:09] it'd seem likely that your networking didnt come pu [20:09] up [20:09] i guess. [20:10] smoser: yup. Based on your examples, I think that's the case . [20:11] the centos 7 log i showed is from a http://cloud.centos.org/centos/7/images/ image. [20:11] on openstack. i can't vouch for the correct (or useful) installation cloud-init on arbitrary ec2 image [20:11] smoser: Can they be imported into AWS as an AMI? [20:12] smoser: understood about vouching for the image. [20:12] maybe [20:12] i ran that one on a openstack. [20:12] i really dont know. [20:12] you could use ubuntu :) [20:12] and our images "just work" [20:13] smoser: Sorry, I'm stuck with CentOS 7. Lotsa reasons too icky to get into here. Well, that's a start. Thanks. [20:13] or debian, and ask in #debian-cloud ;-) [20:14] kwadronaut: Hmmmm ... there is a #centos-cloud channel I think. Worth a query to them too... [20:15] gamename: i'm happy in my debian-ubuntu comfort zone. [20:18] gamename, did you modify that image at all ? [20:18] or is it a "stock" image from some provider [20:19] if stock, then i'd ask the provider of the image === natorious is now known as zz_natorious === zz_natorious is now known as natorious