VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages

vxconﬁgd Warning Messages

Chapter 3

vxconﬁgd Warning Messages

A warning message from the conﬁguration daemon, vxconﬁgd, indicates a problem that

may affect the operation of VxVM. Action should be taken to correct the problem as soon

as possible.

vxvm:vxconfigd: WARNING: Bad request number: client number, portal

[REQUEST|DIAG], size number

• Description: This diagnostic message indicates that a utility sent an invalid request

to vxconﬁgd.

• Action: If you are developing a new utility, this error indicates a bug in your code.

Otherwise, it indicates a bug in VxVM. Contact Customer Support.

vxvm:vxconfigd: WARNING: Cannot change disk group record in kernel:

reason

• Description: This internal error should not occur unless there is a bug in VxVM.

• Action: Contact Customer Support.

vxvm:vxconfigd: WARNING: Cannot create device device_path: reason

• Description: vxconﬁgd cannot create a device node either under /dev/vx/dsk or under

/dev/vx/rdsk. This should happen only if the root ﬁle system has run out of inodes.

• Action: Remove some unwanted ﬁles from the root ﬁle system. Then, regenerate the

device node using the command:

# vxdctl enable

vxvm:vxconfigd: WARNING: 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 vxconﬁgd. 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 ﬁle system. However, this does imply that the /usr ﬁle 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 ﬁle 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.

vxvm:vxconfigd: WARNING: Cannot fork to remove directory directory:

reason

• Description: The given directory could not be removed because vxconﬁgd 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 ﬁle system. The most likely cause for this error is that your system

does not have enough memory or paging space to allow vxconﬁgd 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.

vxvm:vxconfigd: WARNING: Cannot issue internal transaction: reason