From: Volker Lendecke on
On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
> I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
> had to downgrad again because of massive core panics:

Can you try to reproduce that under valgrind?

Thanks,

Volker
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Martin Hochreiter on
Am 2010-01-25 15:41, schrieb Volker Lendecke:
> On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
>
>> I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
>> had to downgrad again because of massive core panics:
>>
> Can you try to reproduce that under valgrind?
>
>
Volker, I am afraid I don't have any clue what valgrind is .... :-[
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Volker Lendecke on
On Mon, Jan 25, 2010 at 03:53:07PM +0100, Martin Hochreiter wrote:
> Am 2010-01-25 15:41, schrieb Volker Lendecke:
> >On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
> >
> >>I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
> >>had to downgrad again because of massive core panics:
> >>
> >Can you try to reproduce that under valgrind?
> >
> >
> Volker, I am afraid I don't have any clue what valgrind is .... :-[

Look under www.valgrind.org. It's a memory check tool.

Volker
From: Jeremy Allison on
On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
> I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
> had to downgrad again because of massive core panics:
>
> I can't really tell you what caused that (maybe while printing via
> samba-cups) - can
> somebody give me a hint or tell me what information you need to analyze
> that please?
>
> [2010/01/25 13:46:52, 0] lib/fault.c:46(fault_report)
> ===============================================================
> [2010/01/25 13:46:52, 0] lib/fault.c:47(fault_report)
> INTERNAL ERROR: Signal 11 in pid 7553 (3.4.5)
> Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2010/01/25 13:46:52, 0] lib/fault.c:49(fault_report)
>
> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2010/01/25 13:46:52, 0] lib/fault.c:50(fault_report)
> ===============================================================
> [2010/01/25 13:46:52, 0] lib/util.c:1480(smb_panic)
> PANIC (pid 7553): internal error
> [2010/01/25 13:46:52, 0] lib/util.c:1584(log_stack_trace)
> BACKTRACE: 25 stack frames:
> #0 /opt/samba345/sbin/smbd(log_stack_trace+0x1a) [0x6bc42b]
> #1 /opt/samba345/sbin/smbd(smb_panic+0x55) [0x6bc52a]
> #2 /opt/samba345/sbin/smbd [0x6ad1ae]
> #3 /lib/libpthread.so.0 [0x7fa381cb77d0]
> #4 /etc/samba/libtalloc.so.1 [0x7fa380da9761]
> #5 /etc/samba/libtalloc.so.1(talloc_free+0x1cc) [0x7fa380dab92e]
> #6 /opt/samba345/sbin/smbd [0x6249ca]
> #7 /opt/samba345/sbin/smbd(api_pipe_request+0x3ac) [0x656ef5]
> #8 /opt/samba345/sbin/smbd [0x650b46]
> #9 /opt/samba345/sbin/smbd(np_write_send+0x912) [0x651a13]
> #10 /opt/samba345/sbin/smbd [0x4a7456]
> #11 /opt/samba345/sbin/smbd [0x4a79d9]
> #12 /opt/samba345/sbin/smbd(reply_trans+0x6b7) [0x4a85af]
> #13 /opt/samba345/sbin/smbd [0x4fee33]
> #14 /opt/samba345/sbin/smbd [0x5012e8]
> #15 /opt/samba345/sbin/smbd [0x501a6c]
> #16 /opt/samba345/sbin/smbd(run_events+0x131) [0x6cb350]
> #17 /opt/samba345/sbin/smbd(smbd_process+0x790) [0x500cb7]
> #18 /opt/samba345/sbin/smbd [0x947e15]
> #19 /opt/samba345/sbin/smbd(run_events+0x131) [0x6cb350]
> #20 /opt/samba345/sbin/smbd [0x6cb5b0]
> #21 /opt/samba345/sbin/smbd(_tevent_loop_once+0x84) [0x6cb929]
> #22 /opt/samba345/sbin/smbd(main+0xf17) [0x947b99]
> #23 /lib/libc.so.6(__libc_start_main+0xf4) [0x7fa3806481c4]
> #24 /opt/samba345/sbin/smbd [0x48e629]
> [2010/01/25 13:46:52, 0] lib/fault.c:326(dump_core)
> dumping core in /var/log/samba/cores/smbd

Can you install the debug symbols, and try and
reproduce the problem please ? Open a bug at bugzilla.samba.org
and add the line:

panic action = "/bin/sleep 99999"

to the [global] section of your smb.conf. Once the crash
re-occurs, attach to the parent process of the sleep using
gdb, and then type "bt" to get a full backtrace with symbols.

Attach this to the bug report please.

Thanks !

Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
From: Martin Hochreiter on

> Can you install the debug symbols, and try and
> reproduce the problem please ? Open a bug at bugzilla.samba.org
> and add the line:
>
> panic action = "/bin/sleep 99999"
>
> to the [global] section of your smb.conf. Once the crash
> re-occurs, attach to the parent process of the sleep using
> gdb, and then type "bt" to get a full backtrace with symbols.
>
> Attach this to the bug report please.
>
> Thanks !
>
> Jeremy.
>
>
Unfortunately it is a production system I did the upgrade
(I compiled 3.4.5 in parallel to 3.0.28 did the necessary changes and
tried to run in it
during lunchtime)

I'll try to reproduce it during lunchtime again ...

BUT

I read the "3.4 Panic in Debian" thread and Ubuntu 8.04 is shipped with
libkrb53 - 1.6.dfsg.3~beta1-2ubuntu1.3

May that hit my problem too?


--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba