Bug 767489

Summary:	Periodically reconnect to LDAP when the first connection fails
Product:	Red Hat Enterprise Linux 6	Reporter:	Adam Tkac <atkac>
Component:	bind-dyndb-ldap	Assignee:	Adam Tkac <atkac>
Status:	CLOSED ERRATA	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	grajaiya, jgalipea, ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://fedorahosted.org/bind-dyndb-ldap/ticket/30
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:51:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	767486

Description Adam Tkac 2011-12-14 08:01:59 UTC

Description of problem:
When the first connection to LDAP fails because LDAP server is down then admin must manually call rndc reload to fetch zones from LDAP:

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

The plugin should periodically reconnect to LDAP itself and fetch zones run-time.
  
Actual results:
Admin must execute `rndc reload` to make plugin working when the first connection to LDAP fails.

Expected results:
The plugin automatically reconnects to LDAP after some time.

Comment 4 Gowrishankar Rajaiyan 2012-05-14 18:55:13 UTC

[root@primenova ~]# service named status
version: 9.8.2rc1-RedHat-9.8.2-0.9.rc1.el6
CPUs found: 2
worker threads: 2
number of zones: 19
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid  1121) is running...
[root@primenova ~]#

in /etc/named.conf, in dynamic-db "ipa" { }; section, replace line 'arg "uri
ldapi:// ...' with 'arg "uri ldap://127.0.0.1";'

[root@primenova ~]# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
REJECT     tcp  --  anywhere             anywhere            tcp dpt:ldap reject-with icmp-port-unreachable 
REJECT     tcp  --  anywhere             anywhere            tcp dpt:ldaps reject-with icmp-port-unreachable 

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
[root@primenova ~]#

[root@primenova ~]# service named restart
Stopping named: .                                          [  OK  ]
Starting named:                                            [  OK  ]
[root@primenova ~]# 

[root@primenova ~]# service named status
version: 9.8.2rc1-RedHat-9.8.2-0.9.rc1.el6
CPUs found: 2
worker threads: 2
number of zones: 19
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid  6956) is running...
[root@primenova ~]# 

Verified:
ipa-server-2.2.0-13.el6.x86_64
bind-9.8.2-0.9.rc1.el6.x86_64
bind-dyndb-ldap-1.1.0-0.9.b1.el6.x86_64

Comment 6 errata-xmlrpc 2012-06-20 13:51:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0837.html