[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#7545) Problem with v2.4.30

Carl.Swenson@dodiis.mil wrote:
> 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.

Well... Oracle now owns your hardware manufacturer and the software in 
question. They'd be the obvious place to ask for help.

Frankly I'm surprised that a military site on a classified network is allowed 
to install freeware binaries from any internet site. You have no idea how 
those binaries were built, and certainly no recourse if they fail in any way 
or happen to have trojans/malware embedded within.

My first step would be to compile current source code. If the behavior still 
exists on current code, then start debugging/diagnosing. BDB 4.7.25 is quite 
old, as Quanah already pointed out. We've never seen any other cases reported 
like this, but it's always possible for a mixture of old binaries and new 
hardware to go bad. For all you know it's an instruction set incompatibility 
and recompiling BDB for your T4 will make it go away.

> Carl
> -----Original Message-----
> From: Quanah Gibson-Mount [mailto:quanah@zimbra.com]
> Sent: Wednesday, March 20, 2013 2:20 PM
> To: Swenson_CNTR, Carl E.; openldap-its@openldap.org
> Subject: RE: (ITS#7545) Problem with v2.4.30
> --On Tuesday, March 19, 2013 8:57 PM +0000 "Swenson_CNTR, Carl E."
> <Carl.Swenson@dodiis.mil> 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

   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/