Support Questions
Find answers, ask questions, and share your expertise

Re: Metron setup - full-dev-platform

Explorer

@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

Re: Metron setup - full-dev-platform

Explorer

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

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

Re: Metron setup - full-dev-platform

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