[Freeipa-devel] named core dump

[Jakub Hrozek]

On Sun, Feb 19, 2012 at 02:44:40PM -0500, Simo Sorce wrote:
> On Sun, 2012-02-19 at 17:17 +0100, Marco Pizzoli wrote:
> > Hi guys,
> > today I'm playing a lot with FreeIPA 2.1.90.
> > I'm not sure about the exact moment, but I had a named core dump.
> > 
> > My system run with named:
> > bind-license-9.8.2-0.2.rc1.fc16.noarch
> > bind-libs-lite-9.8.2-0.2.rc1.fc16.x86_64
> > bind-9.8.2-0.2.rc1.fc16.x86_64
> > bind-libs-9.8.2-0.2.rc1.fc16.x86_64
> > bind-utils-9.8.2-0.2.rc1.fc16.x86_64
> > bind-dyndb-ldap-1.1.0-0.8.a2.fc16.x86_64
> > 
> > Probably it happened during a "ipa-client-install
> > --enable-dns-updates" execution from a client machine. I have saved
> > the core and I can send to you if necessary.
> > Actually my "freeipa01" fedora16 system generated a dir
> > under /var/spool/abrt which I think could be more meaningful in
> > tracking the cause.
> > This is what I saw in my /var/log/messages log
> > 
> > [ 5111.204303] named[1127] general protection ip:7f80d502cd82
> > sp:7f80d6a82148 error:0 in ldap.so[7f80d5024000+1c000]
> > 
> 
> Do you have a backtrace in the abrt dir ?
> If so can you send it to the list ?
> If you need help generating the backtrace from the core dump I can catch
> with you tomorrow on the #freeipa channel.
> 
> Simo.
> 

IIRC the abrt directory contains a coredump and a bunch of other useful
information. I think it would be best to just create a gzipped tarball
of the directory and attach it to a bugzilla or a Trac ticket.

You can try running "abrt-cli -l" to see the list of crashes abrt has
detected. That should also list the directory and the executable that
had crashed.