Bug#492856: Panic or segfault in Samba

2008-07-29 Thread CORNU Frédéric
Package: samba
Version: 3.0.24-6etch10

A few minutes after server startup and after a few successfull queries, I get :

The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 7391 (/usr/sbin/smbd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred.  The Samba log
files may contain additional information about the problem.

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1213172032 (LWP 7391)]
0xb7c15eee in waitpid () from /lib/tls/libc.so.6
#0  0xb7c15eee in waitpid () from /lib/tls/libc.so.6
#1  0xb7bbd699 in strtold_l () from /lib/tls/libc.so.6
#2  0xb7d4e56d in system () from /lib/tls/libpthread.so.0
#3  0x0822c52a in smb_panic (why=0x8321a5f "internal error") at lib/util.c:1608
#4  0x0821a69a in sig_fault (sig=11) at lib/fault.c:47
#5  
#6  0xb7c85b0b in xdr_uint8_t () from /lib/tls/libc.so.6
#7  0xb7c85453 in xdr_uint8_t () from /lib/tls/libc.so.6
#8  0xb7c135a0 in fgetgrent () from /lib/tls/libc.so.6
#9  0xb7c136dd in initgroups () from /lib/tls/libc.so.6
#10 0x08246b3d in sys_getgrouplist (user=0x8418df0 "hcjava", gid=1001, 
groups=0xb7972008, grpcnt=0xbf84c684) at lib/system_smbd.c:72
#11 0x08246ce0 in getgroups_unix_user (mem_ctx=0x841ad48, 
user=0x8418df0 "hcjava", primary_gid=1001, ret_groups=0xbf84c778, 
p_ngroups=0x841ad50) at lib/system_smbd.c:165
#12 0x081ea4b9 in pdb_default_enum_group_memberships (methods=0x83eb018, 
mem_ctx=0x841ad48, user=0x8418f00, pp_sids=0x841ad4c, pp_gids=0xbf84c778, 
p_num_groups=0x841ad50) at passdb/pdb_interface.c:1441
#13 0x081eb6ef in pdb_enum_group_memberships (mem_ctx=0x841ad48, 
user=0x8418f00, pp_sids=0x841ad4c, pp_gids=0xbf84c778, 
p_num_groups=0x841ad50) at passdb/pdb_interface.c:738
#14 0x0826c971 in make_server_info_sam (server_info=0x83ebca0, 
sampass=0x8418f00) at auth/auth_util.c:588
#15 0x082667ae in check_sam_security (auth_context=0x83702f0, 
my_private_data=0x0, mem_ctx=0x8418cd8, user_info=0x8418680, 
server_info=0x83ebca0) at auth/auth_sam.c:348
#16 0x08266aeb in check_samstrict_security (auth_context=0x83702f0, 
my_private_data=0x0, mem_ctx=0x8418cd8, user_info=0x8418680, 
server_info=0x83ebca0) at auth/auth_sam.c:428
#17 0x08264392 in check_ntlm_password (auth_context=0x83702f0, 
user_info=0x8418680, server_info=0x83ebca0) at auth/auth.c:257
#18 0x0826e93d in auth_ntlmssp_check_password (ntlmssp_state=0x841a420, 
user_session_key=0xbf84cbf4, lm_session_key=0xbf84cbe8)
at auth/auth_ntlmssp.c:111
#19 0x08124b29 in ntlmssp_server_auth (ntlmssp_state=0x841a420, request=
  {data = 0x8417600 "NTLMSSP", length = 182, free = 0x8229c10 
}, reply=0xbf84db70) at libsmb/ntlmssp.c:723
#20 0x0812445f in ntlmssp_update (ntlmssp_state=0x841a420, in=
  {data = 0x8417600 "NTLMSSP", length = 182, free = 0x8229c10 
}, out=0xbf84db70) at libsmb/ntlmssp.c:274
#21 0x0826e68b in auth_ntlmssp_update (auth_ntlmssp_state=0x83ebc98, request=
  {data = 0x8417600 "NTLMSSP", length = 182, free = 0x8229c10 
}, reply=0xbf84db70) at auth/auth_ntlmssp.c:204
#22 0x080c1475 in reply_sesssetup_and_X (conn=0x0, inbuf=0xb7a33008 "", 
outbuf=0xb79bd008 "", length=360, bufsize=131072) at smbd/sesssetup.c:625
#23 0x080ea674 in switch_message (type=115, inbuf=0xb7a33008 "", 
outbuf=0xb79bd008 "", size=360, bufsize=131072) at smbd/process.c:992
#24 0x080eb83d in smbd_process () at smbd/process.c:1019
#25 0x082c384f in main (argc=1, argv=0x68) at smbd/server.c:1024


...with a few dozen smbd processes eating up 100% cpu.

A fix for this is :
===

1) stopping samba deamon : /etc/init.d/samba stop
2) killing all smbd processes with 'kill -9 ...'. 'killall smbd' doesn't will 
them.
3) starting samba deamon : /etc/init.d/samba start


More infos on the system :
==

Libc6 version : 2.3.6.ds1-13etch7
Linux SRV025 2.6.20.1-1-686 #1 SMP Sun Mar 4 12:44:55 UTC 2007 i686 GNU/Linux


Content of /etc/samba/smb.conf :


#
# 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 com

Bug#492856: Panic or segfault in Samba

2008-07-29 Thread Steve Langasek
tags 492856 moreinfo unreproducible
thanks

On Tue, Jul 29, 2008 at 02:47:08PM +0200, CORNU Frédéric wrote:
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1213172032 (LWP 7391)]
> 0xb7c15eee in waitpid () from /lib/tls/libc.so.6
> #0  0xb7c15eee in waitpid () from /lib/tls/libc.so.6
> #1  0xb7bbd699 in strtold_l () from /lib/tls/libc.so.6
> #2  0xb7d4e56d in system () from /lib/tls/libpthread.so.0
> #3  0x0822c52a in smb_panic (why=0x8321a5f "internal error") at 
> lib/util.c:1608
> #4  0x0821a69a in sig_fault (sig=11) at lib/fault.c:47
> #5  
> #6  0xb7c85b0b in xdr_uint8_t () from /lib/tls/libc.so.6
> #7  0xb7c85453 in xdr_uint8_t () from /lib/tls/libc.so.6
> #8  0xb7c135a0 in fgetgrent () from /lib/tls/libc.so.6
> #9  0xb7c136dd in initgroups () from /lib/tls/libc.so.6
> #10 0x08246b3d in sys_getgrouplist (user=0x8418df0 "hcjava", gid=1001, 
> groups=0xb7972008, grpcnt=0xbf84c684) at lib/system_smbd.c:72

This is a rather strange failure mode; it doesn't appear to be a bug in
Samba at all, this is glibc that's crashing.

Can you please send us:

- the contents of /etc/nsswitch.conf
- the output of 'groups hcjava'

> A fix for this is :
> ===

> 1) stopping samba deamon : /etc/init.d/samba stop
> 2) killing all smbd processes with 'kill -9 ...'. 'killall smbd' doesn't will 
> them.
> 3) starting samba deamon : /etc/init.d/samba start

Does this /fix/ the problem, or does it just reset it until the next time?

> # Change this to the workgroup/NT-domain name your Samba server will part of
>workgroup = etudes.groupehelice.local

Not that this should be related, but this is not a proper 'workgroup' name -
this appears to be an AD realm name instead, so this is probably not working
as you intended.

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



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



Bug#492856: Panic or segfault in Samba

2008-08-06 Thread Steve Langasek
tags 492856 -moreinfo
reassign 492856 glibc
thanks

On Wed, Jul 30, 2008 at 09:57:08AM +0200, CORNU Frédéric wrote:
> >On Tue, Jul 29, 2008 at 02:47:08PM +0200, CORNU Frédéric wrote:
> >> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> >> [Thread debugging using libthread_db enabled]
> >> [New Thread -1213172032 (LWP 7391)]
> >> 0xb7c15eee in waitpid () from /lib/tls/libc.so.6
> >> #0  0xb7c15eee in waitpid () from /lib/tls/libc.so.6
> >> #1  0xb7bbd699 in strtold_l () from /lib/tls/libc.so.6
> >> #2  0xb7d4e56d in system () from /lib/tls/libpthread.so.0
> >> #3  0x0822c52a in smb_panic (why=0x8321a5f "internal error") at 
> >> lib/util.c:1608
> >> #4  0x0821a69a in sig_fault (sig=11) at lib/fault.c:47
> >> #5  
> >> #6  0xb7c85b0b in xdr_uint8_t () from /lib/tls/libc.so.6
> >> #7  0xb7c85453 in xdr_uint8_t () from /lib/tls/libc.so.6
> >> #8  0xb7c135a0 in fgetgrent () from /lib/tls/libc.so.6
> >> #9  0xb7c136dd in initgroups () from /lib/tls/libc.so.6
> >> #10 0x08246b3d in sys_getgrouplist (user=0x8418df0 "hcjava", gid=1001, 
> >> groups=0xb7972008, grpcnt=0xbf84c684) at lib/system_smbd.c:72

> >This is a rather strange failure mode; it doesn't appear to be a bug in
> >Samba at all, this is glibc that's crashing.

> >Can you please send us:

> >- the contents of /etc/nsswitch.conf
> >- the output of 'groups hcjava'

> Content of /etc/nsswitch.conf :
> ===

> # /etc/nsswitch.conf
> #
> # Example configuration of GNU Name Service Switch functionality.
> # If you have the `glibc-doc' and `info' packages installed, try:
> # `info libc "Name Service Switch"' for information about this file.

> passwd: compat
> group:  compat
> shadow: compat



> Output of 'groups hcjava' :
> ===
> hcjava : hcjava

Ok; between this and the backtrace, I don't see any reason to think that
this is a Samba bug as opposed to a glibc bug.  Reassigning the report.

> >Does this /fix/ the problem, or does it just reset it until the next time?

> This makes samba work flawlessly until machine is rebooted (wich occurs too
> often for me, thanx to buggy server-room air coolers)

Hrm, I would almost suspect that the samba failures were themselves a
hardware issue, except that there's no reason for the failure to be
repeatable at this particular point...

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



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