Bug 832015

Summary: named exits when psearch is enabled and it receives SIGHUP two times.
Product: [Fedora] Fedora Reporter: Gowrishankar Rajaiyan <grajaiya>
Component: bind-dyndb-ldapAssignee: Adam Tkac <atkac>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: atkac, ovasik, pspacek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bind-dyndb-ldap-2.4-1.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-16 10:57:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gowrishankar Rajaiyan 2012-06-14 10:03:20 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
bind-dyndb-ldap-1.1.0-0.20120607T1528Zgit0dcccce.fc17.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install freeipa-server with DNS.
2. Execute "service named reload" twice.

  
Actual results: 
/var/log/messages
Jun 14 05:55:36 dhcp201-207 named[5589]: server.c:2204: unexpected error:
Jun 14 05:55:36 dhcp201-207 named[5589]: unable to obtain neither an IPv4 nor an IPv6 dispatch

Expected results: reload should be successful.

Additional info:

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#

First "service named reload":
Redirecting to /bin/systemctl  reload named.service

/var/log/messages:
Jun 14 05:55:24 dhcp201-207 named[5589]: received SIGHUP signal to reload zones
Jun 14 05:55:24 dhcp201-207 named[5589]: LDAP error: Can't contact LDAP server
Jun 14 05:55:24 dhcp201-207 named[5589]: connection to the LDAP server was lost
Jun 14 05:55:24 dhcp201-207 named[5589]: loading configuration from '/etc/named.conf'
Jun 14 05:55:24 dhcp201-207 named[5589]: using default UDP/IPv4 port range: [1024, 65535]
Jun 14 05:55:24 dhcp201-207 named[5589]: using default UDP/IPv6 port range: [1024, 65535]
Jun 14 05:55:24 dhcp201-207 named[5589]: sizing zone task pool based on 6 zones
Jun 14 05:55:24 dhcp201-207 named[5589]: open: /etc/rndc.key: file not found
Jun 14 05:55:24 dhcp201-207 named[5589]: couldn't add command channel 127.0.0.1#953: file not found
Jun 14 05:55:24 dhcp201-207 named[5589]: open: /etc/rndc.key: file not found
Jun 14 05:55:24 dhcp201-207 named[5589]: couldn't add command channel ::1#953: file not found
Jun 14 05:55:24 dhcp201-207 named[5589]: zone 201.65.10.in-addr.arpa/IN: (master) removed
Jun 14 05:55:24 dhcp201-207 named[5589]: zone testrelm.com/IN: (master) removed
Jun 14 05:55:24 dhcp201-207 named[5589]: reloading configuration succeeded
Jun 14 05:55:24 dhcp201-207 named[5589]: reloading zones succeeded
Jun 14 05:55:24 dhcp201-207 named[5589]: all zones loaded
Jun 14 05:55:24 dhcp201-207 named[5589]: running

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#



#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#

Second "service named reload":
Jun 14 05:55:35 dhcp201-207 named[5589]: received SIGHUP signal to reload zones
Jun 14 05:55:35 dhcp201-207 named[5589]: LDAP error: Can't contact LDAP server
Jun 14 05:55:35 dhcp201-207 named[5589]: connection to the LDAP server was lost
Jun 14 05:55:36 dhcp201-207 named[5589]: loading configuration from '/etc/named.conf'
Jun 14 05:55:36 dhcp201-207 named[5589]: using default UDP/IPv4 port range: [1024, 65535]
Jun 14 05:55:36 dhcp201-207 named[5589]: using default UDP/IPv6 port range: [1024, 65535]
Jun 14 05:55:36 dhcp201-207 named[5589]: sizing zone task pool based on 6 zones
Jun 14 05:55:36 dhcp201-207 named[5589]: server.c:2204: unexpected error:
Jun 14 05:55:36 dhcp201-207 named[5589]: unable to obtain neither an IPv4 nor an IPv6 dispatch
Jun 14 05:55:36 dhcp201-207 named[5589]: reloading configuration failed: unexpected error
Jun 14 05:55:36 dhcp201-207 named[5589]: shutting down
Jun 14 05:55:36 dhcp201-207 named[5589]: no longer listening on ::#53
Jun 14 05:55:36 dhcp201-207 named[5589]: no longer listening on 127.0.0.1#53
Jun 14 05:55:36 dhcp201-207 named[5589]: no longer listening on 10.65.201.207#53
Jun 14 05:55:36 dhcp201-207 named[5589]: exiting
Jun 14 05:55:36 dhcp201-207 sh[5885]: usage: kill [ -s signal | -p ] [ -a ] pid ...
Jun 14 05:55:36 dhcp201-207 sh[5885]: kill -l [ signal ]
Jun 14 05:55:36 dhcp201-207 systemd[1]: named.service: control process exited, code=exited status=1
Jun 14 05:55:36 dhcp201-207 systemd[1]: Unit named.service entered failed state.

#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#


I commented "arg "psearch yes";" in /etc/named.conf and named reload works as expected.
Comment 1 Martin Kosek 2012-06-14 10:18:47 UTC 
Upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/80
Comment 2 Adam Tkac 2012-06-18 13:34:40 UTC 
Fixed in upstream:

http://git.fedorahosted.org/git?p=bind-dyndb-ldap.git;a=commit;h=d52ad09a3942392995e73aa0ebc0daddc823ea75