MB.ACT light OFF --- after Solaris 9 recommended patch cluster applied

After applying the recommended patch cluster to several SunFire V210s/V240s the "system ready" or "activity" light on the front panel no longer illuminates. The systems come up fine and are fully functional, just no light.
While this has absolutely no impact on usability it is a bit disconcerting for the folks in the server room when glancing at the rack and not seeing the typical green light.
I first noticed the problem in mid 2007 and have tried patch clusters as recent as last month, but the light remains out.
One interesting discovery is that if I reset (hard) the ALOM module the light comes back on. However, if the system is subsequently rebooted for any reason the light does not come back on...
If anyone can shed some light on the issue I would greatly appreciate it!
-Sap

continued.
I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
It ends with
! root@jumpstart:/var/spool/patch # patchadd 139555-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Preparing checklist for non-global zone check...
Checking non-global zones...
This patch passes the non-global zone check.
139555-08
Summary for zones:
Zone oem
Rejected patches:
None.
Patches that passed the dependency check:
139555-08
Patching global zone
Adding patches...
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
Patchadd is terminating.
! root@jumpstart:/var/spool/patch #the logfile shows
! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
erver running?): Resource temporarily unavailable
Installation of <SUNWarc> failed (internal error).
No changes were made to the system.Help!
-- Nick

Similar Messages

Management console problem after installing recommended patch cluster

Hello everyone.
I just got a new SUN 440 server, it didn't come with the solaris os installed and so I installed solaris 9 12/03 to it. The installation went fine and I could start the management console with no problems at all. Then I went to sunsolve.sun.com to download the latest recommended patch clusters for solaris 9 (this was yesterday Sept.-06-2006), I downloaded the file, checked it with md5sum, unzipped it, went to single user mode and ran the install_patch script. After the patch cluster finished installing I rebooted the server for the patches to take effect, I logged in, tried to run console management 2.1 and it starts OK but I cannot use any services it offers because it says (in the console events):
"Server Not Running: no solaris management console server was available on the specified server. Please ensure there is a Solaris Management Console server available on the specified host and that it is running"
When I click on "See Exception" I get (for a particular service that is... in this case com.sun.admin.fsmgr.client.VFsMgr - for managing file systems):
java.rmi.RemoteException: Server RMI is null:
at sun.com.management.viperimpl.client.ViperClient.lookupServer(ViperClient.java:376)and so on...
I already checked that the service is running on port 898 and it seems that there is no other app. using that same port. I also restarted the service using /etc/init.d.init stop/status/start but I get the same results.
I don't know solaris very much and don't know what else to do, please help.
Thanks in advance.

Well, I guess what you see isn't what you get.
Guess I'm used to the fact USENET just left things formatted the way they were :-O

Solaris reboot loop after recommended patch cluster

Hi,
I have a problem with my solaris 10 x86 install on my intel notebook. after installing the latest recommended patch cluster and the necessary reboot my latop stays in a loop.
one of the last lines I was able to see:
panic[cpu0]/thread=fec1d660: boot_mapin():No pp for pfnum=20fff
fec33b4c genunix:main+1b ()
skipping system dump - ....
rebooting...
any ideas ?
cu+thx

This horrible patch caught me out too. I found this and it fixed my problem.
http://weblog.erenkrantz.com/weblog/software/solaris
<snip>
[...at the Solaris boot prompt; enable kmdb, debugging, and single-user
so that you can remove the patch and reboot...]
boot -kds
[...wait for it to boot...]
physmax:w
:c
[...you'll see 'stop on write of'...]
physmax/X
[...you'll see something like the following line:
physmax: bff7f
this is a hex number; add one; so if you see bff7f,
your next line will need to be bff80...]
physxmax/W bff80
:c
[...system will boot and go into single user mode...
now, go toss those patches...]
patchrm 118844-19 120662-03 118345-12 118376-04 \
118565-03 118886-01 119076-10 118813-01 \
118881-02 120082-07 119851-02
shutdown -i6 -y -g0 "sun should test their patches"
</snip>

Solaris 10 SPARC Recommended Patch Cluster for 2008 quarter 3 version

Dear All,
Could any one please guide me, where I can download "Solaris 10 SPARC Recommended Patch Cluster" for 2008 quarter 3 version.
I have checked in sunsolve.sun.com, I'm able to find only the latest release.
please guide me.
Thanks and regards,
veera

Ok,
Here's a cute little formula to try using your systems parameters to gain some "head's-up" on an expected or estimated time to complete the patch run.
You will need a few things to prepare.
Number of "real" CPU's (not hyperthreads)
Speed of each CPU as a whole number i.e 2.87Ghz = 2,867
the total number of patches from the cluster i.e. Sept 15th = 381 (Solaris 10)
Network factor if using NFS = 2.5
local cluster file factor = 1.5
Patch cluster on CDROM factor = 3.25
Now, combine all of those elements in this equation:
{ ( #1 * #2 ) / #3 * factor(#4 or #5 or #6) }
This will yield a number in minutes of patch run time. Then all you will need to add is the standard boot up time to get the total of all patching and reboot.
Of course you could write a script to extract all of this information and feed it to "bc -l" to get a quick figure.
Example, on one of my Solaris 10 boxes with the information filled in to the equation:
#> echo "((4*2660)/381)*1.5"|bc -l
#> 41.88976377952755905511
It actually took 44.2 minutes to complete the patching of this box plus another 12 minutes to reboot. But all in all a pretty fair estimate I think.

How to backout a Recommended Patch cluster deployment in Solstice disksuite

Hello Admin's,
I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
1) Will shutdown the applications and the databases on the server:
2) Will capture the output of the following commands :
df -k
ifconfig -a
contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
metastat -p
netstat -rn
prtvtoc /dev/rdsk/c1t0d0s0
prtvtoc /dev/rdsk/c1t1d0s0
3) We bring the system to the ok prompt
4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
=======================================================================================
user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
/dev/dsk
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435895 4740117 43% /
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 16779312 blocks
d11: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay
d12: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay
user1@myserver>
===================================================================================
ok nvalias backup_root <disk path>
Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
ok printenv boot-device
boot-device= disk net
ok setenv boot-device disk backup_root net
boot-device= disk backup_root net
In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
ok boot backup_root
user1@myserver>metadb -i
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
user1@myserver>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435896 4740116 43% /
/dev/md/dsk/d40 2053605 929873 1062124 47% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d30 2053605 937231 1054766 48% /var
swap 2606008 24 2605984 1% /var/run
swap 6102504 3496520 2605984 58% /tmp
/dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
/dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
user1@myserver>metastat d40
d40: Mirror
Submirror 0: d41
State: Okay
Submirror 1: d42
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d41: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Okay
d42: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Okay
user1@myserver>metastat d30
d30: Mirror
Submirror 0: d31
State: Okay
Submirror 1: d32
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d31: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
d32: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay
user1@myserver>metastat d50
d50: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10487070 blocks
d51: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d52: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
user1@myserver>metastat -p
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
user1@myserver>pkginfo -l SUNWmdg
PKGINST: SUNWmdg
NAME: Solstice DiskSuite Tool
CATEGORY: system
ARCH: sparc
VERSION: 4.2.1,REV=1999.11.04.18.29
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Solstice DiskSuite Tool
PSTAMP: 11/04/99-18:32:06
INSTDATE: Apr 16 2004 11:10
VSTOCK: 258-6252-11
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 150 installed pathnames
6 shared pathnames
19 directories
1 executables
7327 blocks used (approx)
user1@myserver>
=======================================================================================
5) After successfully testing the above we will bring the system to the single user mode
# reboot -- -s
6) Detach the following sub-mirrors :
# metadetach -f d10 d12
#metadetach -f d30 d32
#metadetach -f d40 d42
#metadetach -f d50 d52
# metastat =====> (to check if the submirror�s are successfully detached)
7) Applying patch on the server
After patch installation is complete will be rebooting the server to single user mode
# reboot -- -s
confirming if patch installation was successful (uname �a) .
8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
# metattach d12 d10
# metattach d30 d32
#metattach d40 d42
# metattach d50 d52
# metastat d10 =====> (to check the submirror is successfully reattached)
user1@myserver>uname -a ; cat /etc/release ; date
SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Assembled 12 December 2002
Mon Apr 14 17:10:09 BST 2008
-----------------------------------------------------------------------------------------------------------------------------

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Problem: installing Recommend Patch Cluster: patch 140900-10 fails

I don't know if this is correct location for this thread (admin/moderator move as required).
We have a number of Solaris x86 hosts (ie 4) and I'm trying to get the patched and up to date.
I obtained the latest Recommended Patch Cluster (dated 28Sep2010).
I installed it on host A yesterday, 2 hours 9 mins, no problems.
I tried to install it on host B today, and that was just a critical failure.
Host B failed to install 140900-01, because the non global zones rejected the patch because dependancy 138218-01 wasn't installed in the non global zones.
Looking closer, it appears that 138218-01 is for global zone installation only; so it makes sense that the non global zones rejected it.
However, both hosts were in single user mode when installing the cluster and both hosts have non global zones.
140900-01 installed on host A with log:
| This appears to be an attempt to install the same architecture and
| version of a package which is already installed. This installation
| will attempt to overwrite this package.
|
| Dryrun complete.
| No changes were made to the system.
|
| This appears to be an attempt to install the same architecture and
| version of a package which is already installed. This installation
| will attempt to overwrite this package.
|
|
| Installation of <SUNWcsu> was successful.
140900-1 failed on host B with this log:
| Validating patches...
|
| Loading patches installed on the system...
|
| Done!
|
| Loading patches requested to install.
|
| Done!
|
| Checking patches that you specified for installation.
|
| Done!
|
|
| Approved patches will be installed in this order:
|
| 140900-01
|
|
| Preparing checklist for non-global zone check...
|
| Checking non-global zones...
|
| Checking non-global zones...
|
| Restoring state for non-global zone X...
| Restoring state for non-global zone Y...
| Restoring state for non-global zone Z...
|
| This patch passes the non-global zone check.
|
| None.
|
|
| Summary for zones:
|
| Zone X
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
|
| Zone Y
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
|
| Zone Z
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
| Fatal failure occurred - impossible to install any patches.
| X: For patch 140900-01, required patch 138218-01 does not exist.
| Y: For patch 140900-01, required patch 138218-01 does not exist.
| Z: For patch 140900-01, required patch 138218-01 does not exist.
| Fatal failure occurred - impossible to install any patches.
| ----
| patchadd exit code : 1
| application of 140900-01 failed : unhandled subprocess exit status '1' (exit 1 b
| ranch)
| finish time : 2010.10.02 09:47:18
| FINISHED : application of 140900-01
It looks as if the patch strategy is completely different for the two hosts; both are solaris x86 (A is a V40z; B is a V20z).
Trying to use "-G" with patchadd crabs the patch is for global zones only and stops (ie it's almost as if it thinks installation is being attempted in a non global zone).
Without "-G" same behavior as patch cluster install attempt (no surprise there).
I have inherited this machines; I am told each of these machines were upgraded to Solaris 10u6 in June 2009.
Other than the 4-5 months it took oracle to get our update entitlement to us, we've had no problems.
I'm at a loss here, I don't see anyone else having this type of issue.
Can someone point the way...?
What am I missing...?

Well, I guess what you see isn't what you get.
Guess I'm used to the fact USENET just left things formatted the way they were :-O

Recommended patch cluster release

Hello,
How often is the Recommended Patch cluster released?
A Couple of years ago, i was told at a Sun event during a session, that changes has been made en the way patch cluster was created, and that the patch clusters was created 4 times a year, to make it more streamlike, instead of creating patchclusters once in a while, when enough patches has been created. I need to know if it still works the way, that patch cluster are created 4 times a year, it is to be used with patch procedures and recommendations.
Best regards
Yngve Berthelsen

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Problem install Recommended Patch cluster

Trying to install the Recommended patch cluster on Ultra 45s, on each one, the 40th patch, 120272-28, fails, and I don't understand why. Here's the snippet from the log:
STARTING : application of 120272-28
start time : 2010.11.30 08:41:42
# /usr/sbin/patchadd 120272-28
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWsmaS from directory SUNWsmaS in patch 120272-28 is not installed on the system. Changes for package SUNWsmaS will not be applied to the system.
Checking patches that you specified for installation.
Done!
The following requested patches will not be installed because
they are incompatible with patches already installed or with
other patches that you have specified for installation. In order to install these
requested patches you should resolve this incompatibility
by removing incompatible patches from requested-to-install set
or from the system.
0 Patch 120272-28 is declared as incompatible by IDR138540-01, which has already been installed on the system.
No patches to install.
patchadd exit code : 3
application of 120272-28 failed : unhandled subprocess exit status '3' (exit n branch)
finish time : 2010.11.30 08:41:42
FINISHED : application of 120272-28
I don't understand why it fails, rather than just being "skipped", as several other patches are. I assume the failure isn't coming from the fact that it's been declared incompatible, but rather the "unhandled subprocess exit status". How do I determine what that is?
Or, better yet, how do I tell the installcluster script to just not do that one?
Thanks!

did you try and removed the IDR? I.e: patchrm IDR138540-01 ?
.7/M.

SPARC10 not booting after 2.5.1 Recommended Patch Cluster Install

Hi everyone,
Just finished installing the "latest" patch cluster on my ancient SPARC10, and now it doesn't boot. Here's what I see:
ok boot /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0
screen not found.
Can't open input device.
Keyboard not present. Using tty for input and output.
SPARCstation 10 (1 X 390Z55), No Keyboard
ROM Rev. 2.25, 112 MB memory installed, Serial #6332710.
Ethernet address 8:0:20:12:7f:99, Host ID: 7260a126.
Rebooting with command: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0
Boot device: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0 File and args:
not found: abort_enable
not found: abort_enable
not found: tod_validate
not found: tod_fault_reset
krtld: error during initial load/link phase
Memory Address not Aligned
Type help for more information
ok
At first I thought I had a RAM problem. I've swapped RAM, but that didn't make it boot. I then thought I had a system board problem. I've swapped that as well, and still no dice. I wish I'd have kept the list of patches that successfully installed like my gut told me to, but I didn't. Searching Google and the Sun websites didn't turn up any fixes to the problem, so I'm hoping I can find help here.
Did the patches clobber something the machine needs to boot? I believe the OS disks are mirrored, and I've tried booting off each submirror, but the result is the same.
If I can avoid booting off of CD-ROM, that would be ideal since I don't have an external CD-ROM available to boot from.
Thanks for any help!

Ouch !
Haven't seen that one in years !
It's your choice of that ancient Operating Environment, combined with a cpu faster than 419MHz.
I hope you still have the extra OECD disk that was packed with that system when it was first shipped from Sun.
Otherwise you may just be out of luck with using Solaris 2.5.1
Here's a link at a non-Sun 3rd party web site to SRDB document *20576*
http://www.sunshack.org/data/sh/2.1/infoserver.central/data/syshbk/collections/intsrdb/20576.html
Perhaps MAAL and haroldb can contribute their thoughts on this.

Solaris 8 patches added to Solaris 9 patch cluster and vice versa

Has anyone noticed this? On the Solaris 8 and 9 patch cluster readmes, it shows sol 9 patches have been added to the sol 8 cluster and sol 8 patches have been added to the sol 9 cluster. what's the deal? I haven't found any information about whether or not this is a mistake.

Desiree,
Solaris 9's kernel patch 112233-12 was the last revision for that particular patch number. The individual zipfile became so large that it was subsequently supplanted by 117191-xx and that has also been supplanted when its zipfile became very large, by 118558-xx.
Consequently you will never see any newer version than 112233-12 on that particular patch.
What does <b>uname -a</b> show you for that system?
Solaris 8 SPARC was similarly effected, for 108528, 117000 and 117350 kernel patches.
If you have login privileges to Sunsolve, find <font color="teal">Infodoc 76028</font>.

What is the latest Solaris 8 Patch Cluster available?

Currently I'm using SunOS Release 5.8 Kernel Version Generic_108528-29. Is this latest kernel version available on Solaris 8?
-Sarkar

Latest Solaris 8 Patch Bundle is available here:
[SunSolve Patch Access|http://sunsolve.sun.com/show.do?target=patches/patch-access]
Edited by: SolarisSAinPA on May 20, 2008 12:21 PM
Also, you can look up the patch id ( 108528-29 ) for kernel to see if it's latest (it won't be obsoleted)

Solaris 8 Patch Cluster 200801 installation / disk utilization spikes

Hello All,
Since we installed the latest Patch Cluster patch our disk utilization has shot up substantially. Is there anyone having same experience? If you do, could you please help us to identify some areas to take a look?
Thanks very much.
Yi

hi again. i just fixed my problem. apparently when i unzipped the file and then burned it onto cd...the data got corrupted. i fixed it by copying the zip file onto cd and then extracting the patches onto the solaris machine.

Static library not accessed properly after Solaris Kernel patch update !

Hi,
We are facing a sever issue in our application after our customer updated the Solaris 10 kernel patch u9 to u10.
We have two static libraries libdlib.a and libDLIB.a, with exactly same code base, but these two libraries are scattered across the code base and linked by many shared objects in our application.
However, one of the shared objects that links to "libdlib.a" library tries to access a function from "libDLIB.a". This behavior is causing a crash at a later point, since that shared object is supposed to access the function from "libdlib.a". Moreover, we found this is happening through the use of dbx.
I'm unable to understand why this problem surfaced after kernel patch update, though still the shared object works fine on Solaris 10 u9 patch.
Flow is something like this :
1. syslogrecorder.so gets loaded by one of the processes.
2. syslogrecorder.so is linked to "libdlib.a" at compile time, so it uses "libdlib.a" function DLIB_LoadLibrary and gets a handle to all the function pointers of the loaded library ( The purpose of DLIB_LoadLibrary is to load a shared library dynamically using dlopen )
3. syslogrecorder.so tries to do a "dlsym" and to do that it needs access to the library handle which we got in previous call DLIB_LoadLibrary. So syslogrecorder.so calls another function from DLIB_ProcAddress, which actually gives back the access to the loaded shared library.
Here is a catch in step 3, it is supposed to call DLIB_ProcAddress from the libdlib.a but as we observed from dbx output it does so by calling DLIB_ProcAddress from libDLIB.a and hence fails to give back the access to loaded shared library, causing crash at a later point in code.
Can someone put some light here that why this could happen ??
Thanks
Kuldeep

To clarify: You did not modify or rebuild any of your binaries, but after installing a kernel patch, the application stopped working. Most likely, something about your application depended on a accidental behavior of the runtime loader. That accidental behavior changed due to the patch, and your application failed.
For example, if there is a circular dependency among shared libraries, the loader will break the cycle at an arbitrary point to establish an initialization order. By accident, that order might work, in the sense of not causing a problem. A change to the loader could cause the cycle to be broken at a different point, and the resulting initialization order could cause a now-uninitialized object to be accessed. I'm not saying this is what is wrong, but this is an example of a dependency on accidental loader behavior.
Finding your actual problem will require tracing the sequence of operations leading up to the failure. You are more likely to find help in a Solaris linker forum. AFAIK, there are currently no Oracle forums for Solaris, and the old OpenSolaris forums have been converted to mailing lists. You can try the "tools-linking" list found on this page:
http://mail.opensolaris.org/mailman/listinfo
I also suggest you review the paper on best practices for using shared libraries written by Darryl Gove and myself:
http://www.oracle.com/technetwork/articles/servers-storage-admin/linkinglibraries-396782.html
If you have a service contract with Oracle, you can use your support channel to get more help.
Edited by: Steve_Clamage on May 18, 2012 3:21 PM

J2EE Recommended Patch Cluster fails with Kernel patch 108528-26

As part of the J2EE recommended cluster, I attempted installing patch 108528-26 to my Solaris 8 box (all of which was downloaded from sun.com):
SunOS boedev 5.8 Generic_108528-14 sun4u sparc SUNW,UltraAX-MP
It failed and rolled back as part of the cluster with the following error log:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Without rebooting, I then downloaded the patch from sunsolve as a separate patch and attempted to load it with patchadd, to no avail but with additional errors (WARNING:) along with the original ones:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Now I have a box with many J2EE patches but without the proper kernel!!! Halp! jj.

did you try and removed the IDR? I.e: patchrm IDR138540-01 ?
.7/M.

Java Web Console starts in "user local mode" after Sol 10 Patches

After applying Solaris 10 recommended patch cluster, the web console on my SPARC platform starts the web console such that only the local host clients can connect via web (https://localhost:6789/). Webconsole log file states "the console instance "console" is starting in local user mode. Prior to applying the patch cluster, the log file stated "the console instance "console" is starting in user mode." How do I get it to start in regular user mode?
Patch cluster is dated: 24-Apr-2009. I am running Version 3.1 of the webconsole. Using the webconsole primarily for adminsistration of Sun Java Directory Server 6.3.1 using the DSCC.

Thank you for the response. Prior to implementing your recommended fix, I discovered the following Example in the man pages for smcwebserver:
Example 3 Using SMF Property to Allow Remote Access
The following sequence of commands allows remote access to the Sun Web Console server.
# svccfg -s svc:/system/webconsole \
setprop options/tcp_listen = true
# svcadm refresh svc:/system/webconsole
Executing the above commands restored full webconsole access.

MB.ACT light OFF --- after Solaris 9 recommended patch cluster applied

Similar Messages

Maybe you are looking for