If the vxdbd daemon is not running, SFDB commands may fail with an error message. The following steps can help in troubleshooting the instances of the daemon that are down:
Use the /opt/VRTS/bin/vxdbdctrl status to verify that the daemon is running.
If the output states that the daemon is not running, use the /opt/VRTS/bin/vxdbdctrl start command to start the daemon.
If the daemon fails to start, verify that no other process is listening on the same port. If there is such a process, stop that process, or configure vxdbd to listen on a different port.
The daemon generates logs in the file at
/var/vx/vxdba/logs/vxsfaed.log. To enable verbose logging, edit the
/etc/vx/vxdbed/admin.properties configuration file and set LOG_LEVEL to DEBUG.