Troubleshooting Guide for CloudBees Jenkins Platform on Pivotal Cloud Foundry

Note: CloudBees Jenkins Platform for PCF is deprecated, and no further development will be made against this tile.

This topic contains troubleshooting information for CloudBees Jenkins Platform on Pivotal Cloud Foundry (PCF).

Step 1: SSH into the VM

To troubleshoot CloudBees Jenkins Platform on PCF, SSH into its VMs by performing the following steps:

  1. SSH into a host with access to your BOSH installation. Usually, this is the Ops Manager VM. To SSH into Ops Manager, perform the procedures in the SSH into Ops Manager section of the Advanced Troubleshooting with the BOSH CLI topic.
  2. Perform the procedures in the Log into BOSH section of the Advanced Troubleshooting with the BOSH CLI topic to target and log in to the BOSH Director from the host with access to BOSH.

  3. Set the BOSH deployment to the current CloudBees Jenkins Platform tile:

    $ bosh deployment /var/tempest/workspaces/default/deployments/$(bosh deployments | grep p-jenkins | cut -f 2 -d "|" | xargs).yml
    
  4. List the VMs managed by the CloudBees Jenkins Platform tile:

    $ bosh ssh
    
    This command lists the following VMs:

    • jenkins_slave/0
    • jenkins_master/0
    • jenkins_shared_slave/0
    • jenkins-oc/0
  5. Enter the number of the VM you want to troubleshoot.

  6. From the VM, switch to root user:

    $ sudo su

Step 2: Perform Troubleshooting Procedures

Consult the following list for the locations of critical files on the VMs managed by the Cloudbees Jenkins Platform tile:

  • Jenkins storage: /var/vcap/store
  • Logs: /var/vcap/sys/log/
  • JDK installation: /var/vcap/packages/openjdk-8
  • Utilities, including jstack and jstat: /bin/

You can use monit to troubleshoot with the following commands:

  • Check services status: monit status
  • Restart a service: monit restart YOUR-SERVICE
Create a pull request or raise an issue on the source for this page in GitHub