Your message dated Thu, 15 May 2008 18:21:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Pkg-samba-maint] Bug#476667: bug vanished
has caused the Debian Bug report #476667,
regarding [samba] smbd panics
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.)
--
476667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476667
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: samba
Version: 3.0.28a-1
Severity: important
--- Please enter the report below this line. ---
I see frequent PANICs of smbd like the following with various WINXP and Xin2003
clients.
[2008/04/17 15:37:35, 0] lib/fault.c:fault_report(41)
===============================================================
[2008/04/17 15:37:35, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 13309 (3.0.28a)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/04/17 15:37:35, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/04/17 15:37:35, 0] lib/fault.c:fault_report(45)
===============================================================
[2008/04/17 15:37:35, 0] lib/util.c:smb_panic(1633)
PANIC (pid 13309): internal error
[2008/04/17 15:37:35, 0] lib/util.c:log_stack_trace(1737)
BACKTRACE: 34 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x60de0c]
#1 /usr/sbin/smbd(smb_panic+0x43) [0x60def3]
#2 /usr/sbin/smbd [0x5fbd62]
#3 /lib/libpthread.so.0 [0x2b541edbc7d0]
#4 /lib/libc.so.6(gsignal+0x35) [0x2b5420205025]
#5 /lib/libc.so.6(abort+0x110) [0x2b5420206a80]
#6 /lib/libc.so.6(__assert_fail+0xef) [0x2b54201fe42f]
#7 /usr/lib/liblber-2.4.so.2(ber_flush2+0x16f) [0x2b541dbe1eef]
#8 /usr/lib/libldap_r-2.4.so.2(ldap_int_flush_request+0x2c) [0x2b541d9b7b2c]
#9 /usr/lib/libldap_r-2.4.so.2(ldap_send_server_request+0x38f)
[0x2b541d9b7f6f]
#10 /usr/lib/libldap_r-2.4.so.2(ldap_send_initial_request+0x96)
[0x2b541d9b80d6]
#11 /usr/lib/libldap_r-2.4.so.2(ldap_search+0xbd) [0x2b541d9a8cad]
#12 /usr/lib/libldap_r-2.4.so.2(ldap_search_st+0x2a) [0x2b541d9a8dca]
#13 /lib/libnss_ldap.so.2 [0x2b54216fd0a3]
#14 /lib/libnss_ldap.so.2 [0x2b54216fc345]
#15 /lib/libnss_ldap.so.2 [0x2b54216fce6e]
#16 /lib/libnss_ldap.so.2(_nss_ldap_initgroups_dyn+0x27c) [0x2b54216feb0c]
#17 /lib/libc.so.6 [0x2b542026d787]
#18 /lib/libc.so.6(getgrouplist+0x6b) [0x2b542026da3b]
#19 /usr/sbin/smbd [0x6296b5]
#20 /usr/sbin/smbd(getgroups_unix_user+0x6a) [0x62978a]
#21 /usr/sbin/smbd(create_token_from_username+0x3c7) [0x64f797]
#22 /usr/sbin/smbd(create_local_token+0x74) [0x650904]
#23 /usr/sbin/smbd [0x652455]
#24 /usr/sbin/smbd [0x5077be]
#25 /usr/sbin/smbd(ntlmssp_update+0x25f) [0x5071bf]
#26 /usr/sbin/smbd(auth_ntlmssp_update+0x2a) [0x65215a]
#27 /usr/sbin/smbd [0x49af6a]
#28 /usr/sbin/smbd(reply_sesssetup_and_X+0x963) [0x49c3c3]
#29 /usr/sbin/smbd [0x4c6fae]
#30 /usr/sbin/smbd(smbd_process+0x7d2) [0x4c8332]
#31 /usr/sbin/smbd(main+0x8cd) [0x6bde1d]
#32 /lib/libc.so.6(__libc_start_main+0xf4) [0x2b54201f11c4]
#33 /usr/sbin/smbd [0x45a789]
[2008/04/17 15:37:35, 0] lib/fault.c:dump_core(181)
dumping core in /var/log/samba/cores/smbd
[2008/04/17 15:37:35, 1] smbd/service.c:make_connection_snum(1033)
<HOSTNAME> (<IP>) connect to service <USERNAME> initially as user <USERNAME>
(uid=<UID>, gid=<GID>) (pid 16436)
smbd: /build/buildd/openldap2.3-2.4.7/libraries/liblber/io.c:234: ber_flush2:
Assertion `( (sb)->sb_opts.lbo_valid == 0x3 )' failed.
[2008/04/17 16:16:01, 0] lib/fault.c:fault_report(41)
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.24-1-amd64
Debian Release: lenny/sid
--- Package information. ---
Depends (Version) | Installed
==================================-+-================
adduser | 3.107
debconf (>= 0.5) | 1.5.20
OR debconf-2.0 |
libacl1 (>= 2.2.11-1) | 2.2.45-1
libattr1 (>= 2.4.41-1) | 1:2.4.41-1
libc6 (>= 2.7-1) | 2.7-6
libcomerr2 (>= 1.33-3) | 1.40.8-2
libcupsys2 (>= 1.3.4) | 1.3.6-3+lenny1
libgnutls26 (>= 2.2.0-0) | 2.2.2-1
libkrb53 (>= 1.6.dfsg.2) | 1.6.dfsg.3~beta1-4
libldap-2.4-2 (>= 2.4.7) | 2.4.7-6.1
libpam-modules | 0.99.7.1-6
libpam-runtime (>= 0.76-13.1) | 0.99.7.1-6
libpam0g (>= 0.99.7.1) | 0.99.7.1-6
libpopt0 (>= 1.10) | 1.10-3
logrotate | 3.7.1-3
lsb-base (>= 3.0-6) | 3.1-24
procps | 1:3.2.7-6
samba-common (= 3.0.28a-1) | 3.0.28a-1
update-inetd | 4.30
zlib1g | 1:1.2.3.3.dfsg-11
--- End Message ---
--- Begin Message ---
Quoting Christian Salzmann ([EMAIL PROTECTED]):
> with installation of libnss-ldap version 260-1 this bug has vanished.
> Feel free to close this bug report.
OK. Thanks for taking care to notify us.
To Julien Cristau: nice catch!
signature.asc
Description: Digital signature
--- End Message ---
