On la, 05 touko 2018, Timo Aaltonen via FreeIPA-users wrote:
Hi,
Named is crashing here on start, but not if I disable the dyndb part of
named.conf. So I assume it's not getting data out of ldap correctly (or
correct data), and this from slapd logs might suggest so:
[05/May/2018:09:42:02.566222364 +0300] conn=23 op=3 SRCH
base="cn=dns,dc=foo,dc=bar" scope=2
filter="(|(objectClass=idnsConfigObject)(&(objectClass=idnsServerConfigObject)(idnsServerId=host.foo.bar)))"
attrs=ALL
[05/May/2018:09:42:02.568886490 +0300] conn=23 op=3 RESULT err=0 tag=101 nentries=2
etime=0.0002800470
[05/May/2018:09:42:02.715423436 +0300] conn=24 op=-1 fd=96 closed - B1
[05/May/2018:09:42:02.716084255 +0300] conn=23 op=-1 fd=95 closed error 104 (Connection
reset by peer) - TCP connection reset by peer.
looking at the install logs everything seemed to go fine until it started named, and
ldapsearch doesn't provide any hints either..
Any stacktrace?
The LDAP search result with 2 entries suggests it might be a replication
conflict. At least the search is expecting to get a single entry back,
it seems.
--
/ Alexander Bokovoy