Troubleshooting

Use this section as a reference to aid you while using VMware Cloud Director Container Service Extension as a service provider administrator.

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-install-wire_[datetimestamp].log	Logs all server requests and responses originating from VMware Cloud Director Container Service Extension during installation, upgrade or template install activity. This file is generated only if the log_wire field under service section of config file is set to true
cse-server-debug.log, cse-server-info.log	Logs VMware Cloud Director Container Service Extension server’s activity. Server requests and responses are recorded here, as well as outputs of scripts that were run on VMs.
cse-server-wire-debug.log	Logs all REST calls originating from VMware Cloud Director Container Service Extension to VMware Cloud Director. This file is generated only if the log_wire field under service section of config file is set to true
cse-server-cli.log	Logs all the VMware Cloud Director Container Service Extension server CLI activity. VMware Cloud Director Container Service Extension server commands that are executed, the outputs and debugging information are recorded here.
cse-server-cli-wire.log	Logs all the requests and responses originated from VMware Cloud Director Container Service Extension while executing the server CLI commands. This file is generated only if the log_wire field under service section of config file is set to true
nsxt-wire.log	Logs all the REST calls originating from VMware Cloud Director Container Service Extension server to NSX-T server. This file is generated only if the log_wire field under service section of config file is set to true.
cloudapi-wire.log	Logs all the CloudAPI REST calls made to VMware Cloud Director. This file is generated only if the log_wire field under service section of config file is set to true.
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.
cse-install_[datetimestamp].log	Logs VMware Cloud Director Container Service Extension install activity. Any output from scripts or error messages during VMware Cloud Director Container Service Extension installation, VMware Cloud Director Container Service Extension upgrade or template installation are logged here.
vcd.log, vcd_cli_error.log	Log vcd-cli and pyvcloud activity on client side. Stack traces and HTTP messages specific to vcd-cli are recorded here Note: VMware Cloud Director 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
The configuration file fields display errors	Ensure the configuration file fields are correct
VMware Cloud Director Container Service Extension log-in fails	Ensure you are logged in using vcd-cli.
CSE 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 VCD's 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. It is not necessary to make changes in VMware Cloud Director extensibility section or in RabbitMQ.
VMware Cloud Director Container Service Extension installation or template creation fails	If this happens, invalid VMs, clusters or templates may exist. VMware Cloud Director Container Service Extension cannot auto detect that those entities are invalid. Therefore, it is necessary to manually remove these entities from VMware Cloud Director.