Package: winbind
Version: 1:3.0.28a-3
Severity: critical
Justification: breaks unrelated software


We are using winbind to authenticate users to the system for various
services. The winbind daemon seems to crash many times a day. At the
moment I have a cron job that restarts winbind and samba every time as
crash has been detected to minimise the impact on the system.

This happens on two separate servers that we run winbind on.
They are both located in different networks in different Active Directory 
environments.
I'll just report on one of the hosts that is more active and suffers from the 
crashes more frequently.

Output from 'testparm -s /etc/samba/smb.conf' is as follows:

        Load smb config files from /etc/samba/smb.conf
        Processing section "[home_dirs]"
        Loaded services file OK.
        Server role: ROLE_DOMAIN_MEMBER
        [global]
                workgroup = PRY
                realm = PRY.COM.AU
                server string = %h server
                security = ADS
                obey pam restrictions = Yes
                password server = ZEUS ACCOUNTS exchange02
                passdb backend = tdbsam
                passwd program = /usr/bin/passwd %u
                passwd chat = *Enter\snew\s*\spassword:* %n\n 
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
                restrict anonymous = 2
                ntlm auth = No
                client NTLMv2 auth = Yes
                syslog = 0
                log file = /var/log/samba/log.%m
                max log size = 1000
                disable netbios = Yes
                name resolve order = host
                socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
                dns proxy = No
                panic action = /usr/share/samba/panic-action %d
                idmap uid = 10000-20000
                idmap gid = 10000-20000
                template homedir = /var/home/%D/%U
                winbind cache time = 120
                winbind enum users = Yes
                winbind enum groups = Yes
                winbind use default domain = Yes
                invalid users = root
        
        [home_dirs]
                comment = Home Directories
                path = /home
                username = administrator
                force user = root


The dump from the panic-action email shows the following:

        (no debugging symbols found)
        Using host libthread_db library "/lib/libthread_db.so.1".
        (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 0xb7ae06d0 (LWP 25600)]
        (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)
        0xb7cb66be in waitpid () from /lib/libc.so.6
        #0  0xb7cb66be in waitpid () from /lib/libc.so.6
        #1  0xb7c5e02e in ?? () from /lib/libc.so.6
        #2  0x0811eea8 in smb_panic ()
        #3  0x08109aaa in ?? ()
        #4  0x0826bc84 in ?? ()
        #5  0x0826bc20 in ?? ()
        #6  0x0826be13 in ?? ()
        #7  0x0000002d in ?? ()
        #8  0xffffffb8 in ?? ()
        #9  0x0826bc20 in ?? ()
        #10 0x0826be13 in ?? ()
        #11 0x00006400 in ?? ()
        #12 0xbfa06218 in ?? ()
        #13 0xb7d57ff4 in ?? () from /lib/libc.so.6
        #14 0xbfa06178 in ?? ()
        #15 <signal handler called>
        #16 0xb7c50d96 in raise () from /lib/libc.so.6
        #17 0xb7c52541 in abort () from /lib/libc.so.6
        #18 0xb7c4a230 in __assert_fail () from /lib/libc.so.6
        #19 0xb7d79eaa in ldap_parse_result () from /usr/lib/libldap_r-2.4.so.2
        #20 0x0822f5cc in ?? ()
        #21 0x085963a0 in ?? ()
        #22 0x00000000 in ?? ()
        The program is running.  Quit anyway (and detach it)? (y or n) 
[answered Y; input not from terminal]

The above seems to suggest something going wrong with LDAP?
I have the latest libraries for LDAP in the testing distribution installed.
Output from 'dpkg --list | grep ldap' is:

        ii  ldap-utils                  2.4.7-6.3                   OpenLDAP 
utilities
        ii  libldap-2.4-2               2.4.7-6.3                   OpenLDAP 
libraries

Regards,

----------
Jim Barber
DDI Health


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.18 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages winbind depends on:
ii  adduser                     3.107        add and remove users and groups
ii  libc6                       2.7-10       GNU C Library: Shared libraries
ii  libcomerr2                  1.40.8-2     common error description library
ii  libkrb53                    1.6.dfsg.3-2 MIT Kerberos runtime libraries
ii  libldap-2.4-2               2.4.7-6.3    OpenLDAP libraries
ii  libpam0g                    0.99.7.1-6   Pluggable Authentication Modules l
ii  libpopt0                    1.10-3       lib for parsing cmdline parameters
ii  lsb-base                    3.2-11       Linux Standard Base 3.2 init scrip
ii  samba-common                1:3.0.28a-3  Samba common files used by both th

winbind recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to