[Bug 388483] Re: smbd panic action with yield_connection name=0x0
** Changed in: samba (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/388483 Title: smbd panic action with yield_connection name=0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/388483/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
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] 0x7f6f60974f7e in waitpid () from /lib/libc.so.6 #0 0x7f6f60974f7e in waitpid () from /lib/libc.so.6 #1 0x7f6f6090c7e9 in ?? () from /lib/libc.so.6 #2 0x7f6f6399c9c8 in smb_panic (why=0x7f6f63fc9e60 internal error) at lib/util.c:1471 #3 0x7f6f63985085 in fault_report (sig=11) at lib/fault.c:52 #4 0x7f6f6398509a in sig_fault (sig=11) at lib/fault.c:75 #5 signal handler called #6 0x7f6f6094e052 in ?? () from /lib/libc.so.6 #7 0x7f6f6395e04a in rep_strlcpy (d=0x7fff512f17a8 , s=0x0, bufsize=256) at ../lib/replace/replace.c:69 #8 0x7f6f639aefdb in connections_fetch_entry (mem_ctx=0x0, conn=0x7f6f654aa470, name=0x0) at lib/conn_tdb.c:65 #9 0x7f6f635de917 in yield_connection (conn=0x7f6f654aa470, name=0x0) at smbd/connection.c:33 #10 0x7f6f636927a6 in close_cnum (conn=0x7f6f654aa470, vuid=100) at smbd/service.c:1256 #11 0x7f6f635ea8bd in conn_close_all (sconn=0x7f6f653f74f0) at smbd/conn.c:185 #12 0x7f6f63e9ee31 in exit_server_common (how=SERVER_EXIT_NORMAL, reason=0x7f6f63ecde28 failed to receive smb request) at smbd/server.c:848 #13 0x7f6f63e9f211 in exit_server_cleanly ( explanation=0x7f6f63ecde28 failed to receive smb request) at smbd/server.c:927 ** Attachment added: smb.conf https://bugs.launchpad.net/debian/+source/samba/+bug/388483/+attachment/2153574/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/388483 Title: smbd panic action with yield_connection name=0x0 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
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
# 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 = user
# 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
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
I haven't seen it anymore. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/388483 Title: smbd panic action with yield_connection name=0x0 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
** Changed in: samba (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/388483 Title: smbd panic action with yield_connection name=0x0 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
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 member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/388483 Title: smbd panic action with yield_connection name=0x0 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 388483] Re: smbd panic action with yield_connection name=0x0
Hi Serge, No. The error is not happening anymore. Regards. Jorge. On Thu, Apr 14, 2011 at 5:14 PM, Serge Hallyn 388...@bugs.launchpad.netwrote: 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)] 0x7f857b7688f5 in waitpid () from /lib/libc.so.6 #0 0x7f857b7688f5 in waitpid () from /lib/libc.so.6 #1 0x7f857b7002d1 in ?? () from /lib/libc.so.6 #2 0x7f857eda57a8 in smb_panic (why=value optimized out) at lib/util.c:1679 #3 0x7f857ed92be7 in sig_fault (sig=11) at lib/fault.c:46 #4 signal handler called #5 0x7f857ed875c1 in rep_strlcpy (d=0x7fff871e3f58 , s=0x0, bufsize=256) at lib/replace/replace.c:64 #6 0x7f857edb2fb9 in connections_fetch_entry (mem_ctx=0x0, conn=value optimized out, name=0x0) at lib/conn_tdb.c:65 #7 0x7f857ec98171 in yield_connection (conn=0x7f857f555d90, name=0x0) at smbd/connection.c:33 #8 0x7f857ecbcc4c in close_cnum (conn=0x7f857f555d90, vuid=0) at smbd/service.c:1328 #9 0x7f857ec9d795 in conn_close_all () at smbd/conn.c:174 #10 0x7f857ec878b7 in exit_server_common (how=SERVER_EXIT_NORMAL, reason=0x0) at smbd/server.c:917 #11 0x7f857ec87a96 in exit_server_cleanly ( explanation=value optimized out) at smbd/server.c:985 #12 0x7f857ec89cd7 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
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
** Changed in: samba Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/388483 Title: smbd panic action with yield_connection name=0x0 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
Any news on this bug? is there any known workaround? Thanks XabiX duplicate bug: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/596945 -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
** Changed in: samba Status: Unknown = Confirmed -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
** Changed in: samba (Debian) Status: Unknown = New -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
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 ** Bug watch added: Samba Bugzilla #6724 https://bugzilla.samba.org/show_bug.cgi?id=6724 ** Changed in: samba (Ubuntu) Status: Incomplete = Triaged -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
@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 -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
@ 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? -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
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 :-). -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
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. -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 388483] Re: smbd panic action with yield_connection name=0x0
** Summary changed: - The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 30992 (/usr/sbin/smbd) + smbd panic action with yield_connection name=0x0 -- smbd panic action with yield_connection name=0x0 https://bugs.launchpad.net/bugs/388483 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
