cancel
Showing results for 
Search instead for 
Did you mean: 

vxconfigd not starting

DanTek
Level 3

when I try to start vxconfigd, I am getting this error:

 

15:39:15 /etc/init.d : # vxconfigd
vxvm:vxconfigd: NOTICE: ddl_make_dll_info: Invalid library - libvxhpeva.so
vxvm:vxconfigd: NOTICE: ddl_search_and_place: Can't make dll info
 
vxvm:vxconfigd: NOTICE: ddl_search_and_place: Library libvxhpeva.so.3 validation fails
vxvm:vxconfigd: ERROR: Segmentation violation - core dumped
 
First we have an array that did not have a ASL library on the server installed. when I saw that I detached the array and wanted to start it clean but get the above error. This is a solaris 8 box, 3.5 vxvm, attached array is HP EVA. Old legacy stuff..~:), but we are moving away from it soon.

 

Thanks in advance

Dan

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I'm curious about the libvxhpeva.so.3 library - maybe someone else tried to install this library at some point in time?

I found this HP EVA ASL for VxVM 3.5:

http://www.symantec.com/business/support/index?page=content&id=TECH42912

The libname in this package is libvxhpeva2.so.

 

libvxhpeva seems to belong to VxVM 5.0 : https://sort.symantec.com/asl/details/422/95/YXNsL2ZpbmRlcg==

 

Please check installed ASL's for EVA:

pkginfo | grep EVA

Then do pkginfo -l on packages found.

View solution in original post

14 REPLIES 14

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I'm curious about the libvxhpeva.so.3 library - maybe someone else tried to install this library at some point in time?

I found this HP EVA ASL for VxVM 3.5:

http://www.symantec.com/business/support/index?page=content&id=TECH42912

The libname in this package is libvxhpeva2.so.

 

libvxhpeva seems to belong to VxVM 5.0 : https://sort.symantec.com/asl/details/422/95/YXNsL2ZpbmRlcg==

 

Please check installed ASL's for EVA:

pkginfo | grep EVA

Then do pkginfo -l on packages found.

Gaurav_S
Moderator
Moderator
   VIP    Certified

Yep, quite possible that so.3 is new library & is not supported with 3.5 ...

 

I would also suggest to run a pkgchk just to ensure package integrity..

 

# pkgchk VRTSvxvm

# pkgchk <ASL_pkg>  (if installled)

 

Gaurav

 

DanTek
Level 3

Thank you Marianne and Gaurav. here are the outputs:

 

 # pkginfo | grep -i EVA
system      HPEVA2               HP EVA4000, EVA6000 and EVA8000 Array Support Library
system      VRTSHP-EVA           Array Support Library for HP EVA Series Arrays (4400/6400/8400)

 

# pkginfo -l VRTSHP-EVA
   PKGINST:  VRTSHP-EVA
      NAME:  Array Support Library for HP EVA Series Arrays (4400/6400/8400)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  1.1,REV=03.25.2009.08.13
   BASEDIR:  /etc/vx
    VENDOR:  VERITAS Software
      DESC:  Array Support Library for HP EVA Series Arrays (4400/6400/8400)
    PSTAMP:  VERSION-1.1:06-February-2009
  INSTDATE:  Aug 02 2010 13:42
   HOTLINE:  800-342-0652
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:        5 installed pathnames
                   3 shared pathnames
                   3 directories
                   2 executables
                  30 blocks used (approx)
 
 
 # pkginfo -l HPEVA2    
   PKGINST:  HPEVA2
      NAME:  HP EVA4000, EVA6000 and EVA8000 Array Support Library
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  1.0,REV=07.20.2005.16.17
   BASEDIR:  /etc/vx
    VENDOR:  HP
      DESC:  HP EVA4000/EVA6000/EVA8000 Array Support Library
    PSTAMP:  VERSION-1.0:07-March-2005
  INSTDATE:  Nov 03 2008 17:39
    STATUS:  completely installed
     FILES:        4 installed pathnames
                   2 shared pathnames
                   2 directories
                   2 executables
                  31 blocks used (approx)
 
 should I go ahead and uninstall VRTSHP-EVA and see if I can start it?

 

-Dan

Gaurav_S
Moderator
Moderator
   VIP    Certified

Hi Dan,

Yes I would recommend to do that....

as you can see in the pstamp.. PSTAMP: VERSION-1.1:06-February-2009 I am sure that 3.5 had no developments in 2009 (on ASL front) , 3.5 was end of life much before that...

 

Also, if you see the install date for the pkg

INSTDATE:  Aug 02 2010 13:42

so yep, looks like someone installed in Aug 2010

 

 

Gaurav

DanTek
Level 3

Hi Gurav,

I did that and that error is gone and looks better but now I have a different issue. What I would like to do is present disks to the server from another array that is supported by the 3.5 version and re-initailize vxvm.

 

Here are my disks

 # format
Searching for disks...done
 
c2t137d10: configured with capacity of 9.98GB.......................<=== Newly presented disks
c2t138d10: configured with capacity of 9.98GB
c4t8d10: configured with capacity of 9.98GB
c4t9d10: configured with capacity of 9.98GB
 
 
AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w2100002037907f71,0
       1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w2100002037c6bdfa,0
       2. c2t137d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@1/sd@89,a
       3. c2t138d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@1/sd@8a,a
       4. c4t8d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@2/sd@8,a
       5. c4t9d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@2/sd@9,a

Specify disk (enter its number):

I touched a file /etc/vx/reconfig.d/state.d/install-db and vxinstall but it does not see the new disk, when I do vxdctl enable, I get this:

 # vxdctl enable      
vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration copies
        Rootdg disk group has no configuration copies; transactions are disabled.
vxvm:vxdctl: ERROR: enable failed: Error in disk group configuration copies

I tried to initialize rootdg:

 

# vxdg init rootdg
 
# vxdg list

NAME         STATE           ID
rootdg       enabled  1287497305.1028.cbiodb4
 
And I would like to add one of the new disks to the rootdg:

10:08:28 (root@cbiodb4) /opt/progs : # vxdg adddisk c2t137d10
vxvm:vxdg: ERROR: Failed to obtain locks:
        c2t137d10s2: no such object in the configuration
 
10:10:04 (root@cbiodb4) /opt/progs : #

All I want is to be able to add disk to veritas, create my file systems and restore the data.

 

Thank you for your help

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Did you initialize c2t137d10 ?

(vxdisksetup -i c2t137d10 )

Please post output of

vxdisk list c2t137d10s2.

 

Please reconsider adding external disk to rootdg. Better to have a separate dg. You will not be able to import rootdg should the external disk be disconnected.

ScottK
Level 5
Employee

I believe the ASL/APM framework was introduced in VxVM 4.0; there may have been (? just speculating) a precursor internal framework prior. But I don't think you can load on an ASL to VxVM 3.5. So I don't think any ASL will work. You might look for a 3.5 Solaris Hardware Compatability list to (1) if it's supported (2) if a specific patch is required.

DanTek
Level 3

That is what I could not do...initializing the disks I just presented to the server. When I try to use vxdiskadm and list the disks to be initialized, I only see the internal disks

 

List disk information
Menu: VolumeManager/Disk/ListDisk
 
  Use this menu operation to display a list of disks.  You can
  also choose to list detailed information about the disk at
  a specific disk device address.
 
Enter disk device or "all" [<address>,all,q,?] (default: all)
 
DEVICE       DISK         GROUP        STATUS
c1t0d0       -            -            error
c1t1d0       -            -            error
 
Device to list in detail [<address>,none,q,?] (default: none)

 

10:10:04 (root@cbiodb4) /opt/progs : # vxdisk list c2t137d10
vxvm:vxdisk: ERROR: Disk c2t137d10s2: Disk not in the configuration

 

Both internal disks are under svm control, so I could not use internal disks for the roodg.
 
12:12:50 (root@cbiodb4) /opt/progs : # vxdisksetup -i c2t137d10
bash: vxdisksetup: command not found
 
12:14:04 (root@cbiodb4) /opt/progs : # vxdisk list c2t137d10s2
vxvm:vxdisk: ERROR: Disk c2t137d10s2: Disk not in the configuration
 
12:17:39 (root@cbiodb4) /opt/progs : #

 

Thanks Marianne!

DanTek
Level 3

The server worked fine with an odler version of the HP array (HSV210). My understanding was the ASL for the HSV450 is the one that supports only 5.0 and above.

 

 # vxddladm listsupport all | grep -i eva
libvxhpeva2.so                   A/A          HP           HSV200                    
libvxhpeva2.so                   A/A          HP           HSV210                    
 
 #

So when we discovered that we wont be able to get it working with the 8400 EVA, we decided to revert. But now, it does not even see the older EVA disks that the OS sees. I just want to get the disks the OS sees under the vxvm control and be able to create file systems.

Thanks Scott.

Gaurav_S
Moderator
Moderator
   VIP    Certified

Can you list a full output of "vxdisk -e list"

First need to see whether vxvm can see the devices are not..

 

# vxdisk -e list

# vxdisk -o alldgs -e list

 

Also, did you labelled the disks in solaris ?

 

Gaurav

 

DanTek
Level 3

yes, I did label them on solaris

 

# vxdisk -e list
DEVICE       TYPE      DISK         GROUP        STATUS       c#t#d#_NAME   
c1t0d0s2     sliced    -            -            error        c1t0d0s2    
c1t1d0s2     sliced    -            -            error        c1t1d0s2    
 
# vxdisk -o alldgs -e list
DEVICE       TYPE      DISK         GROUP        STATUS       c#t#d#_NAME   
c1t0d0s2     sliced    -            -            error        c1t0d0s2    
c1t1d0s2     sliced    -            -            error        c1t1d0s2 

 

Using vxdiskadm, all it sees is the internal disks


  More than one disk or pattern may be entered at the prompt.  Here are
  some disk selection examples:
 
  all:          all disks
  c3 c4t2:      all disks on both controller 3 and controller 4, target 2
  c3t4d2:       a single disk (in the c#t#d# naming scheme)
  xyz_0 :       a single disk (in the enclosure based naming scheme)
  xyz_ :        all disks on the enclosure whose name is xyz
 
Select disk devices to add: [<pattern-list>,all,list,q,?] list
 
DEVICE       DISK         GROUP        STATUS
c1t0d0       -            -            error
c1t1d0       -            -            error

 
Select disk devices to add: [<pattern-list>,all,list,q,?]

 

and the format command shows:

14:40:00 (root@cbiodb4) /opt/progs : # format
Searching for disks...done
 
 
AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w2100002037907f71,0
       1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w2100002037c6bdfa,0
       2. c2t137d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@1/sd@89,a
       3. c2t138d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@1/sd@8a,a
       4. c4t8d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@2/sd@8,a
       5. c4t9d10 <HP-HSV210-6220 cyl 1278 alt 2 hd 128 sec 128>
          /pci@8,600000/fibre-channel@2/sd@9,a

Specify disk (enter its number):

 

Thank you Gaurav.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

PLEASE consider upgrading to a later version of VxVM - with 3.5 no longer supported, it is very difficult to find any info. TechNotes, HCL's and online documents go back to 4.x. 

 

I have a procedure that entails removing the DMP device paths, disk.info and restarting vxconfigd, BUT I cannot find any information that it will work with 3.5.... So, I'd rather not post any commands...

 

You also did not mention your VxVM patch level?

Even the HPEVA2 ASL is only supported as from 3.5 MP3. Extract from TN mentioned in my 1st post:

Package Name: HPEVA2 (HP EVA4000, EVA6000, and EVA8000 Array Support Library)
Package Version: 1.0,REV=07.20.2005.16.17
Supported Arrays: HP Storage Works EVA 4000/6000/8000 arrays

Supported versions of VERITAS Volume Manager: 3.5 MP3 and 4.x

Gaurav_S
Moderator
Moderator
   VIP    Certified

I agree with Marianne, upgrade would be the best & recommended solution.

the disk devices are not at all visible & 3.5 didn't had disk.info to clear & recreate (usual method to rescan devices)...

There would be couple of things to try (If you wish) but I am not sure of results... ..

-- If the ASL is causing the issues, we can try adding the array lib as JBOD..

# vxddladm addjbod VID= PID=

you can find VID & PID from following command

# vxddladm listsupport libname=libhpeva.so  (give the correct library name here)

 

run a vxdctl enable to see if any differences..

 

Gaurav

DanTek
Level 3

Yes, you are right. The corect path to take is to upgrade since the version is EOL ages ago..~:) We are in the process of doing that but we have few boxes with 3.5. Since I had to recover the data, I finally resolved the issue by clearing all external devices on the box, replicate the data over to another older EVA array using  HP replication tool and added these devices to the box. I was able to start the volumes  and mount the file systems.

 

Thank you both for your help!

 

Dan