Patches won't install after reboot

I have the same experience as Radmanly, maybe I can add this information:

All 11 patches are already downloaded to /var/sadm/spool

spool# ls -l 120665-01.jar

-rw-r--r--1 rootroot114974 Jun 30 15:04 120665-01.jar

spool# smpatch add -i 120665-01

add patch 120665-01

Transition old-style patching.

This patch is obsoleted by patch 118855-14 which has already

been applied to this system.

same result for all eleven patches.

/Oskar

Oskar_H at 2007-7-6 21:45:49 >

The output is in swedish Im afraid (cant just paste) but it says something like "Following patch will not been installed ...... all packages from patch NUMBER has been corrected by a patch with a later version. There is no patches (or "corrections" perhaps...) to be installed".

I paste parts of the output from 'smpatch update' in genuine english:

Installing patches from /var/sadm/spool...

Jul 4 22:43:39 zoe root: => Thread[Thread-19,5,main] <=Problem installing patches: Received a Manipulable event.

Jul 4 22:43:40 zoe root: => com.sun.patchpro.util.PatchBundleInstaller@e580e1 <=Failed to install patch 121126-01.

Jul 4 22:43:40 zoe patchadd utility failed. Reason code :0

Jul 4 22:43:40 zoe Checking installed patches...This patch is obsoleted by patch 118855-14 which has alreadybeen applied to this system.Patchadd is terminating. Transition old-style patching.

Failed to install patch 121126-01.

patchadd utility failed. Reason code :0

Checking installed patches...This patch is obsoleted by patch 118855-14 which has alreadybeen applied to this system.Patchadd is terminating. Transition old-style patching.

Jul 4 22:43:40 zoe root: => Thread[Thread-19,5,main] <=Problem installing patches: ALERT: Failed to install patch 121126-01.

ALERT: Failed to install patch 121126-01.

/Oskar

Oskar_H at 2007-7-6 21:45:49 >

Hello,

> The patches are:

> 120665-01

....

The Sun's patch database is not up-to-date again. The new integrated 06/06 update patches were not registered to patch database (see /var/sadm/spool/cache/Database/*). (the same situation was after 01/06 update). Solution - wait about 1-2 weeks to use update.

M.C>

mcerveny at 2007-7-6 21:45:49 >

What happened is the Kernel Update was succesfully integrated into Solaris 10 06/06 (aka Solaris 10 u2). Upon additional testing on a Solaris 10 U1 box, the patch failed. Sun has the release of 118855-15 as a high priority.

Please note bug 6445915 is a duplicate of 6381983. SunUC should be checking locally to id patches installed and if they obsolete any patches.

kayo_granillo at 2007-7-6 21:45:49 >

Kernel patch 118855-15 is available on sunsolve and via Sun Update Connection (aka Sun Update Manager) / smpatch for Solaris 10 x86. For update 2 users using SunUC/smpatch, the patch resolves the issue of seeing patches for installed which were obsoleted by the Kernel Update integrated into Solaris 10U2.

kayo_granillo at 2007-7-6 21:45:49 >

Hello !

It looks that kernel patch 118855-15 doesn't install after station reboot.

I have installed this patch with Sun Update Connection and after reboot, the uname -a command still reports 118844-30 kernel version and patch is seen on Update Manager interface as requiring reboot.

Here you have output of smpatch get

patchpro.backout.directory""""

patchpro.download.directory/var/sadm/spool/var/sadm/spool

patchpro.install.types-rebootafter:reconfigafter:standard

patchpro.patch.source- https://getupdates1.sun.com/solaris/

patchpro.patchset-current

patchpro.proxy.host172.16.44.219""

patchpro.proxy.passwd********

patchpro.proxy.port69698080

patchpro.proxy.user""""

Any hint ?

P.S. I use GRUB as boot manager.

Adrian_609a at 2007-7-21 15:13:14 >

Hi !

This is the content of /boot/solaris directory

drwxr-xr-x2 rootsys 512 May 30 15:38 bin

-rw-r--r--1 rootsys 607 May 30 15:40 bootenv.rc

-rw-r--r--1 rootother607 May 30 15:40 bootenv.rc.118844-30.29608

drwxr-xr-x2 rootsys 512 May 2 16:44 devicedb

drwxr-xr-x9 rootsys 512 May 2 16:33 drivers

-rw-r--r--1 rootsys 304 Jan 26 23:06 filelist.ramdisk

-rw-r--r--1 rootroot51744 Jul 13 17:57 filestat.ramdisk

drwxr-xr-x2 rootsys 512 May 2 16:33 machines

-rw-r--r--1 rootroot0 Jul 21 13:15 tmp.txt

also, this is menu.lst of GRUB

#pragma ident"@(#)menu.lst1.105/09/01 SMI"

#

# default menu entry to boot

default 0

#

# menu timeout in second before default OS is booted

# set to -1 to wait for user input

timeout 10

#

# To enable grub serial console to ttya uncomment the following lines

# and comment out the splashimage line below

# WARNING: don't enable grub serial console when BIOS console serial

#redirection is active!!!

#serial --unit=0 --speed=9600

#terminal serial

#

# Uncomment the following line to enable GRUB splashimage on console

splashimage /boot/grub/splash.xpm.gz

#

# To chainload another OS

#

# title Another OS

#root (hd<disk no>,<partition no>)

#chainloader +1

#

# To chainload a Solaris release not based on grub

#

# title Solaris 9

#root (hd<disk no>,<partition no>)

#chainloader +1

#makeactive

#

# To load a Solaris instance based on grub

#

# title Solaris <version>

#root (hd<disk no>,<partition no>,x)--x = Solaris root slice

#kernel /platform/i86pc/multiboot

#module /platform/i86pc/boot_archive

#

# To override Solaris boot args (see kernel(1M)), console device and

# properties set via eeprom(1M) edit the "kernel" line to:

#

#kernel /platform/i86pc/multiboot <boot-args> -B prop1=val1,prop2=val2,...

#

#- ADDED BY BOOTADM - DO NOT EDIT -

title Solaris 10 1/06 s10x_u1wos_19a X86

root (hd0,1,a)

kernel /platform/i86pc/multiboot

module /platform/i86pc/boot_archive

#END BOOTADM--

#- ADDED BY BOOTADM - DO NOT EDIT -

title Solaris failsafe

root (hd0,1,a)

kernel /boot/multiboot kernel/unix -s

module /boot/x86.miniroot-safe

#END BOOTADM--

title Windows

rootnoverify (hd0,0)

chainloader +1

I didn't figure how to see what kernel is GRUB using to boot, because in /platform/i86pc the file multiboot is quite old, from January.

Adrian_609a at 2007-7-21 15:13:14 >