[SOLVED] 5.0.7 Upgrade Failure - when hostname of server does not match cert

[dlbewley]

I just did a convoluted upgrade from ZCS 4.5.9 to 5.0.4, then RHEL 4.6 to 5.2, then ZCS 5.0.4 to 5.0.7. It worked fine. I did it that way because that is the way I had tested it previously and knew it would work.

My HTTP hostname and cert differ from my actual server hostname, so while on 5.0.4 I did:

zmlocalconfig -e zimbra_require_interprocess_security=0

which modified zimbra/conf/localconfig.xml. Then, unlike on my testbox, the upgrade to 5.0.7 worked without error.

[inigoml]

Same procedure applied and upgrade finished without problems.

zmlocalconfig -e zimbra_require_interprocess_security=0

[mmorse]

Bdial, just a heads up - someone else reported that they needed to use the workaround even with wildcard certs.

[SOLVED] Zimbra support line down. How do I get U1 support?

[bdial]

great thanks for the heads up

[jmiles]

Now that the offending bug is fixed in 5.0.8, is it safe to upgrade from 5.0.6 to 5.0.8 directly without having to execute any workaround commands?

[The Fold]

I have just upgraded our system from 5.0.5 and had to put in the command

zmlocalconfig -e zimbra_require_interprocess_security=0

as written to complete it, the suggested method in the Release Notes still caused an error to occur and the upgrade to fail.

[jmiles]

Forgive my ignorance, but I'm still not sure if I need to execute any commands prior to upgrading from 5.0.6 to 5.0.8. If the bug is fixed, does that suggest I shouldn't have to?

[dlbewley]

See page 30 of the release notes. They tell you what to do. You need to follow those instructions.

[jaydee]

Originally Posted by jmiles

Forgive my ignorance, but I'm still not sure if I need to execute any commands prior to upgrading from 5.0.6 to 5.0.8. If the bug is fixed, does that suggest I shouldn't have to?

Yes you do, I found that out the hard way.