| Message: 97398 |
 |
BY: Ian Busching (ibusching)
DATE: 2012-01-16 22:28
SUBJECT: Errors copying MS Windows AMI across regions Hi, thanks for your services.
I am currently having an issue copying a MS Windows AMI from US-E to EU-W.
The first time I ran the script it gave the error: "Execution failed in status FailedState due to The key pair 'Key_Pair_Name' does not exist". After checking this board I created a new Key Pair for each region without any spaces/special characters and tried again. Unfortunately it gave the same error with the new key pair files/key pair names.
Below is the output from the second attempt:
Jan, 12 - 00:59:28: checking snapshot 'snap-32278159' accessibility...
Jan, 12 - 00:59:28: 'snap-32278159' accessible
Jan, 12 - 00:59:28: starting up instance to execute the script (AMI = ami-23f53c4a) ...
Jan, 12 - 00:59:29: Architecture of image ami-23f53c4a is i386. Use instance_type m1.small.
Jan, 12 - 00:59:30: Started instance i-a2f9a6c0. wait until it is ready...
Jan, 12 - 00:59:35: instance still starting up...
Jan, 12 - 00:59:41: instance still starting up...
Jan, 12 - 00:59:47: instance still starting up...
Jan, 12 - 00:59:53: instance is up and running
Jan, 12 - 00:59:53: going to create a new EBS volume from the specified snapshot...
Jan, 12 - 00:59:59: EBS volume vol-15a88878 is ready
Jan, 12 - 00:59:59: going to attach volume vol-15a88878 to instance i-a2f9a6c0 on device /dev/sdj...
Jan, 12 - 01:00:18: volume vol-15a88878 successfully attached
Jan, 12 - 01:00:18: connecting 'ec2-user' to ec2-50-17-49-193.compute-1.amazonaws.com...
Jan, 12 - 01:00:40: connected to ec2-50-17-49-193.compute-1.amazonaws.com [sudo]. OS installed is 2.6.35.14-97.44.amzn1.i686
Jan, 12 - 01:00:40: Retrieving '/' root device name...
Jan, 12 - 01:00:42: Using AWS name source device '/dev/sdj' and OS name '/dev/sdj'
Jan, 12 - 01:00:42: going to create a new EBS volume of size 30GB...
Jan, 12 - 01:00:49: EBS volume vol-19a98974 is ready
Jan, 12 - 01:00:49: going to attach volume vol-19a98974 to instance i-a2f9a6c0 on device /dev/sdk...
Jan, 12 - 01:01:07: volume vol-19a98974 successfully attached
Jan, 12 - 01:01:07: Using AWS name source device '/dev/sdk' and OS name '/dev/sdk'
Jan, 12 - 01:01:07: going to create filesystem on ec2-50-17-49-193.compute-1.amazonaws.com to /dev/sdk...
Jan, 12 - 01:01:25: ext3 filesystem system successfully created on device /dev/sdk
Jan, 12 - 01:01:25: going to mount /dev/sdk on /mnt/tmp_vol-19a98974...
Jan, 12 - 01:01:27: creating mount point /mnt/tmp_vol-19a98974...
Jan, 12 - 01:01:38: device /dev/sdk successfully mounted
Jan, 12 - 01:01:38: connecting 'ec2-user' to ec2-50-17-49-193.compute-1.amazonaws.com...
Jan, 12 - 01:01:41: connected to ec2-50-17-49-193.compute-1.amazonaws.com [sudo]. OS installed is 2.6.35.14-97.44.amzn1.i686
Jan, 12 - 01:01:41: going to start dumping and compressing source device '/dev/sdj' to '/mnt/tmp_vol-19a98974/snap-32278159.gz' file. This may take quite a time...
Jan, 12 - 02:06:07: dumping and compressing done (took 3866)s
Jan, 12 - 02:06:07: starting up instance to execute the script (AMI = ami-23f53c4a) ...
Jan, 12 - 02:06:08: Architecture of image ami-23f53c4a is i386. Use instance_type m1.small.
I then tried to run the script again today before posting here, but this time it seems to have hung at "Jan, 16 - 20:22:19: creating mount point /mnt/tmp_vol-25dcea48... ". The script has been running +2hrs and it has not moved past this point, although I do still see activity on the instance the script has created.
If I try to run the script again I get: "Execution failed in status Initial due to image ami-fbbe838f not found"
I suspect this has something to do with the other AMI still running, but wanted to check here before killing it. Don't see a way to stop the copy from the site, but obviously could terminate the instance.
Any ideas? Thanks. | |
Start New Thread
Errors copying MS Windows AMI across regions