Member since
06-20-2016
13
Posts
2
Kudos Received
0
Solutions
10-24-2016
08:29 AM
I am facing this same problem. Did you find any solution to this problem?
... View more
08-25-2016
09:34 AM
while creating threat-intel hits count panel, the "is_alert = true" search is unable to show log visualization.
... View more
Labels:
07-27-2016
06:03 AM
Hi @David Lyle - I thin you wanted to mention 2812 port for monit. The enrichment topology says "execution failed".
... View more
07-25-2016
10:34 AM
I have installed single node Metron 0.2.0beta. Kafka is showing all the topics as listed in the metron docs. I have running squid topology but it is unable to generate enrichment topology. Kindly suggest.
... View more
Labels:
07-21-2016
05:19 AM
I have followed mainly below link https://cwiki.apache.org/confluence/display/METRON/2016/04/25/Metron+Tutorial+-+Fundamentals+Part+1%3A+Creating+a+New+Telemetry Also followed few others https://cwiki.apache.org/confluence/display/METRON/Adding+a+New+Telemetry+Data+Source https://community.hortonworks.com/articles/30291/adding-new-telemetry-data-source-to-apache-metron.html https://github.com/apache/incubator-metron/tree/master/metron-deployment/vagrant/full-dev-platform
... View more
07-20-2016
07:44 AM
# ./platform-info.sh Metron 0.2.0BETA fatal: Not a git repository (or any of the parent directories): .git -- ansible 2.0.0.2 config file = configured module search path = Default w/o overrides -- Vagrant 1.8.1 -- Python 2.6.6 -- Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30) Maven home: /opt/apache-maven-3.3.9 Java version: 1.8.0_60, vendor: Oracle Corporation Java home: /opt/jdk1.8.0_60/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-573.el6.x86_64", arch: "amd64", family: "unix" -- Linux metron.lesl.com 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
... View more
Labels:
07-11-2016
06:43 PM
I have installed with centos6.7 with Java 1.8.0_60, virtualbox5.0-5.0.16, maven 3.3.9, ansible 2.0.0.2, vagrant 1.8.1, python 2.7 and metro 0.2.0beta. Share the output of ./platform-info.sh.
... View more
07-01-2016
08:01 AM
1 Kudo
I have a an existing HDP 2.4 cluster with below mentioned details. node1 & node2 are masters in HA setup node3, 4, 5, 6 are datanodes node1, 2, 3 are journal nodes node4, 5, 6 are zookeeper nodes node7 is Ambari server node12 is client node 8, 9, 10, 11 are metron nodes (search, web & installer) Services Node1: Namenode, History Server, Resource Manager, Timeline Server Node2: HBase Master, Storm UI, Spark History, DRPC, Nimbu, Graphana, Nfs Gateway, Hive Server, Hive Metastore, WebHCat, Hive client Node3-6: Datanode, Kafka broker, Region Server, NodeManager, Supervisor Node7: Ambari server Node12: HDFS Client, MR2 Client, YARN Client, Zookeeper Client, Tez Client, HCat Client, Pig Client, HBase Client, Sqoop Client Node7: Netflow / YAF probe, BRO probe, SNORT probe, PCAP probe Node8 & Node9: Metron Search Node10: Metron Web Node11: Metron Installer I get the below error while issuing ansible-playbook command. [root@2da14a90fa00 playbooks]# ansible-playbook -i /root/incubator-metron/metron-deployment/inventory/$INSTALL_CONF_DIRECTORY metron_install.yml --skip-tags="solr"
PLAY ***************************************************************************
skipping: no hosts matched
PLAY ***************************************************************************
skipping: no hosts matched
PLAY ***************************************************************************
TASK [setup] *******************************************************************
fatal: [node1]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node8]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node6]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node7]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node3]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node4]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node11]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node10]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node5]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node9]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
fatal: [node12]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
TASK [setup] *******************************************************************
fatal: [node2]: UNREACHABLE! => {"changed": false, "msg": "ERROR! 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}
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY ***************************************************************************
PLAY RECAP *********************************************************************
node1 : ok=0 changed=0 unreachable=1 failed=0
node10 : ok=0 changed=0 unreachable=1 failed=0
node11 : ok=0 changed=0 unreachable=1 failed=0
node12 : ok=0 changed=0 unreachable=1 failed=0
node2 : ok=0 changed=0 unreachable=1 failed=0
node3 : ok=0 changed=0 unreachable=1 failed=0
node4 : ok=0 changed=0 unreachable=1 failed=0
node5 : ok=0 changed=0 unreachable=1 failed=0
node6 : ok=0 changed=0 unreachable=1 failed=0
node7 : ok=0 changed=0 unreachable=1 failed=0
node8 : ok=0 changed=0 unreachable=1 failed=0
node9 : ok=0 changed=0 unreachable=1 failed=0 [root@node11 scripts]# ./platform-info.sh Metron 0.2.0BETA
fatal: Not a git repository (or any of the parent directories): .git
-- ansible 2.0.0.2 config file = configured module search path = Default w/o overrides --
./platform-info.sh: line 52: vagrant: command not found
-- Python 2.6.6
-- Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30) Maven home: /opt/apache-maven-3.3.9 Java version: 1.8.0_60, vendor: Oracle Corporation Java home: /opt/jdk1.8.0_60/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-573.el6.x86_64", arch: "amd64", family: "unix"
--
Linux node11.metron 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
... View more
Labels:
06-28-2016
04:49 AM
TASK [metron_streaming : Copy Metron Solr bundle] ****************************** fatal: [node1]: FAILED! => {"changed": false, "failed": true, "msg": "could not find src=/opt/incubator-metron-Metron_0.1_tc3/metron-platform/metron-solr/target/metron-solr-0.1BETA-archive.tar.gz"} PLAY RECAP ********************************************************************* node1 : ok=143 changed=14 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
... View more
Labels:
06-28-2016
02:27 AM
1 Kudo
While performing vagrant provision I am getting the below error. TASK [ambari_config : Start the ambari cluster - no wait] ********************** fatal: [node1]: FAILED! => {"changed": false, "failed": true, "msg": "Ambari client exception occurred: Coud not set cluster state: request code 500, request message {\n \"status\" : 500,\n \"message\" : \"org.apache.ambari.server.controller.spi.SystemException: An internal system exception occurred: Invalid transition for servicecomponenthost, clusterName=metron_cluster, clusterId=2, serviceName=MAPREDUCE2, componentName=HISTORYSERVER, hostname=node1, currentState=INSTALL_FAILED, newDesiredState=STARTED\"\n}"} PLAY RECAP ********************************************************************* node1 : ok=38 changed=6 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
... View more
Labels:
06-28-2016
02:14 AM
Thank you very much. This solved my problem.
... View more
06-20-2016
10:38 PM
What is the difference between TP1, TP2 & TP3 Releases?
... View more
06-20-2016
02:35 AM
Environment Setup: Python2.7 / Ansible 2.0.0.2 / Vagrant 1.8.1 / Virtualbox 5.0.16 / Maven 3.3.9 / incubator-metron-Metron_0.1_tc3 # vagrant up Bringing machine 'node1' up with 'virtualbox' provider... ==> node1: Checking if box 'bento/centos-6.7' is up to date... ==> node1: VirtualBox VM is already running. # vagrant provision ==> node1: Running provisioner: ansible... node1: Running ansible-playbook... PLAY *************************************************************************** skipping: no hosts matched PLAY *************************************************************************** skipping: no hosts matched PLAY *************************************************************************** TASK [setup] ******************************************************************* fatal: [node1]: FAILED! => {"failed": true, "msg": "ERROR! failed to transfer file to /home/vagrant/.ansible/tmp/ansible-tmp-1466407020.4-160303380097709/setup:\n\nsftp: illegal option -- i\nusage: sftp [-1Cv] [-B buffer_size] [-b batchfile] [-F ssh_config]\n [-o ssh_option] [-P sftp_server_path] [-R num_requests]\n [-S program] [-s subsystem | sftp_server] host\n sftp [user@]host[:file ...]\n sftp [user@]host[:dir[/]]\n sftp -b batchfile [user@]host\n"} NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* node1 : ok=0 changed=0 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again. # ./platform-info.sh Metron 0.1BETA fatal: Not a git repository (or any of the parent directories): .git
-- ansible 2.0.0.2 config file = configured module search path = Default w/o overrides -- Vagrant 1.8.1 -- Python 2.6.6 --
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T22:11:47+05:30) Maven home: /opt/apache-maven-3.3.9 Java version: 1.7.0_79, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.79.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-573.el6.x86_64", arch: "amd64", family: "unix" -- Linux nortem 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
... View more
Labels: