forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathazure-troubleshooting.html.md.erb
100 lines (71 loc) · 4.85 KB
/
azure-troubleshooting.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
---
title: Troubleshooting PCF on Azure
owner: Ops Manager
---
<strong><%= modified_date %></strong>
<html class="list-style-none"></html>
This topic describes how to troubleshoot known issues when deploying Pivotal Cloud Foundry (PCF) on Azure.
## <a id="install-issues"></a> Troubleshoot Installation Issues
### <a id="timeouts"></a> Slow Performance or Timeouts
#### Symptom
Developers suffer from slow performance or timeouts when pushing or managing apps, and end users suffer from slow performance or timeouts when accessing apps
#### Explanation
The Azure Load Balancer (ALB) disconnects active TCP connections lying idle for over four minutes.
#### Solution
Because HAProxy sits between the ALB and the router, you can resolve the problem by setting the HAProxy timeout value to be greater than the timeout value of the ALB. Perform the following steps:
1. Target your BOSH Director by following the steps in the [Log into BOSH](./trouble-advanced.html#log-in) section of the _Advanced Troubleshooting with the BOSH CLI_ topic.
1. If necessary, download your PCF manifest:
<pre class="terminal">
$ bosh download manifest DEPLOYMENT-NAME
</pre>
If you do not know your deployment name, run `bosh deployments` to display a list of available deployments.
1. Set your current deployment to your PCF manifest:
<pre class="terminal">
$ bosh deployment PATH-TO-PCF-MANIFEST
</pre>
1. Edit your deployment:
<pre class="terminal">
$ bosh edit deployment
</pre>
1. Locate the `haproxy` section and add the following property:
`request_timeout_in_seconds: 180`
1. Save and exit the edited manifest.
1. Redeploy:
<pre class="terminal">
$ bosh deploy
</pre>
<hr>
### <a id="cannot-copy-om"></a> Cannot Copy the Ops Manager Image
#### Symptom
Cannot copy the Ops Manager image into your storage account when completing [Step 2: Copy Ops Manager Image](./azure-arm-template.html#copy) of the _Launching an Ops Manager Director Instance with an ARM Template_ topic
or [Step 4: Boot Ops Manager](./azure-om-deploy.html#boot) of the _Launching an Ops Manager Director Instance on Azure without an ARM Template_ topic.
#### Explanation
You have an outdated version of the Azure CLI. You need the Azure CLI version 0.9.18 or greater. Run `azure --version` from the command line to display your current Azure CLI version.
#### Solution
Upgrade your Azure CLI to the current version by reinstalling the new version. Run <code>npm update -g azure-cli</code> from the command line, or follow the procedures below for your operating system:
* **Mac OS X**: Download and run the [Mac OS X](http://aka.ms/mac-azure-cli) installer.
* **Windows**: Download and run the [Windows](https://www.microsoft.com/web/handlers/webpi.ashx?command=getinstallerredirect&appid=windowsazurexplatcli&mode=new) installer. Install the Azure CLI on Windows 10. Use the command line, not the PowerShell, to run the Azure CLI.
* **Linux**: Download the [Linux](http://aka.ms/linux-azure-cli) tar file. Install the Azure CLI on Ubuntu Server 14.04 LTS. To install the Azure CLI on Linux, you must first install Node.js and npm, and then run <code>sudo npm install -g PATH-TO-TAR-FILE</code>.
<hr>
### <a id="bosh-init-fails"></a> Deployment Fails at "bosh-init"
#### Symptom
After clicking **Apply Changes** to install Ops Manager and Elastic Runtime, the deployment fails at `bosh-init` with an error message similar to the following:
```
Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Waiting until instance is ready:
Starting SSH tunnel:
Parsing private key file '/tmp/bosh_ec2_private_key.pem':
asn1: structure error: tags don't match (16 vs {class:3 tag:28 length:127
isCompound:false}) {optional:false explicit:false application:false
defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} pkcs1PrivateKey @2
===== 2016-09-29 16:28:22 UTC Finished "bosh-init deploy
/var/tempest/workspaces/default/deployments/bosh.yml";
Duration: 328s; Exit Status: 1
Exited with 1.
```
#### Explanation
You provided a passphrase when creating your key pair in the [Step 2: Copy Ops Manager Image](./azure-arm-template.html#copy) section of the _Launching an Ops Manager Director Instance with an ARM Template_ topic or [Step 4: Boot Ops Manager](./azure-om-deploy.html#boot) section of the _Launching an Ops Manager Director Instance on Azure without an ARM Template_ topic.
#### Solution
Create a new key pair with no passphrase and redo the installation, beginning with the step for creating a VM against the Ops Manager image in the [Step 2: Copy Ops Manager Image](./azure-arm-template.html#copy) section of the _Launching an Ops Manager Director Instance with an ARM Template_ topic or the [Step 4: Boot Ops Manager](./azure-om-deploy.html#boot) section of the _Launching an Ops Manager Director Instance on Azure without an ARM Template_ topic.