- 1 Hyper-V 2012 R2: Pros and Cons of Generation 1 vs. Generation 2 VMs
- 2 Harnessing the Power of Hyper-V Network Virtual Switches
- 3 Working with SSH and Secure FTP Servers in Windows
- 4 Discover Windows 8's Hidden Server Features
- 5 Server Virtualization Customer Reviews: VMware, Hyper-V, XenServer and More
LDAP Master Server Problems
If your master server is down but the slaves are OK, ldapsearch and other lookups will work fine. But if you try to modify the database (e.g., with ldapadd), you'll get this kind of error message:
ldap_add: Referral (10) referrals: ldaps://masterldap.example.com/uid=test,ou=People, dc=example,dc=com
You can confirm the diagnosis by trying: ldapsearch -H ldaps://masterldap.example.com to force a bind to the master server.
The next stage is to find out what's causing the problem. Set the loglevel in /etc/ldap/slapd.conf to 1, then restart slapd and check the logs.
Two common problems:
- An old slapd process that hasn't been killed off properly. Check with ps and kill it if necessary.
- An alock problem, which looks like this in the log:
To resolve, remove the /var/lib/ldap/alock file (or check your slapd.conf for your local data directory). Run db_recover to fix the database, or just restart slapd and it should recover itself. You may need to give it a little time or restart it again.
slapd: bdb_db_open: alock package is unstable slapd: backend_startup_one: bi_db_open failed! (-1)
Remember to return the loglevel to normal afterward, or the server will be very slow. Also, consider using monitoring software to catch these silent problems!