We recently upgraded a Zimbra server to CentOS 5 which was also running an install of Apache + mod_ssl for some other web apps.
The Zimbra installation on the whole working fine. However, incoming emails were not being received. Instead this error was displayed in the log:
Installing the openssl 0.9.7a library solved this problem. But caused another...
May 6 08:46:35 black postfix/smtpd: initializing the server-side TLS engine
May 6 08:46:35 black postfix/master: warning: process /opt/zimbra/postfix-2.2.9/libexec/smtpd pid 29745 killed by signal 11
May 6 08:46:35 black postfix/master: warning: /opt/zimbra/postfix-2.2.9/libexec/smtpd: bad command startup -- throttling
This caused Apache + mod_ssl to segmentation fault on start up. Apache + mod_ssl requires openssl 0.9.8b (installed by default as the openssl package).
Having both libraries installed and creating symlinks for:
Zimbra - /lib/libssl.so.4 -> /lib/libssl.so.0.9.7a
Apache -/lib/libssl.so.6 -> /lib/libssl.so.0.9.8b
Does NOT work either and still causes Apache to seg fault on start up. It appears that Apache also uses the /lib/libssl.so.4 symlink. So having openssl 0.9.7a and openssl 0.9.8b installed together is creating a conflict.
It may be possible to point Zimbra to specifically the libssl.so.0.9.7a library and let Apache use openssl 0.9.8b however, I was not able to get this to work.
Anyone else encountered this problem? Or can suggest a possible solution? I would really love to hear it Otherwise, I'll just wait for Zimbra to be supported on RHEL5.
On another topic, I am seeing lots of these entries in the Zimbra log. What does this mean and is this another problem?
May 6 04:40:02 black slapd: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed