check_patches ERRORS

[Don Palmer]

After installing PHKL_18543 and its dependencies using SAM, the check_patches reports many checksum errors related to PHKL_18543 and implies I should reinstall PHKL_18543 with reinstall=true.

However, several forum items mention difficulties. Should I trust check_patches or what?

[Insu Kim]

This is information for you.

First, check out Patch Package size which should be 19900 KBytes if you're using HPUX 11.0 and then try to see if it's properly configured on the system with commmand.

# swlist -l fileset -a state PHKL_18543
Output will be..
PHKL_18543
PHKL_18543 ........... configured

See files /var/adm/sw/swagent.log, swinstall.log to ensure that there were no errors upon installation.

Regards.

[James R. Ferguson · Accepted solution]

Don:

Document #KBRC00000650 states:

PROBLEM: The following error occurs when the check_patches utility is run:

ERROR: Patch fileset PHKL_18543.CORE2-KRN object module, /usr/conf/lib/libhp-ux.a(mod_object.o), cksum values do not match:
Expected cksum: 1088550886 6088
Actual cksum: 1414926281 6164
This patch should be reinstalled using the
swinstall(1M) option '-x reinstall=true'.

If patch PHKL_18543 is installed, it's dependencies show up with checksum errors. Reinstall PHKL_18543 with all it's dependencies and still receive the above error.

RESOLUTION: This is a known problem with check_patches and patch PHKL_18543. The check_patches utility does not report correct information...Until check_patches is enhanced, the only workaround is to disregard the above error messages with regards to this patch only.

PHCO_22044 corrects this problem.

...JRF...

[John Pyle]

I don't know if anyone is still looking into this problem but I found it on my server as well and I have the 22044 patch. I could not find any errors for either of these patches in the swagent or swinstall logs. My question is do I still have a problem, and if 22044 would fix this what could I do to make check_pataches happy? My output from the swlist for 18543 and 22044 is as follows:

# swlist -l fileset -a state PHKL_18543
# Initializing...
# Contacting target "hostname"...
#
# Target: hostname:/
#

# PHKL_18543
PHKL_18543.C-INC configured
PHKL_18543.CORE-KRN configured
PHKL_18543.CORE2-KRN configured
PHKL_18543.KERN2-RUN configured
PHKL_18543.VXFS-BASE-KRN configured
PHKL_18543.VXFS-PRG configured

# swlist -l fileset -a state PHCO_22044
# Initializing...
# Contacting target "hostname"...
#
# Target: hostname:/
#

# PHCO_22044
PHCO_22044.RELEASE-NOTES configured
PHCO_22044.SD-CMDS configured

[Darrell Allen]

Interesting. I didn't know check_patches had this problem. I'm on 11.0 and have just recently run it. It suggested I re-install a couple of filesets. I did and check_patches then ran without reporting problems. I presumed it performed as advertised when reporting the problems, especially since the error's cleared up after the re-install.

Darrell

[John Pyle]

I'll try a re-install with the flag for re-install even if it exists and see what I get. Thank you for your post.