- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
EC2 hosts unreachable
- Labels:
-
Apache Metron
Created 05-02-2016 08:55 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting the following error when running ansible-playbook -i ec2.py playbook.yml.
TASK [Sanity check Metron web] ************************************************* fatal: [localhost -> localhost]: FAILED! => {"changed": false, "elapsed": 20, "failed": true, "msg": "Timeout when waiting for ec2-52-39-145-200.us-west-2.compute.amazonaws.com:5000"} to retry, use: --limit @playbook.retry PLAY RECAP ********************************************************************* ec2-52-26-145-189.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-33-71-234.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-34-108-164.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-36-240-171.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-37-137-111.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-38-193-214.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-39-145-200.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-39-201-67.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-39-205-252.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 ec2-52-39-88-236.us-west-2.compute.amazonaws.com : ok=2 changed=0 unreachable=1 failed=0 localhost : ok=33 changed=16 unreachable=0 failed=1
I updated the ansible.cfg as outline here https://community.hortonworks.com/questions/24344/aws-unreachable-error-when-executing-metron-instal... to fix similar issue but still getting the same error.
Created 05-06-2016 09:47 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This looks like basic ssh connectivity is having an issue. Some things to try:
Verify that ssh centos@<any-ec2-host> works.
If it does not, run ssh -vvv centos@<any-ec2-host> to troubleshoot the issue.
If you're running a custom ~/.ssh/config, make sure that you're not specifying a non-default (id_rsa) key.
Created 05-02-2016 09:16 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried deleting the id_rsa.pub file and re-created it but still getting the error.
I created the ec2.py file where it's got the hostnames of all ec2 instances. I re-run the command with --limit @playbook.retry but not getting any results.
ansible-playbook -i ec2.py playbook.yml --limit @playbook.retry [WARNING]: Host file not found: ec2.py [WARNING]: provided hosts list is empty, only localhost is available PLAY [localhost] *************************************************************** skipping: no hosts matched PLAY [ec2] ********************************************************************* skipping: no hosts matched PLAY [ec2] ********************************************************************* skipping: no hosts matched PLAY [ec2] ********************************************************************* skipping: no hosts matched PLAY [ambari_*] **************************************************************** skipping: no hosts matched PLAY [ambari_master] *********************************************************** skipping: no hosts matched PLAY [ambari_slave] ************************************************************ skipping: no hosts matched PLAY [ambari_master] *********************************************************** skipping: no hosts matched PLAY [ec2] ********************************************************************* skipping: no hosts matched PLAY [metron] ****************************************************************** skipping: no hosts matched PLAY [hadoop_client] *********************************************************** skipping: no hosts matched PLAY [search] ****************************************************************** skipping: no hosts matched ec2-52-25-211-42.us-west-2.compute.amazonaws.com PLAY [mysql] ******************************************************************* skipping: no hosts matched PLAY [ambari_slave] ************************************************************ skipping: no hosts matched PLAY [sensors] ***************************************************************** skipping: no hosts matched PLAY [enrichment] ************************************************************** skipping: no hosts matched PLAY [web] ********************************************************************* skipping: no hosts matched PLAY [localhost] *************************************************************** skipping: no hosts matched PLAY RECAP *********************************************************************
Created 05-02-2016 10:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could you elaborate on what you meant by creating the ec2.py file? That is a file that ships with Ansible which it uses to dynamically populate the host names for the roles in the play.
Created 05-03-2016 02:04 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I re-run the ansible playbook command with this option '--limit @playbook.retry', it's saying ec2.py file is not found and subsequent messages relates to ec2 hosts not found in the file. So i went ahead and created the ec2.py file with the hostnames separated by new line. It's probably a different issue just don't know what it is.
Created 05-03-2016 09:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You do not want to create an ec2.py file. That will certainly break things good. Please outline exactly what you do step-by-step when you 'start from scratch'. That should allow us to help more. Thanks!
Created 05-03-2016 07:52 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting this consistent error even after starting from scratch 3 times.
Created 05-04-2016 12:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@nallen Here are the steps I did the first time of deployment and subsequent retries.
1. Followed the steps here https://community.hortonworks.com/articles/26030/apache-metron-deployment-first-steps-in-the-cloud.h... to spin up EC2 instances for Metron.
2. I've got all the prerequisites nailed down with no issues.
3. After doing all the steps to deploy Metron from the above blog, it fails after running this command ansible-playbook -i ec2.py playbook.yml .
4. I wiped out the EC2 vms and re-run the command ansible-playbook -i ec2.py playbook.yml. I'm still getting the same error.
5. Tried running mvn package-DskipTests and re-run ansible-playbook -i ec2.py playbook.yml. Same issue.
Created 05-04-2016 01:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you sure that you exported this environment variable?
export EC2_INI_PATH=conf/ec2.ini
Created 05-04-2016 06:24 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. I have this configured prior to running the playbook command.
Created 05-04-2016 01:17 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recently added a shell script to make the process easier and to help catch common errors. If you're bold enough to try master, I'd love to see if that works for you.
If you are able to launch EC2 hosts, with your Amazon credentials, then you can start here:
https://github.com/apache/incubator-metron/tree/master/metron-deployment/amazon-ec2#deploy-metron
Thanks for giving this a go!
