Support Questions

Find answers, ask questions, and share your expertise

how to trace the blueprint , and how to find the reason that BP failed

avatar

in some cases we get failed during blueprint installation on ( new ambari cluster )

the last line that we run in order to install the blueprint is:

      curl -H "X-Requested-By: ambari" -X POST -u "$USER"":""$PASSWORD" http://$host:8080/api/v1/clusters/HDP -d @hostmapping.json

in case of blueprint failed , we can just to look from the ambari cluster GUI and see the secrives that failed

but this isn't gives us the root cause why bluprint failed

please advice how to trace the bluprint installation and find out on which exactly blueprint failed ?

Michael-Bronson
1 ACCEPTED SOLUTION

avatar
Master Mentor

@Michael Bronson

We can take a look at the "/var/log/ambari-server/ambari-serverlog" file to see why it failed. ambari-server.log logs the cause of blueprint installation failure.

View solution in original post

4 REPLIES 4

avatar
Master Mentor

@Michael Bronson

We can take a look at the "/var/log/ambari-server/ambari-serverlog" file to see why it failed. ambari-server.log logs the cause of blueprint installation failure.

avatar

@Jay I see this warning

WARN [Stack Version Loading Thread] LatestRepoCallable:237 - Could not load version definition for HDP-2.6 identified by http://public-repo-1.hortonworks.com/HDP/sles12/2.x/updates/2.6.4.0/HDP-2.6.4.0-91.xml. null javax.xml.bind.UnmarshalException , but its very starnge because we use the lower HDP version

Michael-Bronson

avatar

why he check the repo http://public-repo-1.hortonworks.com/HDP/sles12/2.x/updates/2.6.4.0/HDP-2.6.4.0-91.xml. ? , , we use local repo in ambari server

Michael-Bronson

avatar

@jay if you

think this isnt the direction then what to capture from the log?

Michael-Bronson