[
https://issues.apache.org/jira/browse/METRON-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267090#comment-16267090
]
Otto Fowler commented on METRON-1320:
-------------------------------------
I'm testing out in the docker image, such that it will support:
> mvn package
> mvn package -P build_rpms
Then I'll submit a pr for that and take comment, IE, should we say:
If you have trouble building metron and want the easy button, do XXXX in our
docker image and build there.
That review will review what I did to install the toolset and make sure it is
ok.
So after that, they can make the same changes in their env or use docker off
master post pr.
We can discuss and follow on just using or adding a centos7 docker + vagrant
maybe?
How does that sound?
> Cannot perform a bare-metal installation
> ----------------------------------------
>
> Key: METRON-1320
> URL: https://issues.apache.org/jira/browse/METRON-1320
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.4.0
> Environment: Centos 6
> Reporter: Paweł Białasiewicz
>
> WI'm trying to install Metron using the following how-to:
> https://github.com/apache/metron/blob/master/metron-deployment/other-examples/manual-install/Manual_Install_CentOS6.md
> I'm getting this error:
> {code:java}
> Downloading:
> https://raw.github.com/benelog/multiline/master/maven-repository/javax/ws/rs/jsr311-api/1.1.1/jsr311-api-1.1.1.pom
> [INFO] Cannot find module 'tough-cookie'
> [INFO] Error: Cannot find module 'tough-cookie'
> [INFO] at Function.Module._resolveFilename (module.js:440:15)
> [INFO] at Function.Module._load (module.js:388:25)
> [INFO] at Module.require (module.js:468:17)
> [INFO] at require (internal/module.js:20:19)
> [INFO] at Object.<anonymous>
> (/home/centos/metron/metron-interface/metron-config/node_modules/request/lib/cookies.js:3:13)
> [INFO] at Module._compile (module.js:541:32)
> [INFO] at Object.Module._extensions..js (module.js:550:10)
> [INFO] at Module.load (module.js:458:32)
> [INFO] at tryModuleLoad (module.js:417:12)
> [INFO] at Function.Module._load (module.js:409:3)
> [INFO] at Module.require (module.js:468:17)
> [INFO] at require (internal/module.js:20:19)
> [INFO] at Object.<anonymous>
> (/home/centos/metron/metron-interface/metron-config/node_modules/request/index.js:18:15)
> [INFO] at Module._compile (module.js:541:32)
> [INFO] at Object.Module._extensions..js (module.js:550:10)
> [INFO] at Module.load (module.js:458:32)
> [INFO] at tryModuleLoad (module.js:417:12)
> [INFO] at Function.Module._load (module.js:409:3)
> [INFO] at Module.require (module.js:468:17)
> [INFO] at require (internal/module.js:20:19)
> [INFO] at Leek._enqueue
> (/home/centos/metron/metron-interface/metron-config/node_modules/leek/lib/leek.js:60:30)
> [INFO] at Leek.track
> (/home/centos/metron/metron-interface/metron-config/node_modules/leek/lib/leek.js:87:15)
> [INFO] at Class.Command.validateAndRun
> (/home/centos/metron/metron-interface/metron-config/node_modules/angular-cli/lib/models/command.js:119:18)
> [INFO] at
> /home/centos/metron/metron-interface/metron-config/node_modules/angular-cli/lib/cli/cli.js:86:22
> [INFO] at tryCatch
> (/home/centos/metron/metron-interface/metron-config/node_modules/rsvp/dist/lib/rsvp/-internal.js:198:12)
> [INFO] at invokeCallback
> (/home/centos/metron/metron-interface/metron-config/node_modules/rsvp/dist/lib/rsvp/-internal.js:211:13)
> [INFO] at
> /home/centos/metron/metron-interface/metron-config/node_modules/rsvp/dist/lib/rsvp/then.js:26:14
> [INFO] at flush
> (/home/centos/metron/metron-interface/metron-config/node_modules/rsvp/dist/lib/rsvp/asap.js:80:5)
> [INFO] at _combinedTickCallback (internal/process/next_tick.js:67:7)
> [INFO] at process._tickCallback (internal/process/next_tick.js:98:9)
> [ERROR]
> [ERROR] npm ERR! Linux 2.6.32-696.1.1.el6.x86_64
> [ERROR] npm ERR! argv
> "/home/centos/metron/metron-interface/metron-config/node/node"
> "/home/centos/metron/metron-interface/metron-config/node/node_modules/npm/bin/npm-cli.js"
> "run" "build"
> [ERROR] npm ERR! node v6.2.0
> [ERROR] npm ERR! npm v3.8.9
> [ERROR] npm ERR! code ELIFECYCLE
> [ERROR] npm ERR! [email protected] build:
> `./node_modules/angular-cli/bin/ng build -prod`
> [ERROR] npm ERR! Exit status 1
> [ERROR] npm ERR!
> [ERROR] npm ERR! Failed at the [email protected] build script
> './node_modules/angular-cli/bin/ng build -prod'.
> [ERROR] npm ERR! Make sure you have the latest version of node.js and npm
> installed.
> [ERROR] npm ERR! If you do, this is most likely a problem with the
> metron-management-ui package,
> [ERROR] npm ERR! not with npm itself.
> [ERROR] npm ERR! Tell the author that this fails on your system:
> [ERROR] npm ERR! ./node_modules/angular-cli/bin/ng build -prod
> [ERROR] npm ERR! You can get information on how to open an issue for this
> project with:
> [ERROR] npm ERR! npm bugs metron-management-ui
> [ERROR] npm ERR! Or if that isn't available, you can get their info via:
> [ERROR] npm ERR! npm owner ls metron-management-ui
> [ERROR] npm ERR! There is likely additional logging output above.
> [ERROR]
> [ERROR] npm ERR! Please include the following file with any support request:
> [ERROR] npm ERR!
> /home/centos/metron/metron-interface/metron-config/npm-debug.log
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Metron ............................................. SUCCESS [ 0.615
> s]
> [INFO] metron-analytics ................................... SUCCESS [ 0.031
> s]
> [INFO] metron-maas-common ................................. SUCCESS [ 2.858
> s]
> [INFO] metron-platform .................................... SUCCESS [ 0.131
> s]
> [INFO] metron-test-utilities .............................. SUCCESS [ 2.577
> s]
> [INFO] metron-integration-test ............................ SUCCESS [ 5.267
> s]
> [INFO] metron-maas-service ................................ SUCCESS [ 2.532
> s]
> [INFO] metron-common ...................................... SUCCESS [ 17.766
> s]
> [INFO] metron-statistics .................................. SUCCESS [ 19.020
> s]
> [INFO] metron-writer ...................................... SUCCESS [ 18.165
> s]
> [INFO] metron-storm-kafka-override ........................ SUCCESS [ 0.454
> s]
> [INFO] metron-storm-kafka ................................. SUCCESS [ 0.748
> s]
> [INFO] metron-hbase ....................................... SUCCESS [ 1.798
> s]
> [INFO] metron-profiler-common ............................. SUCCESS [ 0.548
> s]
> [INFO] metron-profiler-client ............................. SUCCESS [ 18.692
> s]
> [INFO] metron-profiler .................................... SUCCESS [ 46.823
> s]
> [INFO] metron-enrichment .................................. SUCCESS [ 49.064
> s]
> [INFO] metron-indexing .................................... SKIPPED
> [INFO] metron-solr ........................................ SKIPPED
> [INFO] metron-pcap ........................................ SUCCESS [ 0.945
> s]
> [INFO] metron-parsers ..................................... SKIPPED
> [INFO] metron-pcap-backend ................................ SUCCESS [ 29.927
> s]
> [INFO] metron-data-management ............................. SKIPPED
> [INFO] metron-api ......................................... SUCCESS [ 26.579
> s]
> [INFO] metron-management .................................. SKIPPED
> [INFO] elasticsearch-shaded ............................... SUCCESS [ 7.616
> s]
> [INFO] metron-elasticsearch ............................... SKIPPED
> [INFO] metron-deployment .................................. SUCCESS [ 0.085
> s]
> [INFO] Metron Ambari Management Pack ...................... SUCCESS [ 1.787
> s]
> [INFO] metron-docker ...................................... SUCCESS [ 0.705
> s]
> [INFO] metron-interface ................................... SUCCESS [ 0.076
> s]
> [INFO] metron-config ...................................... FAILURE [01:49
> min]
> [INFO] metron-rest-client ................................. SUCCESS [ 0.397
> s]
> [INFO] metron-rest ........................................ SKIPPED
> [INFO] site-book .......................................... SUCCESS [ 1.524
> s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 01:50 min (Wall Clock)
> [INFO] Finished at: 2017-11-20T12:15:38+00:00
> [INFO] Final Memory: 1702M/3089M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.3:npm (ng build) on project
> metron-config: Failed to run task: 'npm run build' failed. (error code 1) ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.github.eirslett:frontend-maven-plugin:1.3:npm (ng build) on project
> metron-config: Failed to run task
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.maven.plugin.MojoFailureException: Failed to run task
> at
> com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:95)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 11 more
> Caused by:
> com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'npm run
> build' failed. (error code 1)
> at
> com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:60)
> at
> com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:62)
> at
> com.github.eirslett.maven.plugins.frontend.mojo.AbstractFrontendMojo.execute(AbstractFrontendMojo.java:89)
> ... 13 more
> Downloading:
> https://repo.maven.apache.org/maven2/javax/ws/rs/jsr311-api/1.1.1/jsr311-api-1.1.1.pom
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :metron-config
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
