I've installed node.js. :
Metron 0.6.0 -- * Metron_0.6.0 -- commit 62310743a0c1d4a27db47a89cf79496d594c8bcf Author: justinleet <email@example.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-126.96.36.199-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
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.
Hi @Nor Liana Kamaruzzaman, the single node uses Ambari to deploy the cluster. So what you are seeing is correct.
I am suspecting if there is resource starvation because of which you are seeing the CPU locked out issues. Can you try to find a server with higher resources? Or upgrade the present server?
Hey @Nor Liana Kamaruzzaman ,
I am hoping you have got a chance to set up a different system with CentOS 7 and able to proceed further. In the context of this thread, would you mind marking the best answer if you feel the original question was answered? Thanks!