Have you checked this issue with python-requests package not installed: https://issues.apache.org/jira/browse/METRON-1451 ? ... View more

Hey @Nor Liana Kamaruzzaman, this is great news! I am glad you were able to resolve the issues. Would you mind accepting the answer that helped you the most? Cheers, Anand ... View more

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? ... View more

Hi @Nor Liana Kamaruzzaman, Can you try this solution here for the timeout issue with the vagrant VM? Also, from the platform-info script, I can see that node JS installation is missing. Can you fix that too and try again? node scripts/platform-info.sh: line 77: node: command not found -- npm scripts/platform-info.sh: line 82: npm: command not found ... View more

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! ... View more

Hey @Nor Liana Kamaruzzaman , cool! I would suggest that you try with the Dev VM install for CentOS link, and with the latest 'master' branch. It should be pretty straight forward once you have the pre-requisites setup. Note that the latest master requires ansible version to be 2.4.0+ (see latest instructions here). ... View more

Hey @Nor Liana Kamaruzzaman, this definitely looks to me like an issue with the Docker version. This error message especially: "Sending build context to Docker daemon ", "[ERROR] Command execution failed.", "org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)", "\tat org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:404)", "\tat Would you be able to bring up a CentOS 7 environment afresh? It looks like the Docker pre-requisites asks for CentOS7. Here is an excerpt from their docs: https://docs.docker.com/install/linux/docker-ce/centos/#prerequisites OS requirements To install Docker CE, you need a maintained version of CentOS 7. Archived versions aren’t supported or tested. ... View more

Hm.. that is strange. I see from your output of platform-info.sh that you have the right version of the vagrant hostmanager plugin (ver 1.8.9). The one difference I see is that your machine is named as ' default ', while it should show as ' node1 '. See sample output from my box. Observe the logs.. ➜ ~ vagrant up Running with ansible-skip-tags: ["sensors"] Bringing machine 'node1' up with 'virtualbox' provider... ==> node1: Importing base box 'centos/6'... ==> node1: Matching MAC address for NAT networking... ==> node1: Checking if box 'centos/6' is up to date... ==> node1: Setting the name of the VM: centos6_node1_1537451480618_72587 ==> node1: Clearing any previously set network interfaces... ==> node1: Preparing network interfaces based on configuration... node1: Adapter 1: nat node1: Adapter 2: hostonly ==> node1: Forwarding ports... node1: 22 (guest) => 2222 (host) (adapter 1) ==> node1: Running 'pre-boot' VM customizations... ==> node1: Booting VM... ==> node1: Waiting for machine to boot. This may take a few minutes... node1: SSH address: 127.0.0.1:2222 node1: SSH username: vagrant node1: SSH auth method: private key node1: node1: Vagrant insecure key detected. Vagrant will automatically replace node1: this with a newly generated keypair for better security. node1: node1: Inserting generated public key within guest... node1: Removing insecure key from the guest if it's present... node1: Key inserted! Disconnecting and reconnecting using new SSH key... ==> node1: Machine booted and ready! ==> node1: Checking for guest additions in VM... node1: No guest additions were detected on the base box for this VM! Guest node1: additions are required for forwarded ports, shared folders, host only node1: networking, and more. If SSH fails on this machine, please install node1: the guest additions and repackage the box to continue. node1: node1: This is not an error message; everything may continue to work properly, node1: in which case you may ignore this message. ==> node1: Setting hostname... ==> node1: Configuring and enabling network interfaces... node1: SSH address: 127.0.0.1:2222 node1: SSH username: vagrant node1: SSH auth method: private key ==> node1: Rsyncing folder: /Users/asubramanian/Desktop/Metron/anand-metron-fork/shane-cypress-test/metron/metron-deployment/development/centos6/ => /vagrant ==> node1: [vagrant-hostmanager:guests] Updating hosts file on active guest virtual machines... ==> node1: [vagrant-hostmanager:host] Updating hosts file on your workstation (password may be required)... Password: ==> node1: Running provisioner: ansible... node1: Running ansible-playbook... PLAY [all] ********************************************************************* <br> Can you confirm that you are running the vagrant up command from the following folder location: metron/metron-deployment/development/centos6 Also, as suggested by @Otto Fowler, can you try to compile outside of the full-dev deployment and see if that works? You can do this like follows and look for any failures in the output.: cd <root-level-metron-folder> mvn clean package I would also like to look at your Vagrantfile at the following location. Can you attach it? metron/metron-deployment/development/centos6/Vagrantfile ... View more

Hi @Nor Liana Kamaruzzaman , the vagrant folder not being present seems to be okay. Did the vagrant up command proceed further after upgrading the node and npm? ... View more