#1836 [IPA] ERROR LDAP Error : Can't contact LDAP Server
Closed: Invalid None Opened 12 years ago by dpal.

https://bugzilla.redhat.com/show_bug.cgi?id=739909

Description of problem:
Well, this morning, I did an update of my ipa server in regards of the problem I encountered few month ago about glibc security issue which create problem with IPA.

So, now I am currently using the following recent version of IPA on my IPA Server - See below - and IPA CLIENT on another machine -See below -

And I tried to register my client -ipa-client-install- then I had the following error message :
root  :ERROR LDAP Error : Can't contact LDAP Server:
Failed to verify that ipa.redhat.local is an IPA Server.
This may mean that the remote server is not up or is not reachable due to network or firewall settings.

Believe me, I double check that and it was not the real problem.

Indeed, I looked in the 389 ds config file - /etc/dirsrv/slapd-YOUR_KRB5_DOMAIN/dse.ldif - to see what has changed between the previous installation and the new one and I noticed that the following paramater had changed.

nsslapd-port 0
nsslapd-security: off

So I set the original values which was

nsslapd-port 389
nsslapd-security: on

cause I am almost sure that IPA is not currently using 689 port.

and the IPA client installation worked

So I assume this is a bug in the new IPA release.


Version-Release number of selected component (if applicable):
IPA SERVER
ipa-client-2.0.0-23.el6_1.2.x86_64
ipa-server-selinux-2.0.0-23.el6_1.2.x86_64
ipa-pki-ca-theme-9.0.3-6.el6.noarch
ipa-python-2.0.0-23.el6_1.2.x86_64
ipa-admintools-2.0.0-23.el6_1.2.x86_64
ipa-server-2.0.0-23.el6_1.2.x86_64
ipa-pki-common-theme-9.0.3-6.el6.noarch


IPA CLIENT
How reproducible:


Steps to Reproduce:
1.Install IPA server on a machine
2. Install IPA Client machine on another server
3. and try to register your IPA client to the IPA Server.

Actual results:


Expected results:
IPA Client installation Complete

Additional info:

I think this is an unresolved problem in ipa 2.0.0 that was fixed in ticket #1199. Basically if anything went wrong in the updater there wasn't a global fail-safe to always recover.

We think that this is an updator issue that has been resolved. Closing the bug based on the comment above.

Metadata Update from @dpal:
- Issue assigned to jdennis
- Issue set to the milestone: FreeIPA 2.1.2 (bug fixing)

7 years ago

Login to comment on this ticket.

Metadata