forwarded 351448 https://bugzilla.samba.org/show_bug.cgi?id=3383
merge 351448 346045
thanks

On Sat, Feb 04, 2006 at 11:42:04PM +0100, Francois Lorrain wrote:

> The following message is shown when a crash occurs :
>   ===============================================================
>   [2006/02/04 23:25:25, 0] lib/fault.c:fault_report(37)
>     INTERNAL ERROR: Signal 11 in pid 3822 (3.0.21a)
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
>   [2006/02/04 23:25:25, 0] lib/fault.c:fault_report(39)

>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2006/02/04 23:25:25, 0] lib/fault.c:fault_report(40)
>   ===============================================================
>   [2006/02/04 23:25:25, 0] lib/util.c:smb_panic2(1544)
> smb_panic(): calling panic action [/usr/share/samba/panic-action 3822]
>     [2006/02/04 23:25:27, 0] lib/util.c:smb_panic2(1552)
> smb_panic(): action returned status 0
>     [2006/02/04 23:25:27, 0] lib/util.c:smb_panic2(1554)
>     PANIC: internal error
> [2006/02/04 23:25:27, 0] lib/util.c:smb_panic2(1562)
>   BACKTRACE: 15 stack frames:
>  #0 /usr/sbin/smbd(smb_panic2+0x8c) [0x80204d2c]
>  #1 /usr/sbin/smbd(smb_panic+0x1a) [0x80204f8a]
>  #2 /usr/sbin/smbd [0x801ed9c4]
>  #3 [0xffffe420]
>  #4 /usr/sbin/smbd(ntlmssp_sign_init+0xce) [0x800f058e]
>  #5 /usr/sbin/smbd [0x800ed446]
>  #6 /usr/sbin/smbd(ntlmssp_update+0x23b) [0x800ec44b]
>  #7 /usr/sbin/smbd(auth_ntlmssp_update+0x4b) [0x8024ce8b]
>  #8 /usr/sbin/smbd(reply_sesssetup_and_X+0x8da) [0x8007dc4a]
>  #9 /usr/sbin/smbd [0x800ac25a]
>  #10 /usr/sbin/smbd(process_smb+0x199) [0x800ac6c9]
>  #11 /usr/sbin/smbd(smbd_process+0x1ee) [0x800ad7be]
>  #12 /usr/sbin/smbd(main+0x950) [0x802a8150]
>  #13 /lib/tls/libc.so.6(__libc_start_main+0xd0) [0xb7cabed0]
>  #14 /usr/sbin/smbd [0x8003df61]

> This happens every time I try to list the share available in this machine
> from a Win 2K machine.

Yes, this bug has been reported several times and is fixed upstream.

> Samba is configured "security=server" with the server running the same
> version of samba.

Which is a bad idea; security=server is insecure by design, and is also not
well-tested upstream, which means future bugs like this one are likely. 
Please consider using security=domain instead.

-- 
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/

Attachment: signature.asc
Description: Digital signature

Reply via email to