From: Mike Petersen (mgpeter_at_pcc-services.com)
Date: Mon Jul 02 2007 - 22:12:18 CEST
From: Mike Petersen <mgpeter@pcc-services.com> Date: Mon, 02 Jul 2007 15:12:18 -0500 Message-Id: <1183407138.4948.5.camel@sled-admin.iecompany.com> Subject: Re: [suse-sles-e] SLES 10 SP1 Samba and Windows Vista
FYI:
I am also getting these exact errors here - SLES 10 SP1 ia64bit on a
Dell Poweredge 2800. I haven't seen it on any 32bit servers yet.
Samba is setup as a PDC. All Clients are WinXP Pro.
Mike Petersen
mgpeter@pcc-services.com
On Fri, 2007-06-29 at 17:19 -0300, Carlos Eduardo Pedroza Santiviago
wrote:
> Hi,
>
> On 6/23/07, Lars Müller <lmuelle@suse.de> wrote:
> [...]
> >
> > Feedback in general and in particular for this Vista problem with 3.0.24
> > as shipped with SLE 10 SP 1 is highly welcome!
> >
> > Lars
> > --
> > Lars Müller [ˈlaː(r)z ˈmʏlɐ]
> > Samba Team
> > SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
>
> Since you asked, here we go... :-)
>
> After updating to SLES 10 SP1, i have some Samba clients crashing and
> closing its connections. Here's what the logfile shows:
>
> [2007/06/29 08:54:53, 0] lib/fault.c:fault_report(41)
> ===============================================================
> [2007/06/29 08:54:53, 0] lib/fault.c:fault_report(42)
> INTERNAL ERROR: Signal 11 in pid 26465 (3.0.24-2.23-1296-SUSE-CODE10)
> Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2007/06/29 08:54:53, 0] lib/fault.c:fault_report(44)
>
> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2007/06/29 08:54:53, 0] lib/fault.c:fault_report(45)
> ===============================================================
> [2007/06/29 08:54:53, 0] lib/util.c:smb_panic(1599)
> PANIC (pid 26465): internal error
> [2007/06/29 08:54:53, 0] lib/util.c:log_stack_trace(1706)
> BACKTRACE: 19 stack frames:
> #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021859d]
> #1 /usr/sbin/smbd(smb_panic+0x5d) [0x802186cd]
> #2 /usr/sbin/smbd [0x8020410a]
> #3 [0xffffe420]
> #4 /usr/sbin/smbd [0x8016e246]
> #5 /usr/sbin/smbd(lsa_io_r_lookup_sids+0x9b) [0x8016f58b]
> #6 /usr/sbin/smbd [0x801011ce]
> #7 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162438]
> #8 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162a8e]
> #9 /usr/sbin/smbd [0x8015d5ff]
> #10 /usr/sbin/smbd [0x8015db3c]
> #11 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c36e]
> #12 /usr/sbin/smbd(reply_pipe_write_and_X+0xeb) [0x800736bb]
> #13 /usr/sbin/smbd(reply_write_and_X+0x2a5) [0x8007b3e5]
> #14 /usr/sbin/smbd [0x800b4400]
> #15 /usr/sbin/smbd(smbd_process+0x78b) [0x800b54fb]
> #16 /usr/sbin/smbd(main+0xbd0) [0x802c21d0]
> #17 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7ae587c]
> #18 /usr/sbin/smbd [0x80042f21]
> [2007/06/29 08:54:53, 0] lib/fault.c:dump_core(180)
> dumping core in /var/log/samba/cores/smbd
>
> and this one, right after the first:
>
> [2007/06/29 08:55:01, 0] lib/fault.c:fault_report(41)
> ===============================================================
> [2007/06/29 08:55:01, 0] lib/fault.c:fault_report(42)
> INTERNAL ERROR: Signal 6 in pid 26466 (3.0.24-2.23-1296-SUSE-CODE10)
> Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2007/06/29 08:55:01, 0] lib/fault.c:fault_report(44)
>
> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2007/06/29 08:55:01, 0] lib/fault.c:fault_report(45)
> ===============================================================
> [2007/06/29 08:55:01, 0] lib/util.c:smb_panic(1599)
> PANIC (pid 26466): internal error
> [2007/06/29 08:55:01, 0] lib/util.c:log_stack_trace(1706)
> BACKTRACE: 24 stack frames:
> #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8021859d]
> #1 /usr/sbin/smbd(smb_panic+0x5d) [0x802186cd]
> #2 /usr/sbin/smbd [0x8020410a]
> #3 [0xffffe420]
> #4 /lib/libc.so.6(abort+0x103) [0xb7af9ff3]
> #5 /usr/sbin/smbd [0x8021e906]
> #6 /usr/sbin/smbd(talloc_steal+0x3a) [0x8021eada]
> #7 /usr/sbin/smbd(lookup_sids+0x39a) [0x801d564a]
> #8 /usr/sbin/smbd [0x801075e1]
> #9 /usr/sbin/smbd(_lsa_lookup_sids+0x131) [0x80107dc1]
> #10 /usr/sbin/smbd [0x801011a1]
> #11 /usr/sbin/smbd(api_rpcTNP+0x198) [0x80162438]
> #12 /usr/sbin/smbd(api_pipe_request+0x19e) [0x80162a8e]
> #13 /usr/sbin/smbd [0x8015d5ff]
> #14 /usr/sbin/smbd [0x8015db3c]
> #15 /usr/sbin/smbd(write_to_pipe+0x6e) [0x8015c36e]
> #16 /usr/sbin/smbd [0x8005f381]
> #17 /usr/sbin/smbd [0x8005f8b6]
> #18 /usr/sbin/smbd(reply_trans+0x5e0) [0x800601c0]
> #19 /usr/sbin/smbd [0x800b4400]
> #20 /usr/sbin/smbd(smbd_process+0x78b) [0x800b54fb]
> #21 /usr/sbin/smbd(main+0xbd0) [0x802c21d0]
> #22 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7ae587c]
> #23 /usr/sbin/smbd [0x80042f21]
> [2007/06/29 08:55:01, 0] lib/fault.c:dump_core(180)
> dumping core in /var/log/samba/cores/smbd
>
> However, the core file is not created (enable core files is yes). It
> looks like to be something in the lookup_sids function. Have you ever
> seen this error?
>
> I found a similar question here:
> http://www.ndsengineers.com/sles-updates/509349-samba-sles-10-1-a.html
>
> Thank you,
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Jul 03 2007 - 00:12:15 CEST