Databases
StackOverflow2013
Postsdbo
POFailing to connect to ec2 using Rubber
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFailing to connect to ec2 using Rubber
    primarykey
    data
    text
    <p>I'm trying to upload my rails app to amazon ec2 using the Rubber gem (I'm following a <a href="http://railscasts.com/episodes/347-rubber-and-amazon-ec2" rel="nofollow">Railscasts tutorial</a>). Every time I run <code>cap rubber:create_staging</code> I'm unable to connect to the server. I've been trying everything possible to get this working but after a full day of trying I thought I'd post whats happening here.</p> <pre><code>Andrews-MacBook-Pro:blog andrew$ cap rubber:create_staging Respawning with 'bundle exec' triggering load callbacks * 2013-01-03 17:27:20 executing `rubber:init' * 2013-01-03 17:27:23 executing `rubber:create_staging' Hostname to use for staging instance [production]: Roles to use for staging instance [apache,app,collectd,common,db:primary=true,elasticsearch,examples,graphite_server,graphite_web,graylog_elasticsearch,graylog_mongodb,graylog_server,graylog_web,haproxy,mongodb,monit,passenger,postgresql,postgresql_master,web,web_tools]: * 2013-01-03 17:27:26 executing `rubber:create' * Security Group already in cloud, syncing rules: blog_production_production * Security Group already in cloud, syncing rules: blog_production_graylog_mongodb * Security Group already in cloud, syncing rules: blog_production_mongodb * Security Group already in cloud, syncing rules: blog_production_postgresql * Security Group already in cloud, syncing rules: blog_production_postgresql_master * Security Group already in cloud, syncing rules: blog_production_db * Security Group already in cloud, syncing rules: blog_production_app * Security Group already in cloud, syncing rules: blog_production_web * Security Group already in cloud, syncing rules: blog_production_haproxy * Security Group already in cloud, syncing rules: blog_production_elasticsearch * Security Group already in cloud, syncing rules: blog_production_monit * Security Group already in cloud, syncing rules: blog_production_common * Security Group already in cloud, syncing rules: blog_production_default * Security Group already in cloud, syncing rules: blog_production_graylog_elasticsearch * Security Group already in cloud, syncing rules: blog_production_apache * Security Group already in cloud, syncing rules: blog_production_passenger * Security Group already in cloud, syncing rules: blog_production_examples * Security Group already in cloud, syncing rules: blog_production_graphite_web * Security Group already in cloud, syncing rules: blog_production_graphite_server * Security Group already in cloud, syncing rules: blog_production_graylog_server * Security Group already in cloud, syncing rules: blog_production_collectd * Security Group already in cloud, syncing rules: blog_production_graylog_web * Security Group already in cloud, syncing rules: blog_production_web_tools ** Creating instance ami-eafa5883/m1.small/blog_production_default,blog_production_web,blog_production_web_tools,blog_production_production,blog_production_apache,blog_production_app,blog_production_passenger,blog_production_collectd,blog_production_common,blog_production_monit,blog_production_db,blog_production_postgresql,blog_production_postgresql_master,blog_production_elasticsearch,blog_production_examples,blog_production_graphite_server,blog_production_graphite_web,blog_production_graylog_elasticsearch,blog_production_graylog_mongodb,blog_production_mongodb,blog_production_graylog_server,blog_production_graylog_web,blog_production_haproxy/Default ** Instance production created: i-7b4f840a Waiting for instances to start.......................... ** Instance running, fetching hostname/ip data * 2013-01-03 17:28:37 executing `rubber:_allow_root_ssh' * executing "sudo -p 'sudo password: ' bash -l -c 'cp /home/ubuntu/.ssh/authorized_keys /root/.ssh/'" servers: ["23.20.130.97"] .... ** Failed to connect to 23.20.130.97, retrying * 2013-01-03 17:28:44 executing `rubber:_allow_root_ssh' * executing "sudo -p 'sudo password: ' bash -l -c 'cp /home/ubuntu/.ssh/authorized_keys /root/.ssh/'" servers: ["23.20.130.97"] . ** Failed to connect to 23.20.130.97, retrying * 2013-01-03 17:28:46 executing `rubber:_allow_root_ssh' * executing "sudo -p 'sudo password: ' bash -l -c 'cp /home/ubuntu/.ssh/authorized_keys /root/.ssh/'" servers: ["23.20.130.97"] . ** Failed to connect to 23.20.130.97, retrying * 2013-01-03 17:28:49 executing `rubber:_allow_root_ssh' * executing "sudo -p 'sudo password: ' bash -l -c 'cp /home/ubuntu/.ssh/authorized_keys /root/.ssh/'" servers: ["23.20.130.97"] etc </code></pre> <p>and then it seems to go into an infinite loop and trying to connect to the server like above every few minutes.</p> <p><strong>EDIT:</strong> I finally fixed this issue by reinstalling ruby + gems on my local machine. Still not sure what caused this.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USandmcgregor
    1. USandmcgregor
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POFailing to connect to ec2 using Rubber
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you able to connect to the ec2 instance manually via SSH?
      singulars
      1. POFailing to connect to ec2 using Rubber
      1. USregulatethis
    2. CO@regulatethis Yes I can. I've also downloaded the pem key into the ~/.ec2/ directory (it's in there with no extension and with the .pub extension) as the tutorial says.
      singulars
      1. POFailing to connect to ec2 using Rubber
      1. USandmcgregor
    3. COI have the same error... When I tried to ssh to the server it said to retry with 'ubuntu' user instead of 'root' That way I could log in. Then I changed my user to ubuntu "set :user, 'ubuntu'". But even that way the error persists... So if somebody can describe what is happening here then please do it.
      singulars
      1. POFailing to connect to ec2 using Rubber
      1. USBoti
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload