StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15034498
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-22T22:48:11.260
FavoriteCount
0
LastActivityDate
2013-02-25T18:10:26.160
LastEditDate
2013-02-25T18:10:26.160
LastEditorUserId
677322
OwnerUserId
677322
ParentId
14282825
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I ran into this problem also. After a couple of EC2 instance deploys I ended up getting stuck (it literally worked 1 night, and then got stuck the next morning). My quick fix was to log into Amazon EC2, delete the keypair associated to my deployment.. IE: <pre><code>EC2 = Fog::Compute.new provider: 'AWS', region: REGION, aws_access_key_id: AWS_ACCESS_KEY, aws_secret_access_key: AWS_SECRET_KEY Fog.credential = waffles s = EC2.servers.bootstrap image_id: AMI_ID, flavor_id: FLAVOR_ID, private_key_path: '~/.ssh/id_rsa', public_key_path: '~/.ssh/id_rsa.pub', tags: { Name: TAGGED_NAME }, username: ROOT_USER </code></pre> This will create a key pair called "fog_waffles b6:21:d1:3d:2b:b9:e7:48:b9:75:50:3f:03:5b:fb:85". Delete it and you should be able to move forward. From what I can tell the keypair doesn't get updated/replaced if you create a new instance with the same keypair name. If you delete that instance, and then create a new instance using a new keypair with the same name it seems to run into problems. More on <a href="http://docs.aws.amazon.com/AWSSecurityCredentials/1.0/AboutAWSCredentials.html#EC2KeyPairs" rel="nofollow">EC2 keypairs</a> Addendum The version of fog I'm using is 1.9. If you have multiple people creating instances, you might want to go with something like this: <pre><code>EC2 = Fog::Compute.new provider: 'AWS', region: REGION, aws_access_key_id: AWS_ACCESS_KEY, aws_secret_access_key: AWS_SECRET_KEY Fog.credential = waffles s = EC2.servers.bootstrap image_id: AMI_ID, flavor_id: FLAVOR_ID, private_key_path: '~/.ssh/id_rsa', public_key_path: '~/.ssh/id_rsa.pub', tags: { Name: TAGGED_NAME }, username: ROOT_USER EC2.delete_key_pair("fog_waffles") </code></pre> This will make sure that the key pair never runs into a conflict. It's OK to delete it since it's only needed for the deployment of the instance. Fog drops your public key into authorized_keys once the instance is deployed, which allows you to access the instance. Another option would be to change Fog.credential to be unique for each user (instead of deleting it). IE: <pre><code>Fog.credential = waffles_ryan </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFog hangs on Fog::Compute.servers.bootstrap
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USryanjones
UserOwnerUserId
1. USryanjones
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFog hangs on Fog::Compute.servers.bootstrap
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.