@Mabiin Nam : Try to run 'vagrant ssh'? If it could not work, try disconeecting and re-connecting your network. ... View more

@Mabiin Nam, I haven't encounter this issue before, but @Sohaila Eltanbouly's solution seems to be applicable. It could be that the docker is not enabled to run prior to deploying your Metron. If that did not work, try to re-clone the Metron git. last I checked, I don't have any 'incubator-metron' anymore. ... View more

I see...Can you share more below? The error should continue. This part shows that the error happened when it tried to run mvn package -DSkipTests -Pbuild-debs -T 2C More in the error should explain what happened, particularly starting from "BUILD FAILURE....." until "Ansible failed to..." Can you share that section? ... View more

Hi @asubramanian, I stopped during Ambari server deployment task. Ah....okay, vagrant halt.Will take note of that. but...how can I fix my current issue? Do I have to remove the node and metron, then re-clone the git, run the vagrant again ( the components are already installed)? update: I tried vagrant halt, but the process doesn't seem to stop. My process hangs/ stayed at : TASK [ambari_config : Deploy cluster with Ambari: http://node1:8080 ] ************************** During this, I managed to open the Ambri gui for Metron. Is it meant to stop / stay here? Or was I suppose to wait further? If yes, how can I halt the process, as vagrant halt did nothing? ... View more

Well...I cannot say it's wrong or right...maybe a little incomplete...personally I followed this: Dev VM Install: Ansible Based Vagrant Single Node VM Install - Metron on CentOS 6 , with the exception that I used CentOS 7 instead of 6. So far, from the result, it shows that you have fulfilled all the necessary components. Can you share me the result when you do this: cd metron/metron-deployment/development/centos6 (or ubuntu14, whichever you choose to use) vagrant destroy -f (to remove any previous running vagrant) vagrant up Should any error occur, please share, including which task it started to get the issue. ... View more

I see... May I know why you are running mvn clean package-rf :metron-config instead of cd metron/metron-deployment/development/centos6 vagrant up Also. can you share with me the result when you run metron/metron-deployment/scripts/platform-info.sh ... View more

Try installing the node-sass: npm install node-sass and then run the mvn command again: mvn clean package-rf :metron-config any changes? ... View more

Hi @asubramanian, I've increased the host VM's RAM. It reduces the cpu lock out, and can finally run. 🙂 Thanks. ... View more

Hi @asubramanian, I managed to troubleshoot the problem above by changing folder permission for the .npm and manually remove the _locks, then re-run vagrant up. The thing is, when running vagrant provision, I noticed one of the task were building cluster Ambari. That shouldn't happen for single-VM, right? But it did. The process ended due to several times CPU locked out/ overcommitment error, and then aborted. I have a feeling that this is because it is creating clusters instead of running on single-VM. ... View more

hi @asubramanian, I've installed node.js. : Metron 0.6.0 -- * Metron_0.6.0 -- commit 62310743a0c1d4a27db47a89cf79496d594c8bcf Author: justinleet <justinjleet@gmail.com> Date: Tue Sep 4 19:53:37 2018 -0400 METRON-1764 Update version to 0.6.0 (justinleet) closes apache/metron#1183 -- metron-deployment/development/centos6/ansible.cfg | 3 +++ metron-deployment/development/centos6/ansible/playbook.yml | 12 ++++++++++-- 2 files changed, 13 insertions(+), 2 deletions(-) -- ansible 2.5.0 config file = None configured module search path = [u'/home/<user>/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] -- Vagrant 2.1.5 -- vagrant-hostmanager (1.8.9, global) -- Python 2.7.5 -- Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-18T02:33:14+08:00) Maven home: /usr/local/src/apache-maven Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-862.14.4.el7.x86_64", arch: "amd64", family: "unix" -- Docker version 18.09.0-beta3, build 7718f80 -- node v6.14.3 -- npm 3.10.10 -- g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28) Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Compiler is C++11 compliant -- Linux localhost.localdomain 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Total System Memory = 9670.98 MB Processor Model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz Processor Speed: 3392.409 MHz Total Physical Processors: 2 Total cores: 2 Disk information: /dev/mapper/centos-root 45G 18G 27G 41% / /dev/sda1 1014M 221M 794M 22% /boot This CPU appears to support virtualization <br> This is the error I got, (6000 char exceeded, so I put it on pastebin):Metron Fourth Error Issue ... View more

Hi @asubramanian, Recently I tried with CentOS 7, but ran into a problem: Message from syslogd@localhost at Oct 8 13:32:47 ... kernel:NMI watchdog: BUG: soft lockup - CPU#1 stuck for 33s! [nautilus-deskto:2881] Message from syslogd@localhost at Oct 8 13:33:32 ... kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 37s! [kworker/0:1:13622] fatal: [node1]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Connection timed out during banner exchange\r\n", "unreachable": true} to retry, use: --limit @/home/<user>/metron/metron-deployment/development/centos6/ansible/playbook.retry PLAY RECAP ********************************************************************* node1 : ok=23 changed=14 unreachable=1 failed=0 Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again. Below is the result of platform-info.sh: Metron 0.6.0 -- * Metron_0.6.0 -- commit 62310743a0c1d4a27db47a89cf79496d594c8bcf Author: justinleet <justinjleet@gmail.com> Date: Tue Sep 4 19:53:37 2018 -0400 METRON-1764 Update version to 0.6.0 (justinleet) closes apache/metron#1183 -- -- ansible 2.5.0 config file = /home/<user>/metron/metron-deployment/ansible.cfg configured module search path = [u'/home/<user>/metron/metron-deployment/extra_modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] -- Vagrant 2.1.5 -- vagrant-hostmanager (1.8.9, global) -- Python 2.7.5 -- Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-18T02:33:14+08:00) Maven home: /usr/local/src/apache-maven Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-862.14.4.el7.x86_64", arch: "amd64", family: "unix" -- Docker version 18.09.0-beta3, build 7718f80 -- node scripts/platform-info.sh: line 77: node: command not found -- npm scripts/platform-info.sh: line 82: npm: command not found -- g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28) Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Compiler is C++11 compliant -- Linux localhost.localdomain 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Total System Memory = 9670.97 MB Processor Model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz Processor Speed: 3392.460 MHz Total Physical Processors: 2 Total cores: 2 Disk information: /dev/mapper/centos-root 45G 20G 25G 44% / /dev/sda1 1014M 221M 794M 22% /boot This CPU appears to support virtualization Please advice... ... View more

Hey @asubramanian, Thank you for waiting.I will try 🙂 Before I proceed, which one should I follow to try on CentOS 7? Dev VM install for CentOS or Metron 0.4.1 with HDP 2.5 bare-metal install on Centos 7 with MariaDB for Metron REST. My system is only 12GB RAM and dual processor thought. ... View more

@asubramanian This is the result when I run 'mvn -e package' : https://pastebin.com/3UDfH6GT ... View more

Hi @asubramanian, I re-create the Vagrantfile using 'rm -r Vagrantfile' and 'vagrant init centos/6' And then I run vagrant up, and now I got this: (had to put in pastebin as it exceeds char limit) https://pastebin.com/x99i5zpK Now I'll try clean packages ... View more

Hi @asubramanian, It stopped here, what should I do next? ==> default: Rsyncing folder: /home/akaticentos6/metron/metron-deployment/development/centos6/ => /vagrant ... View more

Hi all, so I am able to update my node and npm, but not docker: Metron 0.6.0 -- * master -- commit 62310743a0c1d4a27db47a89cf79496d594c8bcf Author: justinleet <justinjleet@gmail.com> Date: Tue Sep 4 19:53:37 2018 -0400 METRON-1764 Update version to 0.6.0 (justinleet) closes apache/metron#1183 -- metron-deployment/development/centos6/Vagrantfile | 168 ++++++++------------ 1 files changed, 67 insertions(+), 101 deletions(-) -- ansible 2.5.0 config file = None configured module search path = [u'/home/akaticentos6/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.6/site-packages/ansible executable location = /usr/bin/ansible python version = 2.6.6 (r266:84292, Aug 18 2016, 15:13:37) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] -- Vagrant 2.1.4 -- vagrant-hostmanager (1.8.9, global) -- Python 2.7.15 -- Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T00:41:47+08:00) Maven home: /opt/maven Java version: 1.8.0_181, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_181-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-754.el6.x86_64", arch: "amd64", family: "unix" -- Docker version 1.7.1, build 786b29d/1.7.1 -- node v9.11.2 -- npm 6.4.1 -- g++ (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15) Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Compiler is C++11 compliant -- Linux localhost.localdomain 2.6.32-754.el6.x86_64 #1 SMP Tue Jun 19 21:26:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Total System Memory = 9075.27 MB Processor Model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz Processor Speed: 3392.349 MHz Total Physical Processors: 2 Total cores: 2 Disk information: /dev/mapper/vg_akaticentos6-lv_root /dev/sda1 477M 67M 385M 15% /boot /dev/sr0 71M 71M 0 100% /media/VMware Tools This CPU appears to support virtualization When I try to run vagrant up in metron/metron-deployment/development/centos6 , this show: Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'centos/6'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'centos/6' is up to date... ==> default: Setting the name of the VM: centos6_default_1537433543787_6601 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... default: No guest additions were detected on the base box for this VM! Guest default: additions are required for forwarded ports, shared folders, host only default: networking, and more. If SSH fails on this machine, please install default: the guest additions and repackage the box to continue. default: default: This is not an error message; everything may continue to work properly, default: in which case you may ignore this message. ==> default: Rsyncing folder: /home/akaticentos6/metron/metron-deployment/development/centos6/ => /vagrant Also, I notice that in my metron-deployment, there's no vagrant folder: cd metron-deployment $ dir amazon-ec2 ansible.cfg Kerberos-ambari-setup.md other-examples pom.xml README.md ansible development Kerberos-manual-setup.md packaging readme-images scripts but I saw in other tutorials, there supposed to be one. Is this normal? ... View more

hi @asubramanian Would that require CentOS 7? Just to note, I am using CentOS 6. update:Couldn't. "systemd-units is needed by docker-ce-18.06.1.ce-3.el7.x86_64" Latest one requires it. CentOS 6 does not support it. Doesn't seem to have any option to upgrade CentOS 6 to CentOS 7/ ... View more

@asubramanian: I tried to update npm, but it returned this: npm ERR! Error: CERT_UNTRUSTED npm ERR! at SecurePair.<anonymous> (tls.js:1430:32) npm ERR! at SecurePair.emit (events.js:92:17) npm ERR! at SecurePair.maybeInitFinished (tls.js:1029:10) npm ERR! at CleartextStream.read [as _read] (tls.js:521:13) npm ERR! at CleartextStream.Readable.read (_stream_readable.js:341:10) npm ERR! at EncryptedStream.write [as _write] (tls.js:418:25) npm ERR! at doWrite (_stream_writable.js:226:10) npm ERR! at writeOrBuffer (_stream_writable.js:216:5) npm ERR! at EncryptedStream.Writable.write (_stream_writable.js:183:11) npm ERR! at write (_stream_readable.js:602:24) npm ERR! If you need help, you may report this log at: npm ERR! <http://github.com/isaacs/npm/issues> npm ERR! or email it to: npm ERR! <npm-@googlegroups.com> npm ERR! System Linux 2.6.32-754.el6.x86_64 npm ERR! command "node" "/usr/bin/npm" "install" npm ERR! cwd /usr/lib/node_modules/npm npm ERR! node -v v0.10.48 npm ERR! npm -v 1.3.6 npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /usr/lib/node_modules/npm/npm-debug.log npm ERR! not ok code 0 I had run update, but the error still appear after update. ... View more

@Otto Fowler: when I run 'service docker status' it says: docker (pid 7232) is running... I assume it is running? This is prior to running 'vagrant up' ... View more

Hi @asubramanian, I've changed it to Metron 0.5.0. Had re-run the platform-info.sh, and have docker and npm installed too. And now, when I run vagrant up, this appear: TASK [metron-builder : Build Metron DEB Packages] ****************************** failed: [node1 -> localhost] => (item=mvn package -DskipTests -Pbuild-debs -T 2C) => {"changed": true, "cmd": "mvn package -DskipTests -Pbuild-debs -T 2C", "delta": "0:00:35.055641", "end": "2018-09-02 20:34:42.867931", "failed": true, "item": "mvn package -DskipTests -Pbuild-debs -T 2C", "rc": 1, "start": "2018-09-02 20:34:07.812290", "stderr": "Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.35/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&session=1ce39b31b4db7d891a4cf91af2bbcbef0fa636e60e3e0d639f63cb453868ba8e&shmsize=0&t=deb-docker&target=&ulimits=null: dial unix /var/run/docker.sock: connect: permission denied", "stdout": "[\u001b[1;34mINFO\u001b[m] Scanning for projects...\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1mReactor Build Order:\u001b[m\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] metron-deployment\n[\u001b[1;34mINFO\u001b[m] metron-debs\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] Using the MultiThreadedBuilder implementation with a thread count of 4\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1mBuilding metron-deployment 0.5.0\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mmaven-enforcer-plugin:1.4.1:enforce\u001b[m \u001b[1m(enforce-versions)\u001b[m @ \u001b[36mmetron-deployment\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:prepare-agent\u001b[m \u001b[1m(default)\u001b[m @ \u001b[36mmetron-deployment\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] argLine set to -javaagent:/home/akatiubuntutest/.m2/repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/home/akatiubuntutest/metron/metron-deployment/target/jacoco.exec\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:report\u001b[m \u001b[1m(report)\u001b[m @ \u001b[36mmetron-deployment\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] Skipping JaCoCo execution due to missing execution data file.\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1mBuilding metron-debs 0.5.0\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mmaven-enforcer-plugin:1.4.1:enforce\u001b[m \u001b[1m(enforce-versions)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:prepare-agent\u001b[m \u001b[1m(default)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] argLine set to -javaagent:/home/akatiubuntutest/.m2/repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/home/akatiubuntutest/metron/metron-deployment/packaging/docker/deb-docker/target/jacoco.exec\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:report\u001b[m \u001b[1m(report)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] Skipping JaCoCo execution due to missing execution data file.\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mmaven-resources-plugin:3.0.1:copy-resources\u001b[m \u001b[1m(copy-deb-sources)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m\n[\u001b[1;34mINFO\u001b[m] Using 'UTF-8' encoding to copy filtered resources.\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] Copying 1 resource\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mexec-maven-plugin:1.5.0:exec\u001b[m \u001b[1m(docker-build)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m\nDownloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-exec/1.3/commons-exec-1.3.pom\nDownloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-exec/1.3/commons-exec-1.3.pom (0 B at 0 B/s)\nDownloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-parent/35/commons-parent-35.pom\nDownloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-parent/35/commons-parent-35.pom (0 B at 0 B/s)\n[\u001b[1;31mERROR\u001b[m] Command execution failed.\n\u001b[1;31morg.apache.commons.exec.ExecuteException\u001b[m: \u001b[1;31mProcess exited with an error: 1 (Exit value: 1)\u001b[m\n \u001b[1mat\u001b[m org.apache.commons.exec.DefaultExecutor.executeInternal (\u001b[1mDefaultExecutor.java:404\u001b[m)\n \u001b[1mat\u001b[m org.apache.commons.exec.DefaultExecutor.execute (\u001b[1mDefaultExecutor.java:166\u001b[m)\n \u001b[1mat\u001b[m org.codehaus.mojo.exec.ExecMojo.executeCommandLine (\u001b[1mExecMojo.java:764\u001b[m)\n \u001b[1mat\u001b[m org.codehaus.mojo.exec.ExecMojo.executeCommandLine (\u001b[1mExecMojo.java:711\u001b[m)\n \u001b[1mat\u001b[m org.codehaus.mojo.exec.ExecMojo.execute (\u001b[1mExecMojo.java:289\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (\u001b[1mDefaultBuildPluginManager.java:134\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.MojoExecutor.execute (\u001b[1mMojoExecutor.java:208\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.MojoExecutor.execute (\u001b[1mMojoExecutor.java:154\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.MojoExecutor.execute (\u001b[1mMojoExecutor.java:146\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (\u001b[1mLifecycleModuleBuilder.java:117\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (\u001b[1mMultiThreadedBuilder.java:200\u001b[m)\n \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (\u001b[1mMultiThreadedBuilder.java:196\u001b[m)\n \u001b[1mat\u001b[m java.util.concurrent.FutureTask.run (\u001b[1mFutureTask.java:266\u001b[m)\n \u001b[1mat\u001b[m java.util.concurrent.Executors$RunnableAdapter.call (\u001b[1mExecutors.java:511\u001b[m)\n \u001b[1mat\u001b[m java.util.concurrent.FutureTask.run (\u001b[1mFutureTask.java:266\u001b[m)\n \u001b[1mat\u001b[m java.util.concurrent.ThreadPoolExecutor.runWorker (\u001b[1mThreadPoolExecutor.java:1149\u001b[m)\n \u001b[1mat\u001b[m java.util.concurrent.ThreadPoolExecutor$Worker.run (\u001b[1mThreadPoolExecutor.java:624\u001b[m)\n \u001b[1mat\u001b[m java.lang.Thread.run (\u001b[1mThread.java:748\u001b[m)\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1mReactor Summary:\u001b[m\n[\u001b[1;34mINFO\u001b[m] \n[\u001b[1;34mINFO\u001b[m] metron-deployment .................................. \u001b[1;32mSUCCESS\u001b[m [ 2.426 s]\n[\u001b[1;34mINFO\u001b[m] metron-debs ........................................ \u001b[1;31mFAILURE\u001b[m [ 29.327 s]\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1;31mBUILD FAILURE\u001b[m\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;34mINFO\u001b[m] Total time: 32.066 s (Wall Clock)\n[\u001b[1;34mINFO\u001b[m] Finished at: 2018-09-02T20:34:42-07:00\n[\u001b[1;34mINFO\u001b[m] Final Memory: 19M/233M\n[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m\n[\u001b[1;31mERROR\u001b[m] Failed to execute goal \u001b[32morg.codehaus.mojo:exec-maven-plugin:1.5.0:exec\u001b[m \u001b[1m(docker-build)\u001b[m on project \u001b[36mmetron-debs\u001b[m: \u001b[1;31mCommand execution failed.\u001b[m: Process exited with an error: 1 (Exit value: 1) -> \u001b[1m[Help 1]\u001b[m\n[\u001b[1;31mERROR\u001b[m] \n[\u001b[1;31mERROR\u001b[m] To see the full stack trace of the errors, re-run Maven with the \u001b[1m-e\u001b[m switch.\n[\u001b[1;31mERROR\u001b[m] Re-run Maven using the \u001b[1m-X\u001b[m switch to enable full debug logging.\n[\u001b[1;31mERROR\u001b[m] \n[\u001b[1;31mERROR\u001b[m] For more information about the errors and possible solutions, please read the following articles:\n[\u001b[1;31mERROR\u001b[m] \u001b[1m[Help 1]\u001b[m http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException\n[\u001b[1;31mERROR\u001b[m] \n[\u001b[1;31mERROR\u001b[m] After correcting the problems, you can resume the build with the command\n[\u001b[1;31mERROR\u001b[m] \u001b[1mmvn <goals> -rf :metron-debs\u001b[m", "stdout_lines": ["[\u001b[1;34mINFO\u001b[m] Scanning for projects...", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1mReactor Build Order:\u001b[m", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] metron-deployment", "[\u001b[1;34mINFO\u001b[m] metron-debs", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] Using the MultiThreadedBuilder implementation with a thread count of 4", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1mBuilding metron-deployment 0.5.0\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mmaven-enforcer-plugin:1.4.1:enforce\u001b[m \u001b[1m(enforce-versions)\u001b[m @ \u001b[36mmetron-deployment\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:prepare-agent\u001b[m \u001b[1m(default)\u001b[m @ \u001b[36mmetron-deployment\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] argLine set to -javaagent:/home/akatiubuntutest/.m2/repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/home/.../metron/metron-deployment/target/jacoco.exec", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:report\u001b[m \u001b[1m(report)\u001b[m @ \u001b[36mmetron-deployment\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] Skipping JaCoCo execution due to missing execution data file.", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1mBuilding metron-debs 0.5.0\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mmaven-enforcer-plugin:1.4.1:enforce\u001b[m \u001b[1m(enforce-versions)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:prepare-agent\u001b[m \u001b[1m(default)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] argLine set to -javaagent:/home/.../.m2/repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/home/.../metron/metron-deployment/packaging/docker/deb-docker/target/jacoco.exec", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mjacoco-maven-plugin:0.7.9:report\u001b[m \u001b[1m(report)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] Skipping JaCoCo execution due to missing execution data file.", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mmaven-resources-plugin:3.0.1:copy-resources\u001b[m \u001b[1m(copy-deb-sources)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m", "[\u001b[1;34mINFO\u001b[m] Using 'UTF-8' encoding to copy filtered resources.", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] Copying 1 resource", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] \u001b[1m--- \u001b[0;32mexec-maven-plugin:1.5.0:exec\u001b[m \u001b[1m(docker-build)\u001b[m @ \u001b[36mmetron-debs\u001b[0;1m ---\u001b[m", "Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-exec/1.3/commons-exec-1.3.pom", "Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-exec/1.3/commons-exec-1.3.pom (0 B at 0 B/s)", "Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-parent/35/commons-parent-35.pom", "Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-parent/35/commons-parent-35.pom (0 B at 0 B/s)", "[\u001b[1;31mERROR\u001b[m] Command execution failed.", "\u001b[1;31morg.apache.commons.exec.ExecuteException\u001b[m: \u001b[1;31mProcess exited with an error: 1 (Exit value: 1)\u001b[m", " \u001b[1mat\u001b[m org.apache.commons.exec.DefaultExecutor.executeInternal (\u001b[1mDefaultExecutor.java:404\u001b[m)", " \u001b[1mat\u001b[m org.apache.commons.exec.DefaultExecutor.execute (\u001b[1mDefaultExecutor.java:166\u001b[m)", " \u001b[1mat\u001b[m org.codehaus.mojo.exec.ExecMojo.executeCommandLine (\u001b[1mExecMojo.java:764\u001b[m)", " \u001b[1mat\u001b[m org.codehaus.mojo.exec.ExecMojo.executeCommandLine (\u001b[1mExecMojo.java:711\u001b[m)", " \u001b[1mat\u001b[m org.codehaus.mojo.exec.ExecMojo.execute (\u001b[1mExecMojo.java:289\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (\u001b[1mDefaultBuildPluginManager.java:134\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.MojoExecutor.execute (\u001b[1mMojoExecutor.java:208\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.MojoExecutor.execute (\u001b[1mMojoExecutor.java:154\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.MojoExecutor.execute (\u001b[1mMojoExecutor.java:146\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (\u001b[1mLifecycleModuleBuilder.java:117\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (\u001b[1mMultiThreadedBuilder.java:200\u001b[m)", " \u001b[1mat\u001b[m org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (\u001b[1mMultiThreadedBuilder.java:196\u001b[m)", " \u001b[1mat\u001b[m java.util.concurrent.FutureTask.run (\u001b[1mFutureTask.java:266\u001b[m)", " \u001b[1mat\u001b[m java.util.concurrent.Executors$RunnableAdapter.call (\u001b[1mExecutors.java:511\u001b[m)", " \u001b[1mat\u001b[m java.util.concurrent.FutureTask.run (\u001b[1mFutureTask.java:266\u001b[m)", " \u001b[1mat\u001b[m java.util.concurrent.ThreadPoolExecutor.runWorker (\u001b[1mThreadPoolExecutor.java:1149\u001b[m)", " \u001b[1mat\u001b[m java.util.concurrent.ThreadPoolExecutor$Worker.run (\u001b[1mThreadPoolExecutor.java:624\u001b[m)", " \u001b[1mat\u001b[m java.lang.Thread.run (\u001b[1mThread.java:748\u001b[m)", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1mReactor Summary:\u001b[m", "[\u001b[1;34mINFO\u001b[m] ", "[\u001b[1;34mINFO\u001b[m] metron-deployment .................................. \u001b[1;32mSUCCESS\u001b[m [ 2.426 s]", "[\u001b[1;34mINFO\u001b[m] metron-debs ........................................ \u001b[1;31mFAILURE\u001b[m [ 29.327 s]", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1;31mBUILD FAILURE\u001b[m", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;34mINFO\u001b[m] Total time: 32.066 s (Wall Clock)", "[\u001b[1;34mINFO\u001b[m] Finished at: 2018-09-02T20:34:42-07:00", "[\u001b[1;34mINFO\u001b[m] Final Memory: 19M/233M", "[\u001b[1;34mINFO\u001b[m] \u001b[1m------------------------------------------------------------------------\u001b[m", "[\u001b[1;31mERROR\u001b[m] Failed to execute goal \u001b[32morg.codehaus.mojo:exec-maven-plugin:1.5.0:exec\u001b[m \u001b[1m(docker-build)\u001b[m on project \u001b[36mmetron-debs\u001b[m: \u001b[1;31mCommand execution failed.\u001b[m: Process exited with an error: 1 (Exit value: 1) -> \u001b[1m[Help 1]\u001b[m", "[\u001b[1;31mERROR\u001b[m] ", "[\u001b[1;31mERROR\u001b[m] To see the full stack trace of the errors, re-run Maven with the \u001b[1m-e\u001b[m switch.", "[\u001b[1;31mERROR\u001b[m] Re-run Maven using the \u001b[1m-X\u001b[m switch to enable full debug logging.", "[\u001b[1;31mERROR\u001b[m] ", "[\u001b[1;31mERROR\u001b[m] For more information about the errors and possible solutions, please read the following articles:", "[\u001b[1;31mERROR\u001b[m] \u001b[1m[Help 1]\u001b[m http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException", "[\u001b[1;31mERROR\u001b[m] ", "[\u001b[1;31mERROR\u001b[m] After correcting the problems, you can resume the build with the command", "[\u001b[1;31mERROR\u001b[m] \u001b[1mmvn <goals> -rf :metron-debs\u001b[m"], "warnings": []} PLAY RECAP ********************************************************************* node1 : ok=17 changed=8 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

but at least the main issue had been solved. The next one, I'll make another post after trying out some troubleshooting online. ... View more

Hi @asubramanian, I found out that we have to run vagrant init in the folder, then it will create a vagrantfile. Also, after running 'vagrant up' (which bring up another issue, but different kind), I tried running platform-info-sh to check the pre-requisites. This time, it does not list down the docker, node, and npm availability: Metron 0.3.1 -- -- fatal: your current branch 'master' does not have any commits yet -- -- ansible 2.6.3 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/akatiubuntutest/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/dist-packages/ansible executable location = /usr/bin/ansible python version = 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0] -- Vagrant 2.1.2 -- Python 2.7.15rc1 -- Apache Maven 3.5.2 Maven home: /usr/share/maven Java version: 1.8.0_181, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-oracle/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.15.0-33-generic", arch: "amd64", family: "unix" -- Linux ubuntu 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Total System Memory = 10531.5 MB Processor Model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz Processor Speed: 3392.439 MHz Total Physical Processors: 2 Total cores: 2 Disk information: /dev/sda1 50G 20G 28G 42% / /dev/loop0 141M 141M 0 100% /snap/gnome-3-26-1604/59 /dev/loop1 21M 21M 0 100% /snap/gnome-logs/25 /dev/loop2 3.4M 3.4M 0 100% /snap/gnome-system-monitor/36 /dev/loop4 3.8M 3.8M 0 100% /snap/gnome-system-monitor/54 /dev/loop3 15M 15M 0 100% /snap/gnome-logs/40 /dev/loop5 87M 87M 0 100% /snap/core/5145 /dev/loop6 13M 13M 0 100% /snap/gnome-characters/69 /dev/loop7 1.7M 1.7M 0 100% /snap/gnome-calculator/154 /dev/loop8 13M 13M 0 100% /snap/gnome-characters/117 /dev/loop9 2.4M 2.4M 0 100% /snap/gnome-calculator/199 /dev/loop10 87M 87M 0 100% /snap/core/4486 /dev/loop11 141M 141M 0 100% /snap/gnome-3-26-1604/70 Should that happen? ... View more

Hello @asubramanian, I was following this : Metron 0.3.1 Install on Ubuntu/Debian single-node VM with Vagrant and Ambari. When I run the script, this is the output: Metron 0.5.1 -- * master -- commit 9fdccba371c1f1e0dcb79e00a7207a934b79b64c (HEAD -> master, origin/master, origin/HEAD) Merge: 308c2b27 14e80b3c Author: merrimanr <merrimanr@gmail.com> Date: Fri Aug 17 10:26:51 2018 -0500 METRON-1554 Pcap Query Panel (merrimanr) closes apache/metron#1169 -- -- ansible 2.6.3 config file = .../metron/metron-deployment/ansible.cfg configured module search path = [u'.../metron/metron-deployment/extra_modules'] ansible python module location = /usr/lib/python2.7/dist-packages/ansible executable location = /usr/bin/ansible python version = 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0] -- Vagrant 2.1.2 -- vagrant-hostmanager (1.8.9) -- Python 2.7.15rc1 -- Apache Maven 3.5.2 Maven home: /usr/share/maven Java version: 1.8.0_181, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-oracle/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.15.0-33-generic", arch: "amd64", family: "unix" -- scripts/platform-info.sh: line 68: docker: command not found -- node scripts/platform-info.sh: line 77: node: command not found -- npm scripts/platform-info.sh: line 82: npm: command not found -- g++ (Ubuntu 7.3.0-16ubuntu3) 7.3.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Compiler is C++11 compliant -- Linux ubuntu 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Total System Memory = 10531.5 MB Processor Model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz Processor Speed: 3392.449 MHz Total Physical Processors: 2 Total cores: 2 Disk information: /dev/sda1 20G 7.7G 11G 42% / /dev/loop1 15M 15M 0 100% /snap/gnome-logs/40 /dev/loop0 2.4M 2.4M 0 100% /snap/gnome-calculator/199 /dev/loop8 141M 141M 0 100% /snap/gnome-3-26-1604/59 /dev/loop3 87M 87M 0 100% /snap/core/5145 /dev/loop5 13M 13M 0 100% /snap/gnome-characters/69 /dev/loop4 3.8M 3.8M 0 100% /snap/gnome-system-monitor/54 /dev/loop7 21M 21M 0 100% /snap/gnome-logs/25 /dev/loop10 141M 141M 0 100% /snap/gnome-3-26-1604/70 /dev/loop2 1.7M 1.7M 0 100% /snap/gnome-calculator/154 /dev/loop6 3.4M 3.4M 0 100% /snap/gnome-system-monitor/36 /dev/loop11 13M 13M 0 100% /snap/gnome-characters/117 /dev/loop9 87M 87M 0 100% /snap/core/4486 This CPU appears to support virtualization Strangely, following the guide, there's no instruction to install Docker, npm, and node ( I assume nodejs should be done with npm installation?) p/s:Some how, the snippet came out weird when posted, despite showing in the proper box during editing through HTML and the 'insert code' feature. If you can't see it properly, you can view it at https://pastebin.com/9p2zgjCM ... View more