Your message dated Wed, 5 Aug 2009 12:33:01 +0100
with message-id <[email protected]>
and subject line Re: slapd upgrade 2.3.30-2 to 2.3.30-5 frozen
has caused the Debian Bug report #417405,
regarding slapd upgrade 2.3.30-2 to 2.3.30-5 frozen
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.)


-- 
417405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417405
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: slapd
Version: 2.3.30-2
Severity: normal

My update from 2.3.30-2 to 2.3.30-5 of slapd appears to be frozen; it's
been running for about 45 minutes now, and a "slapcat" process has been
the top process for the entire time:

  20393 root      25   0 11824 3552  10m R 69.1  0.4  17:33.22 slapcat

I'm not sure what it's in the process of doing, or whether it is safe to
kill it.  I haven't killed off the upgrade if you need me to look at
anything that it's doing.

This is what's on the console as it's doing the upgrade:

Unpacking replacement libiodbc2 ...
Preparing to replace slapd 2.3.30-2 (using .../slapd_2.3.30-5_i386.deb)
...
Stopping OpenLDAP: slapd.
start-stop-daemon: warning: failed to kill 11841: No such process
  Dumping to /var/backups/slapd-2.3.30-2: 
  - directory dc=finkdeveloper,dc=net... bdb_db_open: unclean shutdown 
detected; attempting recovery.
bdb_db_open: Warning - No DB_CONFIG file found in directory /var/lib/ldap: (2)
Expect poor performance for suffix dc=finkdeveloper,dc=net.
bdb_db_open: Recovery skipped in read-only mode. Run manual recovery if errors 
are encountered.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages slapd depends on:
ii  adduser                   3.63           Add and remove users and groups
ii  coreutils                 5.97-5.3       The GNU core utilities
ii  debconf [debconf-2.0]     1.4.30.13      Debian configuration management sy
ii  libc6                     2.3.6.ds1-13   GNU C Library: Shared libraries
ii  libdb4.2                  4.2.52-18      Berkeley v4.2 Database Libraries [
ii  libiodbc2                 3.52.4-3       iODBC Driver Manager
ii  libldap-2.3-0             2.3.30-2       OpenLDAP libraries
ii  libltdl3                  1.5.6-6        A system independent dlopen wrappe
ii  libperl5.8                5.8.8-6.1      Shared Perl library
di  libsasl2-2                2.1.22.dfsg1-8 Authentication abstraction library
ii  libslp1                   1.0.11a-2      OpenSLP libraries
ii  libssl0.9.8               0.9.8c-4       SSL shared libraries
ii  libwrap0                  7.6.dbs-8      Wietse Venema's TCP wrappers libra
ii  perl [libmime-base64-perl 5.8.8-6.1      Larry Wall's Practical Extraction 
ii  psmisc                    21.5-1         Utilities that use the proc filesy

-- debconf information:
  slapd/fix_directory: true
* shared/organization: Fink Developer Network
  slapd/upgrade_slapcat_failure:
  slapd/backend: BDB
* slapd/allow_ldap_v2: false
  slapd/no_configuration: false
  slapd/move_old_database: true
  slapd/suffix_change: false
  slapd/slave_databases_require_updateref:
* slapd/dump_database_destdir: /var/backups/slapd-VERSION
  slapd/autoconf_modules: true
* slapd/domain: finkdeveloper.net
  slapd/password_mismatch:
  slapd/invalid_config: true
  slapd/upgrade_slapadd_failure:
* slapd/dump_database: always
  slapd/migrate_ldbm_to_bdb: false
  slapd/purge_database: false


--- End Message ---
--- Begin Message ---
This bug report is specific to an upgrade from a pre-etch version of slapd,
and the requested information needed to debug this problem has not been
forthcoming.  I'm therefore closing this report as no further action is
possible and the bug has not been reported in current releases.

-- 
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