SMBD Crash

[David Rivera]

Hi Ricky,

Yep you're right, it is a different panic than the one you had. I posted
the info in my previous email but I should have included it again.
Here is the backtrace:  http://pastebin.com/Z5R0sXHZ . Samba Version
4.1.0pre1-GIT-ea96d79.

Thanks,
David

On Wed, Sep 19, 2012 at 10:44 AM, Ricky Nance <
ricky.nance at weaubleau.k12.mo.us> wrote:

> Must be a new one, my server seems to be running fine. Can you get a
> gdb_backtrace and post it somewhere?
>
> Ricky
> On Sep 19, 2012 12:32 PM, "David Rivera" <rivera.david87 at gmail.com> wrote:
>
>> Hi,
>>
>> Just wanted to update everyone. This panic is still occurring using
>> samba Version 4.1.0pre1-GIT-ea96d79.
>>
>> Thanks,
>> David
>>
>> On Thu, Sep 13, 2012 at 5:33 PM, David Rivera <rivera.david87 at gmail.com
>> >wrote:
>>
>> > Hi everyone,
>> >
>> > I seem to be getting a different smbd panic, backtrace is here:
>> > http://pastebin.com/Z5R0sXHZ . This was using Version
>> > 4.0.0beta9-GIT-95a643e with the patch from the other thead " RHEL6
>> init.d
>> > script (was Re: Initscript Debian Wheezy) " provided by Jeremy. I won't
>> > be able to update this installation to the current RC until the weekend
>> so
>> > I wasn't able to test if this bug existed in the current build.
>> >
>> > -David
>> >
>> >
>> > On Mon, Sep 10, 2012 at 10:53 AM, Michael Adam <obnox at samba.org> wrote:
>> >
>> >> Hi Ricky, hi Jeremy,
>> >>
>> >> On 2012-09-10 at 09:46 -0700, Jeremy Allison wrote:
>> >> > On Mon, Sep 10, 2012 at 09:46:59AM -0500, Ricky Nance wrote:
>> >> > > I tried the patch from the other thread RHEL6 init.d script (was
>> Re:
>> >> > > Initscript Debian Wheezy) and I am still crashing. Here is the
>> >> backtrace
>> >> > > http://paste.ubuntu.com/1196762/ Let me know if you need more info
>> >> on this.
>> >> >
>> >> > Ah, this is a *completely* different problem ("invalid lock_order"
>> >> > reported from dbwrap_check_lock_order()) - although again in the
>> >> > shutdown code.
>> >> >
>> >> > I'm going to push my first patch, and then look into this
>> >> > one for you.
>> >>
>> >> I am also going to have a look, since this seems to be
>> >> triggered by the new smbXsrv code...
>> >>
>> >> Cheers - Michael
>> >>
>> >>
>> >
>>
>