| Summary | Turba LDAP driver causing empty binds |
| Queue | Turba |
| Queue Version | 2.2.1 |
| Type | Bug |
| State | Assigned |
| Priority | 2. Medium |
| Owners | Horde Developers (at) |
| Requester | webadmin (at) ualberta (dot) ca |
| Created | 09/11/2008 (6089 days ago) |
| Due | |
| Updated | 09/12/2008 (6088 days ago) |
| Assigned | 09/12/2008 (6088 days ago) |
| Resolved | |
| Milestone | |
| Patch | No |
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Turba LDAP driver causing empty binds
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
book source is instantiated with a Turba_Driver object. Basically to
do some permission checks on the driver.
But, when we call the driver factory, some initialization method is
called in the driver, and in the case of an LDAP driver, this method
is connecting to the server. The connections to the server are in the
form of empty bind requests:
Sep 7 18:27:48 ldapcluster4 slapd[30038]: conn=11033182 fd=42 ACCEPT
from IP=xxx.xxx.xxx.xxx:42243 (IP=0.0.0.0:389)
Sep 7 18:27:48 ldapcluster4 slapd[30038]: conn=11033182 op=0 BIND
dn="" method=128
Sep 7 18:27:48 ldapcluster4 slapd[30038]: conn=11033182 op=0 RESULT
tag=97 err=0 text=
Sep 7 18:27:49 ldapcluster4 slapd[30038]: conn=11033182 op=1 UNBIND
Sep 7 18:27:49 ldapcluster4 slapd[30038]: conn=11033182 fd=42 closed
These empty binds happen all over the place, causing large numbers of
requests per session. On a large installation it can result in half a
million LDAP binds per day.
A temporary fix for this problem is to comment out the turba_menu
section in /horde/config/registry.php.