Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

66 Error messages
Understanding messages
V-5-1-92
VxVM vxconfigd WARNING V-5-1-92 Cannot exec /usr/bin/rm to remove
directory: reason
■ Description: The given directory could not be removed because the /usr/
bin/rm utility could not be executed by vxconfigd. This is not a serious
error. The only side effect of a directory not being removed is that the
directory and its contents continue to use space in the root file system.
However, this does imply that the /usr file system is not mounted, or on
some systems, that the rm utility is missing or is not in its usual location.
This may be a serious problem for the general running of your system.
■ Action: 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, restore it.
V-5-1-111
VxVM vxconfigd WARNING V-5-1-111 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, your overall
system performance is probably substantially degraded. Consider adding
more memory or paging space.
V-5-1-116
VxVM vxconfigd WARNING V-5-1-116 Cannot open log file log_filename:
reason
■ Description: The vxconfigd console output log file could not be opened for
the given reason.
■ Action: Create any needed directories, or use a different log file path name as
described in “Logging error messages” on page 53.