topic Re: Errors cmcheckconf : Nonexistent file: HDBXPR. in Operating System - HP-UX

Errors cmcheckconf : Nonexistent file: HDBXPR.

Network Servers — Mon, 02 May 2005 21:06:07 GMT

# cmcheckconf -p HDBXPR

Begin package verification...
"-p" option specified. Opening package reference file: HDBXPR.
cmcheckconf : Nonexistent file: HDBXPR.

The HDBXPR package exists. Also the HDXPR.conf file exists.

Can anyone tell me why I am getting this error.

Thanks!

Re: Errors cmcheckconf : Nonexistent file: HDBXPR.

Denver Osborn — Mon, 02 May 2005 21:18:06 GMT

What do you get if you try this syntax...

cmcheckconf -v -P /etc/cmcluster/pkgdir/pkgname.config

-denver

Re: Errors cmcheckconf : Nonexistent file: HDBXPR.

Network Servers — Mon, 02 May 2005 21:42:47 GMT

Ok that worked!!

Thanks.

Now I am getting errors trying to mount file systems in the package.

fsck: /etc/default/fs is used for determining the file system type
vxfs fsck: cannot stat /dev/vgHDB/rlvHDBoravl10
ERROR: Function check_and_mount
ERROR: Failed to fsck one of the logical volumes.

Re: Errors cmcheckconf : Nonexistent file: HDBXPR.

Denver Osborn — Mon, 02 May 2005 21:56:10 GMT

With the package down, can you manually activate the VG and attempt to mount the filesystem? If mounting fails and complains that a full fsck needs to be run, then run the fsck against your filesystem to set it's state to clean... then deactivate the VG and try to run the pkg again.

# vgchange -a e /dev/vgname
# fsck -F vxfs -o full /dev/vgname/rlvol
# vgchange -a n /dev/vgname

man fsck_vxfs

hope this helps,
-denver

Re: Errors cmcheckconf : Nonexistent file: HDBXPR.

Denver Osborn — Mon, 02 May 2005 21:59:01 GMT

wait a sec, something else must be going on here... Was the VG or LVols changed or anything? Are there more details you could provide about what's really been going on w/ this node/cluster? It would really help us with troubleshooting to know how we got to this point.

-denver

Re: Errors cmcheckconf : Nonexistent file: HDBXPR.

Stephen Doud — Wed, 04 May 2005 08:06:16 GMT

"cannot stat" usually means the resource or file is not active or does not exist.
With the package down, attempt to activate the VG:

# vgchange -a e /dev/vgHDB

And then fsck the file system:
# fsck /dev/vgHDB/rlvHDBoravl10

Isolate the cause to the actual issue. Remember that the package control script only automates a series of HP-UX commands. In most cases, you can do all the steps manually to try to identify the source of the failure.
If all of the commands work manually, inspect the package control script to see if any of the lines that you added have syntax errors. For instance, if the package controls multiple volume groups, or fsck's and mounts multiple file systems, insure that the array index number increments consecutively for each entry.
Example:

VG[0]="vg12"
VG[1]="vg13"
....
LV[0]="/dev/vg01/lvol1"; FS[0]="/PKG1.1"; FS_MOUNT_OPT[0]="-o rw"; FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]=""; FS_TYPE[0]=""
LV[1]="/dev/vg01/lvol2"; FS[1]="/PKG1.2"; FS_MOUNT_OPT[1]="-o rw"; FS_UMOUNT_OPT[1]=""; FS_FSCK_OPT[1]=""; FS_TYPE[1]=""