Once you have finished Installing the Management Pack (VMware Tanzu Application Service) and Configuring the Management Pack (VMware Tanzu Application Service), check the Collection State and Collection Status for the adapter instance on the Solutions page. If they show as Not Collecting or No Data Receiving, respectively, the following troubleshooting topics can help you diagnose and correct common problems with your adapter instance.

  • Test Connection Errors
  • Adapter and Collector Log Files

Test Connection Errors

When Creating an Adapter Instance (VMware Tanzu Application Service), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

  • Nozzle API Errors
  • Cloud Controller API Errors
  • BOSH Director API Errors

Nozzle API Errors

Nozzle API - Valid Configuration: Hostname DNS lookup failed. Verify that the Nozzle hostname is correct, or supply an IP address.

Error Message: "Nozzle API - Valid Configuration: Hostname DNS lookup failed. Verify that the Nozzle hostname is correct, or supply an IP address."

Description: Ensure the Blue Medora Nozzle for PCF API Host is correct when Creating an Adapter Instance (VMware Tanzu Application Service). Alternatively, you may specify an IP address.

Nozzle API - Request Token: Failed to connect to the [Nozzle URL] endpoint. Verify host and/or port.

Error Message: "Nozzle API - Request Token: Failed to connect to the [Nozzle URL] endpoint. Verify host and/or port."

Description: Ensure the Nozzle API endpoint host and port were specified correctly when Creating an Adapter Instance (VMware Tanzu Application Service).

Nozzle API - Request Token: Unexpected exception encountered: Unable to connect to the Nozzle: [<error code>] <error message>

Error Message: "Nozzle API - Request Token: Unexpected exception encountered: Unable to connect to the Nozzle: [<error code>] <error message>."

Example: "Nozzle API - Request Token: Unexpected exception encountered: Unable to connect to the Nozzle: [404] Not Found."

Description: Unable to connect to the specified Nozzle API host. Ensure you have specified the correct Nozzle host (e.g., bluemedora-nozzle.YOUR-PCF-DOMAIN) and corresponding port (e.g., default port for Tile Nozzle deployment method is 443).

Nozzle API - Request Token: Unable to retrieve token in 10,000 ms

Error Message: "Nozzle API - Request Token: Unable to retrieve token in 10,000 ms."

Description: Failed to retrieve response in the specified timeout (10,000 ms, or 10 seconds).

Nozzle API - Request Token: Invalid username and/or password

Error Message: "Nozzle API - Request Token: Invalid username and/or password."

Description: Received a 401 HTTP status code. Ensure the Nozzle username/password specified when Creating a Credential (VMware Tanzu Application Service) are the correct UAA Client credentials (see: Blue Medora Nozzle for PCF Credentials (UAA Client) on the page Obtaining Nozzle, Cloud Controller, and BOSH Director Credentials (VMware Tanzu Application Service)).

Nozzle API - Request Token: Unable to Connect to the Nozzle: %s

Error Message: "Nozzle API - Request Token: Unable to connect to the Nozzle: %s"

Description: Received a non-200 and non-401 HTTP status code. Ensure you are able to connect to the Nozzle host from your browser window (e.g.,bluemedora-nozzle.YOUR-PCF-DOMAIN).

Nozzle API - Request Token: Token not found in header

Error Message: "Nozzle API - Request Token: Token not found in header"

Description: The token was absent from the HTTP response header.

Nozzle API - Request Token: Empty token in header

Error Message: "Nozzle API - Request Token: Empty token in header"

Description: The token returned in the HTTP response header was an empty string.

Nozzle API - Request Token: Unauthorized Credentials

Error Message: "Nozzle API - Request Token: Unauthorized credentials"

Description: Received a 401 HTTP status code. Ensure the Nozzle username/password specified when Creating a Credential (VMware Tanzu Application Service) are a UAA Client and password as described in Blue Medora Nozzle for PCF Credentials (UAA Client) on the page Obtaining Nozzle, Cloud Controller, and BOSH Director Credentials (VMware Tanzu Application Service)).

Nozzle API - Request Token: Invalid SSL Certificate

Error Message: "Nozzle API - Request Token: Invalid SSL Certificate"

Description: The SSL handshake failed due to an invalid SSL certificate. If you set the Validate Certificate Against Truststore Advanced Setting totrue when Creating an Adapter Instance (VMware Tanzu Application Service), ensure you have added the PCF host server SSL certificate to your vROps truststore (see: Adding an SSL Certificate to the vROps Truststore (VMware Tanzu Application Service)).

Nozzle API - Request Token: Unexpected exception encountered: %s

Error Message: "Nozzle API - Request Token: Unexpected exception encountered: %s"

Description: An unexpected exception was encountered when attempting to retrieve a token from the Nozzle API. Please contact Blue Medora Support for assistance.

Cloud Controller API Errors

Cloud Controller API - Valid Configuration: Hostname DNS lookup failed. Verify that the Cloud Controller hostname is correct, or supply an IP address

Error Message: "Cloud Controller API - Valid Configuration: Hostname DNS lookup failed. Verify that the Cloud Controller hostname is correct, or supply an IP address."

Description: Ensure the Cloud Controller API Host is correct when Creating an Adapter Instance (VMware Tanzu Application Service). Alternatively, you may specify an IP address.

Cloud Controller API - Authorization Endpoint: Unable to connect to the [CC URL] endpoint

Error Message: "Cloud Controller API - Authorization Endpoint: Unable to connect to [CC URL] endpoint. Verify host and/or port."

Description: We were unable to successfully connect to the '/info' endpoint on the specified Cloud Controller API host. Ensure you have specified the correct Cloud Controller API host and corresponding port (e.g., default port is 443).

Cloud Controller API - Request Token: Invalid username and/or password

Error Message: "Cloud Controller API - Request Token: Invalid username and/or password."

Description: Received a 401 HTTP status code. Ensure the Cloud Controller API username/password specified when Creating a Credential (VMware Tanzu Application Service) are the correct Cloud Controller API Credentials (UAA User) on the page Obtaining Nozzle, Cloud Controller, and BOSH Director Credentials (VMware Tanzu Application Service).

Cloud Controller API - Authorization Endpoint: Invalid SSL Certificate

Error Message: "Cloud Controller API - Authorization Endpoint: Invalid SSL Certificate"

Description: The SSL handshake failed due to an invalid SSL certificate. If you set theValidate Certificate Against Truststore Advanced Setting totrue when Creating an Adapter Instance (VMware Tanzu Application Service), ensure you have added the PCF host server SSL certificate to your vROps truststore (see: Adding an SSL Certificate to the vROps Truststore (VMware Tanzu Application Service)).

Cloud Controller API - Authorization Endpoint: The authorization_endpoint field was not found in the response from the Cloud API [info] endpoint. Check the host address

Error Message: "Cloud Controller API - Authorization Endpoint: The authorization_endpoint field was not found in the response from the Cloud API [info] endpoint. Check the host address."

Description: The 'authorization_endpoint' field was absent in the response from the '/info' endpoint on the specified Cloud Controller Host. Ensure you have specified the correct Cloud Controller API host.

Cloud Controller API: Authorization Endpoint: Unexpected Exception Encountered: %s

Error Message: "Cloud Controller API - Authorization Endpoint: Unexpected exception encountered: %s"

Description: An unexpected exception was encountered when attempting to retrieve the authorization endpoint from the Cloud Controller API. Please contact Blue Medora Support for assistance.

Cloud Controller API - Request Token: Unable to Connect to Host

Error Message: "Cloud Controller API - Request Token: Unable to connect to host. Check host and/or port."

Description: We were unable to connect to the host that was specified in the 'authorization_endpoint' field that returned by the specified Cloud Controller API host. Ensure you have specified the correct Cloud Controller API host and corresponding port (e.g., default port is 443).

Cloud Controller API - Request Token: The 'access_token' field was absent from the response body

Error Message: "Cloud Controller API - Request Token: The 'access_token' field was absent from the response body."

Description: The required 'access_token' field was blank or absent in the HTTP response body.

Cloud Controller API - Request Token: Invalid username and/or password for Cloud Controller API

Error Message: "Cloud Controller API - Request Token: Invalid username and/or password for Cloud Controller API."

Description: Received a 401 HTTP status code. Ensure the Cloud Controller API username/password specified when Creating a Credential (VMware Tanzu Application Service) are the correct Cloud Controller API Credentials (UAA User) on the page Obtaining Nozzle, Cloud Controller, and BOSH Director Credentials (VMware Tanzu Application Service).

Cloud Controller API - Request Token: Invalid SSL Certificate

Error Message: "Cloud Controller API - Request Token: Invalid SSL Certificate"

Description: The SSL handshake failed due to an invalid SSL certificate. If you set the Validate Certificate Against TruststoreAdvanced Setting totruewhenCreating an Adapter Instance (VMware Tanzu Application Service), ensure you have added the PCF host server SSL certificate to your vROps truststore (see: Adding an SSL Certificate to the vROps Truststore (VMware Tanzu Application Service)).

Cloud Controller API - Request Token: Unexpected Exception Encountered: %s

Error Message: "Cloud Controller API - Request Token: Unexpected exception encountered: %s"

Description: An unexpected exception was encountered when attempting to retrieve a token from the Cloud Controller API. Please contact Blue Medora Support for assistance.

BOSH Director API Errors

Failed to test adapter: BOSH connection info not provided correctly!

Error Message: "Failed to test adapter: BOSH connection info not provided correctly!"

Description: Ensure the BOSH Director API hostname specified when Creating an Adapter Instance (VMware Tanzu Application Service) is correct. See: BOSH Director API Host on the page Obtaining Nozzle, Cloud Controller, and BOSH Director Hostnames/IP Addresses (VMware Tanzu Application Service).

Failed to test adapter: java.net.ConnectException: Connection refused: /[BOSH URL]:[BOSH Port]

Error Message: "Failed to test adapter:java.net.ConnectException: Connection refused: /[BOSH URL]:[BOSH Port]"

Description: Ensure the BOSH Director API port specified when Creating an Adapter Instance (VMware Tanzu Application Service) is correct.

Failed to test adapter: Unable to authenticate to any listed BOSH API UAA authentication URL!

Error Message: "Failed to test adapter:Unable to authenticate to any listed BOSH API UAA authentication URL!"

Description: Ensure the BOSH Director Credentials (BOSH Director UAA Client) specified when Creating a Credential (VMware Tanzu Application Service) are correct.

Adapter and Collector Log Files

You can review adapter errors in the adapter and collector log files, which can be viewed in the vROps UI or in an external log viewer.

  • Adapter log files are located in the $VCOPS_BASE/user/log/adapters/PCFAdapter/ folder.
  • Collector log files are located in the $VCOPS_BASE/user/log/ folder.

To set the base log level for the collector in vROps:

  1. Navigate to Administration > Logs .
  2. Expand the MASTER folder, then select the COLLECTOR folder.
  3. Click the Edit Properties configure_iconicon.
  4. In the Root logger level drop-down menu, select the desired option.
  • The default logging level is warning.
  • To troubleshoot issues, set the logging level to info.

  • To view detailed messages, including micro steps, queries, and returned results, set the logging level to debug.

    Caution: Log files can become large very quickly if the logging level is set to  debug. As such, we recommend that you only set the logging level to debug for short periods of time.

For more information about viewing log files and modifying levels, refer to the vROps online help.