After setting up an ldap server and client on a machine running opensuse 11.3 (32 bit) it’s taking around 20 minutes to boot
It’s hanging mostly on trying to start dbus daemon, hal and nfs mounts. xinetd also fails to start
I had at first thought something from NIS which I was previously using might still be running and causing some kind of conflict but I’ve double-checked that and it’s not the case
Anyone know what I should look for that may be causing this kind of behaviour as I’ve no idea where to even start
It may be trying to resolve the account names using ldap first which will fail because you have no networking at that point but take a long time to fail. Check that the order for passwd, shadow and group in /etc/nsswitch.conf are files ldap, i.e. looks it up in /etc/passwd first.
Can’t reboot just yet though, it’s moving a whole lot of files that isn’t likely to finish before I head off to bed so I’ll check if it’s done the trick in the morning
Putting the correct values in nsswitch.conf didn’t fix anything
I found a pile of errors in /var/log/messages relating to ldap tls so I disabled tls in the ldap server and client and rebooted again, still hanging on dbus but not on hal and xinetd started ok
A further look in /var/log/messages turned these up
Oct 31 12:42:37 gazelle dbus-daemon: nss_ldap: failed to bind to LDAP server ldap://localhost: Can’t contact LDAP server
Oct 31 12:42:37 gazelle dbus-daemon: nss_ldap: could not search LDAP server - Server is unavailable
So it looks to me as if dbus is starting before slapd which would explain it hanging (should slapd be starting before dbus and how would I change that?)
Before I took the tls setting off I could only get it to boot using Failsafe which I think I forgot to mention, now it boots normally but I still can’t login as the test ldap user I’ve added
auth include common-auth
account include common-account
password include common-password
session include common-session
From what you said in your last post Ken sounds like there should be more values, nothing there for ldap at all, a case of Yast not writing all the vaules it should be perhaps?
Those are includes so they “redirect”. You should look at the common-* files, they probably contain calls to some combination of unix and ldap modules.
I’ve no idea what they all should be but I’m guessing the entries with required pam_ldap.so in them are the ones we’re looking for, all new territory to me this
And I just kicked myself for not even realising the includes pointed elsewhere … it’s sunday which ain’t the day I do my best thinking
Never mind, it’s become a moot point for the moment, someone came round today in dire need due to a fried motherboard so I’ve had to reconfigure the machine as a windoze desktop for them to use until a new board for their machine arrives
I’ll have to revisit this when I get the machine I was using for testing this setup back
Thanks for trying to help me with this ken, you’re a true star as always
I’ll give it another shot next week and hopefully get a bit further with it under my own steam