Vparstatus fails (Code 8,4)

[Richard Pereira_1]

2 partitions that sit within a NPAR, both run hpux 11.i.

We just noticed the other day that vparstatus does the following;

vparstatus: Internal error: Cannot open virtual partition monitor database. (Code 8,4)

/:>ll /stand/vpmon
-r-xr-xr-x 1 bin bin 1168728 Apr 8 2004 /stand/vpmon
-rw------- 1 root root 8232 Jun 30 09:30 vpdb

uptime
9:33am up 38 days, 21:43, 1 user, load average: 0.30, 0.24, 0.22

we havent modified the vpars since last year, last kernel change was mid march, 2 succesfull reboots since. Here is what we have vpar related

PHCO_25130 1.0 vPar manpage cumulative patch
PHCO_28175 1.0 vPar commands man pages patch
PHKL_24548 1.0 vPar enablement patch
PHKL_24552 1.0 vPar enablement patch
PHKL_24554 1.0 vPar enablement patch
PHKL_24556 1.0 vPar enablement patch
PHKL_24565 1.0 vPar Enablement patch
PHKL_24585 1.0 Psets & vPar enablement patch
PHKL_25080 1.0 vPar enablement patch
PHKL_26979 1.0 vPar enablement patch with kwdb support
PHKL_27096 1.0 VxVM,EMC,Psets&vPar,slpq1,earlyKRS
PHKL_27750 1.0 vPar enablement, KRNG enablement
PHKL_28139 1.0 vPar enablement patch, select, nanosleep
PHKL_28237 1.0 vPar enablement, CDUMP enablement patch
PHKL_28323 1.0 vPar enablement patch, ktracer, kgmon -B
PHKL_29243 1.0 vPar enablement, cumulative patch
PHKL_29300 1.0 IPMI driver port, LUN change,vPar interface
PHKL_29628 1.0 vPars panic; Syscall cumulative;FSS
PHKL_29890 1.0 vPar enablement,DLKM load panic
PHKL_30067 1.0 I/O,vPar,CDUMP,IM perf,PCI-X perf
PHKL_30197 1.0 Psets, vPar, SLVM, Reboot Hangs, Serial Num
PHKL_30447 1.0 iCOD,vPars,IPMI,PDCnbcall,OLA/R AB
PHKL_30523 1.0 PDC_SCSI_PARMS,iCOD,vPars,IPMI,OLA/R
PHKL_30524 1.0 par fans,cabtype,sinc,hwpath,cell info,vPar
PHKL_30837 1.0 vPar, callout, abstime, shared sync perf
PHKL_31162 1.0 crash,vpars,timeout;SG TOC,nParCnfg,shutdown
PHKL_31993 1.0 Core PM, vPar, Psets, slpq1, FSS, rtprio
vParManager B.11.11.01.02 Virtual Partition Manager for HP-UX


i tried google and the forums, no luck, any suggestions?

[melvyn burnard]

What version of Vpars is this?
have you looked at the other vpar to compare the vpdb in /stand?
Does vparstatus work from the other vpar?

[David Child_1]

Do you get the same error from both vPars? Try running vparstatus from each vPar and see if both show the same problem.

David

[Kent Ostby]

Check your version of vpars. A similar error was seen on a very early version of Vpars (A.02.01), but was not seen after that.

Also, check your permissions on /stand/vpdb and the major number on /dev/vpmon.

[Richard Pereira_1]

the version is above in the listing.
the perms on vpmon and vpdb is also above and the same on both vpars.

Yes, both vpars are giving me this error. Other vpars inside other npars are working fine.

#ll /dev/vpmon
crw-r--r-- 1 root sys 77 0x000000 May 22 11:50 /dev/vpmon
same on both machines

however i notice the minor number changes on other vpars. 96,98 etc

Any other files i should check?

[melvyn burnard]

Actually all that is listed here is the vParManager product which is NOT the vPars product.

do
swlist -l product | grep Virtual

You could also check the /etc/rc.log file to see if the vparinit started correctly
Having said that, I suspect you are running an older version fo vPars that may be unsupported.

[Richard Pereira_1]

it was a HP tech that brought this to our attention. here is the product info


VirtualPartition A.03.01.05 HP-UX Virtual Partitions Functionality
vParManager B.11.11.01.02 Virtual Partition Manager for HP-UX

[Richard Pereira_1]

local tech is out of ideas, i logged a call at the response center but was wondering if any here had any new ideas.

[Tyronne Milton]

Did you ever manage to get this resolved?
I am having the same exact issue now.