[SOLVED] Problems upgrading from 5.0.16 to 5.0.18

hchan · Postby **hchan** » Tue Jul 14, 2009 8:23 pm

In the installation phase, getting:
-------------------------
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
------------------------
When trying to start, getting:
------------------------
Starting ldap...Done.

Unable to determine enabled services from ldap.

Enabled services read from cache. Service list may be inaccurate.

Starting logger...Done.

Starting mailbox...Done.

Starting antispam...Done.

Starting antivirus...Done.

Starting snmp...Done.

Starting spell...Done.

Starting mta...FAILED

Starting zmmtaconfig...zmmtaconfig is already running.

Starting saslauthd...saslauthd[22546] :set_auth_mech : failed to initialize mechanism zimbra

failed.

zmsaslauthdctl failed to start

Starting stats...Done.
--------------------------------
Dead in the water at the moment. Any thoughts? I've been pouring through the forums looking and trying a few things (e.g. permission fix, explicit https URL in saslauthd.conf.in) but still no go.
Thanks in advance.

1542brian · Postby **1542brian** » Tue Jul 14, 2009 8:55 pm

can you provide a little information like the operating system you are running and the full name of the zcs version you downloaded/installed?

hchan · Postby **hchan** » Tue Jul 14, 2009 8:59 pm

RHEL 4.6
zcs-5.0.18_GA_3011.RHEL4.20090707151706.tgz
Hope you're still there...
Thanks.

1542brian · Postby **1542brian** » Wed Jul 15, 2009 3:45 pm

this problem was solved last night via support. turned out to be expired ssl certificates.

hchan · Postby **hchan** » Wed Jul 15, 2009 3:50 pm

Yes, thanks to Brian and support, the issue was resolved to be an expired self signed certificate.
However, why this didn't happen to the last few upgrades is puzzling since the certificates had expired before.
Anyway, I'm going to look for documents here on how best to manage Zimbra servers with self signed certificates. Also, given my experience looking for information on solving this problem, this thread should be another data point that if those error messages come up, one likely source is an expired certificate.

nlongmuir · Postby **nlongmuir** » Thu Jul 30, 2009 8:18 pm

What commands were run and on what servers ... the same is happening to me within a multi-server env