smbd panic action with yield_connection name=0x0

[Amin Akbarali]

Binary package hint: samba

Thread debugging using libthread_db enabled]
[New Thread 0x7f857ebbf710 (LWP 30992)]
0x00007f857b7688f5 in waitpid () from /lib/libc.so.6
#0 0x00007f857b7688f5 in waitpid () from /lib/libc.so.6
#1 0x00007f857b7002d1 in ?? () from /lib/libc.so.6
#2 0x00007f857eda57a8 in smb_panic (why=<value optimized out>)
    at lib/util.c:1679
#3 0x00007f857ed92be7 in sig_fault (sig=11) at lib/fault.c:46
#4 <signal handler called>
#5 0x00007f857ed875c1 in rep_strlcpy (d=0x7fff871e3f58 "", s=0x0, bufsize=256)
    at lib/replace/replace.c:64
#6 0x00007f857edb2fb9 in connections_fetch_entry (mem_ctx=0x0,
    conn=<value optimized out>, name=0x0) at lib/conn_tdb.c:65
#7 0x00007f857ec98171 in yield_connection (conn=0x7f857f555d90, name=0x0)
    at smbd/connection.c:33
#8 0x00007f857ecbcc4c in close_cnum (conn=0x7f857f555d90, vuid=0)
    at smbd/service.c:1328
#9 0x00007f857ec9d795 in conn_close_all () at smbd/conn.c:174
#10 0x00007f857ec878b7 in exit_server_common (how=SERVER_EXIT_NORMAL,
    reason=0x0) at smbd/server.c:917
#11 0x00007f857ec87a96 in exit_server_cleanly (
    explanation=<value optimized out>) at smbd/server.c:985
#12 0x00007f857ec89cd7 in main (argc=<value optimized out>, argv=0x2)
    at smbd/server.c:1516
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]

Here's the smdb.conf file;

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

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

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

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
  security = share

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<email address hidden> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
         SO_RCVBUF=8192 SO_SNDBUF=8192
   socket options = TCP_NODELAY

# 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' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
usershare owner only = false

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

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

# 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 = 0700

# 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 = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
   comment = All Printers
   browseable = yes
   path = /var/spool/samba
   printable = yes
   guest ok = yes
   read only = yes
   create mask = 0700
   security = guest
   public = yes
   writeable = yes
   use client driver = yes
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = yes
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = 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

[Thierry Carrez (ttx)]

What version of samba packages are used ?
Please give the output of:
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba

A little more context information could help: What are you using Samba for ? Just user shares ? Can you reproduce the issue or is it happening randomly ? Is this a new problem since you upgraded your version of Ubuntu ?

[Amin Akbarali (aakbaral)]

Here's the info you requested;
____________________________________
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
libsmbclient 2:3.3.2-1ubuntu3 samba install ok installed
libwbclient0 2:3.3.2-1ubuntu3 samba install ok installed
samba 2:3.3.2-1ubuntu3 install ok installed
samba-common 2:3.3.2-1ubuntu3 samba install ok installed
samba-dbg 2:3.3.2-1ubuntu3 samba install ok installed
samba4 4.0.0~alpha6-1ubuntu1 deinstall ok config-files
samba4-common 4.0.0~alpha6-1ubuntu1 samba4 deinstall ok config-files
smbfs 2:3.3.2-1ubuntu3 samba install ok installed
winbind 2:3.3.2-1ubuntu3 samba install ok installed
______________________________________

It seems to happen when the Server is rebooted or smbd is re-started and
the Win client has not re-connected and sends a print job, that creates
the problem. The client re-connects when you do a file operation on
samba shares, then printing works successfully after that.

It is used as a Home Office Server with Print and File Services for
Windows (2 XP and 1 Vista) Laptops, using exim4 and ined-ipop as an
e-mail server for the domain infostrada-systems.com. Also using it to
browse the Net with Firefox, to convert DVD's to mpeg with FFMPEG, using
VLC Player to view movies and listen to music. Wine is installed to
occasionally run Quicken 98 Home and Business, all seems to work fine.
Yeah it's quite a workhorse. The hardware is AMD Athlon64 3300+
therefore seems to be running 64bit version of OS.

There are 2 printers installed an HP OfficeJet 6310 AIO and an old
Minolta QMS PagePro 1250W BW Laser, both are working fine and printing
Test pages from the Ubuntu Server and Win clients successfully.

There is an entry in fstab to load the memory card share on the
OfficeJet printer using smbfs, it's working fine.

The latest version of Ubuntu is my first install, never upgraded it.
I've been installing Updates automatically as recommended by the System.

One of the laptops it is a corporate laptop therefore locked down, when
at the office or VPN, I connect to the Ubuntu server using ssh, and
tunnelling port 139 for windows shares to the localhost:139

I was using WXPP prior but it was grinding to a halt and having to
reboot daily.

Therefore I decided to give Linux a shot, Ubuntu was recommend by
friends. Installed Ubuntu with wubi (Windows) tool, and now it is the
default OS on reboot. Am very happy with Ubuntu am planning to remove
Windows from that machine.

Thanks,
Amin

Thierry Carrez wrote:
> What version of samba packages are used ?
> Please give the output of:
> dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
>
> A little more context information could help: What are you using Samba
> for ? Just user shares ? Can you reproduce the issue or is it happening
> randomly ? Is this a new problem since you upgraded your version of
> Ubuntu ?
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
>

[Harald (hdmuell)]

Thierry,

I have a similar problem. I get mails like:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 6695 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 6695.
It may have died unexpectedly, or you may not have permission to debug
the process.

I get the mails while file transfers from an XP-Box to the Samba server occur.
I don't use the cups server to print from the XP-Box.

I have also problems to connect with a Ubuntu Remix Netbook, it cannot connect to the Samba server and it cannot see the share.

Here is the info you requested from Armin:

libsmbclient 2:3.3.2-1ubuntu3 samba install ok installed
libwbclient0 2:3.3.2-1ubuntu3 samba install ok installed
samba 2:3.3.2-1ubuntu3 install ok installed
samba-common 2:3.3.2-1ubuntu3 samba install ok installed
smbclient 2:3.3.2-1ubuntu3 samba install ok installed
smbfs 2:3.3.2-1ubuntu3 samba install ok installed
winbind 2:3.3.2-1ubuntu3 samba install ok installed

uname -a: Linux hh-2core 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 i686 GNU/Linux

please let me know if you need further details.

thanks,

Harald

[Thierry Carrez (ttx)]

@Amin:
From your trace it appears that it's a crash during normal shutdown of the Samba server (exit_server_common (how=SERVER_EXIT_NORMAL, reason=0x0)). Would you have Samba server logs corresponding to the issue ? Reproducing the issue with "log level = 3" in your smb.conf might give more information in your logs.

@Harald:
Is it the same backtrace ? In particular calling yield_connection with name=0x0 ?

[Amin Akbarali (aakbaral)]

Hi Thierry,

Thanks for looking into this issue. I've encountered this several times
since our last e-mail exchange, but I managed to find some logs in
/var/log/samba, am attaching the file here.

The last incident was on June 20 16:06:21 I've also attached the text of the
panic e-mail from that incident.

I noticed some permissions errors in the log file, so I attempted a fix by
putting the user nobody in the same group as sambashare and now it seems I'm
not getting the panic e-mails again. So I wonder if that was the issue?

Basically the Ubuntu computer is a unprotected File and Printer Server in a
private network in my home office behind a NAT Firewall therefore I'm not
too concerned about security.

Thanks again,
Amin

On Tue, Jun 23, 2009 at 5:58 AM, Thierry Carrez
<email address hidden>wrote:

> @Amin:
> >From your trace it appears that it's a crash during normal shutdown of the
> Samba server (exit_server_common (how=SERVER_EXIT_NORMAL, reason=0x0)).
> Would you have Samba server logs corresponding to the issue ? Reproducing
> the issue with "log level = 3" in your smb.conf might give more information
> in your logs.
>
> @Harald:
> Is it the same backtrace ? In particular calling yield_connection with
> name=0x0 ?
>
> --
> The Samba 'panic action' script, /usr/share/samba/panic-action, was called
> for PID 30992 (/usr/sbin/smbd)
> https://bugs.launchpad.net/bugs/388483
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “samba” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: samba
>
> Thread debugging using libthread_db enabled]
> [New Thread 0x7f857ebbf710 (LWP 30992)]
> 0x00007f857b7688f5 in waitpid () from /lib/libc.so.6
> #0 0x00007f857b7688f5 in waitpid () from /lib/libc.so.6
> #1 0x00007f857b7002d1 in ?? () from /lib/libc.so.6
> #2 0x00007f857eda57a8 in smb_panic (why=<value optimized out>)
> at lib/util.c:1679
> #3 0x00007f857ed92be7 in sig_fault (sig=11) at lib/fault.c:46
> #4 <signal handler called>
> #5 0x00007f857ed875c1 in rep_strlcpy (d=0x7fff871e3f58 "", s=0x0,
> bufsize=256)
> at lib/replace/replace.c:64
> #6 0x00007f857edb2fb9 in connections_fetch_entry (mem_ctx=0x0,
> conn=<value optimized out>, name=0x0) at lib/conn_tdb.c:65
> #7 0x00007f857ec98171 in yield_connection (conn=0x7f857f555d90, name=0x0)
> at smbd/connection.c:33
> #8 0x00007f857ecbcc4c in close_cnum (conn=0x7f857f555d90, vuid=0)
> at smbd/service.c:1328
> #9 0x00007f857ec9d795 in conn_close_all () at smbd/conn.c:174
> #10 0x00007f857ec878b7 in exit_server_common (how=SERVER_EXIT_NORMAL,
> reason=0x0) at smbd/server.c:917
> #11 0x00007f857ec87a96 in exit_server_cleanly (
> explanation=<value optimized out>) at smbd/server.c:985
> #12 0x00007f857ec89cd7 in main (argc=<value optimized out>, argv=0x2)
> at smbd/server.c:1516
> The program is running. Quit anyway (and detach it)? (y or n) [answered Y;
> input not from terminal]
>
> Here's the smdb.conf file;
>
> #
> # Sample configuration file for the Samba suite for Debian GNU/Linux.
> #
> #
> # This is the main Samba configuration file. You should read the
> # smb.conf(5) manual page in ...

[Thierry Carrez (ttx)]

Please set "log level = 3" in your smb.conf and resend the corresponding log files if you can reproduce the issue.

[Darren (darren-dcook)]

I'm also having this problem.
Samba is running on Ubuntu 8.04, and I when either of two windows XP clients connects it sends me this email:
  The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 9866 ().
  This means there was a problem with the program, such as a segfault. However, the executable could not be found for process 9866. It may have died unexpectedly, or you may not have permission to debug the process.

Connecting to the samba share from another Ubuntu machine does not cause the problem.

It is just a simple read/write file share, with guest users allowed. No printer sharing yet.

I've done a bit of experimentation and just booting windows doesn't cause it (I have the file share set to mount automatically). But opening My Computer (i.e. so I can see the share, and can see free disk space) does. I.e. I do not need to double-click the share and actually see the files inside to trigger the alert.

The alert just appears to be noise - once I open the folder I can see and use all the files without any problem.

The problem is consistent and repeatable. I set "log level = 3" and my /var/log/samba directory is full of various log files, some of them rather large (e.g. 600K). I seem to have one log file per client machine, as well as log.smbd, log.nmbd, a couple of log.winbind* files, and a couple of log.wb-* files.
Which of those do you want to see? I'd rather send it directly to an interested developer rather than post them here, as I'm not knowledgeable about what privacy issues there may be.
Or if you give me a hint of what to look for, I'm happy to trawl through them a bit.

[Harald (hdmuell)]

@ Thierry

I cannot trigger when the error occurs, so my logfile is already too old (time stamp), when I get the mail. It happens probably while the windows machine writes to the samba server.

I couldn't find anything suspect in the logfile for the Windows-machine.

@ all

I had different workgroup names in samba and in windows, since I changed it in windows to the same name, the problem did not reappear. Does anyone having the same problem have two different workgroup names?

[Darren (darren-dcook)]

Harald asked: "different workgroup names?"
My only change from a default samba install is adding the log level line. smb.conf says workgroup is MSHOME.
On the Windows side I just tracked it down and it is called "WORKGROUP".
I've just changed the workgroup to WORKGROUP in smb.conf, restarted samba, rebooted windows, and... the panic email still arrives.
Oh well, it was worth a try :-).

[Thierry Carrez (ttx)]

@Darren: the panic happens on samba stop so you'd get the email only after you reboot. Please stay with the right setup (same workgroup names) and let me know if you get any new panics. If you can reproduce it, please set "log level = 3" in your smb.conf and send the corresponding log files the next time you get a panic.
Thanks

[Chuck Short (zulcss)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

https://bugzilla.samba.org/show_bug.cgi?id=6724

[XabiX (xdealmeida)]

Any news on this bug? is there any known workaround?

Thanks
XabiX

duplicate bug:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/596945

[Serge Hallyn (serge-hallyn)]

Hi,

We are wondering whether this may have been fixed upstream. Are you still seeing this error? If so, please tell us which Ubuntu release you are currently on, and your mysql version.

[Manolo Cabezabolo (hphrey)]

Hi Serge,

No. The error is not happening anymore.

Regards.
Jorge.

On Thu, Apr 14, 2011 at 5:14 PM, Serge Hallyn <email address hidden>wrote:

> Hi,
>
> We are wondering whether this may have been fixed upstream. Are you
> still seeing this error? If so, please tell us which Ubuntu release you
> are currently on, and your mysql version.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (686627).
> https://bugs.launchpad.net/bugs/388483
>
> Title:
> smbd panic action with yield_connection name=0x0
>
> Status in Samba:
> Confirmed
> Status in “samba” package in Ubuntu:
> Triaged
> Status in “samba” package in Debian:
> New
>
> Bug description:
> Binary package hint: samba
>
> Thread debugging using libthread_db enabled]
> [New Thread 0x7f857ebbf710 (LWP 30992)]
> 0x00007f857b7688f5 in waitpid () from /lib/libc.so.6
> #0 0x00007f857b7688f5 in waitpid () from /lib/libc.so.6
> #1 0x00007f857b7002d1 in ?? () from /lib/libc.so.6
> #2 0x00007f857eda57a8 in smb_panic (why=<value optimized out>)
> at lib/util.c:1679
> #3 0x00007f857ed92be7 in sig_fault (sig=11) at lib/fault.c:46
> #4 <signal handler called>
> #5 0x00007f857ed875c1 in rep_strlcpy (d=0x7fff871e3f58 "", s=0x0,
> bufsize=256)
> at lib/replace/replace.c:64
> #6 0x00007f857edb2fb9 in connections_fetch_entry (mem_ctx=0x0,
> conn=<value optimized out>, name=0x0) at lib/conn_tdb.c:65
> #7 0x00007f857ec98171 in yield_connection (conn=0x7f857f555d90, name=0x0)
> at smbd/connection.c:33
> #8 0x00007f857ecbcc4c in close_cnum (conn=0x7f857f555d90, vuid=0)
> at smbd/service.c:1328
> #9 0x00007f857ec9d795 in conn_close_all () at smbd/conn.c:174
> #10 0x00007f857ec878b7 in exit_server_common (how=SERVER_EXIT_NORMAL,
> reason=0x0) at smbd/server.c:917
> #11 0x00007f857ec87a96 in exit_server_cleanly (
> explanation=<value optimized out>) at smbd/server.c:985
> #12 0x00007f857ec89cd7 in main (argc=<value optimized out>, argv=0x2)
> at smbd/server.c:1516
> The program is running. Quit anyway (and detach it)? (y or n) [answered
> Y; input not from terminal]
>
> Here's the smdb.conf file;
>
> #
> # Sample configuration file for the Samba suite for Debian GNU/Linux.
> #
> #
> # This is the main Samba configuration file. You should read the
> # smb.conf(5) manual page in order to understand the options listed
> # here. Samba has a huge number of configurable options most of which
> # are not shown in this example
> #
> # Some options that are often worth tuning have been included as
> # commented-out examples in this file.
> # - When such options are commented with ";", the proposed setting
> # differs from the default Samba behaviour
> # - When commented with "#", the proposed setting is the default
> # behaviour of Samba but the option is considered important
> # enough to be mentioned here
> #
> # NOTE: Whenever you modify this file you should run the command
> # "testparm" to check that you have not made any basic syntactic
> # errors.
> # A well-established practice is to name the original file
> # "smb.conf.master" and create the "real" c...

[Derek Chen-Becker (dchenbecker)]

I haven't seen it anymore.

[Matthew Morgan (lytithwyn)]

I'm having this bug in Lucid Server x86_64. The only things I've done in smb.conf that might be considered different are the "socket options" line (which I've never heard anyone say causes crashes), and the few lines that kill print support. I don't have CUPS installed on this server and I was getting strange hangs during file transfers to windows machines accompanied by CUPS connection timeout messages in the client logs. Disabling printing fixed that part.

Everything is up to date except the kernel which is 2.6.32-28-server #55-Ubuntu SMP Mon Jan 10 23:57:16 UTC 2011 x86_64 GNU/Linux. If you guys think updating the kernel will fix it then I will; I just hadn't bothered to take the server down for a kernel upgrade when I didn't think it had much to do with it.

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Server name
  netbios name = server1

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

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

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

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

...

[Matthew Morgan (lytithwyn)]

I have more information on this bug. I have so far:

* installed cups
* gotten rid of the extra no-printing configuration in my smb.conf
* removed the socket options line I'd added
* installed samba from source

I still get the bug even built from source directly from the v3-5-stable branch of samba's git repo. I'm wondering if the problem is related to a library that samba is linking to since I can't find any mention of this bug online outside of a debian-based distribution. I've attached my new samba configuration. Also, here is a sample of the samba 3.5 version of the crash report. If anyone wants client session logs I can get those too.

[Thread debugging using libthread_db enabled]
0x00007f6f60974f7e in waitpid () from /lib/libc.so.6
#0 0x00007f6f60974f7e in waitpid () from /lib/libc.so.6
#1 0x00007f6f6090c7e9 in ?? () from /lib/libc.so.6
#2 0x00007f6f6399c9c8 in smb_panic (why=0x7f6f63fc9e60 "internal error")
    at lib/util.c:1471
#3 0x00007f6f63985085 in fault_report (sig=11) at lib/fault.c:52
#4 0x00007f6f6398509a in sig_fault (sig=11) at lib/fault.c:75
#5 <signal handler called>
#6 0x00007f6f6094e052 in ?? () from /lib/libc.so.6
#7 0x00007f6f6395e04a in rep_strlcpy (d=0x7fff512f17a8 "", s=0x0, bufsize=256)
    at ../lib/replace/replace.c:69
#8 0x00007f6f639aefdb in connections_fetch_entry (mem_ctx=0x0,
    conn=0x7f6f654aa470, name=0x0) at lib/conn_tdb.c:65
#9 0x00007f6f635de917 in yield_connection (conn=0x7f6f654aa470, name=0x0)
    at smbd/connection.c:33
#10 0x00007f6f636927a6 in close_cnum (conn=0x7f6f654aa470, vuid=100)
    at smbd/service.c:1256
#11 0x00007f6f635ea8bd in conn_close_all (sconn=0x7f6f653f74f0)
    at smbd/conn.c:185
#12 0x00007f6f63e9ee31 in exit_server_common (how=SERVER_EXIT_NORMAL,
    reason=0x7f6f63ecde28 "failed to receive smb request") at smbd/server.c:848
#13 0x00007f6f63e9f211 in exit_server_cleanly (
    explanation=0x7f6f63ecde28 "failed to receive smb request")
    at smbd/server.c:927