slapd has random connection failures related to "do_extended: protocol version (2) too low"

Bug #1026570 reported by Ian Gordon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openldap (Ubuntu)
Triaged
High
Unassigned
Precise
New
Undecided
Unassigned
Quantal
Triaged
High
Unassigned

Bug Description

slapd seems to have random connection failures.

The log files show

Jul 18 14:01:57 simpson slapd[24409]: conn=1387 op=0 do_extended: protocol version (2) too low

for every connection failure.

The same command will succeed 99% of the time but will fail occasionally.

The command I used to test the problem was:

ldapsearch -x -H ldaps://host.domain.ac.uk/ -b dc=domain,dc=ac,dc=uk uid=ig

I found a reference to this problem at http://www.openldap.org/lists/openldap-bugs/201112/msg00019.html for ITS#7107

I have applied the specific 1 line GIT update to the package source and everything is now working properly.

It would be nice if the patch to fix ITS#7101 could be applied to the slapd package.

Thanks for any help you can be.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: slapd 2.4.28-1.1ubuntu4 [modified: usr/sbin/slapd]
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Thu Jul 19 12:10:38 2012
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: openldap
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.slapd: [modified]
mtime.conffile..etc.default.slapd: 2012-07-05T09:19:07

Revision history for this message
Ian Gordon (ian-gordon) wrote :
Revision history for this message
James Page (james-page) wrote :
Revision history for this message
James Page (james-page) wrote :
James Page (james-page)
Changed in openldap (Ubuntu):
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.