[Bug 939212] Re: AMI created from latest i386 Lucid image fails to boot
Scott, I just cleaned everything up and tried again using your steps above (for installing the multiverse package) and everything seems to be working now. I'm quite certain I did previously first remove the installed ec2 tools and then apt-get update and reinstall, so I'm not sure what went wrong. The only difference I can see is that I had added multiverse to only one of the repos (backports or updates, but not both) whereas you added it to all of them. chetan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939212] Re: AMI created from latest i386 Lucid image fails to boot
Scott, I just tested the version in lucid-backports and it doesn't work either. The version in the PPA works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939212] Re: AMI created from latest i386 Lucid image fails to boot
Eric, it looks like you're right -- the version of the EC2 tools contained in multiverse is over 4 years old (1.3-45758 20071010). I manually downloaded the latest version from Amazon and re-bundled and that did the trick. I see that the newer versions are in Precise -- any reason these can't also be provided for Lucid? It's pretty badly broken as is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 939212] [NEW] AMI created from latest i386 Lucid image fails to boot
Public bug reported: I bundled an image based on ami-809a48e9 (latest i386 lucid image) and it will not boot. It fails with the following error in the console: http://pastebin.com/raw.php?i=2m16AfFs I got the same error with the AMI 2-3 releases before this one as well. AMIs from the middle of last year did not have the same problem. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: udisks (not installed) ProcVersionSignature: User Name 2.6.32-342.43-ec2 2.6.32.52+drm33.21 Uname: Linux 2.6.32-342-ec2 i686 Architecture: i386 Date: Wed Feb 22 21:54:59 2012 Ec2AMI: ami-809a48e9 Ec2AMIManifest: ubuntu-us-east-1/images/ubuntu-lucid-10.04-i386-server-20120221.manifest.xml Ec2AvailabilityZone: us-east-1c Ec2InstanceType: c1.medium Ec2Kernel: aki-407d9529 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: udisks Symptom: storage Title: Internal hard disk partition cannot be mounted manually ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939212 Title: AMI created from latest i386 Lucid image fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/939212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708920] Re: Strange 'fork/clone' blocking behavior under high cpu usage on EC2
Robert, Can you confirm what CPU is running on that node? The Librato guys have apparently narrowed it down to only happening on the Intel E5507. See this blog post for more: https://silverline.librato.com/blog/main/EC2_Users_Should_be_Cautious_When_Booting_Ubuntu_10_04_AMIs I checked one of our problem nodes that's still up and sure enough, it's running on an E5507. We have another node using the same CPU but with the same test kernel that was posted by Stefan above. So far, it looks ok, but we haven't put too much load on it yet and it's only been about 4 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/708920 Title: Strange 'fork/clone' blocking behavior under high cpu usage on EC2 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
