question Re: Metron setup - full-dev-platform in Archives of Support Questions (Read Only)

Metron setup - full-dev-platform

nsabharwal — Thu, 07 Jul 2016 18:58:14 GMT

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#

Re: Metron setup - full-dev-platform

nsabharwal — Thu, 07 Jul 2016 19:08:14 GMT

@Neha Sinha

Re: Metron setup - full-dev-platform

nsinha — Thu, 07 Jul 2016 20:19:03 GMT

@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

Re: Metron setup - full-dev-platform

nsabharwal — Thu, 07 Jul 2016 20:44:07 GMT

@Neha Sinha Yes

1467899208 13:46:48 metron green 1 1 0 0 0 0 0 0 - 100.0%

Re: Metron setup - full-dev-platform

nsabharwal — Thu, 07 Jul 2016 20:50:18 GMT

@Neha Sinha I increased the timeout to 1300 but no luck.

Re: Metron setup - full-dev-platform

nsabharwal — Thu, 07 Jul 2016 22:37:29 GMT

xav-us-lap1732:scripts root# ./platform-info.sh

Metron 0.2.0BETA

* master

commit d3257a79d0a853ed511c1231ab79a2bfcc48603f

Author: nickwallen <nick@nickallen.org>

Date: Mon Jun 27 15:34:20 2016 -0700

METRON-259 Using 'any' for Snort's HOME_NETWORK (nickwallen) closes apache/incubator-metron#176

metron-deployment/roles/metron_elasticsearch_templates/tasks/load_templates.yml | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)

ansible 2.0.0.2

config file =

configured module search path = Default w/o overrides

Vagrant 1.8.4

Python 2.7.10

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)

Maven home: /usr/local/Cellar/maven/3.3.9/libexec

Java version: 1.8.0_92, vendor: Oracle Corporation

Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_92.jdk/Contents/Home/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "mac os x", version: "10.11.5", arch: "x86_64", family: "mac"

Darwin xav-us-lap1732.local 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

xav-us-lap1732:scripts root#

Re: Metron setup - full-dev-platform

nallen — Fri, 08 Jul 2016 01:21:19 GMT

If I am not mistaken, this is typically the exact error that you see when you are using an Ansible version that is not 2.0.0.2. Are you sure that when you upgraded `setuptools` (I see that you did this in another HCC thread) that the Ansible version did not also get quietly upgraded? I've seen this happen before.

Re: Metron setup - full-dev-platform

nsabharwal — Fri, 08 Jul 2016 05:13:43 GMT

@nallen I have pasted the platform.sh output in my previous comment.

xav-us-lap1732:scripts root# ./platform-info.sh

Metron 0.2.0BETA

* master

commit d3257a79d0a853ed511c1231ab79a2bfcc48603f

Author: nickwallen <nick@nickallen.org>

Date: Mon Jun 27 15:34:20 2016 -0700

METRON-259 Using 'any' for Snort's HOME_NETWORK (nickwallen) closes apache/incubator-metron#176

metron-deployment/roles/metron_elasticsearch_templates/tasks/load_templates.yml | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)

ansible 2.0.0.2

config file =

configured module search path = Default w/o overrides

Re: Metron setup - full-dev-platform

nsinha — Thu, 14 Jul 2016 16:13:32 GMT

@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.html#answer-45145

Regards,

Neha

Re: Metron setup - full-dev-platform

jmeyer — Sat, 30 Jul 2016 03:30:16 GMT

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

Re: Metron setup - full-dev-platform

pcr4ft — Tue, 06 Sep 2016 16:26:09 GMT

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

Re: Metron setup - full-dev-platform

gauravb117 — Wed, 06 Dec 2017 16:40:44 GMT

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

Re: Metron setup - full-dev-platform

gauravb117 — Wed, 06 Dec 2017 16:43:08 GMT

@nallen

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!!

Re: Metron setup - full-dev-platform

gauravb117 — Wed, 06 Dec 2017 16:43:12 GMT

@nallen

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!!