5.0.11 > 5.0.12

[Bill Brock]

5 out of the top 10 Installation threads are 5.0.12 upgrade issues. Has this frequency of upgrade issues been the norm for other versions?

I would like to hear about successful upgrades as well from anyone out there.

I haven't upgraded in 5 version because of issues. I would like to hear that there aren't so many before I proceed with this one.

[uxbod]

Every upgrade I have performed has gone without issue Bill.

[jholder]

The most common issue is a logger database problem. Usually the logger is corrupt or just not functioning, and the admin never attends to it (or just doesn't care). The upgrade script tries to start it, and access it, but fails resulting in at least 3 of the problems I've seen.

We could do more to prevent this condition, so last night we had a discussion about it, and in 5.0.13 we will give the user an option to check the logger db before upgrading. We already do that for the mailbox mysql db.

A thing to remember is that most people who never have an issue with an upgrade, never post. People only usually only post if they have an issue.

The good news is that the Zimbra community support is by far the very best of anyone. We have some just fantastic moderators and contributors who all stand ready to help should something bad happen.

john

[gnyce]

I've had no problems with any previous upgrades. For 5.0.11 --> 5.0.12, would it make sense to do a check of the logger db before the upgrade? Is there a zimbra script already in place that will do that, and I just need to run?

[Bill Brock]

Thank you for your replies. I have never had any issues in the past. And I don't anticipate any this time around. Just a little gun shy. :-)

[uxbod]

Well you always have you backups Bill just in case ... you are taking them I hope

[kirme3]

Just so you know, if it helps, I upgraded my test system from 5.0.10 to 5.0.12 last night and had no issues.

[Dirk]

Another voice in the wilderness: My upgrade from 5.0.11 to 5.0.12 went swimmingly also.

[tross]

We just upgraded our Dev environment from 5.0.10 NE to 5.0.12 yesterday. It went easily and without issue as usual. Things look good with our testing so far!

[jholder]

I'm probably going to jinx this, but you probably should know.

This is by far one of the most QA's releases we've ever done. That's why it took so long to get it out, because there were issues we felt we just had to fix. Not just with the patch, but with current installs as well.