Quanah, Fine, I get it, you hate Solaris, BDB, etc...... But this is what I have to work with, and I still have an issue that I have never heard of, nor do I know what to even look for. Google searches turn up very little.
Is there an "OpenLDAP forum" where you can get help? I have tried removing the package labeled SMCdb47, and loaded SMCdb. The result is still the same. I know you don't like BDB, (you didn't mention what you do prefer) but in any case we are approved to use OpenLDAP w/ BDB. Normally we download all the supporting packages from sunfreeware.com, and if I remember correctly, it is defaulted to use BDB. So I have to use: Solaris 10 BDB 4.7.25.NC OpenSSL 1.0.1c OpenLDAP 2.4.30 What can I do. I have configured hundreds of servers using these packages, and their predecessors. We have never seen this behavior. Carl -----Original Message----- From: Quanah Gibson-Mount [mailto:[email protected]] Sent: Wednesday, March 20, 2013 2:20 PM To: Swenson_CNTR, Carl E.; [email protected] Subject: RE: (ITS#7545) Problem with v2.4.30 --On Tuesday, March 19, 2013 8:57 PM +0000 "Swenson_CNTR, Carl E." <[email protected]> wrote: > Quanah, > > Thank you for the reply. > > I double checked my versions on some of my systems just to be sure. > One inconsistency I noticed was in the name of the DB package > Possibly downloaded at 2 different times from sunfreeware.com. > > Example - > Sun Enterprise SPARC T5220 (everything works on this system) pkginfo > -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c > pkginfo -l SMCdb - version 4.7.25.NC > > Sun Enterprise SPARC T4-1 (the logs go crazy on this system) pkginfo > -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c > pkginfo -l SMCdb47 - version 4.7.25.NC > > IDK how this would affect the system, but based on your suggestion > there is some difference in the package as the "pkginst" name on one > system is SMCdb, and SMCdb47 on the other while the version is exactly the > same. I have no idea. I abandoned Slowaris years ago... I abandoned using BDB with OpenLDAP last year. However, no one has reported any issues like this. It really appears to be a bug in BDB rather than OpenLDAP however. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
