check_patches returns PROBLEM FOUND

[Artyom Voronchihin]

Where is no error messages in check_patches.report file, only one WARNING (see attached file). But check_patches returns state PROBLEM FOUND. I think the reason is the warning in the report. How can i change state of problem patches ? I've tried to correct every patch with "swconfig " but it skip filesets because they are superseded, and "swconfig -x patch_commit=true " but it has no affect.

[Zeev Schultz]

Privet Artyom,
I don't think it should bother you - these
patch filesets are superseeded anyway.Can run
swlist -l fileset -a state for same results.

Zeev

[Bill McNAMARA_1]

attach the output of

swlist -l patch -a state

is there a file /var/adm/sw/needs_config ?

Later,
Bill

[James R. Ferguson]

Hi:

I would do nothing. 'check_patches' has noted, "...Since these patch filesets have already been superseded on this system, it may not be safe to have the configure script executed via the swconfig(1M) command. Doing so could have a negative effect on the active patch.".

Regards!

...JRF...

[Steven E. Protter]

All I would do is get rid of superseded patch sets.

cleanup -c 1

Anything thats been superseded by more than one patch will be gone. You could set it to zero, but that makes me nervous.

The command above will reduce but not eliminate the messages you are getting.

It is perfectly acceptable though to do nothing.

SEP

[Artyom Voronchihin]

Hi guys !
Thanks for your answers. But I still wonder why check_patches returns "Problems Found" result if all patches are in correct state as you said ? What can i do to get "No problems found" result ?
It's a newly cold installed system HPUX 11.0 (from March 2002 Install/Update/Recovery and Support Plus CDs).
Bill, where is no /var/adm/sw/needs_config file. I attached "swlist -l patch -a state" output.
Steven, "cleanup -c 1" didn't remove any strings in check_patches.report. It only removed files in /var/adm/sw/save folder.

[Bernhard Mueller · Accepted solution]

Hello,

I believe it started with the June 2001 11.00 core/install CD that you have this effect that
installed filesets remain after a standard installation.

The reason is that patches are installed and then there is no configure but superseding patches are installed on top and only then the new (superseding) filesets are getting configured.

The older ones are not configured because the patch state is already "superseded"

You can easily get around your problem by doing the following:
swlist -l fileset -a state | grep installed | awk '{print $1}' > /tmp/inst_fsets
swmodify -a state=configured -f /tmp/inst_fsets

This will modify the state of all "installed" filesets to "configured".

Regards,
Bernhard