Re: [389-users] nscd: nss_ldap: could not search LDAP server - Server is unavailable
by Morris, Patrick
Prashanth Sundaram wrote:
> I have two 389-ds servers with MMR via TLS and client hosts
> authenticating via TLS. I see this error message in all client machines
> in /var/log/messages. It seems nscd is failing at random intervals. Has
> anyone seen this before?
> Dec 29 10:35:35 dmc189 nscd: nss_ldap: could not search LDAP server -
> Server is unavailable
> Dec 29 11:00:21 dmc189 nscd: nss_ldap: could not search LDAP server -
> Server is unavailable
> Dec 29 11:12:15 dmc189 nscd: nss_ldap: could not search LDAP server -
> Server is unavailable
Sure. It can be caused by several things: intermittent connectivity
issues, server malfunctions (the server log's a good place to look for
those), and several other possibilities.
It could also be caused by problems with nss_ldap itself, especially
given the ldap.conf you've provided. What version are you running,
and on which platform?
14 years, 3 months
389-adminutil error
by Prashanth Sundaram
Hi Rich,
I am getting this error when I install 389-adminutil. Any idea which package
gives these dependencies?
[root@ldap02 psundaram]# yum install 389-adminutilLoaded plugins:
fastestmirror
Loading mirror speeds from cached hostfile
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package 389-adminutil.i386 0:1.1.8-4.el5 set to be updated
--> Processing Dependency: libssl3.so for package: 389-adminutil
--> Processing Dependency: libplc4.so for package: 389-adminutil
--> Processing Dependency: libldap60.so for package: 389-adminutil
--> Processing Dependency: libnss3.so for package: 389-adminutil
--> Processing Dependency: libnss3.so(NSS_3.5) for package: 389-adminutil
--> Processing Dependency: libldif60.so for package: 389-adminutil
--> Processing Dependency: libssl3.so(NSS_3.2) for package: 389-adminutil
--> Processing Dependency: libnspr4.so for package: 389-adminutil
--> Processing Dependency: libnss3.so(NSS_3.2) for package: 389-adminutil
--> Processing Dependency: libprldap60.so for package: 389-adminutil
--> Processing Dependency: libssldap60.so for package: 389-adminutil
---> Package 389-adminutil.x86_64 0:1.1.8-4.el5 set to be updated
--> Running transaction check
---> Package 389-adminutil.i386 0:1.1.8-4.el5 set to be updated
--> Processing Dependency: libldap60.so for package: 389-adminutil
--> Processing Dependency: libldif60.so for package: 389-adminutil
--> Processing Dependency: libprldap60.so for package: 389-adminutil
--> Processing Dependency: libssldap60.so for package: 389-adminutil
---> Package nspr.i386 0:4.7.6-1.el5_4 set to be updated
---> Package nss.i386 0:3.12.3.99.3-1.el5.centos.2 set to be updated
--> Finished Dependency Resolution
389-adminutil-1.1.8-4.el5.i386 from epel has depsolving problems
--> Missing Dependency: libldap60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
389-adminutil-1.1.8-4.el5.i386 from epel has depsolving problems
--> Missing Dependency: libssldap60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
389-adminutil-1.1.8-4.el5.i386 from epel has depsolving problems
--> Missing Dependency: libldif60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
389-adminutil-1.1.8-4.el5.i386 from epel has depsolving problems
--> Missing Dependency: libprldap60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
Error: Missing Dependency: libprldap60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
Error: Missing Dependency: libssldap60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
Error: Missing Dependency: libldap60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
Error: Missing Dependency: libldif60.so is needed by package
389-adminutil-1.1.8-4.el5.i386 (epel)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles nodigest
-Prashanth
14 years, 3 months
Looking for some advise
by Scott Kaminski
Hello,
I'm trying to setup a simple Kerberos/LDAP solution instead of going down
the NIS route and I haven't had much luck. I have a mix of around 30 CentOS
5 and 4 machines. I want to use 389 as my directory server. Is anyone
aware of a complete howto on how to set this up using 389?
Also I was wondering if someone could clarify the relationship between
kerberos and ldap? I've got a functional kerberos and ldap server running on
two vm's and i've setup one server as the primary kdc and admin server and
configured it to replicate the kerberos data. I've setup both machines to
authenticate using kerberos and to obtain user info using ldap. How do i
know that i'm actually using ldap + kerberos properly?
14 years, 3 months