VERITAS Volume Manager 3.1 Reference Guide

70 Chapter2
Error Messages
Volume Manager Configuration Daemon Error Messages
If the /usr file system is not mounted, you need to determine how to
get it mounted. If the rm utility is missing or is not in the /usr/bin
directory, you should restore it from somewhere.
Cannot fork to remove directory
vxvm:vxconfigd: WARNING:
Cannot fork to remove directory directory : reason
• Description
The given directory could not be removed because vxconfigd could
not fork in order to run the rm utility. This is not a serious error. The
only side effect of a directory not being removed is that the directory
and its contents will continue to use space in the root file system. The
most likely cause for this error is that your system does not have
enough memory or paging space to allow vxconfigd to fork.
• Action
If your system is this low on memory or paging space, then your
overall system performance is probably being substantially effected.
Consider adding more memory or paging space.
Cannot issue internal transaction
vxvm:vxconfigd: WARNING:
Cannot issue internal transaction: reason
• Description
This problem usually occurs only if there is a Volume Manager bug.
However, it may occur in cases where memory is low.
• Action
Contact Customer Support for more information.
Cannot open log file
vxvm:vxconfigd: WARNING: Cannot open log file
log_filename : reason
• Description
The vxconfigd console output log file could not be opened for the
given reason. A log file is opened if -x log is specified, or if a log file is
specified with -x logfile= file . The default log file is
/var/vxvm/vxconfigd.log. The most likely cause for failure is “No