[00:36] <LyricHartley> stupid question, but I just don't see it....what is the syntax for the AWS_CREDENTIAL_FILE
[00:37] <LyricHartley> AWSAccessKeyId works for one
[00:37] <LyricHartley> but can't figure out the other
[00:37] <LyricHartley> tried versions of AWSSecretAccessKey
[00:37] <LyricHartley> don't see in docs
[00:38] <LyricHartley> ?
[00:42] <LyricHartley> appears to be AWSSecretKey
[13:25] <uvirtbot`> New bug: #412143 in ubuntu-on-ec2 "ec2-init init script has bad Required-Start header" [Low,Confirmed] https://launchpad.net/bugs/412143
[16:05] <ahasenack> guys, is the wiki the official and up-to-date source for the official ubuntu AMI names?
[16:05] <ahasenack> https://help.ubuntu.com/community/EC2StartersGuide#Getting%20the%20images specifically
[16:05] <ahasenack> I'm still running into the network bug during startup. The bug is in "fix released" state, but there is no AMI mentioned in the ticket
[16:06] <ahasenack> https://bugs.launchpad.net/vmbuilder/+bug/308530 is the bug
[16:06] <uvirtbot`> Launchpad bug 308530 in ubuntu-on-ec2 "Wait for network before downloading ssh credentials or user-data" [Medium,Fix released]
[16:20] <agussman> Would anyone care to hazard a guess as to why this is causing a segfault?  #  du -hc / | grep -P '\t/[^/]+$'
=== zul_ is now known as zul
[18:18] <ahasenack> agussman: check dmesg
[18:20] <agussman> ahasenack: thanks.  After playing around with it, I realized it was the grep that was causing problems but I could avoid using it by providing the --max-depth 1 option to du
[18:20] <ahasenack> agussman: the dmesg would be to check if there was any kernel panic or oops happening
[18:20] <ahasenack> bar that, yeah, it's just a user space bug in grep or du
=== jeremydei_ is now known as jeremydei
[22:14] <walski> Hi there
[22:14] <walski> I'm looking for an AMI to build a high load web server for static pages.
[22:14] <walski> It's just to test a load generator and must only run for about an hour
[22:15] <walski> so it would be nice to have something that comes pretty much pre configured
[22:15] <walski> high load means something about 100 req/sec
[22:15] <walski> can you give me a hint what would be a good image?
[22:16] <erichammond> walski: Since you're presumably using Ubuntu, it's easy to start with a clean server AMI and install Apache.
[22:16] <walski> is there a clean ubuntu image?
[22:17] <walski> looked at the comunity rep[ository
[22:17] <walski> but found only a lot of preconfigured stuff which i just does not need
[22:17] <erichammond> walski: What release (version) would you like to use?
[22:17] <walski> Doesn't matter ;)
[22:18] <walski> As I said it's more a fire and forget thing
[22:18] <walski> would take what comes as the easiest solution
[22:18] <erichammond> walski: I publish a number of Ubuntu releases on http://alestic.com which are pretty popular for production use.
[22:19] <erichammond> I'd recommmend picking a "server 32-bit" Hardy or Jaunty.
[22:19] <erichammond> I also list the AMIs published by Canonical.
[22:24] <erichammond> Then: apt-get update && apt-get upgrade -y && apt-get install -y apache2
[22:25] <erichammond> Drop your static files in /var/www and you should be set.
[22:29] <walski> thanks!
[22:30] <erichammond> If you find it can't perform to your expectations with m1.small, then upgrade to c1.medium which gives 5x the CPU for 2x the price.
[22:30] <erichammond> Then step up to a c1.xlarge (which requires 64-bit AMI)
[22:42] <walski> works great, thank you a lot!