Troubleshooting PCF on Azure

Page last updated:

This topic describes how to troubleshoot known issues when deploying Pivotal Cloud Foundry (PCF) on Azure.

Troubleshoot Installation Issues

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.
  2. Select the Networking tab.
  3. Enter your desired time, in seconds, within the Router Timeout to Backends (in seconds) field. Router timeout ert
  4. Click Save.


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 of the Launching an Ops Manager Director Instance with an ARM Template topic or Step 4: Boot Ops Manager 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.


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 section of the Launching an Ops Manager Director Instance with an ARM Template topic or Step 4: Boot Ops Manager 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 section of the Launching an Ops Manager Director Instance with an ARM Template topic or the Step 4: Boot Ops Manager section of the Launching an Ops Manager Director Instance on Azure without an ARM Template topic.

Create a pull request or raise an issue on the source for this page in GitHub