incubator-ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hitesh Shah <hit...@hortonworks.com>
Subject Re: ambari install error
Date Wed, 01 Aug 2012 14:31:28 GMT
Hi again, 

On the puppet master i.e. the ambari master, could you go into /var/lib/puppet/reports/9-3-2/.
There should be 2 report files in there for each host in question. Could you grep through
them to find "err)" - the first match in each file will tell you what command failed causing
the install failure. 

-- Hitesh 

On Aug 1, 2012, at 3:05 AM, shidongjie wrote:

> Hi,everyone   
>      I encountered an error while installing ambari,error is
>      
>  "3": {
>         "nodeReport": {
>             "PUPPET_KICK_FAILED": [],
>             "PUPPET_OPERATION_FAILED": [
>                 "hadooptestnode2.qyops.com",
>                 "hadooptestnode3.qyops.com"
>             ],
>             "PUPPET_OPERATION_TIMEDOUT": [],
>             "PUPPET_OPERATION_SUCCEEDED": []
>         },
>         "nodeLogs": {
>             "hadooptestnode2.qyops.com": {
>                 "reportfile": "/var/lib/puppet/reports/9-3-2/hadooptestnode2.qyops.com",
>                 "overall": "FAILED",
>                 "finishtime": "2012-08-01 17:57:56.253304 +08:00",
>                 "message": [
>                     "Loaded state in 0.00 seconds",
>                     "Loading facts in kadm_keytab",
>                     "Loading facts in kadm_keytab",
>                     "Not using expired catalog for hadooptestnode2.qyops.com from cache;
expired at Wed Aug 01 08:57:51 +0800 2012",
>                     "Using cached catalog",
>                     "\"catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml;
using pson\"",
>                     "Caching catalog for hadooptestnode2.qyops.com",
>                     "Creating default schedules",
>                     "Loaded state in 0.00 seconds",
>                     "Applying configuration version '9-3-2'",
>                     "\"requires Exec[untar_modules]\"",
>                     "\"requires Exec[puppet_apply]\"",
>                     "Skipping device resources because running on a host",
>                     "Skipping device resources because running on a host",
>                     "Skipping device resources because running on a host",
>                     "Skipping device resources because running on a host",
>                     "Skipping device resources because running on a host",
>                     "Skipping device resources because running on a host",
>                     "\"file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson\"",
>                     "Finishing transaction 23557468746320",
>                     "\"FileBucket adding {md5}687ce724cdb45cc92c9a03cfcea4f8a8\"",
>                     "Filebucketed /etc/puppet/agent/modules.tgz to puppet with sum 687ce724cdb45cc92c9a03cfcea4f8a8",
>                     "&id005 \"content changed '{md5}687ce724cdb45cc92c9a03cfcea4f8a8'
to '{md5}d978d81059216cfaa660e9e180587b26'\"",
>                     "\"The container Class[Manifestloader] will propagate my refresh
event\"",
>                     "Executing 'rm -rf /etc/puppet/agent/modules ; tar zxf /etc/puppet/agent/modules.tgz
-C /etc/puppet/agent/ --strip-components 3'",
>                     "Executing 'rm -rf /etc/puppet/agent/modules ; tar zxf /etc/puppet/agent/modules.tgz
-C /etc/puppet/agent/ --strip-components 3'",
>                     "&id002 executed successfully",
>                     "\"The container Class[Manifestloader] will propagate my refresh
event\"",
>                     "Executing 'sh /etc/puppet/agent/modules/puppetApply.sh'",
>                     "Executing 'sh /etc/puppet/agent/modules/puppetApply.sh'",
>                     "\"Wed Aug 01 17:57:58 +0800 2012 Puppet (info): Loading facts in
kadm_keytab\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>                     "\"Could not retrieve selinux: Invalid argument - /proc/self/attr/current\"",
>  
> Cluster operating system is centos 5.8 ,
> May I ask how to solve it
> shidongjie


Mime
View raw message