Mingyur Koblensky wrote:
Hi all,
I'm playing with a redhat enterprise 4 that uses ldap, since a few days i've notice that the slapd daemon is not able to bind to the default port 389, i'm very new to this server so i could being doing something of very stupid!
[root@ myserver etc]# netstat -tuan | grep 389 [root@ myserver etc]#
i was wondering if a run time file of the server hasn't been properly removed due to a brutal restart, and now the process isn't able to bind to any port, does that make sense? which files should i look for?
[root@ myserver etc]# ls /var/run/openldap/ [root@ myserver etc]# ls /var/lock/ dmraid lvm rpm subsys [root@ myserver etc]#
i've tried to reinstall/downgrade various packages but nothing:
[root@ myserver etc]# rpm -q openldap openldap-2.2.13-12.el4_8.2 [root@ myserver etc]# rpm -q openldap-servers openldap-servers-2.2.13-12.el4_8.2 [root@ myserver etc]# rpm -q openldap-clients openldap-clients-2.2.13-12.el4_8.2 [root@ myserver etc]# rpm -q nss_ldap nss_ldap-253-7.el4 [root@ myserver etc]#
Hi,
I know I'm not helping, but-
# Subject: OpenLDAP 2.2.13 released # From: "Kurt D. Zeilenga" Kurt@OpenLDAP.org # Date: Thu, 10 Jun 2004 17:10:50 -0700
bash-4.0$ date Mon Mar 1 15:39:35 CET 2010
Please, update to the latest OpenLDAP 2.4.21 release. The one you're playing with is 6 years old.
You can try to start % slapd; from command line and see what the problem is/might be.
As a root or whoever is supposed to run OpenLDAP: # slapd -h 'ldap://127.0.0.1' -d 256;
You might want to supply full path to # slapd; binary and I'm no familiar with 2.2.x version, but I guess this (parameters) apply as well.
Regards, Zdenek
PS: whatever