#107 [abrt] bind-dyndb-ldap-2.4-1.fc18.i686: zr_flush_all_caches: Process /usr/sbin/named was killed by signal 11 (SIGSEGV)
Closed: Fixed None Opened 11 years ago by pspacek.

https://bugzilla.redhat.com/show_bug.cgi?id=907133 (Fedora)

Description of problem:
Not sure exactlt what happens, but it seems like thist happens when named
looses the connection to the ldap backend server (389-ds) during an update
of FreeIPA, where the ldap is restarted multiple times.

Version-Release number of selected component:
bind-9.9.2-6.P1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/sbin/named -u named
crash_function: zr_flush_all_caches
executable:     /usr/sbin/named
kernel:         3.7.4-204.fc18.i686.PAE
remote_result:  NOTFOUND
uid:            25

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 zr_flush_all_caches at zone_register.c:271
 #1 ldap_psearch_watcher at ldap_helper.c:3822

The plugin can crash after successful reconnection to LDAP server.

Steps to reproduce:

  • create a TCP relay: socat tcp-listen:3899,fork,reuseaddr tcp-connect:localhost:389
  • configure BIND to connect to localhost, port 3899
  • start BIND
  • terminate socat
  • start socat again and let BIND to reconnect
  • wait for reconnection & crash

Excerpt from /var/log/messages:

04-Feb-2013 17:31:28.518 connection to the LDAP server was lost
04-Feb-2013 17:31:28.519 bind to LDAP server failed: Can't contact LDAP server
04-Feb-2013 17:31:28.519 [ldap_helper.c  : 2209: ldap_connect         ] check failed: socket is not connected
04-Feb-2013 17:31:28.519 ldap_psearch_watcher failed to handle LDAP connection error. Reconnection in 1s
04-Feb-2013 17:31:29.519 connection to the LDAP server was lost
04-Feb-2013 17:31:29.603 successfully reconnected to LDAP server
04-Feb-2013 17:31:29.635 LDAP error: Can't contact LDAP server
04-Feb-2013 17:31:29.635 connection to the LDAP server was lost
04-Feb-2013 17:31:29.684 successfully reconnected to LDAP server
<<segfault right here>>

Bug introduced by commit b367091 (ticket #91).

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 19

7 years ago

Login to comment on this ticket.

Metadata