<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Vparstatus fails (Code 8,4) in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574159#M228693</link>
    <description>the version is above in the listing. &lt;BR /&gt;the perms on vpmon and vpdb is also above and the same on both vpars.&lt;BR /&gt;&lt;BR /&gt;Yes, both vpars are giving me this error. Other vpars inside other npars are working fine.&lt;BR /&gt;&lt;BR /&gt;#ll /dev/vpmon&lt;BR /&gt;crw-r--r--   1 root       sys         77 0x000000 May 22 11:50 /dev/vpmon&lt;BR /&gt;same on both machines&lt;BR /&gt;&lt;BR /&gt;however i notice the minor number changes on other vpars. 96,98 etc&lt;BR /&gt;&lt;BR /&gt;Any other files i should check?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 30 Jun 2005 09:37:02 GMT</pubDate>
    <dc:creator>Richard Pereira_1</dc:creator>
    <dc:date>2005-06-30T09:37:02Z</dc:date>
    <item>
      <title>Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574155#M228689</link>
      <description>2 partitions that sit within a NPAR, both run hpux 11.i.&lt;BR /&gt;&lt;BR /&gt;We just noticed the other day that vparstatus does the following;&lt;BR /&gt;&lt;BR /&gt;vparstatus: Internal error: Cannot open virtual partition monitor database. (Code 8,4)&lt;BR /&gt;&lt;BR /&gt;/:&amp;gt;ll /stand/vpmon&lt;BR /&gt;-r-xr-xr-x   1 bin        bin        1168728 Apr  8  2004 /stand/vpmon&lt;BR /&gt;-rw-------   1 root       root          8232 Jun 30 09:30 vpdb&lt;BR /&gt;&lt;BR /&gt;uptime&lt;BR /&gt;  9:33am  up 38 days, 21:43,  1 user,  load average: 0.30, 0.24, 0.22&lt;BR /&gt;&lt;BR /&gt;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&lt;BR /&gt;&lt;BR /&gt;  PHCO_25130            1.0            vPar manpage cumulative patch&lt;BR /&gt;  PHCO_28175            1.0            vPar commands man pages patch&lt;BR /&gt;  PHKL_24548            1.0            vPar enablement patch&lt;BR /&gt;  PHKL_24552            1.0            vPar enablement patch&lt;BR /&gt;  PHKL_24554            1.0            vPar enablement patch&lt;BR /&gt;  PHKL_24556            1.0            vPar enablement patch&lt;BR /&gt;  PHKL_24565            1.0            vPar Enablement patch&lt;BR /&gt;  PHKL_24585            1.0            Psets &amp;amp; vPar enablement patch&lt;BR /&gt;  PHKL_25080            1.0            vPar enablement patch&lt;BR /&gt;  PHKL_26979            1.0            vPar enablement patch with kwdb support&lt;BR /&gt;  PHKL_27096            1.0            VxVM,EMC,Psets&amp;amp;vPar,slpq1,earlyKRS&lt;BR /&gt;  PHKL_27750            1.0            vPar enablement, KRNG enablement&lt;BR /&gt;  PHKL_28139            1.0            vPar enablement patch, select, nanosleep&lt;BR /&gt;  PHKL_28237            1.0            vPar enablement, CDUMP enablement patch&lt;BR /&gt;  PHKL_28323            1.0            vPar enablement patch, ktracer, kgmon -B&lt;BR /&gt;  PHKL_29243            1.0            vPar enablement, cumulative patch&lt;BR /&gt;  PHKL_29300            1.0            IPMI driver port, LUN change,vPar interface&lt;BR /&gt;  PHKL_29628            1.0            vPars panic; Syscall cumulative;FSS&lt;BR /&gt;  PHKL_29890            1.0            vPar enablement,DLKM load panic&lt;BR /&gt;  PHKL_30067            1.0            I/O,vPar,CDUMP,IM perf,PCI-X perf&lt;BR /&gt;  PHKL_30197            1.0            Psets, vPar, SLVM, Reboot Hangs, Serial Num&lt;BR /&gt;  PHKL_30447            1.0            iCOD,vPars,IPMI,PDCnbcall,OLA/R AB&lt;BR /&gt;  PHKL_30523            1.0            PDC_SCSI_PARMS,iCOD,vPars,IPMI,OLA/R&lt;BR /&gt;  PHKL_30524            1.0            par fans,cabtype,sinc,hwpath,cell info,vPar&lt;BR /&gt;  PHKL_30837            1.0            vPar, callout, abstime, shared sync perf&lt;BR /&gt;  PHKL_31162            1.0            crash,vpars,timeout;SG TOC,nParCnfg,shutdown&lt;BR /&gt;  PHKL_31993            1.0            Core PM, vPar, Psets, slpq1, FSS, rtprio&lt;BR /&gt;  vParManager           B.11.11.01.02  Virtual Partition Manager for HP-UX&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;i tried google and the forums, no luck, any suggestions?&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Jun 2005 08:35:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574155#M228689</guid>
      <dc:creator>Richard Pereira_1</dc:creator>
      <dc:date>2005-06-30T08:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574156#M228690</link>
      <description>What version of Vpars is this?&lt;BR /&gt;have you looked at the other vpar to compare the vpdb in /stand?      &lt;BR /&gt;Does vparstatus work from the other vpar?&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Jun 2005 08:46:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574156#M228690</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2005-06-30T08:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574157#M228691</link>
      <description>Do you get the same error from both vPars? Try running vparstatus from each vPar and see if both show the same problem.&lt;BR /&gt;&lt;BR /&gt;David</description>
      <pubDate>Thu, 30 Jun 2005 08:49:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574157#M228691</guid>
      <dc:creator>David Child_1</dc:creator>
      <dc:date>2005-06-30T08:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574158#M228692</link>
      <description>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.&lt;BR /&gt;&lt;BR /&gt;Also, check your permissions on /stand/vpdb and the major number on /dev/vpmon.&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Jun 2005 09:02:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574158#M228692</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2005-06-30T09:02:11Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574159#M228693</link>
      <description>the version is above in the listing. &lt;BR /&gt;the perms on vpmon and vpdb is also above and the same on both vpars.&lt;BR /&gt;&lt;BR /&gt;Yes, both vpars are giving me this error. Other vpars inside other npars are working fine.&lt;BR /&gt;&lt;BR /&gt;#ll /dev/vpmon&lt;BR /&gt;crw-r--r--   1 root       sys         77 0x000000 May 22 11:50 /dev/vpmon&lt;BR /&gt;same on both machines&lt;BR /&gt;&lt;BR /&gt;however i notice the minor number changes on other vpars. 96,98 etc&lt;BR /&gt;&lt;BR /&gt;Any other files i should check?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Jun 2005 09:37:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574159#M228693</guid>
      <dc:creator>Richard Pereira_1</dc:creator>
      <dc:date>2005-06-30T09:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574160#M228694</link>
      <description>Actually all that is listed here is the vParManager product which is NOT the vPars product.&lt;BR /&gt;&lt;BR /&gt;do&lt;BR /&gt;swlist -l product | grep Virtual&lt;BR /&gt;&lt;BR /&gt;You could also check the /etc/rc.log file to see if the vparinit started correctly&lt;BR /&gt;Having said that, I suspect you are running an older version fo vPars that may be unsupported.</description>
      <pubDate>Thu, 30 Jun 2005 09:56:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574160#M228694</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2005-06-30T09:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574161#M228695</link>
      <description>it was a HP tech that brought this to our attention. here is the product info&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;  VirtualPartition      A.03.01.05     HP-UX Virtual Partitions Functionality&lt;BR /&gt;  vParManager           B.11.11.01.02  Virtual Partition Manager for HP-UX&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Jun 2005 12:17:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574161#M228695</guid>
      <dc:creator>Richard Pereira_1</dc:creator>
      <dc:date>2005-06-30T12:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574162#M228696</link>
      <description>local tech is out of ideas, i logged a call at the response center but was wondering if any here had any new ideas.</description>
      <pubDate>Tue, 05 Jul 2005 09:16:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574162#M228696</guid>
      <dc:creator>Richard Pereira_1</dc:creator>
      <dc:date>2005-07-05T09:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: Vparstatus fails (Code 8,4)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574163#M228697</link>
      <description>Did you ever manage to get this resolved?&lt;BR /&gt;I am having the same exact issue now.</description>
      <pubDate>Thu, 22 Feb 2007 09:52:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vparstatus-fails-code-8-4/m-p/3574163#M228697</guid>
      <dc:creator>Tyronne Milton</dc:creator>
      <dc:date>2007-02-22T09:52:26Z</dc:date>
    </item>
  </channel>
</rss>

