Re: Fwd: Call For Assistance #4 - slapd won't die gracefully, multiple versions.
On Sat, Apr 17, 2004 at 07:23:44AM -0700, Kris Kennaway wrote: > On Sat, Apr 17, 2004 at 11:44:25AM +0100, Matthew Seaman wrote: > > > In the mean time, you need a work-around. I'm not sure if you can run > > FreeBSD 5.x in 32bit mode on an AMD64 box, but that might be a thing > > to try. > > You can...it runs just like a more expensive i386 box :-) Opteron isn't any more expensive than a 32-bit Intel Xeon i386 box :-) -- -- David ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fwd: Call For Assistance #4 - slapd won't die gracefully, multiple versions.
On Sat, Apr 17, 2004 at 11:44:25AM +0100, Matthew Seaman wrote: > In the mean time, you need a work-around. I'm not sure if you can run > FreeBSD 5.x in 32bit mode on an AMD64 box, but that might be a thing > to try. You can...it runs just like a more expensive i386 box :-) Kris pgp0.pgp Description: PGP signature
Re: Fwd: Call For Assistance #4 - slapd won't die gracefully, multiple versions.
Jason, On Sat, Apr 17, 2004 at 01:22:00AM -0400, Jason Lixfeld wrote: > I've been having this issue with openldap for over a month now and they > folks at openldap seem to think this may be a FreeBSD issue. Not sure > if it's a general FreeBSD issue or an AMD64 issue so it's going to > both. > > Can anyone have a look at this and tell me what they think? It looks to me as if you've discovered quite a tricky bug here. It's not clear from the symptoms you describe if the fault is in the OpenLDAP code, the code of any of the dependencies it links against -- although I think your testing of BDB vs LDBM has eliminated those as suspects -- or the underlying FreeBSD system libraries. Neither is it clear if the problem is a coding mistake in any of those projects, or perhaps a bug in the compiler. Now, I assume that egregious errors due to being on a 64bit rather than a 32bit platform are not likely to happen in the OpenLDAP code, since it runs on any number of 64bit platforms like solaris-sparc. Subtle errors are a different matter. AMD64 is now a tier-1 platform on FreeBSD, which means it's been through a lot of testing to prove it's stability and correct operation, but that status is new with 5.x, so there are undoubtedly plenty of bugs still there to fix. 5.x is also using gcc-3.3.x as the system compiler, again in a large part for the ability to support the new tier-1 platforms. In other words it's pretty hard to even predict which of those areas is most likely to be the cause of the problem. As Kris said, running the program under a debugger -- in the hands of an expert programmer -- will be the best route towards dignosing the problem and finding a cure. If you're not capable of doing that sort of thing yourself, finding such a person will be your best route to a proper fix. If you need the LDAP server for business purposes, then offering payment would not be out of order. In the mean time, you need a work-around. I'm not sure if you can run FreeBSD 5.x in 32bit mode on an AMD64 box, but that might be a thing to try. Compiling the software with different versions of gcc (there are several available in ports) and with different optimization levels is worth a go. Failing that, probably the best thing would be to find a spare IA32 machine and use that for your server temporarily. or even (horrors!) try a different OS on your AMD64 box. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Fwd: Call For Assistance #4 - slapd won't die gracefully, multiple versions.
On Sat, Apr 17, 2004 at 01:22:00AM -0400, Jason Lixfeld wrote: > I've been having this issue with openldap for over a month now and they > folks at openldap seem to think this may be a FreeBSD issue. Not sure > if it's a general FreeBSD issue or an AMD64 issue so it's going to > both. > > Can anyone have a look at this and tell me what they think? You may have to do some debugging on your own, e.g. with gdb, to try and isolate the problem. Kris pgp0.pgp Description: PGP signature
Fwd: Call For Assistance #4 - slapd won't die gracefully, multiple versions.
I've been having this issue with openldap for over a month now and they folks at openldap seem to think this may be a FreeBSD issue. Not sure if it's a general FreeBSD issue or an AMD64 issue so it's going to both. Can anyone have a look at this and tell me what they think? Begin forwarded message: From: Jason Lixfeld <[EMAIL PROTECTED]> Date: April 17, 2004 12:38:44 AM EDT To: [EMAIL PROTECTED] Subject: Call For Assistance #4 - slapd won't die gracefully, multiple versions. My machine is AMD64. I'm running 5.2.1-RELEASE-p1. I've tried 2.1.29, 2.1.30, 2.2.7, 2.2.8 and 2.2.10 all from FreeBSD ports. no special make options, just plain make. No modifications to the config files, all plain vanilla out-of-the-box configs. I've tried with BDB and LDBM. Same issue with both types of databases. All openldap server versions i have tried exhibit the same problem (this output is from 2.1.29. Output is identicle on all versions, with the exception of the Berkeley DB version in the -d 256 output): If I start slapd and kill it without issuing a transaction to the server, slapd will die gracefully, no problem: su-2.05b# /etc/rc.d/slapd start ps: kvm_getprocs: No such process Starting slapd. su-2.05b# ps xa|grep slap 92971 ?? Ss 0:00.01 /usr/local/libexec/slapd -h ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap://0.0.0.0/ -u ldap -g ldap su-2.05b# /etc/rc.d/slapd stop Stopping slapd. Waiting for PIDS: 92971. su-2.05b# ps xa|grep slapd su-2.05b# If I start slapd and issue a transaction to the server, slapd will NOT die gracefully. I need to kill -9 it which will do bad things to the database. kill -INT will not work either: su-2.05b# /usr/local/libexec/slapd -d 256 bdb_initialize: Sleepycat Software: Berkeley DB 4.1.25: (December 19, 2002) bdb_db_init: Initializing BDB database slapd starting conn=0 fd=12 ACCEPT from IP=127.0.0.1:48071 (IP=0.0.0.0:389) conn=0 op=0 BIND dn="" method=128 conn=0 op=0 RESULT tag=97 err=0 text= conn=0 op=1 SRCH base="" scope=0 filter="(objectClass=*)" conn=0 op=1 SRCH attr=namingContexts conn=0 op=1 RESULT tag=101 err=0 text= conn=0 op=2 UNBIND conn=0 fd=12 closed ^Cslapd shutdown: waiting for 0 threads to terminate ^C^C^C^C^C The transaction I performed was the one from the Quickstart guide here: http://www.openldap.org/doc/admin22/quickstart.html su-2.05b# ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts # extended LDIF # # LDAPv3 # base <> with scope base # filter: (objectclass=*) # requesting: namingContexts # # dn: namingContexts: dc=my-domain,dc=com # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 su-2.05b# I've been struggling with this since my first post regarding this issue on March 7th and I still haven't figured it out. I'm asking anyone who may have some experience with OpenLDAP to PLEASE help me sort this out. This has really got me by the balls... Thanks in advance. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
