Your message dated Sat, 19 Jul 2008 09:57:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Pkg-openldap-devel] Bug#491148: [Fwd: Bug#491148: 
Acknowledgement (upgrade fails, /etc/default/slapd is the solution)]
has caused the Debian Bug report #491148,
regarding upgrade fails, /etc/default/slapd is the solution
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
491148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491148
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: slapd
Version: 2.4.10-2
Severity: important



-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (650, 'testing'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages slapd depends on:
ii  adduser                  3.108           add and remove users and groups
ii  coreutils                6.10-6          The GNU core utilities
ii  debconf [debconf-2.0]    1.5.22          Debian configuration management sy
ii  libc6                    2.7-10          GNU C Library: Shared libraries
ii  libdb4.2                 4.2.52+dfsg-4   Berkeley v4.2 Database Libraries [
ii  libgnutls26              2.4.1-1         the GNU TLS library - runtime libr
ii  libldap-2.4-2            2.4.10-2        OpenLDAP libraries
ii  libltdl3                 1.5.26-4        A system independent dlopen wrappe
ii  libperl5.10              5.10.0-11       Shared Perl library
ii  libsasl2-2               2.1.22.dfsg1-21 Cyrus SASL - authentication abstra
ii  libslp1                  1.2.1-7.3       OpenSLP libraries
ii  libwrap0                 7.6.q-15        Wietse Venema's TCP wrappers libra
ii  perl [libmime-base64-per 5.10.0-11       Larry Wall's Practical Extraction 
ii  psmisc                   22.6-1          Utilities that use the proc filesy
ii  unixodbc                 2.2.11-16       ODBC tools libraries

Versions of packages slapd recommends:
ii  libsasl2-modules         2.1.22.dfsg1-21 Cyrus SASL - pluggable authenticat

-- debconf information:
  slapd/internal/adminpw: (password omitted)
* slapd/password1: (password omitted)
* slapd/password2: (password omitted)
  slapd/password_mismatch:
  slapd/tlsciphersuite:
  slapd/invalid_config: true
  shared/organization: test.domain.com
  slapd/upgrade_slapcat_failure:
  slapd/slurpd_obsolete:
  slapd/backend: HDB
  slapd/dump_database: when needed
  slapd/allow_ldap_v2: false
  slapd/no_configuration: false
  slapd/migrate_ldbm_to_bdb: false
  slapd/move_old_database: true
  slapd/suffix_change: false
  slapd/dump_database_destdir: /var/backups/slapd-VERSION
  slapd/purge_database: false
  slapd/domain: test.domain.com


In replsync configuration upgrading slapd will fail.
there are problems locating pid id and/or locating slapd.conf

upgrade contineus after setting in /etc/default/slapd
user and group to openldap
pid to /var/run/slapd/slapd.pid
conf to /etc/ldap/slapd.conf

without these 4 setting upgrade wil always fail.
same problem in Etch and same fix is used.

this is the config used in slapd.conf

#######################################################################
# Global Directives:
# Features to permit
allow bind_v2

# Schema and objectClass definitions
include         /etc/ldap/schema/core.schema
include         /etc/ldap/schema/cosine.schema
include         /etc/ldap/schema/nis.schema
include         /etc/ldap/schema/inetorgperson.schema
include         /etc/ldap/schema/samba.schema
include         /etc/ldap/schema/qmail.schema
include         /etc/ldap/schema/zarafa.schema

schemacheck     on

modulepath      /usr/lib/ldap
moduleload      back_bdb
moduleload      syncprov
moduleload      accesslog

pidfile         /var/run/slapd/slapd.pid
argsfile        /var/run/slapd/slapd.args

#The <hash> to use for userPassword generation.  One
#of   {SSHA},   {SHA},   {SMD5},   {MD5},   {CRYPT},
#KERBEROS}, {SASL}, and  {UNIX}.   The  default  is {SSHA}.
password-hash   {MD5}

# timeout (in seconds) for dead connections
#timeout         60

loglevel        0
#loglevel        256
#loglevel       65535

#Server and CA Certificates
TLSCipherSuite  HIGH:MEDIUM:+SSLv2
TLSCACertificateFile    /etc/ldap/ssl/certs/ca.pem
TLSCertificateKeyFile   /etc/ldap/ssl/ldap.key
TLSCertificateFile      /etc/ldap/ssl/ldap.pem
TLSVerifyClient allow

# Each client that will access the OpenLDAP server using ldaps://
# needs to have a copy of cacert.pem. The ldap.conf file must
# point to the certificate:
#TLS_CACERT             /etc/ldap/ssl/certs/ca.pem


# The maximum number of entries that is returned for a search operation
#default: sizelimit      500
sizelimit       -1

# The tool-threads parameter sets the actual amount of cpu's that is used
# for indexing.
tool-threads    1

#######################################################################
# Specific Directives for database #1, of type bdb:
# Database specific directives apply to this databasse until another
# 'database' directive occurs
database        bdb

# For the Debian package we use 2MB as default but be sure to update this
# value if you have plenty of RAM
dbconfig        set_cachesize 0 2097152 0

# Sven Hartge reported that he had to set this value incredibly high
# to get slapd running at all. See http://bugs.debian.org/303057
# for more information.

# Number of objects that can be locked at the same time.
dbconfig        set_lk_max_objects 1500
# Number of locks (both requested and granted)
dbconfig        set_lk_max_locks 1500
# Number of lockers
dbconfig        set_lk_max_lockers 1500

suffix          "dc=test,dc=domain,dc=com"
rootdn          "cn=admin,dc=test,dc=domain,dc=com"
rootpw          {SSHA}REMOVED

directory       "/var/lib/ldap"
checkpoint      512 60
lastmod         on

overlay         syncprov
syncprov-checkpoint 100 10
syncprov-sessionlog 100

access  REMOVED

## for indexing replsync items
index entryCSN                  eq
index entryUUID                 eq

# Indices to maintain
index objectClass             eq
index cn                      pres,sub,eq
index sn                      pres,sub,eq
index uid                     pres,sub,eq
index displayName             pres,sub,eq
index uidNumber               eq
index gidNumber               eq
index memberUID               eq
index sambaSID                eq
index sambaPrimaryGroupSID    eq
index sambaDomainName         eq
index default                 sub



--- End Message ---
--- Begin Message ---
On Fri, Jul 18, 2008 at 08:31:10AM +0200, Louis van Belle wrote:
> as requested, more info.
> This is reproducable over and over again. ( with my config )

> during the upgrade the upgrade script needs to stop the slapd server.
> This fails, the upgrade script does not stop slapd correctie with my config.
> This is why i reported this bug. the happens with the config used.
> if this happens, i have 2 options. 1 stop slapd myself and do apt-get
> upgrade again, or enter the info in /etc/default/slapd.

> as i say you can reproduce this over and over again.
> this is the part you of dpkg.log

<snip>

> Log started: 2008-07-11  10:37:45
> Selecting previously deselected package slapd.
> (Reading database ... 46670 files and directories currently installed.)
> Unpacking slapd (from .../slapd_2.4.9-1_amd64.deb) ...
> Processing triggers for man-db ...
> Setting up slapd (2.4.9-1) ...

This shows that slapd is *not* being upgraded; this shows a new install of
the package.  If you already have something bound to the ldap port before
slapd is installed, that's not the responsibility of the newly-installed
package to try to correct.  Whatever failure there was happened on removal
of the old version of the package (which you don't show in your log), or as
a result of something you've done by hand outside of the package structure.

I suspect that it's the latter, since your upgrade log also shows a large
number of conffile conflicts:

> Configuration file `/etc/init.d/slapd'
> Configuration file `/etc/default/slapd'
> Configuration file `/etc/ldap/schema/cosine.schema'
> Configuration file `/etc/ldap/schema/nis.schema'
> Configuration file `/etc/ldap/schema/inetorgperson.schema'
> Configuration file `/etc/ldap/schema/ppolicy.schema'
> Configuration file `/etc/ldap/schema/openldap.ldif'
> Configuration file `/etc/ldap/schema/README'
> Configuration file `/etc/ldap/schema/java.schema'
> Configuration file `/etc/ldap/schema/core.ldif'
> Configuration file `/etc/ldap/schema/corba.schema'
> Configuration file `/etc/ldap/schema/misc.schema'
> Configuration file `/etc/ldap/schema/dyngroup.schema'
> Configuration file `/etc/ldap/schema/openldap.schema'
> Configuration file `/etc/ldap/schema/core.schema'

Between the large number of customized conffiles, and the fact that the init
script has always worked as intended for all other users (consistently, for
years, and across multiple stable releases), I don't think there's a package
bug here.  There might still be one, but you would need to show a full log
that would explain why slapd wasn't stopped when the old package version was
/removed/.

> You see now log ended, upgraded stopped.
> now i stopped slapd by myself.
> and dit upgrade again.
> Log started: 2008-07-11  10:38:39
> (Reading database ... 46850 files and directories currently installed.)
> Removing slapd ...
> Stopping OpenLDAP: slapd.
> Purging configuration files for slapd ...
> Removing slapd configuration... done
> dpkg - warning: while removing slapd, directory `/usr/lib/ldap' not empty
> so not removed.
> dpkg - warning: while removing slapd, directory `/usr/share/slapd' not
> empty so not removed.
> Processing triggers for man-db ...
> Log ended: 2008-07-11  10:38:43

That's not an upgrade either, that's a removal.  And it shows no errors at
all.  So I don't believe that the problem was what you say it is.

If you can show me that, when using standard /etc/init.d/slapd and
/etc/default/slapd files, calling "/etc/init.d/slapd stop" leaves a daemon
running, then we can investigate further.  Until then, there's no evidence
of a bug here, so I'm closing this report.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
[EMAIL PROTECTED]                                     [EMAIL PROTECTED]


--- End Message ---

Reply via email to