instance had no console output

Hi Scott,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 588725

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I really think this is related to bug 588715 . And I really think its hypervisor / aws failure.
I saw it reported on forums at http://developer.amazonwebservices.com/connect/thread.jspa?threadID=52656&tstart=0 . I asked to see what kernel/ami was being run.

It appears that this is happening more frequently now. awstrial has been using the same kernel since launch. At the beginning of this maverick offering, there were rarely any such failures. Yesterday I looked at 9 instances, of them 6 did not have console output (that 6 includes 1 that had "post-shutdown only" -- bug 588715).

Marking Natty as Won't Fix for now. Can you confirm this is an issue still in Natty? I have left the development task open so that this issue stays on our radar.

Thanks!

~JFo

@Scott

Do you happen to know if this is still an issue with Oneiric?

As I've stated elsewhere, I really think its a hypervisor bug, something beyond Ubuntu's control.

Amazon is asking for users that see this bug report it on the AWS Forums.

Please post instance ID and AMI ID in your forum post.

https://forums.aws.amazon.com/forum.jspa?forumID=30

per kirkland in ubuntu-server irc just now:
<kirkland> smoser: fyi, i just launched a precise t1.micro, it's up and running, but 30 minutes later, no console output

so i marked this as affecting precise.

I've posted a thread at https://forums.aws.amazon.com/thread.jspa?threadID=86174 . If you see this, please append the requested data to that thread.

Possibly worth mentioning... I subsequently started another instance, which did come up and run just fine. Until I tried to apt-get install something, and then I started hanging on:
0% [Connecting to us-east-1.ec2.archive.ubuntu.com (10.210.205.172)]

I ctrl-c cancelled that operation, and then retried, and the install worked just fine.

So I wonder if perhaps a dead or non-responsive archive might cause ubuntu instances to not boot all the way?

Troublesome ami and id:

RESERVATION r-46926926 357813986684 default
INSTANCE i-f700a492 ami-051acb6c terminated ec2-keypair 0 t1.micro 2012-01-31T21:53:35+0000 us-east-1d aki-825ea7eb monitoring-disabled ebs paravirtual xen sg-d5d135bc default

Again. This time, a cc2.8xlarge.

us-east-1/hvm/ubuntu-precise-alpha1-amd64-server-20111130
i-5fbc163a

RESERVATION r-9e4b89fe 357813986684 default
INSTANCE i-5fbc163a ami-11dd1678 ec2-72-44-50-148.compute-1.amazonaws.com ip-10-58-113-227.ec2.internal running ec2-keypair 0 cc2.8xlarge 2012-02-02T17:07:26+0000 us-east-1a monitoring-disabled 72.44.50.148 10.58.113.227 ebs hvm xen sg-d5d135bc default
BLOCKDEVICE /dev/sda1 vol-58986d34 2012-02-02T17:07:41.000Z

Happened again:

RESERVATION r-9a5391fa 357813986684 default
INSTANCE i-718a2014 ami-11dd1678 ec2-184-72-183-147.compute-1.amazonaws.com ip-10-58-6-213.ec2.internal shutting-down ec2-keypair 0 cc2.8xlarge 2012-02-02T17:15:06+0000 us-east-1a monitoring-disabled 184.72.183.147 10.58.6.213 ebs hvm xen sg-d5d135bc default
BLOCKDEVICE /dev/sda1 vol-7c867310 2012-02-02T17:15:22.000Z

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

natty has seen the end of its life and is no longer receiving any updates. Marking the natty task for this ticket as "Won't Fix".

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release