AWS unreachable error when executing Metron Installer

[#1]

I'm following the instructions for installing Metron here: https://github.com/apache/incubator-metron/tree/master/deployment/amazon-ec2

In the ansible.log, I'm seeing the following error during the ansible [Setup] task:

2016-03-24 03:46:50,950 p=62171 u=gvetticaden |  TASK [setup] *******************************************************************

2016-03-24 03:46:51,893 p=62171 u=gvetticaden |  fatal: [ec2-54-191-176-45.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:51,895 p=62171 u=gvetticaden |  fatal: [ec2-54-186-187-148.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:51,913 p=62171 u=gvetticaden |  fatal: [ec2-54-201-6-61.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:51,915 p=62171 u=gvetticaden |  fatal: [ec2-54-191-196-153.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:51,989 p=62171 u=gvetticaden |  fatal: [ec2-54-201-176-11.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:52,021 p=62171 u=gvetticaden |  fatal: [ec2-54-191-12-47.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:52,173 p=62171 u=gvetticaden |  fatal: [ec2-54-201-9-33.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:52,175 p=62171 u=gvetticaden |  fatal: [ec2-54-201-175-153.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:52,308 p=62171 u=gvetticaden |  fatal: [ec2-54-201-198-3.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

2016-03-24 03:46:52,489 p=62171 u=gvetticaden |  fatal: [ec2-54-186-178-244.us-west-2.compute.amazonaws.com]: UNREACHABLE! => {"changed": false, "msg": "SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue", "unreachable": true}

How do I resolve this?

[#2 · Accepted solution]

This is primarly caused because the path to the metron code is too long. You can solve this problem by shortening the path or changing the control_path

from

control_path = %(directory)s/%%h-%%p-%%r

to

control_path = %(directory)s/%%C

[#3]

You may also see those types of errors present as:

SSH Error: unix_listener: "/really/long/path/hostname.tempcharacters" too long for Unix domain socket

Same fix as above, shorten the path to your deployment scripts or modify the control_path in ansible.cfg as @George Vetticaden indicated above. in

[#4]

Also incase anyone else comes across this, the file you need to modify from the root of your metron dir is:

./deployment/amazon-ec2/ansible.cfg