problem connecting to amazon ec2 instance after copying it to another region

Question

I have a running instance on us-east which I can connect to. It is an EBS volume based on one of the ubuntu 10.10 server AMIs.

It was created by starting a default image, and then customizing it and then saving that as an AMI. I then terminated the original and ran an image of the AMI, and was able to connect.

At this point I used cloudy scripts "copy ami to different region" script (at https://cloudyscripts.com/tool/show/5) to copy it to us-west. This script copies the EBS

Once there, when I run it, I am unable to connect. I am trying to connect to it exactly the same way as I did in us-east. That is,

ssh -i <KEYFILE I USED TO START INSTANCE> ubuntu@<PUBLIC_DNS_NAME>

but this results in a timeout with error "bad file number"

I went back to the original image on us-east and restored it, and was still able to connect to it.

The instance is launched in security group: default which is configured this way in both regions:

protocol: tcp from port: 22 to port:22 source CDR 0.0.0.0/0

I really can't see any difference between the two setups - both are launched from an AMI, which should be the same one, but one works and the other doesn't. Any ideas?

Answer 1

aha, it turned out that the instance was crashing upon restart due to kernel mismatch. I found out from checking the console output.