-
20th September 2006, 02:39 PM
#16
Bump!
Editing the /etc/nsswitch.conf before/after rebooting can't be a solution......
I agree.
Is there some time-out setting in nsswitch.conf? Something like: time out after 5 seconds looking for LDAP, then continue on.
Thanks,
Dan
-
20th September 2006, 05:09 PM
#17
Originally Posted by
UraniumWilly
Is there some time-out setting in nsswitch.conf? Something like: time out after 5 seconds looking for LDAP, then continue on.
My lines look like this:
passwd: files ldap
shadow: files ldap
group: files ldap
and the system doesn't boot. I think this entry means: Try files first, if it fails try ldap... (could be continued). But
passwd: files
shadow: files
group: files
works.
My system hangs on "starting named", but what has named to do with this ldap entry? And if my system is up there is no problem restarting named (with "passwd: files ldap" and so on of course).
With kind regards,
carlsan
-
20th September 2006, 05:29 PM
#18
You are correct:
I think this entry means: Try files first, if it fails try ldap.
For me some services (all services are in /etc/passwd) still hang on boot up.
-
20th September 2006, 06:45 PM
#19
Originally Posted by
UraniumWilly
For me some services (all services are in /etc/passwd) still hang on boot up.
The same here... ...
I'm wondering that nobody else has that problem.
-
30th September 2006, 02:25 AM
#20
I had similar issues when the system was unable to contact the ldap server - noticed when using a laptop and I was disconnected.
It was corrected by changing the reconnect policy (bind_policy parameter) to soft (default is hard). This tells ldap to fail immediately with failure to contact the ldap server instead of using exponential backoff.
-
30th September 2006, 02:26 AM
#21
Sorry, forgot to say that is a parameter in the ldap config file... oops.
-
4th October 2006, 09:59 PM
#22
Originally Posted by
jwepaterson
Sorry, forgot to say that is a parameter in the ldap config file... oops.
Thanks for that hint. I'll try that next reboot.... or has anybody already tried it?
Last edited by carlsan; 11th October 2006 at 11:07 AM.
-
14th October 2006, 05:53 AM
#23
Check network Cable connection...
-
17th October 2006, 12:15 PM
#24
I Found !!!
Try "bind_policy soft" in ldap.conf !
-
18th October 2006, 11:14 AM
#25
Thanks, it works for me, but only with nscd running too. Otherwise (ldap-)users can't login via ssh.
My ldap.conf:
timelimit 5
bind_timelimit 5
bind_policy soft
-
6th November 2006, 05:27 PM
#26
hmmmm I dont have LDAP configured (SAMBA has been a bit peculiar last couple of days) but after a rebbot my machine is just hanging at starting "system message bus" my nsswitch.conf file appears to be the same as its always been and I cant find the authconfig file that is mentioned.
I am running FC5.
Any help would be greatly appreciated.
-
5th December 2006, 08:21 PM
#27
I had this exact same issue. edit nsswitch.conf and change the following
passwd: files winbind
shadow: files winbind
group: files winbind
Your mileage may vary
-
4th February 2007, 09:05 PM
#28
Thanks! Worked for me! Just booted with the Ubuntu CD (Why else do you have it?) and did following:
Start Terminal
sudo passwd
<Type new password twice>
su
<Type new password>
mount /dev/hda2 /mnt # Assuming your disk is dual boot, else chane 2 for 1
cd /mnt
cd etc
vi nsswitch.conf
/ldap
dw
/
dw
... etc etc untill all ldap entries are gone ...
:wq
sync;sync
cd /
umount /mnt
reboot
Thanks a million, I used to install the OS when I got this message...
Sincerely,
Huub
Last edited by huub.knops; 4th February 2007 at 09:12 PM.
-
9th March 2007, 05:03 AM
#29
ldap startet einfach zu spaet..
ich hab mich nit darum gekuemmert was message-bus, namd und Konsorten aus protocols, passe etc haben wollen.. Es ist nut Fakt das die Dieste vor Ldap starten und dei nsswitch entweder files ldap , oder ldap files sagt .. Die Info schein aber wohl in beiden Dirs nicht zu finden zu sein, und die Diesste warten einfach auf eine LDAP Antwort. message-bus wird als 22 gestartet , LDap erst als 29..
einfach ..
chkconfig ldap off ... /etc/init.d/ladp bearbeiten unc chkconfig von 27 auf 21 umstellen,,
chkconfig ldap on , rebooten und es laueft so durch
Gruss
Andre
-
20th April 2007, 12:48 AM
#30
For me, I had the incorrect LDAP info. D'oh!
Similar Threads
-
By terrabite in forum Using Fedora
Replies: 4
Last Post: 28th May 2009, 02:29 PM
-
By sudhir_rao in forum Programming & Packaging
Replies: 0
Last Post: 29th June 2007, 04:57 AM
-
By jhegge in forum Using Fedora
Replies: 0
Last Post: 14th May 2007, 09:23 PM
-
By danielsender in forum EOL (End Of Life) Versions
Replies: 2
Last Post: 8th July 2004, 11:53 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
[[template footer(Guest)]]