On Sun, Feb 19, 2012 at 8:44 PM, Simo Sorce <s...@redhat.com> 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 ?

Honestly, I'm not a great expert in dealing with these things. I hope to
have followed the right steps.
Please give me a feedback in both cases.

[root@freeipa01 ccpp-2012-02-19-16:37:03-1126]# gdb coredump
GNU gdb (GDB) Fedora (
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
Reading symbols from /usr/sbin/named...Reading symbols from
[New LWP 1127]
[New LWP 1128]
[New LWP 1129]
[New LWP 1126]

warning: Can't read pathname for load map: Input/output error.
Core was generated by `/usr/sbin/named -u named'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f80d502cd82 in ldap_cache_enabled (cache=0xdededededededede) at
216             return (cache->rbt != NULL) ? ISC_TRUE : ISC_FALSE;
Missing separate debuginfos, use: debuginfo-install
cyrus-sasl-lib-2.1.23-27.fc16.x86_64 cyrus-sasl-md5-2.1.23-27.fc16.x86_64
cyrus-sasl-plain-2.1.23-27.fc16.x86_64 glibc-2.14.90-24.fc16.4.x86_64
keyutils-libs-1.5.2-1.fc16.x86_64 krb5-libs-1.9.2-6.fc16.x86_64
libattr-2.4.46-2.fc16.x86_64 libcap-2.22-1.fc15.x86_64
libcom_err-1.41.14-2.fc15.x86_64 libdb-5.2.36-1.fc16.x86_64
libselinux-2.1.6-6.fc16.x86_64 libxml2-2.7.8-6.fc16.x86_64
nspr-4.8.9-2.fc16.x86_64 nss-3.13.1-11.fc16.x86_64
nss-softokn-freebl-3.13.1-15.fc16.x86_64 nss-util-3.13.1-3.fc16.x86_64
openldap-2.4.26-6.fc16.x86_64 openssl-1.0.0g-1.fc16.x86_64
sssd-client-1.7.0-5.fc16.x86_64 zlib-1.2.5-6.fc16.x86_64
(gdb) bt
#0  0x00007f80d502cd82 in ldap_cache_enabled (cache=0xdededededededede) at
#1  0x00007f80d502cdd9 in ldap_cache_getrdatalist (mctx=0x7f80dc968250,
cache=0xdededededededede, name=0x7f80d6a82260,
    rdatalist=0x7f80d6a82240) at cache.c:177
#2  0x00007f80d503617a in ldapdb_rdatalist_get (mctx=0x7f80dc968250,
ldap_inst=0x7f80da7b2f10, name=0x7f80d6a82260, origin=0x7f80d0207c58,
    rdatalist=0x7f80d6a82240) at ldap_helper.c:1466
#3  0x00007f80d502fc7e in find (db=0x7f80d0207c40, name=0x7f80d0738020,
version=<optimized out>, type=28, options=<optimized out>,
    now=<optimized out>, nodep=0x7f80d6a82880, foundname=0x7f80d0737ee0,
rdataset=0x7f80d073b050, sigrdataset=0x0) at ldap_driver.c:498
#4  0x00007f80da82c01f in query_find (client=0x7f80d06943a0, event=0x0,
qtype=28) at query.c:5474
#5  0x00007f80da833011 in ns_query_start (client=0x7f80d06943a0) at
#6  0x00007f80da81a6de in client_request (task=<optimized out>,
event=<optimized out>) at client.c:1913
#7  0x00007f80d8ae3e98 in dispatch (manager=0x7f80da78f010) at task.c:1012
#8  run (uap=0x7f80da78f010) at task.c:1157
#9  0x00007f80d8499d90 in ?? ()
#10 0x0000000000000000 in ?? ()

> If you need help generating the backtrace from the core dump I can catch
> with you tomorrow on the #freeipa channel.

Freeipa-devel mailing list

Reply via email to