[06:21] <koolhead11|> hi all
[09:02] <kim0> Morning everyone
[15:12] <koolhead17> kim0, awake?
[15:23] <kim0> koolhead17: yeah sure
[17:59] <navanjr> im having trouble adding a repository to my instance... i suspect it has to do with my cloud config.  Im not sure what questions to ask specificly...
[18:00] <navanjr> but im getting the following error:
[18:00] <navanjr> gpgkeys: HTTP fetch error 7: couldn't connect to host
[18:00] <navanjr> when i...  sudo add-apt-repository ppa:jerome-etienne/neoip
[18:06] <hazmat> navanjr, perhaps a transient error? can you reach launchpad from the instance?
[18:06] <hazmat> navanjr, specifically ppa.launchpad.net
[18:57] <smoser> navanjr, i suspect transient error
[18:58] <smoser> i just tested this user data:
[18:58] <smoser>  #cloud-config
[18:58] <smoser> apt_sources:
[18:58] <smoser>  - source: "ppa:jerome-etienne/neoip"
[19:14] <navanjr> i can resolve to ppa.launchpad.net and ping it from my instance
[19:16] <navanjr> also I get a "sudo: unable to resolve host ip-172-19-1-3" message whenever I apt-get anything...
[19:57] <smoser> navanjr, you're running on ec2 ?
[19:57] <smoser> and the suggestion was that it was a transient error, ie, if you did it again it would work
[19:58] <smoser> but you can try 'sudo apt-add-repository ppa:jerome-etienne/neoip' and it should work.
[19:58] <navanjr> private cloud uec
[19:59] <smoser> so try running the apt-add. it "should work" if not, then doing the same thing via cloud-config is also going to fail
[20:00] <navanjr> yeah, apt-add is what i was doing...  i have not tested it with userdata yet ... i guess i assumed it would do the same thing
[20:29] <SpamapS> smoser: so I may have figured out the problem with udev..
[20:29] <SpamapS> smoser: I am writing a test case today
[20:30] <smoser> navanjr, i tested that here, and it worked. so there is something network related if its not working for you.
[20:30] <smoser> SpamapS, what is it?
[20:30] <SpamapS> smoser: I *think* there's actually a brief period where the pipe is not actually open between the fork and the write
[20:30] <smoser> between what fork?
[20:30] <SpamapS> smoser: and it may every well be that the latency of fork and such have gotten low enough to expose it.
[20:32] <SpamapS> smoser: if thats the case, we actually need to add a 2-way channel so the parent will wait for the child's write before continuing.
[20:32] <SpamapS> smoser: the parent forks, then writes a message to the child
[20:32] <SpamapS> smoser: there's an open, shared pipe between them, but the child may not have actually finished even forking/duplicating itself by that point
[20:33] <smoser> its a filedescriptor ?
[20:35] <smoser> well, i'm interested in learning more. but feel free to get to work and ignore me for th emoment.
[21:15] <navanjr> is this the right place to ask about the CLC and IPTABLES
[21:18] <navanjr> I am struggling to find documentation to help me understand how i need to configure my CLC.  My instances can reach the internet but they are having issues with apt-get