Hortonworks Docs » Cloudbreak 2.9.0 » Troubleshooting Cloudbreak

Troubleshooting Cloudbreak

Also available as:

PDF

loading table of contents...

Getting help
Create a troubleshooting bundle
Checking Cloudbreak logs
Troubleshooting Cloudbreak
Troubleshooting Cloudbreak on AWS
- User is not authorized to perform: sts:AssumeRole
Troubleshooting Cloudbreak on Azure
Troubleshooting cluster creation
Troubleshooting Cloudbreak CLI

Checking Cloudbreak logs

When troubleshooting, you can access the following Cloudbreak logs.

Cloudbreak logs
When installing Cloudbreak using a pre-built cloud image, the Cloudbreak deployer location and the cbd root folder is /var/lib/cloudbreak-deployment. You must execute all cbd actions from the cbd root folder as "cloudbreak" user.
Saltstack logs
Cloudbreak uses Saltstack to install Ambari and the necessary packages for the HDP/HDF provisioning. Salt Master always runs alongside the Ambari Server node. Each instance in the cluster runs a Salt Minion, which connects to the Salt Master.
Ambari logs
Cloudbreak uses Ambari to orchestrate the installation of the different HDP/HDF components. Each instance in the cluster runs an Ambari agent which connects to the Ambari server. Ambari server is declared by the user during the cluster installation wizard.
Recipe logs
Cloudbreak supports “recipes” - user-provided customization scripts that can be run prior to or after cluster installation. It is the user’s responsibility to provide an idempotent well tested script. If the execution fails, the recipe logs can be found at /var/log/recipes on the nodes on which the recipes were executed.

© 2012–2019, Hortonworks, Inc.

Document licensed under the Creative Commons Attribution ShareAlike 4.0 License.

Hortonworks.com | Documentation | Support | Community