forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
azure-troubleshooting.html.md.erb
82 lines (53 loc) · 3.88 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
---
title: Troubleshooting PCF on Azure
owner: Ops Manager, Release Integration
---
<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
To mitigate slow performance or timeouts, the default value of the **Router Timeout to Backends (in seconds)** field is set to 900 seconds. This default value is set high to mitigate performance issues but operators should tune this parameter to fit their infrastructure.
To edit the **Router Timeout to Backends (in seconds)** field:
1. Select the **Pivotal Elastic Runtime** tile that is located within your **Installation Dashboard**.
1. Select the **Networking** tab.
1. Enter your desired time, in seconds, within the **Router Timeout to Backends (in seconds)** field.
<%= image_tag('images/router-timeout-ert.png') %>
1. Click **Save**.
<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 2.0.0 or greater. Run `az --version` from the command line to display your current Azure CLI version.
#### Solution
Install the Azure CLI 2.0 by following the instructions for your operating system in the [Azure documentation](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli).
<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.