Use this section as a reference to aid you if you encounter any errors while using VMware Cloud Director Container Service Extension.

Troubleshooting with logs

You can refer to the logs provided by the actions VMware Cloud Director Container Service Extension performs. You can find the log bundles in the .cse-logs folder in the home directory on your local machine.

Table 1. Log bundles

Log

Description

cse-client-info.log, cse-client-debug.log

Logs VMware Cloud Director Container Service Extension client CLI activities. Requests made to VMware Cloud Director Container Service Extension server, their responses and debugging information are recorded here.

cse-client-wire.log

Logs all REST calls originating from VMware Cloud Director Container Service Extension CLI client to the server. This file is generated only if the environment variable CSE_CLIENT_WIRE_LOGGING is set to true.

vcd.log, vcd_cli_error.log

Log the vcd-cli and pyvcloud activity on client side. Stack traces and HTTP messages specific to vcd-cli are recorded here

Note:

vcd-cli logs can be found in the path where the command was executed.

Common Errors

This section describes the common errors that occur when using VMware Cloud Director Container Service Extension.

Table 2. Common errors

Error

Solution

VMware Cloud Director Container Service Extension login fails

Ensure you are logged in using vcd-cli.

VMware Cloud Director Container Service Extension does not communicate with VMware Cloud Director

Ensure you specify a unique amqp exchange in the VMware Cloud Director Container Service Extension configuration file. Do not use the exchange that is specified in the VMware Cloud Director extensibility section for VMware Cloud Director Container Service Extension. As long as a uniquely-named exchange is specified in the configuration file, VMware Cloud Director Container Service Extension creates that exchange and uses it to communicate with VMware Cloud Director. No changes are necessary in VMware Cloud Director extensibility section or in RabbitMQ.