burned out on dizzy patches.

[Steve Post]

When I run netstat -a, I see a port is stuck in a "FIN_WAIT_2" state.
From looking the hp documents, I see I need patch PHNE_1935
and that needs PHNE_22566
and that needs PHNE_17662
and PHNE_17662 was replaced with PHNE_21767
and that PHNE_21767 was replaced with PHNE_24715
and PHNE_24715 needs patches
a. PHKL_21847, b. PHKL_22142, and c. PHNE_22566
OK. I'll go down the PHKL_21847 branch for a moment......
PHKL_21847 was replaced with PHKL_18543
PHKL_18543 needs..........7 more patches.
WHOAH.
I don't see an end in sight here.

My question is: How far do I have to dig????

[Patrick Wallek · Accepted solution]

Unfortunately tracking down ALL the patch dependencies for a sinlge patch can be a royal pain in the a**.

Other than getting the response center to generate a patch bundle for you, I know of no easy way, via the ITRC or otherwise, to generate a list of all patch dependencies for a single patch.

[harry d brown jr]

If you have access to the Custom Patch manager you can "bundle" all of the necessary patches together. Go to it and check it out.

live free or die
harry

[Sanjay_6]

Hi Steve,

http://us-support.external.hp.com/cki/bin/doc.pl/sid=013fa9dd07c7d63381/screen=ckiDisplayDocument?docId=200000048088545

http://us-support.external.hp.com/cki/bin/doc.pl/sid=013fa9dd07c7d63381/screen=ckiDisplayDocument?docId=200000048972606

Patch PHNE_19375 has been superceded by patch PHNE_24715. This patch dependencies are
s700: 11.00: PHKL_21857 PHKL_22142 PHNE_22566
s800: 11.00: PHKL_21857 PHKL_22142 PHNE_22566

Hope this helps.

thanks

[James R. Ferguson]

Hi Steve:

Nope, this is not always fun nor always easy ;-)

Having said that, my advice is to take one of two paths

First, use a current Support Plus Quality Pack (QPK) at September 2001 or perhaps the June 2001 General Release (GR) bundle and apply it. You can check to see if the patch you want is in it by going to Maintenance and Support -> Patching -> Standard Patch Bundles -> View Support Plus Releases.

Second, if the patch you want isn't contained in one of these, download the patch (or its successor), *and* all the dependencies that it references. Do not worry if you are downloading patches you already have. Rather, collection all your patches into one depot with 'swcopy' and let 'swinstall' sort out what needs installation.

Regards!

...JRF...

[Craig Rants]

Steve,
I would create a custom bundle through the ITRC patch manager, it takes a while to work through all the little dependencies and conflicts but it will save you a lot of time.

Also, why are you looking for a patch for a port showing FIN_WAIT_2. It could be a client hasn't sent any communitcation back to your server... Did HP tell you to get a patch? Just curious.

Craig

[Darrell Allen]

Ditto on the CPM. It has an analyze function to check for dependencies and conflicts with both your installed patches (provided you upload the lastest info from your system) and the patches you have chosen. It has saved me a bunch of time.

Even if you only want 1 patch you can go thru the motions of collecting your system's info and uploading it, select at least one patch (even if you really don't want it - you've got to have a starting place), add the patch you want, remove the one(s) you didn't really want, and do the analysis.

Darrell

[linuxfan]

Hi Steve,


Welcome to WWP(Worse world of patches). If you want to avoid doing it manually, the option is to call up HP and get the dependencies.

I don't believe custom patch manager allows you to specify one single patch and list out all the dependencies for that patch and dependencies of those dependencies. Although you can create custom depots for your systems.


-Regards
Ramesh

[Patrick Wallek]

Which patch do you need exactly? PHNE_1935 is for HP-UX 9.X on a Series 3XX/4XX machine.

Anyway, to get a list of all patches required for a given patch do the following:

Go to http://itrc.hp.com

Then click on 'individual patches'

Then go to 'hp-ux'

Now select your appropriate machine and OS level in step 1.

Then in step 2 select 'Search by Patch IDs' from the drop down box and then put in the patch number in the box below that and then click on 'search'

This will take you to a page that lists your original patch that you searched on and also ALL patches requird by that patch.

It appears to me that you can download all the patches from that screen, but you can't bundle them into an individual depot. You'll have to do that yourself.

There are numerous threads on doing that in these Forums. Click on search on the left and search for something like 'patch bundle' and you should get some good results.

[Steve Post]

Man! It's going to take an hour to research the replies! I really won't dig through the patches one click at a time. (but writing a perl script to do it is a thought).

I'll load Sep2001 QPK.
I'll try the custom patch manager provided it doesn't cost anything and I have a day to run with it.

The reason why I need the "one" patch is there is a clunky Windows application that hangs a port on the HPbox. Of course since it's windows, I don't expect the software to be fixed....ever.

I don't need PHNE_1935. That was my fingers typing too fast. Sanjay pointed out the 2 documents I saw. In there is PHNE_193*7*5.Of course the patch dependencies are meaningless because those dependencies will lead to more, and more, and more, and more, ....hence my question.

I wouldn't want to load an infinite number of patches on the system, because /var and /opt would overload. And I can't extend them unless I power down the computer.

thanks for the help. Points are a-comin'
Steve

[James R. Ferguson]

Hi (again) Steve:

With regard to space problems in /var -- you can use the 'cleanup' command to reduce the size of your /var/adm/sw directory. (...and don't diddle with this directory in any other way!).

There are man pages that come with 'cleanup'. Have a look at them for more explanation. If you have any kind of relatively recent GR bundle applied, you should have the utility already. Otherwise for 11.0 the latest container is PHCO_24347. Its not a bad idea before loading a new GR or QPK bundle to commit a good current state with 'cleanup'.

Regards!

...JRF...