Zimbra: Problem after upgrading from 5.0.10 to 5.0.14

Zimbra: Problem after upgrading from 5.0.10 to 5.0.14

Zimbra: Problem after upgrading from 5.0.10 to 5.0.14 150 150 Roderick Derks

Problem

Release 5.0.14_GA_2850.F7_20090303145157 F7

I can not contact the Zimbra server anymore using a Zimbra client or the website.

# tail -f /var/log/zimbra.log
Mar 28 01:12:15 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Sleeping…Key lookup failed.
Mar 28 01:12:16 my_servername postfix/smtpd[6505]: warning: problem talking to service rewrite: Success
Mar 28 01:12:16 my_servername postfix/master[3629]: warning: process /opt/zimbra/postfix/libexec/trivial-rewrite pid 7850 exit status 1
Mar 28 01:12:16 my_servername postfix/master[3629]: warning: /opt/zimbra/postfix/libexec/trivial-rewrite: bad command startup — throttling
Mar 28 01:12:22 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping Global system configuration update.
Mar 28 01:12:22 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
Mar 28 01:12:28 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping All Reverse Proxy URLs update.
Mar 28 01:12:28 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
Mar 28 01:12:32 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping All Reverse Proxy Backends update.
Mar 28 01:12:32 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
Mar 28 01:12:35 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping All Memcached Servers update.
Mar 28 01:12:35 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
Mar 28 01:12:38 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update.
Mar 28 01:12:38 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
Mar 28 01:12:42 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Skipping Configuration for server my_servername.r71.nl update.
Mar 28 01:12:42 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: gs:my_servername.r71.nl ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)
Mar 28 01:12:42 my_servername zimbramon[2461]: 2461:info: zmmtaconfig: Sleeping…Key lookup failed.

Hostfiles seem to be OK, DNS works great… ip address did not change…
I tried to follow up advice in the ZIMBRA forum but I could not find a solution.

Problem started after the time I restarted ZIMBRA for the first time after the upgrade, so first it worked after the upgrade!

Solution

Well… this one took me a while.

I had to recreate the certificate. The guide was very helpfull.

Then I ran into the problem the MTA would not start anymore:

[zimbra@my_servername ~]$ zmcontrol start
Host ventoux.r71.nl
Starting ldap…Done.
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.
postalias: warning: /etc/aliases, line 97: need name:value pair
postsuper: fatal: scan_dir_push: open directory defer: Permission denied
postfix failed to start
Starting saslauthd…done.
Starting stats…Done.

Solution to this problem:
# /opt/zimbra/libexec/zmfixperms (run as root)

I’m back in business again.

Roderick Derks

Liefhebber van fietsen, van het oplossen van IT puzzels, en van het delen van informatie om anderen te helpen.

All stories by:Roderick Derks

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Your Name (required)

Your Email (required)

Subject

Your Message

Your Name (required)

Your Email (required)

Subject

Your Message