The vxdbd daemon handles communication to and from the Veritas Storage Foundation product software. By default, vxdbd communicates with product over port number 3233. If there are conflicts with this port or other port-related problems, you can change the port by changing the VXDBD_SOCKET setting located in the /etc/vx/vxdbed/admin.properties file.
Normally the vxdbd daemon starts automatically when the host boots up. However, if the daemon reports errors or if the daemon process dies, you may have to manually start or stop it. There is also a status command that reports the current state of the daemon to confirm that it is currently running.
Only the root user can stop vxdbd. Any user can start vxdbd or display its status.
To change the communications port used by the vxdbd daemon
As the root user, stop the vxdbd daemon:
/opt/VRTSdbed/common/bin/vxdbdctrl stop
In the /etc/vx/vxdbed/admin.properties file, change the value of the VXDBD_SOCKET variable to a new port number:
VXDBD_SOCKET=3233
/opt/VRTSdbed/common/bin/vxdbdctrl start
If the system is part of a multi-host configuration, change the port on all hosts involved by repeating this procedure on each host.
The vxdbd daemon log is located in /var/vx/vxdba/logs/vxdbd.log. If you have trouble with the vxdbd daemon, you can turn on debug mode.
To enable the debug mode
Uncomment the following two lines in /opt/VRTSdbed/common/bin/vxdbdctrl:
#VXDBDDEBUG=108 #export VXDBDDEBUG
Restart the vxdbd daemon by running /opt/VRTSdbed/common/bin/vxdbdctrl stop and /opt/VRTSdbed/common/bin/vxdbdctrl start.
Rerun the problem commands and debugged messages will be generated in /var/vx/vxdba/logs/vxdbd.log.
Then run vxexplorer to save all the log files to send to support.