Miscellaneous Issues

Symptom Recommended Action
Unable to expand a virtual cluster. Collect and analyze bd-mgmt.log.
Unable to create a root disk. Collect and analyze /var/log/secure.
Infinite loop occurs post-configuration. Collect and analyze all logs under /var/log/bluedata on the Controller host.
The bds-controller service stopped unexpectedly. Collect a Level 2 support bundle, as described in Generating a Support Bundle.
The UserAuth service fails on several clusters. Collect /var/log/sssd.log, and then restart the sssd service by executing the following command:
service sssd restart
There is a problem with the bds-mgmt service. On the Controller host, collect and analyze /var/log/bluedata/bds-mgmt.log.
Miscellaneous DataTap issues.

Collect and analyze the following:

  • /var/log/bluedata/bds-cachingnode.log
  • /var/log/bluedata/bds-dataserver.log
Miscellaneous problem inside a container. On the affected container, collect and analyze /var/log/bluedata/vagent.
A container has crashed.
  1. On the Controller host, collect and analyze /var/log/bluedata/bds-mgmt.log.
  2. Log in to the physical host where the container was running using the command bdconfig --getvms.
  3. In /var/log/messages, look for Out of memory.
  4. Collect the following files after the container crash:
    • Container Platform host:/var/log/messages
    • Container Platform host:/var/log/docker
    • Container Platform host:"% docker stats" output
BDFS error 6 (mount_point _initialization failure) occurs. See Storage Issues.
For 7.x OS installs, rebooting a host may cause some services that depend on network services to go down and not restart, as shown in the Services tab of the Platform Administrator Dashboard screen.

Restart the services after disabling the NetworkManager by executing the following commands on the Container Platform host:

systemctl stop NetworkManager
systemctl disable NetworkManager
systemctl restart network
systemctl restart bds-controller
systemctl restart bds-worker
After restarting the monitoring container, services may fail to start, as shown in the Services tab of the Platform Administrator Dashboard screen.

On the Controller host, restart the service manually by executing the following command:

docker exec <Id-of-Container-running-"epic/monitoring"-Image> service metricbeat restart