Your message dated Wed, 7 Jun 2006 17:36:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Not a bug
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Subject: libnss-ldap: abort during useradd (ber_free_buf error)
Package: libnss-ldap
Version: 238-1.2
Severity: critical
Justification: breaks unrelated software
*** Please type your report below this line ***
I can't install nfs-common because the configuration script makes a call
to adduser that fails with the following error:
Setting up nfs-common (1.0.7-12) ...
Adding system user `statd' with uid 107...
Adding new user `statd' (107) with group `nogroup'.
useradd: /home/devel/openldap/openldap2-2.1.30/libraries/liblber/io.c:161:
ber_free_buf: Assertion
`((ber)->ber_opts.lbo_valid==0x2)' failed.
adduser: `/usr/sbin/useradd -d /var/lib/nfs -g nogroup -s /bin/false -u 107
statd' exited from
signal 6. Aborting.
dpkg: error processing nfs-common (--configure):
subprocess post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of nfs-kernel-server:
nfs-kernel-server depends on nfs-common (>= 1:0.3.3-3); however:
Package nfs-common is not configured yet.
dpkg: error processing nfs-kernel-server (--configure):
dependency problems - leaving unconfigured
I'm not sure how to debug this. It seems wrong that useradd is trying
to create the user statd over LDAP. Shouldn't it be a local system user
only?
-- System Information:
Debian Release: testing/unstable
APT prefers oldstable
APT policy: (900, 'oldstable'), (900, 'unstable'), (900, 'testing'), (900,
'stable'), (600,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Versions of packages libnss-ldap depends on:
ii debconf 1.5.0 Debian configuration management sy
ii libc6 2.3.6-7 GNU C Library: Shared libraries
ii libkrb53 1.4.3-7 MIT Kerberos runtime libraries
ii libldap2 2.1.30-13 OpenLDAP libraries
Versions of packages libnss-ldap recommends:
ii libpam-ldap 180-1 Pluggable Authentication Module al
ii nscd 2.3.6-7 GNU C Library: Name Service Cache
-- debconf information:
* libnss-ldap/dblogin: false
libnss-ldap/override: true
* shared/ldapns/base-dn: dc=company,dc=com
* shared/ldapns/ldap-server: 192.168.100.1
* libnss-ldap/confperm: true
* shared/ldapns/ldap_version: 3
libnss-ldap/binddn: cn=proxyuser,dc=example,dc=net
* libnss-ldap/nsswitch:
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--- End Message ---
--- Begin Message ---
Greetings,
If this is a bug at all (which I doubt), the assertion failure is
actually in the LDAP code, not in the libnss-ldap code at all.. In
the end I expect this is a configuration problem though and if the
user doesn't want system accounts in LDAP then they need to adjust
their /etc/nsswitch.conf appropriately to handle it correctly.
Thanks,
Stephen
--- End Message ---
