How to know if you are running a DS 5.2 Patch5 timebomb affected system and how to fix it

Am I running a DS 5.2 Patch5 time-bombed instance (Bug 6587775)?

If you installed/upgraded your instance 5.2 Patch5 directory server before August 1st, 2007 and you have never applied any hotfixes to it as the server has been working on nicely since it was first installed/upgraded, then you are most likely running a DS 5.2 Patch5 time-bombed instance, but pleaaaase, don't panic yet: the following steps will allow you to get rid of it without even knowing about it... You can in the meantime keep your DS instance up and running safely as long as you DO NOT STOP it. If you do, then you will not be able to start it again until you will get a hotfix for the bug.

How can I confirm the presence of Bug 6587775 in my system?

Here are a couple of easy ways to know if you are running a DS 5.2 Patch5 time-bombed instance, none of them will affect your already running instance, so you can safely execute any of both:

  • Running ns-slapd and verifying the build number (5.2_Patch_5 B2007.093.0058 indicates the bug):
./ns-slapd  -v
Sun Microsystems, Inc.
Sun Java(TM) System Directory Server/5.2_Patch_5 B2007.093.0058

  • Hitting the bug as follows (this should produce a "beta software has expired" message):
./ns-slapd -D ../../../slapd-incus -V
[01/Aug/2007:18:08:37 +0200] - DEBUG  - conn=-1 op=-1 msgId=-1 -  ERROR: \*\* This beta software has expired \*\*


Which implications does this bug have for my directory services?

None, as long as you DO NOT STOP your instances. If you do, then you will not be able to start them again until you will get a hotfix for the bug. Also, the offline import/exports and backup/restores will not work due to this bug, so it is highly recommended to use the online import/export procedures (db2ldif.pl, ldif2db.pl, etc) until a fix for this bug will be in place.

How can I fix the bug?

The easiest and safest way is to contact Sun Support for a delivery of a hotfix for your particular OS.  Please make sure you specify the type of distribution you have installed (Zip or Native Package).

Once you will have that hotfix delivered (that should happen really fast), you will need to install it following Sun Support instructions which are different depending whether you installed a Native Package or a Zip distribution of the product. In any case, the installation of the hotfix is pretty simple, as such hotfix will only affect the ns-slapd binary, no other library in your system will be touched.


Comments:

What does this mean for people that have not installed patch 5 yet?
As long as its installed after Aug. 1st (past already) I am OK?
Is there going to be another release of patch 5 that is not affected by the bug?

TIA

Posted by guest on August 13, 2007 at 04:12 AM PDT #

Yes, this problem apply both to people which has not installed patch5 yet and to people who installed it before August 1st. Nobody can avoid this bug in 5.2patch5 without a binary hotfix.

Yes, 5.2Patch6 will fix this issue completely.

Posted by Marcos Ares on September 10, 2007 at 08:07 PM PDT #

How can I get this hotfix if I dont have a sun support contract? I've looked around for the patch, but I can't find it - and I am being affected by this right now :(

Thanks!

Posted by Jim K on September 11, 2007 at 10:51 PM PDT #

Post a Comment:
Comments are closed for this entry.
About

marcos

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today