Zimbra Forums

Typo on my part
/opt/zimbra/conf/ca
--Quanah

Given that 5.0 will rely heavily on TLS support, simply removing the certs definitions will not work. 5.0 beta 3 in fact relies on being able to negotiate startTLS as part of a migration script if you already have ZCS installed.

What are the contents of

/opt/zimbra/ca

?

[quote user="jgiese"]Edit the /etc/redhat-release file replacing original release information:

[/QUOTE]
I believe this will be fixed in the next 4.5 release so that modifying /etc/redhat-release is not necessary on CentOS installs.
--Quanah

No guess, and the current release doesn't support SLES 10 64-bit, so a rebuild won't help.
You can track Bug 15165 - SLES10 64 bit support
to see when a release is assigned to it.
--Quanah

SLES10_64 is also targeted for 4.5, but no specific release yet.

The error you are reporting appears to indicate that slapd cannot bind to port 389 on the system you are using. In general, this would be because something else (OpenDirectory?) is already listening on that port, or there is a hostname mismatch, etc.

[quote user="phantom32i"]

__________________
Does that mean if i do not backup manually.. db_recover will still work most of the time?[/QUOTE]
Depends on the type of failure. If your disk died, then no, there's nothing it could do about that.
--Quanah

The alock file is used by slapd to track the state of the BDB database that is used to store the data. In your case, it appear something happened that made the alock file unstable. Sometimes removing it will allow slapd to recover. It didn't in your case. The db_recover command does a force recover ...

Okay... Try this:
cd ~/openldap-data

/opt/zimbra/sleepycat/bin/db_recover