Options
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Solved
Go to solution
Module Failure Error in Ambari
Labels:
- Labels:
-
Apache Ambari
-
Apache Metron
Contributor
Created ‎09-07-2016 05:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am getting this error while i am trying to install the latest apache metron using quick-dev-platform
TASK [ambari_config : Start the ambari cluster - no wait] ********************** changed: [node1] TASK [ambari_config : Start the ambari cluster - wait] ************************* fatal: [node1]: FAILED! => {"changed": false, "failed": true, "module_stderr": "", "module_stdout": "", "msg": "MODULE FAILURE", "parsed": false} PLAY RECAP ********************************************************************* node1 : ok=15 changed=1 unreachable=0 failed=1 Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again.
Following is the output of my platform
./metron-deployment/scripts/platform-info.shMetron 0.2.0BETA fatal: Not a git repository (or any of the parent directories): .git -- ansible 2.0.0.2 config file = configured module search path = Default w/o overrides -- Vagrant 1.8.1 -- Python 2.7.11 -- Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T21:41:47+05:00) Maven home: /usr/share/apache-maven Java version: 1.8.0_45, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_45/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-642.el6.x86_64", arch: "amd64", family: "unix" -- Linux CentOS17 2.6.32-642.el6.x86_64 #1 SMP Tue May 10 17:27:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Any help will be appreciated.
1 ACCEPTED SOLUTION
Contributor
Created ‎10-05-2016 07:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was problem due to insufficient RAM. I increased the RAM to 64 GB and its now starting to up.
1 REPLY 1
Contributor
Created ‎10-05-2016 07:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was problem due to insufficient RAM. I increased the RAM to 64 GB and its now starting to up.
