My server went into some altered state of reality and Zimbra (open source) was unresponsive to clients. I couldn't stop zimbra, nor could I restart the machine in an orderly fashion. I had to do a hard stop by holding down the power button until it stopped, then reboot. The system itself came back pretty much normally, but Zimbra won't start up normally. I tried this:

# su - zimbra
$ ldap stop
$ cd /opt/zimbra/openldap-data
$ /opt/zimbra/sleepycat/bin/db_recover

But that didn't do it this time. Here is what I get when I try to start up:

G4-Server:~ zimbra$ zmcontrol stop
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
G4-Server:~ zimbra$ zmcontrol start
Starting ldap...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting snmp...Done.
Starting spell...FAILED

Starting mta...Done.
G4-Server:~ zimbra$ zmcontrol status
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Stopped
zmapachectl is not running
G4-Server:~ zimbra$

I am hoping that someone out there knows what to do about this...