Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It sounds like you're going to be failing at the "getent passwd" stage in the fault tracing I'd recommend, which given success with ldapsearch would say that most likely the /etc/ldap.conf file is invalid in some way.
Chris, I am not very clear on what you are saying here. But as it stands I can able to log on as the ldap user from the ldap client machine (which, as I originally mentioned, is Fedora14) let alone ldapsearch.
It only takes a very very long time to log on into the gnome session after the reboot (as I also mentioned for some reason, the mdmonitor takes a very long time to start - but I can disable mdmonitor for now). Then it takes no time to log in from the terminals, even if it is the ldap user. I have no /etc/ldap.conf on the client machine.
But I do have one on the server to which I have made changes as follows:
#host 127.0.0.1
base dc=mydomain,dc=com
uri ldap://servername.mydomain.com/
ssl no
tls_cacertdir /etc/openldap/cacerts
Sadly I have to reopen this thread. The problems regarding the ldap server and client are solved now. But my problem with the log in time still remains. It takes painfully a long long time to log in even as the local user. Another thing I noticed was that the mdmonitor service takes a very very long time to start. If I disable ldap from the nsswitch.conf, the delay does not happen (and of course, I can not log on to the ldap server).
Thanks. My client uses a wireless network with network manager running. Ignore option for IPv6 is what is chosen when I open 'Edit Connections' GUI. Is there any other way to do this?
Check you /etc/nsswitch.conf file for ldap entries for services and protocols. If you are using ldap for only user info you can remove ldap for those services. It is possible that attempted ldap lookups are having to time out on login.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.