LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.9

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

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 section of the Advanced Troubleshooting with the BOSH CLI topic.
  2. If necessary, download your PCF manifest:
    $ bosh download manifest DEPLOYMENT-NAME
    
    If you do not know your deployment name, run bosh deployments to display a list of available deployments.
  3. Set your current deployment to your PCF manifest:
    $ bosh deployment PATH-TO-PCF-MANIFEST
    
  4. Edit your deployment:
    $ bosh edit deployment
    
  5. Locate the haproxy section and add the following property: request_timeout_in_seconds: 180
  6. Save and exit the edited manifest.
  7. Redeploy:
    $ bosh deploy
    


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 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 npm update -g azure-cli from the command line, or follow the procedures below for your operating system:

  • Mac OS X: Download and run the Mac OS X installer.
  • Windows: Download and run the Windows installer. Install the Azure CLI on Windows 10. Use the command line, not the PowerShell, to run the Azure CLI.
  • Linux: Download the Linux 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 sudo npm install -g PATH-TO-TAR-FILE.


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.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub