Troubleshooting And Log Files

Troubleshooting Block Storage Service Problems

If your Private Cloud Director Service Health dashboard is reporting that the block storage service is unhealthy, or if you are running into unexpected issues when performing block storage service operations such as volume creation, attachment etc, this likely means:

1. One or more hosts assigned with Block Storage role may be offline or unavailable

2. The hosts with Block Storage role assigned may be online but the service components may be offline or experiencing error connecting to or working with your specific storage backend.

Refer to the block storage service Log Files to debug the issues further.

Log Files

• The log file that corresponds to all block storage attach / detach operations is located at /var/log/pf9/cindervolume-base.log.This file contains information about:

  • Storage backend driver used

  • Whether the Block Storage Service could connect to the storage backend being used

  • Any errors when creating volumes, copying volumes, and attaching/detaching volumes to virtual machines

• Look at the compute service log file /var/log/pf9/ostackhost.log file for further details when debugging any issues related to volume attachment to virtual machines.