Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

2006-01-06 Thread Andy Chittenden 
 Does the samba log give a more useful backtrace here?

It seems so. Here's the output from smbd in syslog:

Jan  6 08:41:12 boco smbd[27555]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[27555]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27555]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[27555]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27555]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[27555]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27555]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:write_data(554)
Jan  6 08:41:12 boco smbd[27555]:   write_data: write failure in writing
to client 10.1.16.13. Error Connection reset by peer
Jan  6 08:41:12 boco smbd[27555]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:send_smb(762)
Jan  6 08:41:12 boco smbd[27555]:   Error writing 4 bytes to client. -1.
(Connection reset by peer)
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/fault.c:fault_report(36)
Jan  6 08:41:12 boco smbd[27556]:
===
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/fault.c:fault_report(37)
Jan  6 08:41:12 boco smbd[27556]:   INTERNAL ERROR: Signal 11 in pid
27556 (3.0.21a-Debian)
Jan  6 08:41:12 boco smbd[27556]:   Please read the Trouble-Shooting
section of the Samba3-HOWTO
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/fault.c:fault_report(39)
Jan  6 08:41:12 boco smbd[27556]:
Jan  6 08:41:12 boco smbd[27556]:   From:
http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/fault.c:fault_report(40)
Jan  6 08:41:12 boco smbd[27556]:
===
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/util.c:smb_panic2(1544)
Jan  6 08:41:12 boco smbd[27556]:   smb_panic(): calling panic action
[/usr/share/samba/panic-action 27556]
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/util.c:smb_panic2(1552)
Jan  6 08:41:12 boco smbd[27556]:   smb_panic(): action returned status
0
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/util.c:smb_panic2(1554)
Jan  6 08:41:12 boco smbd[27556]:   PANIC: internal error
Jan  6 08:41:12 boco smbd[27556]: [2006/01/06 08:41:12, 0]
lib/util.c:smb_panic2(1562)
Jan  6 08:41:12 boco smbd[27556]:   BACKTRACE: 15 stack frames:
Jan  6 08:41:12 boco smbd[27556]:#0 /usr/sbin/smbd(smb_panic2+0x6d)
[0x5573adcd]
Jan  6 08:41:12 boco smbd[27556]:#1 /usr/sbin/smbd [0x55727c44]
Jan  6 08:41:12 boco smbd[27556]:#2 /lib/libc.so.6 [0x2bdacea0]
Jan  6 08:41:12 boco smbd[27556]:#3
/usr/sbin/smbd(smb_arc4_init+0x37) [0x557480d7]
Jan  6 08:41:12 boco smbd[27556]:#4
/usr/sbin/smbd(ntlmssp_sign_init+0xfa) [0x5564ea2a]
Jan  6 08:41:12 boco smbd[27556]:#5 /usr/sbin/smbd [0x5564b7ee]
Jan  6 08:41:12 boco smbd[27556]:#6
/usr/sbin/smbd(ntlmssp_update+0x273) [0x5564a793]
Jan  6 08:41:12 boco smbd[27556]:#7
/usr/sbin/smbd(auth_ntlmssp_update+0x2a) [0x55778d1a]
Jan  6 08:41:12 boco smbd[27556]:#8
/usr/sbin/smbd(reply_sesssetup_and_X+0x8d8) [0x555e5c78]
Jan  6 08:41:12 boco smbd[27556]:#9 /usr/sbin/smbd [0x5560ece0]
Jan  6 08:41:12 boco smbd[27556]:#10
/usr/sbin/smbd(process_smb+0x190) [0x5560f1d0]
Jan  6 08:41:12 boco smbd[27556]:#11
/usr/sbin/smbd(smbd_process+0x1b7) [0x556100d7]
Jan  6 08:41:12 boco smbd[27556]:#12 /usr/sbin/smbd(main+0x78b)
[0x557c42eb]
Jan  6 08:41:12 boco smbd[27556]:#13
/lib/libc.so.6(__libc_start_main+0xda) [0x2bd994ca]
Jan  6 08:41:12 boco smbd[27556]:#14 /usr/sbin/smbd [0x555abe8a]
Jan  6 08:41:12 boco smbd[27556]:
Jan  6 08:41:12 boco smbd[24303]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[24303]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27598]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[27598]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27598]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[27598]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27598]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan  6 08:41:12 boco smbd[27598]:   getpeername failed. Error was
Transport endpoint is not connected
Jan  6 08:41:12 boco smbd[27598]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:write_data(554)
Jan  6 08:41:12 boco smbd[27598]:   write_data: write failure in writing
to client 0.0.0.0. Error Connection reset by peer
Jan  6 08:41:12 boco smbd[27598]:

Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

2006-01-05 Thread Andrew Chittenden 
Package: samba
Version: 3.0.21a-1
Severity: grave
Justification: renders package unusable


Everytime I attempt to map a drive or browse an already mapped drive
from a PC running WinXP Pro with all updates applied, I receive the
following email (I have installed samba-dbg package):

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 21799 (/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 occurred. 

If the problem persists, you are encouraged to first install the 
samba-dbg package which contains the debugging symbols for samba 
binaries. The, submit the provided 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.

Using host libthread_db library /lib/libthread_db.so.1.
0x2be0fc15 in ?? ()
#0  0x2be0fc15 in ?? ()
#1  0xffc0 in ?? ()
#2  0x7fd83d1c in ?? ()
#3  0x0001 in ?? ()
#4  0x2bdb8415 in ?? ()
#5  0x0001 in ?? ()
#6  0x0001 in ?? ()
#7  0x in ?? ()

Having downgraded to samba 3.0.20b-3, I can map and browse OK.

Andy, BlueArc Engineering

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-amd64-k8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages samba depends on:
ii  debconf [debc 1.4.67 Debian configuration management sy
ii  libacl1   2.2.34-1   Access control list shared library
ii  libattr1  2.4.25-1   Extended attribute shared library
ii  libc6 2.3.5-11   GNU C Library: Shared libraries an
ii  libcomerr21.38+1.39-WIP-2005.12.10-1 common error description library
ii  libcupsys21.1.23-15  Common UNIX Printing System(tm) - 
ii  libkrb53  1.4.3-5MIT Kerberos runtime libraries
ii  libldap2  2.1.30-12  OpenLDAP libraries
ii  libpam-module 0.79-3 Pluggable Authentication Modules f
ii  libpam-runtim 0.79-3 Runtime support for the PAM librar
ii  libpam0g  0.79-3 Pluggable Authentication Modules l
ii  libpopt0  1.7-5  lib for parsing cmdline parameters
ii  logrotate 3.7.1-2Log rotation utility
ii  lsb-base  3.0-13 Linux Standard Base 3.0 init scrip
ii  netbase   4.23   Basic TCP/IP networking system
ii  samba-common  3.0.21a-1  Samba common files used by both th

Versions of packages samba recommends:
pn  smbldap-tools none (no description available)

-- debconf information:
  samba/nmbd_from_inetd:
* samba/run_mode: daemons
  samba/log_files_moved:
  samba/tdbsam: false
* samba/generate_smbpasswd: true


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

Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

2006-01-05 Thread Christian Perrier 
severity 346069 important
thanks

(rationale: up to now we have no indication that the package is
unusable for everyone.)

 Using host libthread_db library /lib/libthread_db.so.1.
 0x2be0fc15 in ?? ()
 #0  0x2be0fc15 in ?? ()
 #1  0xffc0 in ?? ()
 #2  0x7fd83d1c in ?? ()
 #3  0x0001 in ?? ()
 #4  0x2bdb8415 in ?? ()
 #5  0x0001 in ?? ()
 #6  0x0001 in ?? ()
 #7  0x in ?? ()
 
 Having downgraded to samba 3.0.20b-3, I can map and browse OK.

Is that all what is outputted?

Steve, others, is it expected that we get so few information even with
samba-dbg?




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

Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

2006-01-05 Thread Steve Langasek 
On Thu, Jan 05, 2006 at 05:52:19PM +0100, Christian Perrier wrote:
 severity 346069 important
 thanks

 (rationale: up to now we have no indication that the package is
 unusable for everyone.)

  Using host libthread_db library /lib/libthread_db.so.1.
  0x2be0fc15 in ?? ()
  #0  0x2be0fc15 in ?? ()
  #1  0xffc0 in ?? ()
  #2  0x7fd83d1c in ?? ()
  #3  0x0001 in ?? ()
  #4  0x2bdb8415 in ?? ()
  #5  0x0001 in ?? ()
  #6  0x0001 in ?? ()
  #7  0x in ?? ()

  Having downgraded to samba 3.0.20b-3, I can map and browse OK.

 Is that all what is outputted?

 Steve, others, is it expected that we get so few information even with
 samba-dbg?

Only in cases of stack corruption or gdb bugs.

Does the samba log give a more useful backtrace here?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature