Ctdb Error

[Martin Schwenke]

On Fri, 19 Dec 2014 09:02:58 -0500, Zinny <eibeagbazi at gmail.com> wrote:

> Thanks again Martin, could you please point me to a link or outline
> the steps I can follow that will assist me in generating the core
> dump, I have not worked on that before and wasn't successful in
> generating one as I tried it from your suggestion.

When a program crashes, in most circumstances, it generates a file
called "core".

First of all, take a look in /var/log/messages at the time of the
crash.  This should tell you if abrtd handled the core dump and might
even tell you where the information is.  Otherwise it will probably
just tell you that a core file was dumped.  If you're lucky there might
be something useful logged telling you what the problem is.  It might
also be worth trying /var/log/samba/log.smbd or similar, depending how
things are configured on your system.

If there's a message like this:

  2014-12-24T06:51:25.152400+11:00 m1n1 abrtd: Package 'samba' isn't
 signed with proper key
  2014-12-24T06:51:25.154292+11:00 m1n1 abrtd: 'post-create' on '/var/spool/abrt/ccpp-2014-12-24-06:51:24-22775' exited with 1
  2014-12-24T06:51:25.154302+11:00 m1n1 abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2014-12-24-06:51:24-22775'

then the easiest thing to do is to stop abrtd trying to handle things,
like this:

  echo > /proc/sys/kernel/core_pattern

then try restarting ctdbd and hopefully a core file will be created
again and it won't be deleted by abrtd.

When you have a core file (e.g. I
have /var/log/samba/cores/smbd/core.22775), then you can do something
like:

  gdb /usr/sbin/smbd /var/log/samba/cores/smbd/core.22775 

At the (gdb) prompt type "bt" and hit enter.  This should give you a
stack backtrace, which might help the team to determine the cause of
the issue.  You might need to installed some extra debuginfo packages -
gdb should tell you.  There is a lot more analysis you can do in gdb but
I'll leave that up to you...  :-)

peace & happiness,
martin