Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Metron setup - full-dev-platform

avatar
Master Mentor

ansible 2.0.0.2

TASK [elasticsearch : Configure Elasticsearch] *********************************

changed: [node1] => (item={u'regexp': u'^# *cluster\\.name:', u'line': u'cluster.name: metron'})

changed: [node1] => (item={u'regexp': u'^# *network\\.host:', u'line': u'network.host: _eth1:ipv4_'})

changed: [node1] => (item={u'regexp': u'^# *discovery\\.zen\\.ping\\.unicast\\.hosts:', u'line': u'discovery.zen.ping.unicast.hosts: [ node1 ]'})

changed: [node1] => (item={u'regexp': u'^# *path\\.data', u'line': u'path.data: /data1/elasticsearch,/data2/elasticsearch'})

TASK [elasticsearch : Create Logrotate Script for Elasticsearch] ***************

ok: [node1]

TASK [metron_elasticsearch_templates : include] ********************************

included: /private/var/root/incubator-metron/metron-deployment/roles/metron_elasticsearch_templates/tasks/load_templates.yml for node1

TASK [metron_elasticsearch_templates : Start Elasticsearch] ********************

ok: [node1]

TASK [metron_elasticsearch_templates : Wait for Elasticsearch Host to Start] ***

ok: [node1]

TASK [metron_elasticsearch_templates : Wait for Index to Become Available] *****

fatal: [node1]: FAILED! => {"failed": true, "msg": "ERROR! The conditional check 'result.content.find(\"green\") != -1 or result.content.find(\"yellow\") != -1' failed. The error was: ERROR! error while evaluating conditional (result.content.find(\"green\") != -1 or result.content.find(\"yellow\") != -1): ERROR! 'dict object' has no attribute 'content'"}

PLAY RECAP *********************************************************************

node1 : ok=66changed=9 unreachable=0 failed=1

Ansible failed to complete successfully. Any error output should be

visible above. Please fix these errors and try again.

xav-us-lap1732:full-dev-platform root#

1 ACCEPTED SOLUTION

avatar
Contributor

@Neeraj Sabharwal

Hi Neeraj,

Do you see any response when you put the following url in your browser :- http://node1:9200/_cat/health

For example you should see some output like this :- 1467897265 13:14:25 metron yellow 1 1 5 5 0 0 5 0 - 50.0%

it might be a case where the system is slow and it's taking more time than expected.

If it's due to slowness then you might have to increase the timeout in the following file and rerun the deployment :-

metron-deployment/roles/metron_elasticsearch_templates/tasks/load_templates.yml

Regards,

Neha

View solution in original post

13 REPLIES 13

avatar
Contributor

@Neeraj Sabharwal

Hi Neeraj,

You can look up my comment for the following thread incase you still facing the same issue :-

https://community.hortonworks.com/questions/45060/metron-errors-while-running-vagrant-up-provision.h...

Regards,

Neha

avatar
Contributor

I fixed this issues by downgrading Vagrant 1.8.1. There is a bug in Vagrant 1.8.5.

avatar
New Contributor

The reason in 2 records in /etc/hosts for node1:

cat /etc/hosts
127.0.0.1       node1   node1

## vagrant-hostmanager-start
192.168.66.121  node1

## vagrant-hostmanager-end

127.0.0.1   localhost


For python requests package node1 is resolved as 127.0.0.1 and it gets "socket.error: [Errno 111] Connection refused"

For curl (and I believe for browser) node1 is resolved as below:

[vagrant@node1 ~]$ curl -v http://node1:9200/_cat/health
* About to connect() to node1 port 9200 (#0)
*   Trying 127.0.0.1... Connection refused
*   Trying 192.168.66.121... connected
* Connected to node1 (192.168.66.121) port 9200 (#0)

To fix it you can just remove "127.0.0.1 node1 node1" from /etc/hosts and run "vagrant provision" again

avatar
Explorer

Hey, even I am not able to setup Metron on a single node VM, it is giving me heartbeat lost error and when I check ambari-agent logs it gives me SSL certificate verify failed

Need Help!! @Vladimir Shlkhtn