Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

New Contributor

Hi everyone,

CyberSecurity enthusiast newbie here!

Currently I wanted to try out Apache Metron, and following the installation guide here:Metron 0.3.1 Install on Ubuntu/Debian single-node VM with Vagrant and Ambari.

I've already installed Vagrant ( "vagrant --version" showed that I have installed Vagrant 2.1.2). Another strange thing is that when I run "dir /usr/bin", I saw vagrant in the directory, but when I run "cd /usr/bin/vagrant", it came out "no such file or directory", contrary to what I saw.

I've also ran "vagrant plugin install vagrant-hostmanager".

But I still got stuck at this part:

  • cd metron-deployment/vagrant/(select the module you want to run)

Upon checking, there was no such file or directory:

bash: cd: /home/liana/incubator-metron/metron-deployment/vagrant: No such file or directory

I'm running out of ideas and solutions. Tried to find online, but it seems no one else have this issue of the missing vagrant folder containing the needed modules.

For further information, I'm using Ubuntu 18.04 to install, so far there's no compatibility issues (not that I know of).

p/s: While searching for howtos and solutions for this, I noticed most posts about Apache Metron and Vagrant is under "CyberSecurity", but I'm not sure whether mine is under Community Help (being a newbie question) or CyberSecurity (which seems advanced, but more fitting). Do inform if I put it on the wrong track.

7 REPLIES 7

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

Super Collaborator

Hello @Nor Liana Kamaruzzaman , welcome to Metron!

Can you tell more about which version of metron you are trying to use? And about your setup where are trying to do this?

The simplest way to get Metron up and running is to follow these steps:

https://github.com/apache/metron/tree/master/metron-deployment/development/centos6

Get the pre-requisites installed and deploy metron.

If you happen to run into any issues, please post the error output and also the output of the script metron-deployment/scripts/platform-info.sh

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

New Contributor

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

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

Super Collaborator

Hi @Nor Liana Kamaruzzaman ,

Yes, docker and nodejs are requisites. Here is a more recent version of the README for Ubuntu:

https://github.com/apache/metron/tree/master/metron-deployment/development/ubuntu14

Let me know how it goes.

Highlighted

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

New Contributor

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?

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

New Contributor

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

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

Super Collaborator

Hi @Nor Liana Kamaruzzaman ,

The docker and npm not getting listed should not happen. Also, I notice that you are using an older version of Metron (0.3.1). Can you try with a more recent version? i.e. Metron 0.5.0 (which is released) or 0.5.1 (master).

Re: Apache Metron Installation Issue incubator-metron/metron-deployment/vagrant: no such file or directory

New Contributor

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=&cpuper... 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\nDownl... 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\nDow... 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.
Don't have an account?
Coming from Hortonworks? Activate your account here