Support Questions
Find answers, ask questions, and share your expertise

[Apache Metron] Ansible Failed To Complete Successfully

Solved Go to solution

Re: [Apache Metron] Ansible Failed To Complete Successfully

Super Collaborator

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?

Re: [Apache Metron] Ansible Failed To Complete Successfully

Explorer

Hi @asubramanian,

It stopped here, what should I do next?

==> default: Rsyncing folder: /home/akaticentos6/metron/metron-deployment/development/centos6/ => /vagrant

Re: [Apache Metron] Ansible Failed To Complete Successfully

Super Collaborator

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

Re: [Apache Metron] Ansible Failed To Complete Successfully

Explorer

Hi @asubramanian,

I re-create the Vagrantfile using 'rm -r Vagrantfile' and 'vagrant init centos/6' And then I run vagrant up, and now I got this: (had to put in pastebin as it exceeds char limit) https://pastebin.com/x99i5zpK

Now I'll try clean packages

Re: [Apache Metron] Ansible Failed To Complete Successfully

Explorer

@asubramanian

This is the result when I run 'mvn -e package' : https://pastebin.com/3UDfH6GT

Re: [Apache Metron] Ansible Failed To Complete Successfully

Super Collaborator

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.

Re: [Apache Metron] Ansible Failed To Complete Successfully

Explorer

Hey @asubramanian,

Thank you for waiting.I will try :)

Before I proceed, which one should I follow to try on CentOS 7?
Dev VM install for CentOS or Metron 0.4.1 with HDP 2.5 bare-metal install on Centos 7 with MariaDB for Metron REST. My system is only 12GB RAM and dual processor thought.

Re: [Apache Metron] Ansible Failed To Complete Successfully

Super Collaborator

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).

Re: [Apache Metron] Ansible Failed To Complete Successfully

Explorer

Hi @asubramanian,

Recently I tried with CentOS 7, but ran into a problem:

Message from syslogd@localhost at Oct  8 13:32:47 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#1 stuck for 33s! [nautilus-deskto:2881]

Message from syslogd@localhost at Oct  8 13:33:32 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 37s! [kworker/0:1:13622]
fatal: [node1]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Connection timed out during banner exchange\r\n", "unreachable": true}
    to retry, use: --limit @/home/<user>/metron/metron-deployment/development/centos6/ansible/playbook.retry

PLAY RECAP *********************************************************************
node1                      : ok=23   changed=14   unreachable=1    failed=0   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.


Below is the result of platform-info.sh:

Metron 0.6.0
--
* Metron_0.6.0
--
commit 62310743a0c1d4a27db47a89cf79496d594c8bcf
Author: justinleet <justinjleet@gmail.com>
Date:   Tue Sep 4 19:53:37 2018 -0400

    METRON-1764 Update version to 0.6.0 (justinleet) closes apache/metron#1183
--
--
ansible 2.5.0
  config file = /home/<user>/metron/metron-deployment/ansible.cfg
  configured module search path = [u'/home/<user>/metron/metron-deployment/extra_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-1.8.0.181-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
scripts/platform-info.sh: line 77: node: command not found
--
npm
scripts/platform-info.sh: line 82: npm: command not found
--
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.97 MB
Processor Model: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
Processor Speed: 3392.460 MHz
Total Physical Processors: 2
Total cores: 2
Disk information:
/dev/mapper/centos-root   45G   20G   25G  44% /
/dev/sda1               1014M  221M  794M  22% /boot
This CPU appears to support virtualization


Please advice...

Re: [Apache Metron] Ansible Failed To Complete Successfully

Super Collaborator

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