[SOLVED] Upgrade from NE 6.0.5 to 6.0.6 failures

[batfastad]

Hi everyone

I just tried an upgrade from a perfectly working installation of the NE trial on 6.0.5 and all was going well until I noticed all the skins failed to install
Then zimlets and a whole bunch of other stuff
I was planning on purchasing the full license next week once I'd migrated our 3 remaining users.

Digging through the zmsetup log that was created, the first failure was this...

Sat Apr 10 11:36:24 2010 Returning cached server config attribute for zimbra.mydomain.com: zimbraId=0b49b7be-5335-4a49-b15a-13767e317027
Sat Apr 10 11:36:24 2010 already exists.
Sat Apr 10 11:36:24 2010 Saving CA in ldap ...
Sat Apr 10 11:36:24 2010 *** Running as root user: /opt/zimbra/bin/zmcertmgr deployca
** Importing CA /opt/zimbra/ssl/zimbra/ca/ca.pem into CACERTS...done.
** Saving global config key zimbraCertAuthorityCertSelfSigned...failed.
** Saving global config key zimbraCertAuthorityKeySelfSigned...failed.
** Copying CA to /opt/zimbra/conf/ca...done.
Sat Apr 10 11:36:29 2010 done.
Sat Apr 10 11:36:29 2010 Saving SSL Certificate in ldap ...
Sat Apr 10 11:36:29 2010 *** Running as root user: /opt/zimbra/bin/zmcertmgr savecrt self
** Saving server config key zimbraSSLCertificate...failed.
** Saving server config key zimbraSSLPrivateKey...failed.
Sat Apr 10 11:36:33 2010 done.
Sat Apr 10 11:36:33 2010 checking isEnabled zimbra-store
Sat Apr 10 11:36:33 2010 zimbra-store is enabled
Sat Apr 10 11:36:33 2010 Setting spell check URL...
Sat Apr 10 11:36:33 2010 Updating cached config attribute for Server zimbra.mydomain.com: zimbraSpellCheckURL=http://zimbra.mydomain.com:7780/aspell.php
ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException Loading the socket factory)
Sat Apr 10 11:36:34 2010 failed.
Sat Apr 10 11:36:34 2010 Setting service ports on zimbra.mydomain.com...

Then the skins failed to install, with this error being added after each one

ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException Loading the socket factory)

Then finally a whole bunch of these:

com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:main:1270895971136:adb87a73c04eeb6b
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:391)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:345)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getZimlet(LdapProvisioning.java:3829)
	at com.zimbra.cs.account.ldap.LdapProvisioning.getZimlet(LdapProvisioning.java:3805)
	at com.zimbra.cs.zimlet.ZimletUtil.deployZimlet(ZimletUtil.java:563)
	at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1789)
	at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:1888)
Caused by: javax.naming.CommunicationException: Loading the socket factory [Root exception is java.lang.ClassNotFoundException: com.zimbra.common.util.EasySSLSocketFactory]
	at com.sun.jndi.ldap.LdapPoolManager.isPoolingAllowed(LdapPoolManager.java:228)
	at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1570)
	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652)
	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)
	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
	at javax.naming.InitialContext.init(InitialContext.java:223)
	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)
	at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:377)
	... 6 more
Caused by: java.lang.ClassNotFoundException: com.zimbra.common.util.EasySSLSocketFactory
	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:247)
	at com.sun.jndi.ldap.VersionHelper12.loadClass(VersionHelper12.java:57)
	at com.sun.jndi.ldap.LdapPoolManager.isPoolingAllowed(LdapPoolManager.java:220)
	... 18 more

Tried rebooting the box then running zmcontrol status

Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Host zimbra.ourdomain.com
        antispam                Running
        antivirus               Running
        convertd                Running
        ldap                    Running
        logger                  Stopped
                zmlogswatchctl is not running
        mailbox                 Stopped
                zmmtaconfig is running.
                mailboxd is not running.
                zmmailboxdctl is not running
        mta                     Running
        snmp                    Running
        spell                   Running
        stats                   Running

And I can't access the Admin UI or ZWC
Anyone got any ideas?

Should I uninstall then re-install 6.0.5 and restore from backup?
Will restoring a full backup restore all my settings or is it just the account data?

So much for my weekend

Cheers, B

[batfastad]

Right well I managed to get up and running again but by uninstalling and re-installing 6.0.5 and doing a disaster recovery. Phew!!

However if anyone has any idea why this failed so spectacularly I'd love to know!
I'd quite like to be able to upgrade at some point

Also, would be really useful on the config screen after installation if you can select a localconfig file to load rather than going through all the menus.

Cheers, B

[ewilen]

I thought that upgrades weren't "allowed" on trials, but I don't know if the installer is smart enough to prevent you from trying.

[batfastad]

Oh really? Interesting!
I actually hope that is the problem otherwise my confidence in the Zimbra upgrade procedure has taken a major blow

Can anyone else confirm or deny that?

Or can anyone see anything obviously borked from my setup log snippets above?

Cheers, B

[batfastad]

Sorry to bump but can anyone confirm/deny that I can't upgrade the NE trial version?

About to put the money down for a full NE license tomorrow and don't really want to be paying money for more of the pain I suffered at the weekend

Cheers, B

[uxbod]

Out of curiosity has the cert expired or become corrupt ? Please check in the Admin GUI; and as you are using a self cert you could regenerate it.

[batfastad]

The cert was fine. I'd only been running the NE trial for about 45 days and already had migrated the "easy" users so it was just running on the self-signed cert generated at install time

Cheers, B

[ewilen]

I'm afraid I can't point to a definitive answer about upgrading trials, except that I found an earlier occasion when I said the same thing: [SOLVED] Upgrading from 5.x to 6.x NE

Back then I was only a few months off our trial/transition to paid license, so I probably knew what I was talking about. I seem to recall I learned this when I was trying to migrate a trial install to a different OS, which requires reinstalling.

[batfastad]

I'm hoping that's the case. Certainly hoping I won't see such a dramatic fail when I try and upgrade in the future!

I'll be buying the 15-mailbox starter pack tomorrow to extend our license... then at some point in the next week or so I'll try and upgrade again.
You'll hear it here first if it borks!

[tonster]

Originally Posted by ewilen

I thought that upgrades weren't "allowed" on trials, but I don't know if the installer is smart enough to prevent you from trying.

I'm unsure where you got that idea from, but we do not discourage or prevent upgrades for trial accounts. We like to keep our customers as close to the current released version as possible, so we would certainly like to have the customers who wish to purchase keep their systems up to date during the trial.