Bug #28021 “samba: Segfault in Samba after upgrade to 3.0.21a-1” : Bugs : samba package : Ubuntu

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-05:

#1

Download full text (3.3 KiB)

Message-ID: <email address hidden>
Date: Thu, 05 Jan 2006 11:56:26 +0000
From: Andrew Chittenden <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: samba: Segfault in Samba after upgrade to 3.0.21a-1

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".
0x00002aaaabe0fc15 in ?? ()
#0 0x00002aaaabe0fc15 in ?? ()
#1 0xffffffffffffffc0 in ?? ()
#2 0x00007fffffd83d1c in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x00002aaaabdb8415 in ?? ()
#5 0x0000000000000001 in ?? ()
#6 0x0000000000010000 in ?? ()
#7 0x0000000000000000 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 libcomerr2 1.38+1.39-WIP-2005.12.10-1 common error description library
ii libcupsys2 1.1.23-15 Common UNIX Printing System(tm) -
ii libkrb53 1.4.3-5 MIT 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-2 Log 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 ...

Message-Id: <E1EuU36-0005od-LW@boco.dev.bluearc.com>
Date: Thu, 05 Jan 2006 12:16:56 +0000
From: Andy Chittenden <andyc@bluearc.com>
To: 346069@bugs.debian.org
Cc: achittenden@bluearc.com
Subject: attaching smb.conf

--=_43bd0e38.TGlyoH12KeBgEuxYiWJlGDSaPEmivnYmB4cv6P9TQx2oFDVl
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="smb.conf"

;
; /etc/smb.conf
;
; Sample configuration file for the Samba suite for Debian GNU/Linux
;
; Please see the manual page for smb.conf for detailed description of
;	every parameter.
;

[global]

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d
   printing = bsd
   printcap name = /etc/printcap
   load printers = yes
   guest account = nobody
   invalid users = root
   syslog only = yes
   hosts deny = usprint

; "security = user" is always a good idea. This will require a Unix account
;	in this server for every user accessing the server.
   security = server
   password server = ukdc uk-dc2 
   ; password server = uspdc
   ; username map = /etc/samba/username.map

; Change this for the workgroup your Samba server will part of
   workgroup = TERASTACK

server string = %h server (Samba %v)

; This socket options really speed up Samba under Linux, according to my
;	own tests.
   socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=16384 SO_RCVBUF=16384

; Passwords are encrypted by default. This way the latest Windows 95 and NT
;	clients can connect to the Samba server with no problems.
   encrypt passwords = true

; It's always a good idea to use a WINS server. If you want this server
;	to be the WINS server for your network change the following parameter
;	to "yes". Otherwise leave it as "no" and specify your WINS server
; 	below (note: only one Samba server can be the WINS server).
;	Read BROWSING.txt for more details.
   wins support = no

; If this server is not the WINS server then specify who is it and uncomment
;	next line.
   wins server = 10.1.1.1

; Please read BROWSING.txt and set the next four parameters according
;	to your network setup. There is no valid default so they are commented
;	out.
;   os level = 0
   domain master = no
   local master = no
;   preferred master = no
    ; debug level = 255

; What naming service and in what order should we use to resolve host names
;	to IP addresses
   name resolve order = lmhosts host wins bcast

; This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

; Name mangling options

preserve case = yes
   short preserve case = yes
   default case = lower
   hide dot files = no
   dos filetime resolution = true

; This boolean parameter controlls whether Samba attempts to sync. the Unix
;	password with the SMB password when the encrypted SMB password in the
;	/etc/samba/smbpasswd file is changed.
   unix password sync = false

; For Unix password sync. to work on a Debian GNU/Linux system, the following
;	parameters must be set (thanks to Culus for pointing this out):
   passwd program = /usr/bin/passwd %u
   passwd chat = *New\spassword:* %n\n *Re-enter\snew\spassword:* %n\n *Password\schanged.* .

; The following parameter is useful only if you have the linpopup package
;	installed. The samba maintainer and the linpopup maintainer are
;	working to ease installation and configuration of linpopup and samba.
   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

; The default maximum log file size is 5 MBytes. That's too big so this
;	next parameter sets it to 1 MByte. Currently, Samba rotates log
;	files (/var/log/{smb,nmb} in Debian) when these files reach 1000 KBytes.
;	A better solution would be to have Samba rotate the log file upon
;	reception of a signal, but for now on, we have to live with this.
   max log size = 1000

; don't map archive bit so files generated by DOS won't get execute
; permission set
   map archive = no

; allow deletion of read-only files
   delete readonly = yes

[homes]
   comment = Home Directories
   browseable = no

; By default, the home directories are exported read only. Change next
;	parameter to "no" if you want to be able to write to them.
   read only = no

; File creation mask is set to 0700 for security reasons. If you want to
;	create files with group=rw permissions, set next parameter to 0775.
   create mask = 0664

; Directory creation mask is set to 0700 for security reasons. If you want to
;	create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0775

[printers]
   comment = All Printers
   browseable = no
   path = /tmp
   printable = yes
   public = no
   writable = no
   create mode = 0700

; A sample share for sharing your CD-ROM with others.
[cdrom]
   comment = Samba server's CD-ROM
   writable = no
   locking = no
   path = /var/autofs/misc/cd
   public = yes
;
; The next two parameters show how to auto-mount a CD-ROM when the
;	cdrom share is accesed. For this to work /etc/fstab must contain
;	an entry like this:
;
;       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
;
; The CD-ROM gets unmounted automatically after the connection to the
;
; If you don't want to use auto-mounting/unmounting make sure the CD
;	is mounted on /cdrom
;
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom

[tmp]
   comment = /tmp on %h
   path = /tmp
   writable = yes
   browseable = yes
   read only = no

create mask = 0664

directory mask = 0775

[tmps]
   comment = %u/tmp on %h
   path = %H/tmp
   writable = yes
   browseable = no
   read only = no

create mask = 0664

directory mask = 0775

[homedocs]
   comment = %u/docs on %h
   path = %H/docs
   writable = yes
   browseable = no
   read only = no

create mask = 0664

directory mask = 0775

[workdocs]
   comment = %u/work/docs on %h
   path = %H/work/docs
   writable = yes
   browseable = no
   read only = no

create mask = 0664

directory mask = 0775

[u4]
   comment = u4 on %h
   path = /u4
   writable = yes
   create mask = 0664

directory mask = 0775

--=_43bd0e38.TGlyoH12KeBgEuxYiWJlGDSaPEmivnYmB4cv6P9TQx2oFDVl--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-05:

#3

Message-ID: <email address hidden>
Date: Thu, 5 Jan 2006 17:52:19 +0100
From: Christian Perrier <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

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".
> 0x00002aaaabe0fc15 in ?? ()
> #0 0x00002aaaabe0fc15 in ?? ()
> #1 0xffffffffffffffc0 in ?? ()
> #2 0x00007fffffd83d1c in ?? ()
> #3 0x0000000000000001 in ?? ()
> #4 0x00002aaaabdb8415 in ?? ()
> #5 0x0000000000000001 in ?? ()
> #6 0x0000000000010000 in ?? ()
> #7 0x0000000000000000 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?

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-05:

#4

Message-ID: <email address hidden>
Date: Thu, 5 Jan 2006 13:32:46 -0800
From: Steve Langasek <email address hidden>
To: Christian Perrier <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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".
> > 0x00002aaaabe0fc15 in ?? ()
> > #0 0x00002aaaabe0fc15 in ?? ()
> > #1 0xffffffffffffffc0 in ?? ()
> > #2 0x00007fffffd83d1c in ?? ()
> > #3 0x0000000000000001 in ?? ()
> > #4 0x00002aaaabdb8415 in ?? ()
> > #5 0x0000000000000001 in ?? ()
> > #6 0x0000000000010000 in ?? ()
> > #7 0x0000000000000000 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?

--=20
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 address hidden> http://www.debian.org/

--mYCpIKhGyMATD0i+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDvZB+KN6ufymYLloRAqy1AJsGF1wljvH+XsuV1KdDISTxf4m60QCfVbq/
x+WxPPXgKIwXbfZInPQocVA=
=qrc2
-----END PGP SIGNATURE-----

--mYCpIKhGyMATD0i+--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-05:

#5

Message-ID: <email address hidden>
Date: Thu, 5 Jan 2006 14:00:27 -0800
From: Steve Langasek <email address hidden>
To: Andy Chittenden <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#346069: attaching smb.conf

--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Andy,

On Thu, Jan 05, 2006 at 12:16:56PM +0000, Andy Chittenden wrote:
> ; "security =3D user" is always a good idea. This will require a Unix acc=
ount
> ; in this server for every user accessing the server.
> security =3D server
> password server =3D ukdc uk-dc2=20
> ; password server =3D uspdc
> ; username map =3D /etc/samba/username.map

Why are you using security =3D server? This is an insecure misfeature, and
I'm not at all surprised if this isn't getting upstream testing prior to
release. I strongly recommend converting your system to use security =3D
domain instead (with the cooperation of the domain admin).

--=20
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 address hidden> http://www.debian.org/

--UugvWAfsgieZRqgk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDvZb7KN6ufymYLloRAk1sAKCHbIS+yFtrnaR6uy6AIIXyf9jzsQCcDork
2hZUFem4DTx9riCenyWn6mM=
=+D2P
-----END PGP SIGNATURE-----

--UugvWAfsgieZRqgk--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-06:

#6

Download full text (11.7 KiB)

Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 08:45:08 -0000
From: "Andy Chittenden" <email address hidden>
To: "Steve Langasek" <email address hidden>, "Christian Perrier" <email address hidden>,
<email address hidden>
Subject: RE: Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

> 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]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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 s...

Message-ID: <89E85E0168AD994693B574C80EDB9C2703286D88@uk-email.terastack.bluearc.com>
Date: Fri, 6 Jan 2006 08:45:08 -0000
From: "Andy Chittenden" <AChittenden@bluearc.com>
To: "Steve Langasek" <vorlon@debian.org>, "Christian Perrier" <bubulle@debian.org>,
	<346069@bugs.debian.org>
Subject: RE: Bug#346069: samba: Segfault in Samba after upgrade to 3.0.21a-1

> 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]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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)
[0x55555573adcd]
Jan  6 08:41:12 boco smbd[27556]:    #1 /usr/sbin/smbd [0x555555727c44]
Jan  6 08:41:12 boco smbd[27556]:    #2 /lib/libc.so.6 [0x2aaaabdacea0]
Jan  6 08:41:12 boco smbd[27556]:    #3
/usr/sbin/smbd(smb_arc4_init+0x37) [0x5555557480d7]
Jan  6 08:41:12 boco smbd[27556]:    #4
/usr/sbin/smbd(ntlmssp_sign_init+0xfa) [0x55555564ea2a]
Jan  6 08:41:12 boco smbd[27556]:    #5 /usr/sbin/smbd [0x55555564b7ee]
Jan  6 08:41:12 boco smbd[27556]:    #6
/usr/sbin/smbd(ntlmssp_update+0x273) [0x55555564a793]
Jan  6 08:41:12 boco smbd[27556]:    #7
/usr/sbin/smbd(auth_ntlmssp_update+0x2a) [0x555555778d1a]
Jan  6 08:41:12 boco smbd[27556]:    #8
/usr/sbin/smbd(reply_sesssetup_and_X+0x8d8) [0x5555555e5c78]
Jan  6 08:41:12 boco smbd[27556]:    #9 /usr/sbin/smbd [0x55555560ece0]
Jan  6 08:41:12 boco smbd[27556]:    #10
/usr/sbin/smbd(process_smb+0x190) [0x55555560f1d0]
Jan  6 08:41:12 boco smbd[27556]:    #11
/usr/sbin/smbd(smbd_process+0x1b7) [0x5555556100d7]
Jan  6 08:41:12 boco smbd[27556]:    #12 /usr/sbin/smbd(main+0x78b)
[0x5555557c42eb]
Jan  6 08:41:12 boco smbd[27556]:    #13
/lib/libc.so.6(__libc_start_main+0xda) [0x2aaaabd994ca]
Jan  6 08:41:12 boco smbd[27556]:    #14 /usr/sbin/smbd [0x5555555abe8a]
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]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:send_smb(762)
Jan  6 08:41:12 boco smbd[27598]:   Error writing 4 bytes to client. -1.
(Connection reset by peer)
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(36)
Jan  6 08:41:13 boco smbd[27597]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(37)
Jan  6 08:41:13 boco smbd[27597]:   INTERNAL ERROR: Signal 11 in pid
27597 (3.0.21a-Debian)
Jan  6 08:41:13 boco smbd[27597]:   Please read the Trouble-Shooting
section of the Samba3-HOWTO
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(39)
Jan  6 08:41:13 boco smbd[27597]:
Jan  6 08:41:13 boco smbd[27597]:   From:
http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(40)
Jan  6 08:41:13 boco smbd[27597]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1544)
Jan  6 08:41:13 boco smbd[27597]:   smb_panic(): calling panic action
[/usr/share/samba/panic-action 27597]
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1552)
Jan  6 08:41:13 boco smbd[27597]:   smb_panic(): action returned status
0
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1554)
Jan  6 08:41:13 boco smbd[27597]:   PANIC: internal error
Jan  6 08:41:13 boco smbd[27597]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1562)
Jan  6 08:41:13 boco smbd[27597]:   BACKTRACE: 15 stack frames:
Jan  6 08:41:13 boco smbd[27597]:    #0 /usr/sbin/smbd(smb_panic2+0x6d)
[0x55555573adcd]
Jan  6 08:41:13 boco smbd[27597]:    #1 /usr/sbin/smbd [0x555555727c44]
Jan  6 08:41:13 boco smbd[27597]:    #2 /lib/libc.so.6 [0x2aaaabdacea0]
Jan  6 08:41:13 boco smbd[27597]:    #3
/usr/sbin/smbd(smb_arc4_init+0x37) [0x5555557480d7]
Jan  6 08:41:13 boco smbd[27597]:    #4
/usr/sbin/smbd(ntlmssp_sign_init+0xfa) [0x55555564ea2a]
Jan  6 08:41:13 boco smbd[27597]:    #5 /usr/sbin/smbd [0x55555564b7ee]
Jan  6 08:41:13 boco smbd[27597]:    #6
/usr/sbin/smbd(ntlmssp_update+0x273) [0x55555564a793]
Jan  6 08:41:13 boco smbd[27597]:    #7
/usr/sbin/smbd(auth_ntlmssp_update+0x2a) [0x555555778d1a]
Jan  6 08:41:13 boco smbd[27597]:    #8
/usr/sbin/smbd(reply_sesssetup_and_X+0x8d8) [0x5555555e5c78]
Jan  6 08:41:13 boco smbd[27597]:    #9 /usr/sbin/smbd [0x55555560ece0]
Jan  6 08:41:13 boco smbd[27597]:    #10
/usr/sbin/smbd(process_smb+0x190) [0x55555560f1d0]
Jan  6 08:41:13 boco smbd[27597]:    #11
/usr/sbin/smbd(smbd_process+0x1b7) [0x5555556100d7]
Jan  6 08:41:13 boco smbd[27597]:    #12 /usr/sbin/smbd(main+0x78b)
[0x5555557c42eb]
Jan  6 08:41:13 boco smbd[27597]:    #13
/lib/libc.so.6(__libc_start_main+0xda) [0x2aaaabd994ca]
Jan  6 08:41:13 boco smbd[27597]:    #14 /usr/sbin/smbd [0x5555555abe8a]
Jan  6 08:41:13 boco smbd[27597]:
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(36)
Jan  6 08:41:13 boco smbd[27615]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(37)
Jan  6 08:41:13 boco smbd[27615]:   INTERNAL ERROR: Signal 11 in pid
27615 (3.0.21a-Debian)
Jan  6 08:41:13 boco smbd[27615]:   Please read the Trouble-Shooting
section of the Samba3-HOWTO
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(39)
Jan  6 08:41:13 boco smbd[27615]:
Jan  6 08:41:13 boco smbd[27615]:   From:
http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/fault.c:fault_report(40)
Jan  6 08:41:13 boco smbd[27615]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1544)
Jan  6 08:41:13 boco smbd[27615]:   smb_panic(): calling panic action
[/usr/share/samba/panic-action 27615]
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1552)
Jan  6 08:41:13 boco smbd[27615]:   smb_panic(): action returned status
0
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1554)
Jan  6 08:41:13 boco smbd[27615]:   PANIC: internal error
Jan  6 08:41:13 boco smbd[27615]: [2006/01/06 08:41:13, 0]
lib/util.c:smb_panic2(1562)
Jan  6 08:41:13 boco smbd[27615]:   BACKTRACE: 15 stack frames:
Jan  6 08:41:13 boco smbd[27615]:    #0 /usr/sbin/smbd(smb_panic2+0x6d)
[0x55555573adcd]
Jan  6 08:41:13 boco smbd[27615]:    #1 /usr/sbin/smbd [0x555555727c44]
Jan  6 08:41:13 boco smbd[27615]:    #2 /lib/libc.so.6 [0x2aaaabdacea0]
Jan  6 08:41:13 boco smbd[27615]:    #3
/usr/sbin/smbd(smb_arc4_init+0x37) [0x5555557480d7]
Jan  6 08:41:13 boco smbd[27615]:    #4
/usr/sbin/smbd(ntlmssp_sign_init+0xfa) [0x55555564ea2a]
Jan  6 08:41:13 boco smbd[27615]:    #5 /usr/sbin/smbd [0x55555564b7ee]
Jan  6 08:41:13 boco smbd[27615]:    #6
/usr/sbin/smbd(ntlmssp_update+0x273) [0x55555564a793]
Jan  6 08:41:13 boco smbd[27615]:    #7
/usr/sbin/smbd(auth_ntlmssp_update+0x2a) [0x555555778d1a]
Jan  6 08:41:13 boco smbd[27615]:    #8
/usr/sbin/smbd(reply_sesssetup_and_X+0x8d8) [0x5555555e5c78]
Jan  6 08:41:13 boco smbd[27615]:    #9 /usr/sbin/smbd [0x55555560ece0]
Jan  6 08:41:13 boco smbd[27615]:    #10
/usr/sbin/smbd(process_smb+0x190) [0x55555560f1d0]
Jan  6 08:41:13 boco smbd[27615]:    #11
/usr/sbin/smbd(smbd_process+0x1b7) [0x5555556100d7]
Jan  6 08:41:13 boco smbd[27615]:    #12 /usr/sbin/smbd(main+0x78b)
[0x5555557c42eb]
Jan  6 08:41:13 boco smbd[27615]:    #13
/lib/libc.so.6(__libc_start_main+0xda) [0x2aaaabd994ca]
Jan  6 08:41:13 boco smbd[27615]:    #14 /usr/sbin/smbd [0x5555555abe8a]
Jan  6 08:41:13 boco smbd[27615]:

--=20
Andy, BlueArc Engineering

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-06:

#7

Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 08:46:15 -0000
From: "Andy Chittenden" <email address hidden>
To: "Steve Langasek" <email address hidden>,
<email address hidden>
Subject: RE: Bug#346069: attaching smb.conf

> ... I strongly recommend converting your system to use=20
> security =3D
> domain instead (with the cooperation of the domain admin).

In the past that hasn't been forthcoming and that's why we've used
security =3D server. I'll try and persuade our new incumbants to create =
me
an account.

--=20
Andy, BlueArc Engineering

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-06:

#8

Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 10:51:52 -0000
From: "Andy Chittenden" <email address hidden>
To: "Steve Langasek" <email address hidden>,
<email address hidden>
Subject: RE: Bug#346069: attaching smb.conf

After much toing and froing, our domain admin managed to create me an
account and samba's now working. Now for the other 45 machines ... :-)

--=20
Andy, BlueArc Engineering

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-06:

#9

Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 18:06:26 +0100
From: Christian Perrier <email address hidden>
To: Andy Chittenden <email address hidden>, <email address hidden>
Subject: Re: Bug#346069: attaching smb.conf

Quoting Andy Chittenden (<email address hidden>):
> After much toing and froing, our domain admin managed to create me an
> account and samba's now working. Now for the other 45 machines ... :-)

Which leaves us with an interesting thing to think about?

Is the bug worth investigating, given that it occurs with a setting
that is not deeply supported?

My opinion: I'm not sure that the Samba Team considers
"security=server" as completely obsolete and, on the other hand, we
seem to have valid debug output so it might be worth sending the whole
stuff to upstream Bugzilla. Comments?

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-07:

#10

Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 23:39:50 -0800
From: Steve Langasek <email address hidden>
To: Christian Perrier <email address hidden>, <email address hidden>
Subject: Re: Bug#346069: attaching smb.conf

--jq0ap7NbKX2Kqbes
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 06, 2006 at 06:06:26PM +0100, Christian Perrier wrote:
> Quoting Andy Chittenden (<email address hidden>):
> > After much toing and froing, our domain admin managed to create me an
> > account and samba's now working. Now for the other 45 machines ... :-)

> Which leaves us with an interesting thing to think about?

> Is the bug worth investigating, given that it occurs with a setting
> that is not deeply supported?

> My opinion: I'm not sure that the Samba Team considers
> "security=3Dserver" as completely obsolete and, on the other hand, we
> seem to have valid debug output so it might be worth sending the whole
> stuff to upstream Bugzilla. Comments?

Sure, it's worth forwarding upstream. I'll continue encouraging people not
to use security=3Dserver, though. :)

--=20
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 address hidden> http://www.debian.org/

--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDv3BGKN6ufymYLloRArYWAKDCfhsZl+QpOGFE1RJo5HR6JLPbywCgii5P
UzJZNwMYp+QwWV4pzrLpgqY=
=hJH9
-----END PGP SIGNATURE-----

--jq0ap7NbKX2Kqbes--

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-07:

#11

Message-ID: <email address hidden>
Date: Sat, 7 Jan 2006 09:06:46 +0100
From: Christian Perrier <email address hidden>
To: <email address hidden>
Subject: Re: Bug#346069: attaching smb.conf

forwarded 346069 https://bugzilla.samba.org/show_bug.cgi?id=3383
thanks

> Sure, it's worth forwarding upstream. I'll continue encouraging people not
> to use security=server, though. :)

Done forwarding, with th log and smb.cofn information.

I actually should find a way to have automatic notices from samba's
bugzilla go to our BTS instead of my own email address....will try but
I'm opened to suggestions.

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2006-01-09:

#12

Download full text (3.7 KiB)

Message-ID: <email address hidden>
Date: Mon, 9 Jan 2006 08:36:41 -0000
From: "Andy Chittenden" <email address hidden>
To: "Christian Perrier" <email address hidden>,
<email address hidden>
Subject: RE: Bug#346069: attaching smb.conf

> Is the bug worth investigating, given that it occurs with a setting
> that is not deeply supported?

Well I spoke too soon saying it no longer occurs: over the weekend I
received a number of emails giving the same backtrace that I reported
originally. In syslog, there are a number of backtraces from winbindd:

Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
lib/util_sock.c:write_data(556)
Jan 7 10:04:38 boco winbindd[6677]: write_data: write failure. Error
=3D Connection reset by peer
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
libsmb/clientgen.c:write_socket(138)
Jan 7 10:04:38 boco winbindd[6677]: write_socket: Error writing 108
bytes to socket 3: ERRNO =3D Connection reset by peer
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
libsmb/clientgen.c:cli_send_smb(168)
Jan 7 10:04:38 boco winbindd[6677]: Error writing 108 bytes to
client. -1 (Connection reset by peer)
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
rpc_client/cli_ds.c:rpccli_ds_enum_domain_trusts(93)
Jan 7 10:04:38 boco winbindd[6677]: PANIC: assert failed at
rpc_client/cli_ds.c(93)
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
lib/util.c:smb_panic2(1544)
Jan 7 10:04:38 boco winbindd[6677]: smb_panic(): calling panic action
[/usr/share/samba/panic-action 6677]
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
lib/util.c:smb_panic2(1552)
Jan 7 10:04:38 boco winbindd[6677]: smb_panic(): action returned
status 0
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
lib/util.c:smb_panic2(1554)
Jan 7 10:04:38 boco winbindd[6677]: PANIC: bad auth level
Jan 7 10:04:38 boco winbindd[6677]: [2006/01/07 10:04:38, 0]
lib/util.c:smb_panic2(1562)
Jan 7 10:04:38 boco winbindd[6677]: BACKTRACE: 12 stack frames:
Jan 7 10:04:38 boco winbindd[6677]: #0
/usr/sbin/winbindd(smb_panic2+0x6d) [0x555555605aed]
Jan 7 10:04:38 boco winbindd[6677]: #1
/usr/sbin/winbindd(rpc_api_pipe_req+0x129) [0x55555566c9a9]
Jan 7 10:04:38 boco winbindd[6677]: #2
/usr/sbin/winbindd(rpccli_ds_enum_domain_trusts+0x19f) [0x555555678dff]
Jan 7 10:04:38 boco winbindd[6677]: #3 /usr/sbin/winbindd
[0x5555555b3814]
Jan 7 10:04:38 boco winbindd[6677]: #4 /usr/sbin/winbindd
[0x5555555a50dc]
Jan 7 10:04:38 boco winbindd[6677]: #5
/usr/sbin/winbindd(winbindd_dual_list_trusted_domains+0x63)
[0x5555555a96b3]
Jan 7 10:04:38 boco winbindd[6677]: #6 /usr/sbin/winbindd
[0x5555555b4e01]
Jan 7 10:04:38 boco winbindd[6677]: #7
/usr/sbin/winbindd(init_child_connection+0x24f) [0x55555559f82f]
Jan 7 10:04:38 boco winbindd[6677]: #8
/usr/sbin/winbindd(rescan_trusted_domains+0xfd) [0x55555559f9ad]
Jan 7 10:04:38 boco winbindd[6677]: #9
/usr/sbin/winbindd(main+0x44b) [0x555555598e2b]
Jan 7 10:04:38 boco winbindd[6677]: #10
/lib/libc.so.6(__libc_start_main+0xda) [0x2aaaab9644ca]
Jan 7 10:04:38 boc...

Affects		Status	Importance	Assigned to	Milestone
	samba (Debian)	Fix Released	Unknown	debbugs #346069
	samba (Ubuntu)	Fix Released	High	Adam Conrad

Ubuntu
samba package

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

Bug Description

Other bug subscribers

Remote bug watches

Changed in samba:
status:	Unconfirmed → Fix Released

Ubuntusamba package

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

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
samba package