Hortonworks Docs » Cloudbreak 2.9.2 » Troubleshooting Cloudbreak

Troubleshooting Cloudbreak

Also available as:

PDF

loading table of contents...

Migrate existing clusters to access new packages behind the paywall
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

Troubleshooting cluster creation

The following section lists common issues related to cluster creation.

Configure communication via private IPs on AWS
Cloudbreak uses public IP addresses when communicating with cluster nodes. On AWS, you can configure it to use private IPs instead of public IPs by setting the CB_AWS_VPC variable in the Profile.
Cannot access Oozie web UI
Ext JS is GPL licensed software and is no longer included in builds of HDP 2.6. Because of this, the Oozie WAR file is not built to include the Ext JS-based user interface unless Ext JS is manually installed on the Oozie server.
Failed to retrieve the server's certificate
Cloudbreak-managed cluster fails with "Infrastructure creation failed. Reason: Failed to retrieve the server's certificate".
Quota limitations
Each cloud provider has quota limitations on various cloud resources, and these quotas can usually be increased on request. If there is an error message in Cloudbreak stating that there are no more available EIPs (Elastic IP Address) or VPCs, you need to request more of these resources.
Connection timeout when ports are not open
A common reason for connection timeout is security group misconfiguration.
Blueprint errors
The following sections list common blueprint-related issues.
Recipe errors
The following sections list common recipe related issues.

© 2012–2019, Hortonworks, Inc.

Document licensed under the Creative Commons Attribution ShareAlike 4.0 License.

Hortonworks.com | Documentation | Support | Community