<?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: swinstall Proceed at your own risk! in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571136#M873178</link>
    <description>Hi Bill,&lt;BR /&gt;&lt;BR /&gt;I don't have a real clue I would only try to guess ....&lt;BR /&gt;&lt;BR /&gt;Are 100% sure that the depot is not corrupted somehow. Have you tried a checksum on the L2k and A500? Do they match? &lt;BR /&gt;&lt;BR /&gt;If the depot is not corrupted (I hope it is) then the script that comes with the patch might be buggy. You could try to set to false all enforce_script enforce_dependecies options. &lt;BR /&gt;&lt;BR /&gt;Do you have any new core dump on the system? You could then find out which exec failed.If that exec does just a verification you could replace it with an "exit 0" script. I would do that only on a sandbox unless you want to "Proceed at your own risk!"&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ovidiu</description>
    <pubDate>Tue, 28 Aug 2001 12:38:11 GMT</pubDate>
    <dc:creator>Ovidiu D. Raita</dc:creator>
    <dc:date>2001-08-28T12:38:11Z</dc:date>
    <item>
      <title>swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571135#M873177</link>
      <description />
      <pubDate>Tue, 28 Aug 2001 11:43:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571135#M873177</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-28T11:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571136#M873178</link>
      <description>Hi Bill,&lt;BR /&gt;&lt;BR /&gt;I don't have a real clue I would only try to guess ....&lt;BR /&gt;&lt;BR /&gt;Are 100% sure that the depot is not corrupted somehow. Have you tried a checksum on the L2k and A500? Do they match? &lt;BR /&gt;&lt;BR /&gt;If the depot is not corrupted (I hope it is) then the script that comes with the patch might be buggy. You could try to set to false all enforce_script enforce_dependecies options. &lt;BR /&gt;&lt;BR /&gt;Do you have any new core dump on the system? You could then find out which exec failed.If that exec does just a verification you could replace it with an "exit 0" script. I would do that only on a sandbox unless you want to "Proceed at your own risk!"&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ovidiu</description>
      <pubDate>Tue, 28 Aug 2001 12:38:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571136#M873178</guid>
      <dc:creator>Ovidiu D. Raita</dc:creator>
      <dc:date>2001-08-28T12:38:11Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571137#M873179</link>
      <description />
      <pubDate>Tue, 28 Aug 2001 13:04:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571137#M873179</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-28T13:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571138#M873180</link>
      <description>Bill, have you checked the state of PHKL_18543 and all of its filesets?</description>
      <pubDate>Tue, 28 Aug 2001 13:47:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571138#M873180</guid>
      <dc:creator>Alan Riggs</dc:creator>
      <dc:date>2001-08-28T13:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571139#M873181</link>
      <description>I'm not sure it's that..&lt;BR /&gt;&lt;BR /&gt;The system is just randomly panicing at least twice a day.. I must have a hw failure somewhere.&lt;BR /&gt;Attached is a pdcinfo output.&lt;BR /&gt;&lt;BR /&gt;# swverify PHKL_18543&lt;BR /&gt;&lt;BR /&gt;=======  08/28/01 18:01:20 METDST  BEGIN swverify SESSION&lt;BR /&gt;         (non-interactive)&lt;BR /&gt;&lt;BR /&gt;       * Session started for user "root@kibo".&lt;BR /&gt;&lt;BR /&gt;       * Beginning Selection&lt;BR /&gt;       * Target connection succeeded for "kibo:/".&lt;BR /&gt;       * Software selections:&lt;BR /&gt;             PHKL_18543.C-INC,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_32/64&lt;BR /&gt;             PHKL_18543.CORE-KRN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_32/64&lt;BR /&gt;             PHKL_18543.CORE2-KRN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_64&lt;BR /&gt;             PHKL_18543.KERN2-RUN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_64&lt;BR /&gt;             PHKL_18543.VXFS-BASE-KRN,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_64&lt;BR /&gt;             PHKL_18543.VXFS-PRG,l=/,r=1.0,a=HP-UX_B.11.00_32/64,v=HP,fa=HP-UX_B.11.00_32/64&lt;BR /&gt;       * Selection succeeded.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;       * Beginning Analysis&lt;BR /&gt;       * Session selections have been saved in the file&lt;BR /&gt;         "/.sw/sessions/swverify.last".&lt;BR /&gt;       * The analysis phase succeeded for "kibo:/".&lt;BR /&gt;       * Verification succeeded.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;NOTE:    More information may be found in the agent logfile (location&lt;BR /&gt;         is kibo:/var/adm/sw/swagent.log).&lt;BR /&gt;&lt;BR /&gt;=======  08/28/01 18:01:25 METDST  END swverify SESSION&lt;BR /&gt;         (non-interactive)&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Aug 2001 14:06:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571139#M873181</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-28T14:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571140#M873182</link>
      <description>I kinda doubt it's fully h/w problem (I've got uncommon lab prototype h/w installed!) because as mentioned installing the patch on the L2k fixed the exact same pim output.  I'm sure this patch will fix the A, but just can't install it.&lt;BR /&gt;&lt;BR /&gt;points will come!..&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 28 Aug 2001 14:08:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571140#M873182</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-28T14:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571141#M873183</link>
      <description>Hi Bill&lt;BR /&gt;&lt;BR /&gt;Have you tried making a change to kernel and doing a rebuild, and see if the panic goes away?&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Tue, 28 Aug 2001 14:24:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571141#M873183</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2001-08-28T14:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571142#M873184</link>
      <description />
      <pubDate>Tue, 28 Aug 2001 14:37:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571142#M873184</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-28T14:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: swinstall Proceed at your own risk!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571143#M873185</link>
      <description>I'm going to allow the system to stay running after modifying the kernel, rebooting installing, by Proceeding at my own risk and rebooting.. if it panics again, I'll just reinstall everything...&lt;BR /&gt;&lt;BR /&gt;I'll let you know..&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Tue, 28 Aug 2001 15:12:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/swinstall-proceed-at-your-own-risk/m-p/2571143#M873185</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-28T15:12:50Z</dc:date>
    </item>
  </channel>
</rss>

