Re: [Samba] Possible bug with Samba and LDAP
Andrew Bartlett <[EMAIL PROTECTED]> on Thursday, November 04, 2004 at 11:31 PM -0800 wrote: >On Fri, 2004-11-05 at 11:49, Jeremy Allison wrote: >> On Thu, Nov 04, 2004 at 04:40:07PM -0800, Erik Horn wrote: >> > >> > The ldap client libraries are from openldap-2.1.29. >> >> I would use strace to find out who is resetting that signal >> handler. It isn't smbd. > > >nss_ldap? That was the suspect in one of these cases before. > > >Andrew Bartlett > After doing some doing some searching around, I believe that it is nss_ldap that is causing the problem. I found some references to a bug in signal handling that affected nss_ldap versions <200 and 213-219. We are running 217 (the current version for FC2). Before we upgraded, we were running version 202 therefore didn't see the problem. I am building a test system so that I can verify that the newer nss_ldap library fixes the problem. If it does, I'll file a bug report with the fedora project so they can update the distribution. References: PADL bug #173: http://bugzilla.padl.com/show_bug.cgi?id=173 Redhat bug #84344: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=84344 Thanks, Erik -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Possible bug with Samba and LDAP
On Fri, 2004-11-05 at 11:49, Jeremy Allison wrote: > On Thu, Nov 04, 2004 at 04:40:07PM -0800, Erik Horn wrote: > > > > The ldap client libraries are from openldap-2.1.29. > > I would use strace to find out who is resetting that signal > handler. It isn't smbd. nss_ldap? That was the suspect in one of these cases before. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Authentication Developer, Samba Teamhttp://samba.org Student Network Administrator, Hawker College [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Possible bug with Samba and LDAP
On Thu, Nov 04, 2004 at 04:40:07PM -0800, Erik Horn wrote: > > The ldap client libraries are from openldap-2.1.29. I would use strace to find out who is resetting that signal handler. It isn't smbd. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Possible bug with Samba and LDAP
Jeremy Allison <[EMAIL PROTECTED]> on Thursday, November 04, 2004 at 4:25 PM -0800 wrote: >On Thu, Nov 04, 2004 at 04:04:44PM -0800, Erik Horn wrote: >> Configuration Overview: >> >> OS: Fedora Core 2 >> Samba: 3.0.7-2 (as distributed) configured as a PDC using ldap for >> authentication info >> LDAP:openldap 2.1.29 >> >> >> Ever since we upgraded to Samba 3 we've been having problems with users >> randomly getting disconnected from our server. I have managed to trace >the >> problem down to our LDAP server. Our LDAP server is configured with >> idletimeout 60. This closes any ldap connections that are idle for more >> than a minute, which keeps the number of open connections to the ldap >> server down to a reasonable level (around 100) rather than one per >active >> session on the server (1000+). >> >> After Samba gets disconnected from the LDAP server, then tries to access >> it, it receives a SIGPIPE and dies, disconnecting the user. Ideally, >Samba >> should re-attach to the LDAP server and continue working without any >> problems. >> >> This same LDAP server option was used for years with Samba 2.x without >any >> problems. > > >What client libraries are you using ? Samba is configured to ignore >sigpipe. >Something dynamically linked into your smbd binary is re-enabling it. > > >Jeremy. The ldap client libraries are from openldap-2.1.29. Erik -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Possible bug with Samba and LDAP
On Thu, Nov 04, 2004 at 04:04:44PM -0800, Erik Horn wrote: > Configuration Overview: > > OS: Fedora Core 2 > Samba:3.0.7-2 (as distributed) configured as a PDC using ldap for > authentication info > LDAP: openldap 2.1.29 > > > Ever since we upgraded to Samba 3 we've been having problems with users > randomly getting disconnected from our server. I have managed to trace the > problem down to our LDAP server. Our LDAP server is configured with > idletimeout 60. This closes any ldap connections that are idle for more > than a minute, which keeps the number of open connections to the ldap > server down to a reasonable level (around 100) rather than one per active > session on the server (1000+). > > After Samba gets disconnected from the LDAP server, then tries to access > it, it receives a SIGPIPE and dies, disconnecting the user. Ideally, Samba > should re-attach to the LDAP server and continue working without any > problems. > > This same LDAP server option was used for years with Samba 2.x without any > problems. What client libraries are you using ? Samba is configured to ignore sigpipe. Something dynamically linked into your smbd binary is re-enabling it. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Possible bug with Samba and LDAP
Configuration Overview: OS: Fedora Core 2 Samba: 3.0.7-2 (as distributed) configured as a PDC using ldap for authentication info LDAP: openldap 2.1.29 Ever since we upgraded to Samba 3 we've been having problems with users randomly getting disconnected from our server. I have managed to trace the problem down to our LDAP server. Our LDAP server is configured with idletimeout 60. This closes any ldap connections that are idle for more than a minute, which keeps the number of open connections to the ldap server down to a reasonable level (around 100) rather than one per active session on the server (1000+). After Samba gets disconnected from the LDAP server, then tries to access it, it receives a SIGPIPE and dies, disconnecting the user. Ideally, Samba should re-attach to the LDAP server and continue working without any problems. This same LDAP server option was used for years with Samba 2.x without any problems. For now, I'm going to reconfigure my LDAP server to work around the problem. Does anybody else have any ideas that might help? Thanks, Erik -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
