Operating System - HP-UX
1747984 Members
4669 Online
108756 Solutions
New Discussion юеВ

Re: Question about Patching

 
SOLVED
Go to solution
Marty Metras
Super Advisor

Question about Patching

I got this message while trying to do the patches HP's custom patch manager said.
Along with the log attached.
It installed a mess of stuff but not all.
I aborted and it still installed the rest.
I have seen no adverse effects yet.
What does this mean?
Marty

==========================================
ERROR: The command "/usr/sbin/mk_kernel", which is used to rebuild
the kernel, has failed. Because kernel-related filesets were
installed, this command must be executed by "swinstall",
without failures, before the load can continue. Check the
above output for details about the failure.
NOTE: The Install Phase has suspended. Check the above output for
reasons.
=============================================
The only thing that always remain the same are the changes.
10 REPLIES 10
Karthik S S
Honored Contributor

Re: Question about Patching

Hi,

The attached file only contains the result of the Analysis phase and there were no problems with that. If you have started the installation you can see the actual error messages in /var/adm/sw/swinstall.log.

I think some of the PHKL/PHNE patches would have failed to install properly due to kernel compilation errors.

Post swinstall.log

-Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
Victor_5
Trusted Contributor

Re: Question about Patching

The attached log no problem at all, post the /var/adm/sw/swinstall.log and grep all the "ERROR".

Any reason for stopping the installation? You may need to reinstall.
Marty Metras
Super Advisor

Re: Question about Patching

Attached is swinstall.log
Marty
The only thing that always remain the same are the changes.
Karthik S S
Honored Contributor

Re: Question about Patching

What it appears to be from the log file is that after the Analysis Process was over the swinstall got terminated/crashed for some reasons and I can not see any reference to the actual installation. Better idea would be to reinstall all the patches.

-Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
Victor_5
Trusted Contributor

Re: Question about Patching

The swinstall.log looks fine to me too, can you tell me how did you do the installation, also, it will be helpful if you can post /var/adm/sw/swagent.log as well.
Victor_5
Trusted Contributor

Re: Question about Patching

Sorry forgot to mention, I don't need the whole log, only those logs with "ERROR" on Dec. 6.
Marty Metras
Super Advisor

Re: Question about Patching

Here is the swagant.log for 12/06/03.

Marty
The only thing that always remain the same are the changes.
Victor_5
Trusted Contributor

Re: Question about Patching

ld: Unsatisfied symbol "prf_klog_getcount" in file /usr/conf/lib/libhp-ux.a[klog.o]
ld: Unsatisfied symbol "prf_klog_getstring" in file /usr/conf/lib/libhp-ux.a[klog.o]
ld: Unsatisfied symbol "pwrite" in file /usr/conf/lib/libhp-ux.a[scall_stubs.o]
ld: Unsatisfied symbol "lock_claim" in file /usr/conf/lib/liblvm.a[lv_hp.o]
ld: Unsatisfied symbol "set_timedout" in file /usr/conf/lib/libhp-ux.a[safety_time.o]
ld: Unsatisfied symbol "pread" in file /usr/conf/lib/libhp-ux.a[scall_stubs.o]
ld: Unsatisfied symbol "lock_disown" in file /usr/conf/lib/liblvm.a[lv_hp.o]

For all your ld complains, you can follow these steps to go through one by one trying to find out which one related with which patch, then reinstall those patches.
1. cd /usr/conf/lib
2. nm *|grep -e Symbol -e prf_klog_getcount| pg
3. what /usr/conf/lib/libhp-ux.a | grep klog.0

Or, another simply way, run swinstall to do the reinstallation from beginning,
options --> change options --> check
[] reinstall filesets even if same revision exists
[] reinstall files even if same one already there

Hope it helps. Good luck!
Marty Metras
Super Advisor

Re: Question about Patching

Victor,
Looks Like that did the trick. Reinstalling and forcing it to rewrite the files.
I learned enough to do the patches on our Production server this weekend.

Thanks all of you for the help.
Have a Happy Holliday.
Marty
The only thing that always remain the same are the changes.