VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible

[SM_3]

I have a RHEL4(AS) server. Just installed VxVM 4.1. Whenever I reboot the server the "vxconfigd" daemon does not start. However, when I issue the command "vxdisk list" I get "VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible". However, I can start the daemon manually via vxconfigd command. I have checked as much as I can. All the necessary modules are loaded etc. Can someone pls help.

[root@proliant1 sbin]# lsmod |grep vx
vxportal 8064 0
vxfs 1529904 2 fdd,vxportal
vxspec 15500 2
vxio 1735704 1
vxdmp 198308 4
scsi_mod 116557 3 vxdmp,cciss,sd_mod

cd /lib/modules/`uname -r`

[root@proliant1 2.6.9-5.ELsmp]# grep vx modules.dep
/lib/modules/2.6.9-5.ELsmp/kernel/fs/freevxfs/freevxfs.ko:
/lib/modules/2.6.9-5.ELsmp/kernel/sound/drivers/vx/snd-vx-lib.ko: /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-pcm.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-timer.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-page-alloc.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-hwdep.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/soundcore.ko
/lib/modules/2.6.9-5.ELsmp/kernel/sound/pci/vx222/snd-vx222.ko: /lib/modules/2.6.9-5.ELsmp/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-pcm.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-timer.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-page-alloc.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd-hwdep.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/core/snd.ko /lib/modules/2.6.9-5.ELsmp/kernel/sound/soundcore.ko
/lib/modules/2.6.9-5.ELsmp/veritas/vxfs/vxportal.ko: /lib/modules/2.6.9-5.ELsmp/veritas/vxfs/vxfs.ko
/lib/modules/2.6.9-5.ELsmp/veritas/vxfs/vxfs.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxfs/fdd.ko: /lib/modules/2.6.9-5.ELsmp/veritas/vxfs/vxfs.ko
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpapf.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpaaa.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/vxio.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/vxspec.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpjbod.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/vxdmp.ko: /lib/modules/2.6.9-5.ELsmp/kernel/drivers/scsi/scsi_mod.ko
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpap.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpapg.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpsvc.ko:
/lib/modules/2.6.9-5.ELsmp/veritas/vxvm/dmpaa.ko:

[root@proliant1 2.6.9-5.ELsmp]# chkconfig --list |grep boot.vxvm
boot.vxvm_rhel5 0:off 1:on 2:on 3:on 4:on 5:on 6:off

[Steven E. Protter]

Shalom,

I recommend restoring the system from a backup.

This product is clearly not meant for a base unupdated RHEL 4 installation.

SEP

[smatador]

Hi,
You have probably read this doc and made some troubleshoot yet
http://seer.entsupport.symantec.com/docs/301909.htm
but it's for rhel5 not for rhel4, so I think your could waste time to troubleshoot an issue with rhel4 with solution on rhel5.
If you could update/reinstall your redhat to rhel5 and restart the vxvm install.

[SM_3]

Many Thanks to those people who replied. I have now solved the problem. Silly me, I did not remove the file /etc/vx/reconfig.d/state.d/install-db. Instead I spent too much focusing on loading the modules.