-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Sean O'Connell Sent: Tuesday, September 06, 2005 1:14 AM To: CentOS mailing list Subject: RE: [CentOS] LDAP/iptables
On Mon, 2005-09-05 at 21:29 -0400, Thomas E Dukes wrote:
Hello Sean,
I uncommented rootpw secret commented out the sasl reference. Still won't connect. :-(
I have been working on this for a week. Its beating the
heck out of me.
Thanks for your help!!!!
OK. I took the slapd.conf that you had posted earlier, and I was able to get it to work on a CentOS 4.1 box without too much trouble (clean up a typo in the rootdn name and a cut and paste issue). I had to comment out some stuff in /etc/openldap/ldap.conf. Something truly odd is going on there. The fact that ldap is starting but not creating tcp sockets is quite weird.
Hi Sean,
Ooops, I found the typo, too. Fixed it but still won't connect.
Have you tried rebooting? (I know, I know :) Sometimes system updates can cause subtle issues from time to time. Maybe something is goofy with the network on your machine. Have you been starting and stopping the network service? Can you ping localhost? I have seen some linux boxes (been a while, though) forget about how to talk to localhost and it caused all sorts of weird behavior.
Yes, I have rebooted but to no avail. Also, I can ping 'localhost', 'palmettodomains.com', '127.0.0.1' and '10.10.0.1'. I still can't figure why I can't telnet to one of those using port 389.
As a shot in the dark, are you running with selinux enabled? It has caused many a subtle problem in which a configuration that should "just work" has failed to work. Try running setenforce 0 and then restarting ldap. I run my machines with selinux=0 on the kernel line in grub.conf
No, I don't run selinux.
Thanks, again!!
-- Sean
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos