Successful upgrade here, too, with ZCS 5.0.6 --> ZCS 5.0.7 on CentOS 5.2 64-bit (which was upgraded from CentOS 5.1 64-bit simply with `yum update` and `reboot`). Great job, Zimbra!
Just FYI for in case anyone has a separate Apache installation coexisting with Zimbra, I did run into something small, but was *easily* resolved. Here's my story and I hope it helps someone:
During the upgrade, a "port conflicts" message came up. Apache and Zimbra coexists using the instructions here:
ZimbraApache - Zimbra :: Wiki Provide HTTP(s) Integration with Apache - Zimbra :: Wiki CLI zmtlsctl to set Web Server Mode - Zimbra :: Wiki
The installation of Apache runs on port 80 and 443 and Zimbra on alternative http and https ports. (Apache was installed and running prior to the Zimbra installation and under the current circumstances, it cannot be moved off to another server).
I did run into the following messages:
Code:
[root@hostname zcs-5.0.7_GA_2444.RHEL5_64.20080626020449]# ./install.sh --platform-override
...<snip>...
Checking for port conflicts
Port conflict detected: 80 (zimbra-store)
Port conflict detected: 443 (zimbra-store)
Port conflicts detected! - Any key to continue
There, I opened new shell and shutdown Apache (note: from here on, host and FQDN have been changed):
Code:
[root@hostname ~]# /etc/init.d/httpd stop
Stopping httpd: [ OK ]
[root@hostname ~]#
and continued with the installation. It finished succesfully.

I started Apache back up:
Code:
[root@hostname log]# /etc/init.d/httpd start
Starting httpd: [ OK ]
I then logged into the browser for the admin GUI (
https://hostname:7071) and found that mailbox was not running. The /var/log/zimbra.log agreed:
Code:
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: antispam: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: antivirus: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: ldap: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: logger: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: mailbox: Stopped
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: mta: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: snmp: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: spell: Running
Jun 29 22:38:06 hostname zimbramon[24896]: 24896:info: 2008-06-29 22:38:01, STATUS: hostname.domain.com: stats: Running
Solution:
I just simply stopped and started Zimbra again:
Code:
[root@hostname log]# /etc/init.d/zimbra start
[root@hostname log]# /etc/init.d/zimbra stop
Everything's been running great since!
To summarize:
1. Stop Apache: `/etc/init.d/httpd stop`
2. Upgrade zimbra: `./install.sh` or `./install.sh --platform-override`
3. Start Apache: `/etc/init.d/httpd start`
4. Restart Zimbra: `/etc/init.d/zimbra stop` and `/etc/init.d/zimbra start`
5. Log in the admin GUI and check.
