Bug#350598: Segfault in samba
severity 350598 important forwarded 350598 https://bugzilla.samba.org/show_bug.cgi?id=3383 merge 350598 346069 thanks On Mon, Jan 30, 2006 at 06:27:56PM -0500, Ambrose Li wrote: On Mon, Jan 30, 2006 at 09:44:47PM +0100, Christian Perrier wrote: Do you have any mor einformation about what is exactly done on the server when the crash happens? Does this happens when clients are doing some action and, if so, which action? I am not sure. It just started a few days ago, roughly coinciding with my dist-upgrade and adding an XP box to the network. I don't know if the crash has to do with either of these. The crashes just happen without clients doing anything obvious. They usually come in batches (e.g., a dozen crashes in a short time, and then it stops for a long while). # 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/ServerType.html in the samba-doc # package for details. ; security = user security = server password server = X X security = server is a bad idea security-wise, and is weakly supported upstream. I highly recommend moving to domain-based security instead. At any rate, this appears to be the same bug as bug #346069, which is reported fixed upstream. Thanks, -- 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
Bug#350598: Segfault in samba
On Tue, Jan 31, 2006 at 06:48:32AM -0800, Steve Langasek wrote: security = server is a bad idea security-wise, and is weakly supported upstream. I highly recommend moving to domain-based security instead. Thanks for the hint. I used security = server only because I had used security = domain a few years ago and it gave me lots of headaches. I guess I'll have to switch to that now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#350598: Segfault in samba
Package: samba Version: 3.0.21a-4 Severity: normal I got about a couple of dozens of emails about segfault in samba and was asked to report it here. According to apt-get dist-upgrade, my system (unstable) should be up-to-date. I have installed the samba-dbg package as instructed, but the stack trace does not seem to be any different. It looks like this: - cut here --- 8 The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 14677 (/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. Then 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. 0x0034fe88 in ?? () #0 0x0034fe88 in ?? () #1 0x003dcff4 in ?? () #2 0x002fcd40 in __FUNCTION__.38748 () #3 0x3958 in ?? () #4 0xbfffcae8 in ?? () #5 0x in ?? () - cut here --- 8 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.28-ow1 Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5 (charmap=BIG5) Versions of packages samba depends on: ii debconf [debc 1.4.69 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-12 GNU C Library: Shared libraries an ii libcomerr21.38+1.39-WIP-2005.12.31-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-14 Linux Standard Base 3.0 init scrip ii netbase 4.24 Basic TCP/IP networking system ii samba-common 3.0.21a-4 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/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]
Bug#350598: Segfault in samba
Quoting Ambrose Li ([EMAIL PROTECTED]): Package: samba Version: 3.0.21a-4 Severity: normal I got about a couple of dozens of emails about segfault in samba and was asked to report it here. Do you have any mor einformation about what is exactly done on the server when the crash happens? Does this happens when clients are doing some action and, if so, which action? Do you have traces in the logs (possible by raising the log leve to 3)? Can you also please send your smb.conf file? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#350598: Segfault in samba
On Mon, Jan 30, 2006 at 09:44:47PM +0100, Christian Perrier wrote:
Do you have any mor einformation about what is exactly done on the
server when the crash happens? Does this happens when clients are
doing some action and, if so, which action?
I am not sure. It just started a few days ago, roughly coinciding with
my dist-upgrade and adding an XP box to the network. I don't know if
the crash has to do with either of these.
The crashes just happen without clients doing anything obvious. They
usually come in batches (e.g., a dozen crashes in a short time, and
then it stops for a long while).
Do you have traces in the logs (possible by raising the log leve to 3)?
Can you also please send your smb.conf file?
I'll raise the log level see what happens tomorrow, in the meantime
my smb.conf is below (with workgroup and server addresses removed):
cut here - 8 ---
#
# 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
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command
# testparm to check that you have not many any basic syntactic
# errors.
#
#=== Global Settings ===
[global]
## Browsing/Identification ###
netbios aliases = sugar
hosts allow = 172.17.1. 127.
username map = /etc/samba/smbusers
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup =
# server string is the equivalent of the NT Description field
# server string = %h server (Samba %v)
server string = Admin office, Debian Sid test machine #1 (Unix)
# 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
wins server = 172.17.1.XX
# 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
Debugging/Accounting
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Put a capping on the size of the log files (in Kb).
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/ServerType.html in the samba-doc
# package for details.
; security = user
security = server
password server = X X
# 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 guest
obey pam restrictions = yes
; guest account = nobody
invalid users = root
# 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 = no
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Augustin Luton [EMAIL PROTECTED] for
# sending the correct chat script for the passwd program in Debian Potato).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n .
# 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 = no
## Printing ##
# If you want to automatically load your printer list rather
# than setting them up individually then you'll
