07-14-2011 05:11 AM
After running swmodify -x patch_commit=true \* we receive this error.
ERROR: Could not select the software
software is in a corrupt state and is not available for
selection. Corrupt software can be removed with the swremove
command, or replaced with the swcopy command.
ERROR: Failed to select all the software which exists in the target.
Swlist -l fileset -a state | grep corrupt shows:
If this was just a patch I would remove it, or at least try to remove it, and reapply it. Sys-files sounds like some serious trouble though.
Is there a safe way to correct this problem? If we ignore it would this create patching problems down the road?
Any suggestions are greatly appreciated.
07-14-2011 06:18 AM
Paul Coffey_1 wrote:
... If this was just a patch I would remove it, or at least try to remove it, and reapply it.
It is most likely a patch that needs to be removed and/or reapplied as the message states. To see what *patch* delivered the fileset try doing:
# swlist -l file | grep PH
07-14-2011 07:24 AM
You may need to swremove the software.
swconfig might work for you as well, just the corrupt patch.
swverify \* or swverify <patch name>
Owner of ISN Corporation
07-14-2011 11:48 AM
>swlist -l fileset -a state | grep corrupt shows:
I would have thought if this was HP's product, it would have some caps in the name.
What's in it: swlist -l file sys-files
>Is there a safe way to correct this problem? If we ignore it would this create patching problems down the road?
swremove might do it but how important is it?
Do you have an ignite backup?
07-14-2011 01:58 PM
Yes there might be problems patching the system down the road.
This may have been broken for some time. To pick the ignite backup to restore you would need a time line as to when it got broken.
There are likely dependencies, but swremove followed by re-install is a good first step.
Owner of ISN Corporation
07-19-2011 09:13 AM
This doesn't appear to be a patch. When I run swlist for PH none of the patches list sys-files. When I pull a complete swlist from the system the items that are sys-files are things like /etc/mail, /etc/nsswitch.conf, /sbin.
If I run swlist grepping for PH and corrupt I find two items listed:
# PHKL_24026 1.0 JFS Filesystem swap corruption
# PHKL_29911 1.0 Improper core file mesg, corrupt core file
I've attached a text file with the swlist output that shows the sys-files items. I'm going to get that index file and check it.
I don't believe this is something I can just fix.
07-19-2011 11:21 AM
The index file shows corrupt as well. Is there a way to fix this?
title "Systems Files"
07-19-2011 02:05 PM
What of the state of other INDEX files within the IPD? What of the master INDEX (/var/adm/sw/products/INDEX)?
You could try the following to try and rebuild the Master INDEX file....though if only this product is the problem, then I dont think this will help.
The following will install a "void" fileset and then remove it. Doing so without having an INDEX file to reference will cause the system to scan the /var/adm/products directory tree and build a new INDEX file and update the IPD in whole
Run the following commands to rebuild the IDP:
# cd /var/adm/sw/products
# mv INDEX INDEX.bad (save the original so you can restore if it this goes bad)
# cd /tmp
# vi void.psf (create a file called void.psf with the following contents)
:wq! (Save and quit out of the VI session)
# swpackage -s /tmp/void.psf
# swinstall void This may take several minutes to complete.
# swremove void
# rm void.psf
# swremove -d void
If for some reason other parts of the IPD are corrupt, then the entire directory structure may need restoring from backup.
07-19-2011 02:14 PM - edited 07-19-2011 02:16 PM
>I've attached a text file with the swlist output that shows the sys-files items.
This appears to be a site specific sysadmin SD product.
I would suggest you swremove it but all of your configuration values may be lost?
First make sure you have an ignite backup or tar of this part of the IPD.
You might just change that state to: state configured
Then try: swverify sys-files
07-19-2011 02:53 PM
The only non hp software on this box is a DB. I'll try your suggestions tomorrow but I think I'm out of luck. I'm going to proceed with patches and see what happens and just know it might be a problem down the road.