[SOLVED] Upgrade: 5.0.19 --> 6.0.5. Good to go?

[AutootuA]

I finally have Zimbra 5.0.19 moved from my old server running Ubuntu 6.10 to my new one running Ubuntu 8.04 LTS. I now want to start the upgrade process for Zimbra to 6.0.5.

I've haven't read any gotchas about skipping 5.0.20 - 5.0.21 and going straight from 5.0.19 to 5.0.22 first. But is that necessary? I'm thinking about going straight to 6.0.5?

I read in the release notes for 6.0.x:

"Important: Upgrades from ZCS 5.0.19 or later 5.0.x releases to ZCS 6.0.0 or
6.0.1 will fail. We recommend customers running 5.0.19 or later 5.0.x releases
upgrade to 6.02 or later 6.0.x releases when they choose to move to the 6.0.x
series. (Bug 42609)"

Anyone have any experience here going from 5.0.19 to 6.0.5?

[padraig]

upgraded from 5.0.18 -> 6.0.4NE on RHEL4_64 no problem

[padraig]

Also Upgrading 5.0.21 -> 6.0.5 SSL Server Certs Changed

[lindsey]

We had a few gotchas for a 5.0.19 -> 6.0.5 upgrade last night:

1. Our mailboxd_java_options specified -Xss options for the stack size.
Zimbra 6.0 no longer honors that option, so it falls back to the value
of mailboxd_thread_stack_size, but ours was set to 1024 (who knows
why), so mailboxdctl was failing with 'The stack size specified is too small'
errors.

2. None of our zimlets were installed. We had to copy them into the
new zimlets-deployed directory and restart.

3. Our changes to httpd.conf were lost, so we had to re-add them.

4. /var/log/zimbra-stats.log needed to be created and owned by zimbra
before zmlogger would start (that's probably because we use syslog-ng
instead of syslog).

5. We can no longer log into the Admin interface.

Chris

[AutootuA]

Upgraded this morning with NO issues. Smooooooth as silk...


This was a update to a fresh installation of 5.0.19 on a Ubuntu 8.04 LTS server. Basic install. Nothing added. I had already moved all our email accounts from my old 5.0.19 install running on a 6.10 Ubuntu server using zmztozmig before the upgrade. The new godaddy certificate also installed without a hitch.
.
.
.