Your message dated Mon, 04 Feb 2008 20:04:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#463915: libnss-ldapd: Segfaulting on AMD64
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 ---
Package: libnss-ldapd
Version: 0.5+b1
Severity: important
On my AMD64 box the nslcd demon crashes quite frequently.
After the crash no mappings are resolved any more as far as they are fetched
from the LDAP server in the LAN. Local mappings still work.
Those crashes occur about ten to twenty times a day without any visible
action, although I was not able to find a way to reproduce the crash
reliably:
[EMAIL PROTECTED]:/var/log# grep nslcd.*segfault syslog.0
Feb 3 08:19:10 sofa kernel: nslcd[5358]: segfault at ffffffffac0008c0 rip
0000000000408eb0 rsp
0000000041000f70 error 4
Feb 4 05:44:37 sofa kernel: nslcd[18186]: segfault at ffffffffac00af90 rip
000000000040b6ee rsp
0000000041801b60 error 4
Feb 4 05:44:44 sofa kernel: nslcd[18234]: segfault at ffffffffac00af90 rip
000000000040b6ee rsp
00000000407ffb60 error 4
Feb 4 05:50:02 sofa kernel: nslcd[18745]: segfault at ffffffffac000a50 rip
0000000000408eb0 rsp
0000000041000f70 error 4
Feb 4 06:09:23 sofa kernel: nslcd[21479]: segfault at ffffffffac00b350 rip
00000000004041f6 rsp
0000000041000630 error 4
Feb 4 06:10:01 sofa kernel: nslcd[21563]: segfault at ffffffffac00b150 rip
0000000000408eb0 rsp
0000000041801f70 error 4
Feb 4 06:25:02 sofa kernel: nslcd[22085]: segfault at ffffffffac000a20 rip
0000000000408eb0 rsp
0000000042002f70 error 4
Feb 4 06:35:02 sofa kernel: nslcd[24194]: segfault at ffffffffac003d00 rip
0000000000408eb0 rsp
00000000407fff70 error 4
Feb 4 07:25:02 sofa kernel: nslcd[28654]: segfault at ffffffffac0009c0 rip
0000000000408eb0 rsp
0000000042803f70 error 4
Feb 4 07:35:01 sofa kernel: nslcd[32760]: segfault at ffffffffac001c20 rip
0000000000408eb0 rsp
0000000041000f70 error 4
Feb 4 07:39:01 sofa kernel: nslcd[1077]: segfault at ffffffffac00b150 rip
0000000000408eb0 rsp
0000000041000f70 error 4
The backtrace of the coredump is as follows:
#0 0x0000000000408eb0 in ?? ()
No symbol table info available.
#1 0x0000000000409069 in ?? ()
No symbol table info available.
#2 0x0000000000403565 in ?? ()
No symbol table info available.
#3 0x00002b84742dc3f7 in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#4 0x00002b84745c897d in clone () from /lib/libc.so.6
No symbol table info available.
#5 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)
The syslog shows regarding this segfault nothing more than:
Feb 4 07:39:01 sofa kernel: nslcd[1077]: segfault at ffffffffac00b150 rip
0000000000408eb0 rsp 0000000041000f70 error 4
Another crashed session which was done via "nslcd -d" on
the commandline revealed this log:
nslcd: DEBUG: connection from pid=4932 uid=0 gid=0
nslcd: DEBUG: nslcd_group_all()
nslcd: DEBUG: myldap_search(base="dc=antepoth,dc=de",
filter="(objectClass=posixGroup)")
nslcd: DEBUG: connection from pid=4932 uid=0 gid=0
nslcd: DEBUG: nslcd_passwd_byuid(15325)
nslcd: DEBUG: myldap_search(base="dc=antepoth,dc=de",
filter="(&(objectClass=posixAccount)(uidNumber=15325))")
nslcd: DEBUG: connection from pid=4932 uid=0 gid=0
nslcd: DEBUG: nslcd_group_all()
nslcd: DEBUG: myldap_search(base="dc=antepoth,dc=de",
filter="(objectClass=posixGroup)")
Speicherzugriffsfehler
The user having this UID 15325 is existing and resolvable by LDAP when
issuing an "getent passwd 15325" after a restart of nslcd.
A third session using "gdb" is yet to come and appended to this bugreport
later.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23.9 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libnss-ldapd depends on:
ii debconf [debconf-2.0] 1.5.18 Debian configuration management sy
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.7-3+b1 OpenLDAP libraries
Versions of packages libnss-ldapd recommends:
ii libpam-ldap 184-2+b1 Pluggable Authentication Module al
ii nscd 2.7-6 GNU C Library: Name Service Cache
-- debconf information:
libnss-ldapd/ldap-bindpw: (password omitted)
* libnss-ldapd/ldap-rootbindpw: (password omitted)
* libnss-ldapd/ldap-base: dc=antepoth,dc=de
* libnss-ldapd/nsswitch: passwd, group, shadow
* libnss-ldapd/ldap-binddn:
* libnss-ldapd/ldap-rootbinddn:
* libnss-ldapd/ldap-uris: ldap://192.168.186.254/
--- End Message ---
--- Begin Message ---
Package: libnss-ldapd
Version: 0.6
On Mon, 2008-02-04 at 08:13 +0100, Thomas Antepoth wrote:
> On my AMD64 box the nslcd demon crashes quite frequently.
This is most likely a result of the rebuild with OpenLDAP 2.4 in version
0.5+b1 of nss-ldapd. See bug #463421 for more details. This also means
that this problem should be fixed in version 0.6 that has just been
released.
Thanks for the detailed bugreport.
If you can reproduce this bug with version 0.6, please reopen this
bugreport.
--
-- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
--- End Message ---
