Package: samba Version: 3.0.14a-3 Severity: important
About 50 users tried to login in a few minutes. Nearly all logins are succeeded, but on some cliens a few trials were neccessary. This behaviour is unusal in our network. I've got about 10 nearly identical mails from the server about an smbd panic-action. Mail contents (of couse the pid was different for each related smbd process): The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 331 (/usr/sbin/smbd). Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occured. You are encouraged to submit this information as a bug report to Debian. For information about the procedure for submitting bug reports , please see http://www.debian.org/Bugs/Reporting or the reportbug(1) manpage. (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1212940160 (LWP 331)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7cea3ae in waitpid () from /lib/tls/libc.so.6 #0 0xb7cea3ae in waitpid () from /lib/tls/libc.so.6 #1 0xb7c7fd12 in system () from /lib/tls/libc.so.6 #2 0x081eb261 in smb_panic2 () #3 0x081eb1ea in smb_panic () #4 0x081d7368 in dbgtext () #5 <signal handler called> #6 0xb7c6983b in raise () from /lib/tls/libc.so.6 #7 0xb7c6afa2 in abort () from /lib/tls/libc.so.6 #8 0xb7c632df in __assert_fail () from /lib/tls/libc.so.6 #9 0xb7eaf37d in ber_get_next () from /usr/lib/liblber.so.2 #10 0xb7ec4096 in ldap_result () from /usr/lib/libldap_r.so.2 #11 0xb7ec3da5 in ldap_result () from /usr/lib/libldap_r.so.2 #12 0xb7866f8a in ?? () from /lib/libnss_ldap.so.2 #13 0x083fb388 in ?? () #14 0x00000005 in ?? () #15 0x00000000 in ?? () #16 0x00000000 in ?? () #17 0x083fc458 in ?? () #18 0x00000000 in ?? () #19 0x00000020 in ?? () #20 0xb7873888 in ?? () from /lib/libnss_ldap.so.2 #21 0x083fc458 in ?? () #22 0x00000000 in ?? () #23 0xbf911008 in ?? () #24 0x00000034 in ?? () #25 0x083fc448 in ?? () #26 0xbf911080 in ?? () #27 0x00000000 in ?? () #28 0xb7873888 in ?? () from /lib/libnss_ldap.so.2 #29 0x083fc448 in ?? () #30 0x00000000 in ?? () #31 0xbf911008 in ?? () #32 0xb7866b7a in ?? () from /lib/libnss_ldap.so.2 #33 0x083fc448 in ?? () #34 0x00000000 in ?? () #35 0x00000005 in ?? () #36 0xb7873888 in ?? () from /lib/libnss_ldap.so.2 #37 0xb7873888 in ?? () from /lib/libnss_ldap.so.2 #38 0xffffffff in ?? () #39 0xbf9110b8 in ?? () #40 0xb786a6f0 in _nss_ldap_initgroups_dyn () from /lib/libnss_ldap.so.2 I assumed that this was a problem with nss, nscd or ldap. I've increased the number of concorrent nscd connections from the default 5 to 30 and LDAP connections from the default 6 to 30. Next day I've tested the configuration with 31 logins in a few minutes. No panic actions reported this time. I've submitted this bug report, because the panic-action suggested to do so. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.13 Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2) Versions of packages samba depends on: ii debconf [debconf-2.0] 1.4.30.13 Debian configuration management sy ii libacl1 2.2.23-1 Access control list shared library ii libattr1 2.4.16-1 Extended attribute shared library ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libcupsys2-gnutls10 1.1.23-10 Common UNIX Printing System(tm) - ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libldap2 2.1.30-8 OpenLDAP libraries ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpopt0 1.7-5 lib for parsing cmdline parameters ii logrotate 3.7-5 Log rotation utility ii netbase 4.21 Basic TCP/IP networking system ii samba-common 3.0.14a-3 Samba common files used by both th -- debconf information: samba/nmbd_from_inetd: samba/log_files_moved: samba/tdbsam: false samba/generate_smbpasswd: true samba/run_mode: daemons -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
