@Jon Zeolla - is on the right track. Your Kafka broker seems to have died and as a result, the Metron service start process cannot contact it to create the topics it needs. I'd recommend either using Metron's Full-Dev environment. If you're determined to get it running on the Sandbox, you'll need to do a resource sizing activity to make sure all the services can live in the amount of memory available to the container. ... View more

It looks like Yaf is sending some ipv6 traffic. The Yaf parser is only setup for ipv4. Try adding --ip4-only to the yaf startup script (/opt/yaf/start-yaf.sh). Please let me know if that works and we can open up a JIRA to address it. Thanks! -David... ... View more

Hi, It seems that the Ambari client gets unhappy when you ask it to start services and they are all started. I have opened METRON-466 to track it. In the meantime, you should be able to comment out lines 34-42 in metron-deployment/roles/ambari_config/start_hdp.yml to get you going. I hope to have a fix up shortly. Thanks! -D... ... View more

This wiki should describe the process. ... View more

That error is often caused by running a version of Ansible that is not 2.0.0.2. Could you run incubator-metron/metron-deployment/scripts/platform-info.sh and verify that the versions output match Required Versions? ... View more

It looks like Elasticsearch is down. From node1, have you done a 'sudo service elasticsearch status' to verify? ... View more

The above answer gives a lot of good detail, but for what you're trying to do, the WARN messages are actually okay. Though, I'll be happy when they're gone. If you run /usr/metron/0.2.0BETA/bin/zk_load_configs.sh -i /usr/metron/0.2.0BETA/config/zookeeper -m DUMP -z hostname:2181 you should see the changes you PUSHed. ... View more