openldap-bugs

openldap-bugs@openldap.org

20960 discussions

Re: (ITS#8669) Slapd service becomes unresponsive intermittently
by michael＠stroeder.com 07 Jun '17

07 Jun '17

quanah(a)symas.com wrote: >> Is it possible we have the idletimeout set too high and it should be >> lowered? I=C2=B9m wondering if there is some sweet-spot value for this >> particular setting. > > I generally leave it unset unless one is encountering an issue of running > out of connections. Generally, it would be fairly strange for idletimeout > to affect things this way at all. I generally recommend to set idletimeout even somewhat tight in case you don't have a strictly defined set of clients. Because a client application which does not use its LDAP connection for ~5 min. is most times simply not closing connections. And running out of file handles can affect all file creation on your system (e.g. creating BDB's transaction log files). Only the original poster can find out with monitoring. One can find out stale connections via back-monitor in sub-tree cn=Connections,cn=Monitor. IITC attribute 'monitorConnectionActivityTime' contains last client access time on this connection. (Ummh, I have to add this to my own monitoring script...) And of course normal system monitoring of file handles would be also helpful. Ciao, Michael. (Keep repeating this mantra: monitoring, monitoring, monitoring, monitoring…)

1 0

Re: (ITS#8669) Slapd service becomes unresponsive intermittently
by quanah＠symas.com 07 Jun '17

07 Jun '17

--On Wednesday, June 07, 2017 7:07 AM -0600 Joaquin Estrada=20 <jmestrada69(a)gmail.com> wrote: > Quanah, > > We are running the Berkley DB back-end, =C2=B3back-bdb=C2=B2 in the = slapd.conf > file. > > Our server vendor did the upgrade to version 2.4.39 last year in April. = In > asking them about upgrading to a newer version, as a potential fix, I was > told the last version in the RHEL repository that they can upgrade to is > 2.4.40. I=C2=B9m not certain that our vendor will support our choice to > upgrade to a newer version than what RHEL provides them in the > repository, but if it will fix our problem, I=C2=B9ll have to push the > envelope on that matter. > > Were there any known fragmentation issues with back-bdb in the 2.4.39 > version that could also be causing these pauses? No, back-bdb is not remotely the same as back-mdb. However, I've no idea=20 what options RedHat compiles their BDB library with and there were specific = options that had an effect on OpenLDAP. Generally, I would note that the=20 back-bdb backend and back-hdb backends are deprecated at this point. > Is it possible we have the idletimeout set too high and it should be > lowered? I=C2=B9m wondering if there is some sweet-spot value for this > particular setting. I generally leave it unset unless one is encountering an issue of running=20 out of connections. Generally, it would be fairly strange for idletimeout=20 to affect things this way at all. It simply drops idle connections based=20 off of the timer. Disabling rate throttling in rsyslogd is a good idea,=20 but may be unrelated as well. We've also seen cases with RHEL7 where Redhat = has set things up so that journald also gets all the syslog messages, which = causes severe performance degredation. You could spend some time seeing if you can isolate an exact cause. For=20 example, set loglevel to 0 and see if you still encounter the issue. If=20 you do, it is unrelated to syslog activity. Another test would be to set idletimeout to 0. If you still encounter the=20 issue, it is unrelated to idle connections being dropped. etc. As Michael noted, Redhat builds are somewhat questionable as they make=20 various changes to the code base that the OpenLDAP project have not been=20 reviewed. Your issues may or may not be related to such a change, it's=20 generally impossible to know. Hope that helps. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: ITS#8504 fix breaks Solaris builds
by quanah＠symas.com 07 Jun '17

07 Jun '17

--On Wednesday, June 07, 2017 3:35 PM +0200 Hallvard Breien Furuseth <h.b.furuseth(a)usit.uio.no> wrote: > On 06. juni 2017 21:59, quanah(a)openldap.org wrote: >> /usr/include/signal.h:233:12: note: declared here >> extern int sigwait(sigset_t *); >> ^ > > POSIX says it has two arguments: > http://pubs.opengroup.org/onlinepubs/9699919799/functions/sigwait.html > Is there a two-argument version of sigwait in the Solaris headers > somewhere, > maybe enabled by #define POSIX_C_SOURCE 1 or something like that? It's insanely long.... /* * sigwait() prototype is defined here. */ #if defined(__EXTENSIONS__) || (!defined(_STRICT_STDC) && \ !defined(__XOPEN_OR_POSIX)) || (_POSIX_C_SOURCE - 0 >= 199506L) || \ defined(_POSIX_PTHREAD_SEMANTICS) #if defined(__STDC__) #if (_POSIX_C_SOURCE - 0 >= 199506L) || defined(_POSIX_PTHREAD_SEMANTICS) #ifdef __PRAGMA_REDEFINE_EXTNAME #pragma redefine_extname sigwait __posix_sigwait extern int sigwait(const sigset_t *_RESTRICT_KYWD, int *_RESTRICT_KYWD); #else /* __PRAGMA_REDEFINE_EXTNAME */ extern int __posix_sigwait(const sigset_t *_RESTRICT_KYWD, int *_RESTRICT_KYWD); #ifdef __lint #define sigwait __posix_sigwait #else /* !__lint */ static int sigwait(const sigset_t *_RESTRICT_KYWD __setp, int *_RESTRICT_KYWD __signo) { return (__posix_sigwait(__setp, __signo)); } #endif /* !__lint */ #endif /* __PRAGMA_REDEFINE_EXTNAME */ #else /* (_POSIX_C_SOURCE - 0 >= 199506L) || ... */ extern int sigwait(sigset_t *); #endif /* (_POSIX_C_SOURCE - 0 >= 199506L) || ... */ #else /* __STDC__ */ #if (_POSIX_C_SOURCE - 0 >= 199506L) || defined(_POSIX_PTHREAD_SEMANTICS) #ifdef __PRAGMA_REDEFINE_EXTNAME #pragma redefine_extname sigwait __posix_sigwait extern int sigwait(); #else /* __PRAGMA_REDEFINE_EXTNAME */ extern int __posix_sigwait(); #ifdef __lint #define sigwait __posix_sigwait #else /* !__lint */ static int sigwait(__setp, __signo) sigset_t *__setp; int *__signo; { return (__posix_sigwait(__setp, __signo)); } #endif /* !__lint */ #endif /* __PRAGMA_REDEFINE_EXTNAME */ #else /* (_POSIX_C_SOURCE - 0 >= 199506L) || ... */ extern int sigwait(); #endif /* (_POSIX_C_SOURCE - 0 >= 199506L) || ... */ #endif /* __STDC__ */ #endif /* defined(__EXTENSIONS__) || (!defined(_STRICT_STDC) ... */ -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8669) Slapd service becomes unresponsive intermittently
by jmestrada69＠gmail.com 07 Jun '17

07 Jun '17

Yes, I've reached out to our vendor about this. I am hoping we can sidestep t= he RHEL releases. Thanks for the info on this.=20 Sent from my iPhone > On Jun 7, 2017, at 6:16 AM, Michael Str=C3=B6der <michael(a)stroeder.com> wr= ote: >=20 > jmestrada69(a)gmail.com wrote: >> Our server vendor did the upgrade to version 2.4.39 last year in April. I= n >> asking them about upgrading to a newer version, as a potential fix, I was= >> told the last version in the RHEL repository that they can upgrade to is >> 2.4.40. >=20 > They seem to just recommend what seems to be the easiest choice for them a= nd not what > would be the recommended choice for *you*. RHEL packages are heavily patch= ed by Red Hat > and generally not recommended. The upstream developers cannot oversee what= 's the current > patch state of RHEL packages. >=20 > =3D> You should kick out your server vendor from doing the OpenLDAP suppor= t. >=20 > Ciao, Michael.

1 0

Re: ITS#8504 fix breaks Solaris builds
by h.b.furuseth＠usit.uio.no 07 Jun '17

07 Jun '17

On 06. juni 2017 21:59, quanah(a)openldap.org wrote: > /usr/include/signal.h:233:12: note: declared here > extern int sigwait(sigset_t *); > ^ POSIX says it has two arguments: http://pubs.opengroup.org/onlinepubs/9699919799/functions/sigwait.html Is there a two-argument version of sigwait in the Solaris headers somewhere, maybe enabled by #define POSIX_C_SOURCE 1 or something like that? -- Hallvard

1 0

Re: (ITS#8669) Slapd service becomes unresponsive intermittently
by michael＠stroeder.com 07 Jun '17

07 Jun '17

jmestrada69(a)gmail.com wrote: > Our server vendor did the upgrade to version 2.4.39 last year in April. In > asking them about upgrading to a newer version, as a potential fix, I was > told the last version in the RHEL repository that they can upgrade to is > 2.4.40. They seem to just recommend what seems to be the easiest choice for them and not what would be the recommended choice for *you*. RHEL packages are heavily patched by Red Hat and generally not recommended. The upstream developers cannot oversee what's the current patch state of RHEL packages. => You should kick out your server vendor from doing the OpenLDAP support. Ciao, Michael.

1 0

Re: (ITS#8669) Slapd service becomes unresponsive intermittently
by jmestrada69＠gmail.com 07 Jun '17

07 Jun '17

Quanah, We are running the Berkley DB back-end, =B3back-bdb=B2 in the slapd.conf file. Our server vendor did the upgrade to version 2.4.39 last year in April. In asking them about upgrading to a newer version, as a potential fix, I was told the last version in the RHEL repository that they can upgrade to is 2.4.40. I=B9m not certain that our vendor will support our choice to upgrade to a newer version than what RHEL provides them in the repository, but if it will fix our problem, I=B9ll have to push the envelope on that matter. Were there any known fragmentation issues with back-bdb in the 2.4.39 version that could also be causing these pauses? Initially, when we started having problems with the pausing, the server would go offline for about 15-20 minutes then recover itself. The developers had initially set the idletimeout to 8 minutes (480) and we also noted that rsyslogd was constantly logging entries about the slapd service, which stated that the the PID of the slapd service was losing messages to the log due to rate-limiting. Rate limiting was enabled by default for rsyslog so our vendor recommended to turn this off. At the same time, when they did this we scaled back the idletimeout period to 5 minutes (300). This seemed to aggravated the problem. With the original settings, we would encounter this =B3pause=B2 problem maybe once or twice in a 3 month period, and now after these changes were made we=B9re seeing this more frequently, although when it does pause it seems to only be for about 10 minutes, where it was pausing for 15-20 before. We currently have the logging level set to the recommended =B3256=B2, but we=B9re considering lowing the logging level also. Is it possible we have the idletimeout set too high and it should be lowered? I=B9m wondering if there is some sweet-spot value for this particular setting. The reason our developers had it set so high was because, in the past they used to run some really long reports. I=B9m pretty sure they do not run these any longer. I appreciate your feedback. Thanks On 6/6/17, 6:57 PM, "Quanah Gibson-Mount" <quanah(a)symas.com> wrote: >--On Tuesday, June 06, 2017 8:39 PM +0000 jmestrada69(a)gmail.com wrote: > >> Is there a known bug with this version that could be causing this? > >Hard to say. It is 3.5 years old and 6 releases behind. You don't state >which backend you're using, which may be relevant as well. There were >known fragmentation issues with back-mdb in that release, for example, >that=20 >could cause extensive pauses. Without knowing significantly more about >your system configuration, there's only a ton of speculation that can >ensue. > >You may want to see about using the builds from the LTB project >(<http://ltb-project.org/wiki/download#openldap>), or if you require >support for your deployment, Symas (my employer) offers packaged builds >and=20 >various support options. > >Regards, >Quanah > >-- > >Quanah Gibson-Mount >Product Architect >Symas Corporation >Packaged, certified, and supported LDAP solutions powered by OpenLDAP: ><http://www.symas.com> >

1 0

Re: (ITS#8671) Declare ldap_init_fd() in ldap.h to help external consumers
by abokovoy＠redhat.com 07 Jun '17

07 Jun '17

--ce5n3c4hsgyizewc Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Patch attached. -- / Alexander Bokovoy --ce5n3c4hsgyizewc Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="abokovoy-ldap_init_fd-move-ldap_init_fd-definition-to-ldap.h.patch" Content-Transfer-Encoding: quoted-printable =46rom 2c1f3afd8098b2a345a900effa1a2e5c3f9e3b08 Mon Sep 17 00:00:00 2001 =46rom: Alexander Bokovoy <abokovoy(a)redhat.com> Date: Mon, 5 Jun 2017 14:43:58 +0300 Subject: [PATCH] ldap_init_fd: move ldap_init_fd() definition to ldap.h While OpenLDAP team position is that all code in OpenLDAP source distribution can be used by users, most distributions do not ship ldap_pvt.h as part of openldap-devel (sub)package. Move ldap_init_fd() to ldap.h to facilitate external users who have a need to integrate OpenLDAP with their own event loop processing. --- doc/man/man3/ldap_open.3 | 5 +---- include/ldap.h | 8 ++++++++ include/ldap_pvt.h | 2 -- 3 files changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/man/man3/ldap_open.3 b/doc/man/man3/ldap_open.3 index 1d5e2b5..4f980f2 100644 --- a/doc/man/man3/ldap_open.3 +++ b/doc/man/man3/ldap_open.3 @@ -3,7 +3,7 @@ .\" Copyright 1998-2017 The OpenLDAP Foundation All Rights Reserved. .\" Copying restrictions apply. See COPYRIGHT/LICENSE. .SH NAME -ldap_init, ldap_initialize, ldap_open \- Initialize the LDAP library and o= pen a connection to an LDAP server +ldap_init, ldap_initialize, ldap_open, ldap_init_fd \- Initialize the LDAP= library and open a connection to an LDAP server .SH LIBRARY OpenLDAP LDAP (libldap, \-lldap) .SH SYNOPSIS @@ -45,9 +45,6 @@ LDAPURLDesc **url; void *params; .LP .ft B -#include <ldap_pvt.h> -.LP -.ft B int ldap_init_fd(fd, proto, uri, ldp) .ft ber_socket_t fd; diff --git a/include/ldap.h b/include/ldap.h index 588e906..dd0c118 100644 --- a/include/ldap.h +++ b/include/ldap.h @@ -1548,6 +1548,14 @@ LDAP_F( LDAP * ) ldap_dup LDAP_P(( LDAP *old )); =20 +/* open */ +LDAP_F (int) +ldap_init_fd LDAP_P(( + ber_socket_t fd, + int proto, + LDAP_CONST char *url, + LDAP **ldp )); + /* * in tls.c */ diff --git a/include/ldap_pvt.h b/include/ldap_pvt.h index f1d93ac..49f674c 100644 --- a/include/ldap_pvt.h +++ b/include/ldap_pvt.h @@ -344,8 +344,6 @@ ldap_get_message_ber LDAP_P(( /* open */ LDAP_F (int) ldap_open_internal_connection LDAP_P(( struct ldap **ldp, ber_socket_t *fdp )); -LDAP_F (int) ldap_init_fd LDAP_P(( - ber_socket_t fd, int proto, LDAP_CONST char *url, struct ldap **ldp )); =20 /* sasl.c */ LDAP_F (int) ldap_pvt_sasl_generic_install LDAP_P(( Sockbuf *sb, --=20 2.9.3 --ce5n3c4hsgyizewc--

1 0

(ITS#8671) Declare ldap_init_fd() in ldap.h to help external consumers
by abokovoy＠redhat.com 07 Jun '17

07 Jun '17

Full_Name: Alexander Bokovoy Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (88.115.170.217) As discussed on the openldap-devel@, Samba team would like to use ldap_init_fd() to allow Samba handle actual sockets. To do so we would like to see ldap_init_fd() declared in ldap.h instead of ldap_pvt.h. The latter is not shipped by most distributions at all. Proposed patch moves ldap_init_fd() declaration to ldap.h and changes references to it in the corresponding manual pages. You can do what you want with the proposed patch since it does not really contain any code I have written.

1 0

Re: (ITS#8669) Slapd service becomes unresponsive intermittently
by quanah＠symas.com 07 Jun '17

07 Jun '17

--On Tuesday, June 06, 2017 8:39 PM +0000 jmestrada69(a)gmail.com wrote: > Is there a known bug with this version that could be causing this? Hard to say. It is 3.5 years old and 6 releases behind. You don't state which backend you're using, which may be relevant as well. There were known fragmentation issues with back-mdb in that release, for example, that could cause extensive pauses. Without knowing significantly more about your system configuration, there's only a ton of speculation that can ensue. You may want to see about using the builds from the LTB project (<http://ltb-project.org/wiki/download#openldap>), or if you require support for your deployment, Symas (my employer) offers packaged builds and various support options. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs