Everything has been running fine for months. ...
... it seems after the LDAP daemon was stopped, it could not restart.
Have you tried to figure out why this is?
Jan 20 11:27:56 school1 rpc.statd nss_ldap: failed to bind to
server ldap://10.0.0.100 Can't contact LDAP server
Jan 20 11:27:56 school1 rpc.statd nss_ldap: reconnecting to LDAP
server (sleeping 64 seconds)...
That's just a client program letting you know that it can't contact
its LDAP server. It would be more interesting to know what's
preventing that LDAP server (slapd) from starting up.
The 10.0.0.100 and 127.0.0.1 are the same server and is the one that
LDAP is sitting on so it is not trying to contact another server with
Irrelevant. What is preventing slapd from starting up? If the loglevel
statement in your slapd.conf is still set to "none", comment it out,
or set it to something more helpful (like 256), restart slapd and see
what shows up in the syslog. If that doesn't give you enough
information, increase the loglevel until it tells you why it's not
Is my db corrupted possibly after the electric outage?
Possibly, but you will likely save yourself a lot of time and effort
if you first try to figure out what the actual cause of the problem is
before you start jumping to conclusions. Still, it's always good to
have a backup.