Quote:
Originally Posted by marcmac 
makes me think that ldap isn't starting right, or can't be read.
Shut everything down
ps auxww | grep slapd
if it's still running, try killall -TERM slapd
then, ldap start, and ldap status
As to what caused this - what is ldap_url and ldap_master_url set to in zmlocalconfig?
|
Here is what I ran:
Code:
[root@mail ~]# su - zimbra
[zimbra@mail ~]$ zmcontrol stop
Host mail.hddbroker.com
Stopping stats...Done
Stopping mta...Done
Stopping spell...Done
Stopping snmp...Done
Stopping antivirus...Done
Stopping antispam...Done
Stopping imapproxy...Done
Stopping mailbox...Done
Stopping logger...Done
Stopping ldap...Done
[zimbra@mail ~]$ ps auxww | grep slapd
zimbra 17752 0.0 0.0 2400 432 pts/0 S+ 13:35 0:00 grep slapd
[zimbra@mail ~]$ ldap start
Started slapd: pid 17995
[zimbra@mail ~]$ ldap status
slapd running pid: 17995 After ldap was running, I tried to start Zimbra again and got this:
Code:
[zimbra@mail ~]$ zmcontrol start
Host mail.hddbroker.com
Unable to determine enabled services from ldap.
Unable to determine enabled services. Cache is out of date or doesn't exist.
Here is are the values from the zmlocalconfig as well:
Code:
[zimbra@mail ~]$ zmlocalconfig ldap_url
ldap_url = ldap://mail.hddbroker.com:389
[zimbra@mail ~]$ zmlocalconfig ldap_master_url
ldap_master_url = ldap://mail.hddbroker.com:389
At the time I didn't realize that zmldapinit would cause more problems otherwise I wouldn't have run it. I originally thought it was a password problem and that this command reset the passwords. Once I get this resolved I will file a feature request that any commands like zmldapinit should warn or require confirmation before executing. If I had seen a warning message I would have canceled.
As for the openldap.bak file, I have searched the entire server and cannot find a file by that name. I have a backup of Zimbra from the day before all of this happened. Is it possible to retrieve the ldap information from that backup?
Thank you.