Sun Solaris SCTP Denial Patch 127127-11 (Unloading SCTP module Solaris 10

THe patch 127127-11 is suppose to address the SCTP Denial of service vulnerability for solaris 10.
i am planning not to install this patch but instead to unload this SCTP driver module from the system kernel
i tried using modunload or update_drv , but (see below). My question , i believe these 2 commands only unload for this session but is not permanent across next reboot. i am thinking to make permanent change will require modiification to /etc/system file. But what is the entry to do this, is it something like....
/etc/system
forceunload SCTP driver
# modinfo | grep sctp
93 7bf118d8 588 235 1 sctp (SCTP device)
94 7bf11b90 588 236 1 sctp6 (SCTP6 device)
myausuv00100443:/usr/kernel
# modunload -i 93
can't unload the module: Device busy

I think the root of the problem is in your "userdir". It is possible that some files are in invalid state there,
and that's why you cannot start Sun Studio IDE using your account. When you start it using root account,
you use another "userdir", and that's how you avoid the problem.
So, where is your "userdir"? By default it is under $HOME/.sunstudio directory.
On Solaris x86 its name is "12.0-SunOS-i386":
bash-3.00$ ls -la $HOME/.sunstudio
total 10
drwxr-xr-x   4 nikm     staff        512 Feb 13 21:42 .
drwxr-xr-x 38 nikm     staff       1536 Mar 1 15:30 ..
drwxr-xr-x   5 nikm     staff        512 Feb 28 21:31 12.0-SunOS-i386
drwxr-xr-x   2 nikm     staff        512 Mar 1 11:07 user_infoI think on sparc its name is "12.0-SunOS-sparc".
First of all, you can try to run the IDE using your account, but with a new "userdir":
% sunstudio --userdir /tmp/ud1
(note: there are 2 '-' characters!)
If it works for you, there are two ways:
1. To remove your old "userdir", restart Sun Studio IDE, and reopen all your projects.
2. Try to repair your old "userdir".
This second way is very risky, so I suggest you to use the first one.
In future try to use Sun Studio IDE to delete your old projects - I hope it will work better for you.
Thanks,
Nik

Similar Messages

Solaris 10 kernel Patch 127127-11

we need to apply solaris 10 kernel Patch 127127-11 in our prod server as a prerequisite for oracle10g patch set 10.2.0.4 installation
but i found a Doc 242366 (May Cause a system Panic from ip_wput_ioctl()).It is mentioned in doc that Binary relief is available through normal
support channels.Is that Binary complete fix of this problem?If yes, then i need that binary please give me the link where i can download the binary,
If not, then what is the solution of this problem.?
Thanks

These kinds of binary hotfixes/IDR's are only available through sun support to contract customers.
If your concerned, I suggest you raise a support case.
That being said, 127127-11 is kinda old. So I would be surprised if the bug hadnt been fixed by now.
Its been replaced by either 137111 or 137137.
Ive upgraded at least a dozen systems past that level and never seen a problem.
So it can't be too common..

LMS 3.2 Installation - Solaris 10/09 Patch Conflict:

Hello all,
We are running Sun Solaris 10/09,working on installing LMS 3.2.As per documentation,attempted to install the two recommended patches,127127-11 and 122032-05.
The 127127-11 patch is already contained in this OS packaging.The second recommended patch - 122032-05 - does not install since there exists another patch - 141518-11 - that makes the second recommended patch(122032-05) obsolete.
The 141518-11 patch cannot be uninstalled since there is no backout data for it.
What do you recommend I do to solve this issue as I cannot move ahead with the installation as things stand.
Should I use an older release of Solaris 10 that is still downloadable from the Sun Website?If so,can anyone recommend a tried and tested release I can use.
Many thanks,
W.

Hi all,
Just resifted through the documentation and they have stated the supported releases:
"The following Solaris 10 releases are supported in LMS 3.2:
–Solaris 10, 05/09 release
–Solaris 10, 10/08 release
–Solaris 10, 05/08 release
–Solaris 10, 08/07 release
–Solaris 10, 11/06 release"
Will give the installation a shot with 10/08.
Regards,
W.

Sun VDI 3.0 patch 2 - linux guest display is laggy/unusable

Hello.
We have setup Sun VDI 3.0 to test out ubuntu desktop images. We have it functionaly setup but the lag/redraw is unusable. For example opening, closing and moving windows around has a horrible lag and takes a second or two to redraw. Just doing an "ls" from the command line is noticeably slow. I couldn't figure out any good way to measure the visual slowness I am seeing so I hope my plain english description makes sense.
The environment is setup as follows
Solaris 10 update 7 on x64 hardware.
Sun VDI 3.0 patch 2 (patch 1 behaved the same)
virtualbox 2.0.10 (version 2.0.8 with patch 1 behaved the same)
Sun 7110 as storage device
Desktop Images tried on the desktop
RedHat 5.3 (32 bit) and Ubuntu 8.04.3 (32 bit)
We installed the Sun VDI software into the all on one host demo mode. Our host is configured with 24GB of memory (24gb of swap as well per requirements). The virtualbox installs were done on the 2.0.8 version of virtualbox and then imported into the vdi solution. We ran between 2 or 3 vm's at one time so the box still had plenty of ram left since we only allocated 512MB to each vm (tried uppping that to 3GB with no perf improvements).
The Sun Ray units we tried is a stand alone 270 and 1 2FS unit. Surely i'm not the only one attempting linux desktops. I loaded up an windows XP desktop for testing purposes and it functioned great. Barely noticeable performance difference. Any ideas on what I'm missing?
Thanks. Deet.

Dirk.
Thanks for the input. I made the changes you mentioned and got an order of magnitude improvement! I was guilty of being a Solaris admin looking for a Solaris problem:)
Deet.

Solaris 8 linker patch 109147-21 / 109148-21 breaks runtime linker

The "Sun ONE Studio 8, Compiler Collection Early Access" release requires the
installation of a linker patch (109147-21 sparc / 109148-21 x86).
It seems that the solaris 8 linker patch breaks the runtime linker audit feature
for multithreaded applications.
I can reproduce the problem like this (using $LD_PROFILE, which makes
use of the runtime linker audit feature):
% cat thr.c
#define _REENTRANT
#include <stdio.h>
#include <stdlib.h>
#include <pthread.h>
void*
thr_main(void*arg)
printf("hello, world!\n");
int
main(int argc, char **argv)
pthread_t tid;
void *rval;
pthread_create(&tid, NULL, thr_main, NULL);
pthread_join(tid, &rval);
exit(0);
% cc -o thr thr.c -lpthread
% thr
hello, world!
OK, fine so far...
Now we try to run the application under rtld audit control:
% env LD_PROFILE=libc.so.1 thr
< the multithreaded application hangs >
% env LD_PROFILE=libc.so.1 LD_LIBRARY_PATH=/usr/lib/lwp thr
< the multithreaded application hangs >
(on a S8 system with 109148-14 installed, this works without hanging!!)
A "pstack `pgrep thr`" command shows multiple LWPs, all blocked
waiting in an lwp_mutex_lock() call, all trying to lock the same
mutex - which happens to be the dynamic linker's global 'rtldlock'.
% pstack `pgrep thr`
7631: thr
----------------- lwp# 1 --------------------------------
dfbd6b5f lwp_mutex_lock (dfbf1618)
dfbd69f6 lwpmutex_lock (dfbf1618) + 2a
dfbc8739 rt_mutex_lock (dfbf1618) + 19
dfbcd575 enter () + 29
dfbd2193 elf_bndr (dfa94eac, 50) + 23
dfbc3339 elf_rtbndr () + 5
----------------- lwp# 2 / thread# 2 --------------------
dfbd6b5f lwp_mutex_lock (dfbf1618)
dfbd69f6 lwpmutex_lock (dfbf1618) + 2a
dfbc8739 rt_mutex_lock (dfbf1618) + 19
dfbcd575 enter () + 29
dfbd2193 elf_bndr (dfa94eac, 238) + 23
dfbc3339 elf_rtbndr () + 5
----------------- lwp# 3 --------------------------------
dfbd6b5f lwp_mutex_lock (dfbf1618)
dfbd69f6 lwpmutex_lock (dfbf1618) + 2a
dfbc8739 rt_mutex_lock (dfbf1618) + 19
dfbcd575 enter () + 29
dfbd4257 auditpltenter () + bb
dfbd431a audit_pltenter (dfa94eac, dfa60414, df92131c, 48, df8a4cd0, df921318) + 7a
dfbc32a2 elf_plt_trace (3, ffffffff, df8a4d44) + 52
df8f435e scsetup (ffffffff, 1) + 7a
df8ea13e lwpstart () + 22
-------------------------- thread# 1 --------------------
df8e961b _swtch   (0) + 3b3
df8eb806 _dopreempt (0) + ea
df8ed247 _sigon   () + 37
df8f41d0 bindclear (1) + 48
dfbc8799 rt_bind_clear (1) + 19
dfbcd87c leave (dfbef0f4) + e8
dfbca8f7 call_init (df8d0288, 1) + 10f
dfbca339 setup (80470fc, 80471e4, 0, 8047ff2, 1000, dfbc17af, dfbf06e4, dfbc0000, ...) + cd5
dfbd3393 _setup   () + 2f7
dfbc323a rtboot () + 58
0804725c ???????? ()
-------------------------- thread# 3 --------------------
df8e7958 threadstart ()
% dbx - `pgrep thr`
Reading -
Reading ld.so.1
Reading libpthread.so.1
Reading libc.so.1
Reading libdl.so.1
Reading libthread.so.1
Reading ldprof.so.1
Reading libmapmalloc.so.1
detected a multithreaded program
Attached to process 7631 with 3 LWPs
t@3 (l@null) stopped in threadstart at 0xdf8e7958
0xdf8e7958: threadstart : call threadstart+0x5 <0xdf8e795d>
(dbx) x 0xdfbf1618 /4X
dbx: warning: unknown language, 'c' assumed
0xdfbf1618: rtldlock : 0x00000000 0x00000000 0x00000000 0x01010000
(dbx) q
detaching from process 7631
Is this a known bug?
Are there patches to fix this issue?

I think this is bugid 4804328.
Synopsis: auditing of threaded applications results in deadlock
It doesn't look like the next patch is avilable
yet, but the bug seems to be on track for being
fixed in patchid 109147-22 (the next rev of the
patch you mention. There should be new patches
for Solaris 8 sparc/intel and Solaris 9 sparc/intel.

Sun update manager with patch manager

I need to use both products since I have systems running Solaris 10, 9 and 8. Is there a way to get them to work together?
Ideally, I would like to have 1 system talk to SUN to manage the application and downloads. I would want the system to distribute the patches to all the other systems.

Yes, this is possible. We would recommend setting up Sun Update Manager on Solaris 10 as your patch proxy (with a connection to Sun). Both Update Manager on Solaris 10 and Patch Manager on Solaris 8 and 9 can then be configured as clients.

Solaris 8 Security patches after 03/2009?

Hi,
I need to know if Security patches will continue to be developped after EOL of Solaris 8 on 03/2009.
Thanks

Ok,
You will need a Solaris 8 Vintage Patch Service Contract.
http://www.sun.com/service/eosl/solaris/solaris8eosl.pdf

Sun VDI 3.0 Patch 3 is now available at SunSolve

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Hi folks,
we just released a third patch revision for Sun VDI 3.0. The patch binaries are available at SunSolve:
[Patch ID 141481-03 (Solaris 10 sparc) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141481-03-1]
[Patch ID 141482-03 (Solaris 10 x86) |http://sunsolve.sun.com/search/document.do?assetkey=1-21-141482-03-1]
Please notice that due to CR 6880209 ("The VirtualBox 2.0.x web service doesn't require clients to authenticate") both patch binaries are flagged as security relevant. This affects customers using VirtualBox as virtualization platform. A corresponding Sun Alert (268328) will be published soon.
This patch is accompanied with a minor update release of VirtualBox (*VirtualBox 2.0.12*). This updated VirtualBox version must be installed after applying the Sun VDI 3.0 patch 3 (see instructions below). The updated VirtualBox installer for Solaris 10 is available from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp]. VirtualBox binaries for other operating systems, for example, for creating desktop templates on your preferred platform, are available here.
- Klaus
The following steps are recommended for updating VirtualBox installations:
1. Login to the Sun VDI administration UI (http://yourserver:1800)
2. Select the affected VirtualBox desktop provider
3. Switch to the "Hosts" tab
4. Select the desired VirtualBox host and click on "Disable"
This ensures that no new desktops/virtual machines will be balanced/started on this host. Please notice, that this will not stop any already running desktops on this host. Thus you either need to ask users to shutdown their desktops or you explicitly trigger the shutdown/power off yourself using the administration UI. After the shutdown, users can immediately request their desktops again - new desktops will automatically be started on the remaining (enabled) VirtualBox hosts (assuming that more than one VirtualBox host is configured in your setup).
5. Download the updated VirtualBox installer from the [Sun VDI 3.0 download page|http://www.sun.com/software/vdi/get.jsp] and extract the archive in a temporary location.
6. Un-install the previous VirtualBox version by triggering
# vbox_2.0/vbox-install -u7. Install the new VirtualBox version by executing
# vbox_2.0/vbox-install8. If the installation fails due to an issue with the VirtualBox kernel module, reboot the machine and repeat step 7 again.
The installation of the new VirtualBox version will change the SSL certificate of the web service. Thus you need to re-import the certificate in Sun VDI 3.0 to establish the communication again.
1. In the Sun VDI administration UI select the affected VirtualBox desktop provider.
2. Switch to the "Hosts" tab
3. Select the desired VirtualBox host and click on "Edit"
4. In the host wizard confirm the changed certificate and click on "Finish"
The last step is to enable the VirtualBox host again:
5. On the "Hosts" tab select the disabled VirtualBox host and click on "Enable"
At this point the Sun VDI 3.0 system will again balance desktops to the updated VirtualBox host. You can now update the next VirtualBox host in your setup.

Where to find previous Solaris 9 Recommend patch ?

Hi:
Is it possible to find the specific version of sun Solaris 9 Recommend patch? As I know, sun keep on upgrade the it on the WEB site. But I need to find out some old version.
Thanks.

I believe older patches are not deleted from the web site, so you can download any revision of the patch you need. Check out http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage

Unable to install Solaris 8 OE patches

I'm trying to install the Solaris 8 recommended patch cluster on my new Blade 150. I downloaded and unzipped the patch file, dropped into single user mode, and executed the install_cluster script.
After asking me if I was ready to continue to install (I pressed "y"), a message appeared that it was checked for available disk space, followed by the system prompt-- the script had terminated.
Looking at the raw script file I can see that it should have either told me there was insufficient space (don't think this is a problem) or continued. Instead all it does it silently quit. I'm stuck!

are there enough space on your system
df -kl output

SMC not getting suggested patch info from Update Manager in Solaris 10

Hi All,
why SMC not getting suggested patch info from Update Manager in Solaris 10??
Thank you in advance.

Hi All,
why SMC not getting suggested patch info from Update Manager in Solaris 10??
Thank you in advance.

Solaris 2.6 Patch cluster

Is there anyone out there knows where I can get the last Solaris 2.6 patch cluster? I know it's de-supported now but sadly some legacy applications are still out there and need to run on old software/hardware.
Many thanks in advance,
Jonathan

if you run a pstack against the core, I might
recognize the failure. Usually, logging is of no
use, as we don't log a crash. . .Thanks. I'll do that. It just generated a new core file.
>
I don't know of any problems with installing 4.15p7,
nor of installing later hotfixes on top of it, and
I've been supporting Messaging Server since 4.0 came
out. . . .
If you've had file permission issues since 4.05,
that's truly news to me, unless it was that pesky
problem with Admin Server, where it would change the
permissions of the logs when it went to roll them
over. I don't remember when we fixed that one, but
we did..We've had file permission issues with the patches since 4.0. When we'd upgrade some of the files would be owned by root and not exec'able by nobody. Some of the patches would fail when the patch process would try to bind to the directory (I don't know why). We've used NMS since the 3.x version. It has also been a long time since we tried to patch to app because our experience was bad. It was stable for a long time (once we disabled shared folders and resolved the nscd issue).

Solaris 8 x86 patch cluster installation

hi. i recently installed solaris 8 x86 on my intel p4 machine. i got through the installation fine but i am now running into problems with installing the 8x86 recommended patch cluster.
whenever i run the install_cluster script, it says every patch failed to install due to return code 1. i even tried manually installing the patches manually via patchadd...but i end up getting a message saying the patch directory is not valid.
i basically downloaded the 8x86 recommended patch cluster zip file on a windows 2k machine. i unzip the file and then burn the patches onto a cd. i then copy the patches from the cd onto my solaris machine and try to install the patches that way. so far...this doesn't work..and i dont know what im doing wrong.
does anyone know how to fix this problem? thx.

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.

Performace problem in oracle DB after Solaris 10 recommended patching

Dear All,
We are facing some performance problems in our oracle DB qerries and reports recently. We applied Solaris 10 recommended patchset on april 24th. Our monthly report generation acitivity is now running for last 3 days i.e may 11,12,13 and application team is complaining of degraded performance. I can see that the cpu usage on the server is about 100% during the report generation , but everything else is fine. Free memory is 15gb , all mountpoints are under 80% and there is no other hardware issue as well.
Now app team is suspecting that last month patching could be the cause of the problem, because till last month they were performing this activity without having a performance degradtion.
I just need to be sure that solaris 10 recommended patches are not causing this issue. Any of you ever faced such an issue after patch installation ?
The server is V490 with 8 cpu / 32gb RAM. Any hints will be appreciated ?
Thanks in Advance.
Edited by: 1005720 on May 13, 2013 9:58 PM

I did not archive the o/p of prstat but have o/p of top with me
195 processes: 175 sleeping, 13 running, 1 zombie, 6 on cpu
CPU states: 0.0% idle, 78.4% user, 21.6% kernel, 0.0% iowait, 0.0% swap
Memory: 32G phys mem, 16G free mem, 70G total swap, 70G free swap
PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
18964 oracle 39 41 0 6389M 5488M cpu/1 2:50 15.04% oracle
19638 oracle 26 59 0 6390M 5490M run 0:27 8.58% oracle
19648 oracle 36 31 0 6418M 5516M run 0:21 5.92% oracle
19023 oracle 34 30 0 6398M 5498M run 0:37 5.88% oracle
7229 oracle 38 30 0 6427M 5514M run 234:24 5.69% oracle
6912 oracle 45 31 0 6395M 5483M cpu/16 218:04 5.31% oracle
7216 oracle 28 31 0 6430M 5517M run 232:40 5.04% oracle
19644 oracle 35 40 0 6390M 5490M cpu/17 0:24 4.74% oracle
6897 oracle 112 30 0 6392M 5479M run 236:38 4.52% oracle
3813 oracle 106 31 0 6428M 5528M run 100:11 4.43% oracle
18970 oracle 234 31 0 6398M 5499M cpu/0 1:45 4.15% oracle
19749 oracle 1 32 0 6386M 5486M run 0:00 4.05% oracle
19646 oracle 23 31 0 6405M 5505M run 0:25 3.61% oracle
18972 oracle 11 32 0 6398M 5497M run 2:18 3.61% oracle
7220 oracle 258 32 0 6468M 5555M cpu/3 113:13 3.56% oracle
During the entire issue there was no %iowait.

Patch 10.1.2.2 for Solaris is avalialble ?

Dear Oracle,
When patch 10.1.2.2 for Solaris is available ?
Thanks,
Yorke

Sorry, I post missing platform.
I mean patch 10.1.2.2 for Linux not Solaris.

Sun Solaris SCTP Denial Patch 127127-11 (Unloading SCTP module Solaris 10

Similar Messages

Maybe you are looking for