The solution is upgrading the C++ compiler on CentOS, details to the fix are 
here 
https://community.hortonworks.com/questions/148454/metron-041-build-failure-metron-config-failed-to-e.html?childToView=148635#answer-148635

To summarize, there is an undocumented dependency on C++11, portions of the 
Metron web assets require C++ 11 to build properly.

> On Nov 26, 2017, at 12:26 PM, Pawel Bialasiewicz <[email protected]> wrote:
> 
> I am having the same error for 0.4.0 and 0.4.1. I tried different versions of 
> Node and NPM. 
> I also tried building it using the Metron vagrant file, but it fails with the 
> same error. 
> Here are the issues:
> https://issues.apache.org/jira/browse/METRON-1318 
> <https://issues.apache.org/jira/browse/METRON-1318>
> https://issues.apache.org/jira/browse/METRON-1320 
> <https://issues.apache.org/jira/browse/METRON-1320>
> https://issues.apache.org/jira/browse/METRON-1327 
> <https://issues.apache.org/jira/browse/METRON-1327>
> Let me know If you will mange to find a solution.
> 
> Paweł
> 
> On 11/26/2017 06:19 PM, Eliel Garcia wrote:
>> Hello,
>> 
>> I’ve been trying to build Metron 0.4.1 via the following guide:
>>  
>> https://cwiki.apache.org/confluence/display/METRON/Metron+0.4.1+with+HDP+2.5+bare-metal+install+on+Centos+7+with+MariaDB+for+Metron+REST
>>  
>> <https://cwiki.apache.org/confluence/display/METRON/Metron+0.4.1+with+HDP+2.5+bare-metal+install+on+Centos+7+with+MariaDB+for+Metron+REST>
>>  
>> 
>> When executing mvn clean package -DskipTests -T 2C -P HDP-2.5.0.0,mpack I 
>> get the following error output:
>> 
>> [ERROR]
>> [ERROR] npm ERR! Linux 3.10.0-693.5.2.el7.x86_64
>> [ERROR] npm ERR! argv 
>> "/root/metron/metron-interface/metron-config/node/node" 
>> "/root/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] 
>> <mailto:[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] 
>> <mailto:[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!     
>> /root/metron/metron-interface/metron-config/npm-debug.log
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Metron ............................................. SUCCESS [  1.117 
>> s]
>> [INFO] metron-stellar ..................................... SUCCESS [  0.088 
>> s]
>> [INFO] stellar-common ..................................... SUCCESS [ 15.581 
>> s]
>> [INFO] metron-analytics ................................... SUCCESS [  0.006 
>> s]
>> [INFO] metron-maas-common ................................. SUCCESS [  0.807 
>> s]
>> [INFO] metron-platform .................................... SUCCESS [  0.004 
>> s]
>> [INFO] metron-zookeeper ................................... SUCCESS [  0.256 
>> s]
>> [INFO] metron-test-utilities .............................. SUCCESS [  2.140 
>> s]
>> [INFO] metron-integration-test ............................ SUCCESS [  7.068 
>> s]
>> [INFO] metron-maas-service ................................ SUCCESS [  3.411 
>> s]
>> [INFO] metron-common ...................................... SUCCESS [ 13.567 
>> s]
>> [INFO] metron-statistics .................................. SUCCESS [ 17.822 
>> s]
>> [INFO] metron-writer ...................................... SUCCESS [ 23.868 
>> s]
>> [INFO] metron-storm-kafka-override ........................ SUCCESS [  0.368 
>> s]
>> [INFO] metron-storm-kafka ................................. SUCCESS [  0.463 
>> s]
>> [INFO] metron-hbase ....................................... SUCCESS [  2.462 
>> s]
>> [INFO] metron-profiler-common ............................. SUCCESS [  9.078 
>> s]
>> [INFO] metron-profiler-client ............................. SUCCESS [ 15.297 
>> s]
>> [INFO] metron-profiler .................................... SUCCESS [ 41.862 
>> s]
>> [INFO] metron-hbase-client ................................ SUCCESS [  5.793 
>> s]
>> [INFO] metron-enrichment .................................. SUCCESS [ 41.032 
>> s]
>> [INFO] metron-indexing .................................... SUCCESS [ 14.053 
>> s]
>> [INFO] metron-solr ........................................ SUCCESS [ 13.584 
>> s]
>> [INFO] metron-pcap ........................................ SUCCESS [  1.415 
>> s]
>> [INFO] metron-parsers ..................................... SUCCESS [ 43.693 
>> s]
>> [INFO] metron-pcap-backend ................................ SUCCESS [ 22.508 
>> s]
>> [INFO] metron-data-management ............................. SUCCESS [ 47.151 
>> s]
>> [INFO] metron-api ......................................... SUCCESS [ 22.144 
>> s]
>> [INFO] metron-management .................................. SUCCESS [  6.126 
>> s]
>> [INFO] elasticsearch-shaded ............................... SUCCESS [  4.191 
>> s]
>> [INFO] metron-elasticsearch ............................... SUCCESS [ 47.117 
>> s]
>> [INFO] metron-deployment .................................. SUCCESS [  0.002 
>> s]
>> [INFO] Metron Ambari Management Pack ...................... SUCCESS [  0.735 
>> s]
>> [INFO] metron-contrib ..................................... SUCCESS [  0.002 
>> s]
>> [INFO] metron-docker ...................................... SUCCESS [  9.590 
>> s]
>> [INFO] metron-interface ................................... SUCCESS [  0.002 
>> s]
>> [INFO] metron-config ...................................... FAILURE [04:31 
>> min]
>> [INFO] metron-alerts ...................................... SKIPPED
>> [INFO] metron-rest-client ................................. SKIPPED
>> [INFO] metron-rest ........................................ SKIPPED
>> [INFO] site-book .......................................... SKIPPED
>> [INFO] 3rd party Functions (just for tests) ............... SKIPPED
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] Total time: 11:46 min
>> [INFO] Finished at: 2017-11-25T21:09:22-05:00
>> [INFO] Final Memory: 153M/597M
>> [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]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
>> switch.
>> [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 
>> <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
>> 
>> 
>> I made sure that I have the latest version of npm and nodejs via yum. Is 
>> there something that is missing out of the guide? I believe that I’ve 
>> followed it step by step. 
>> 
>> 
> 

Reply via email to