zmprov crashes asfter upgradefrom zimbra 8.6 to zimbra 8.8.15

[kkimani]

I'm getting an error whenever I run the zmprov command as below
zimbra@mail:~$ zmprov ms mail.xxxxx.com zimbraMtaSmtpSaslPasswordMaps lmdb:/opt/zimbra/conf/relay_password
Exception in thread "main" java.lang.NoSuchFieldError: INSTANCE
at org.apache.http.impl.io.DefaultHttpRequestWriterFactory.<init>(DefaultHttpRequestWriterFactory.java:53)
at org.apache.http.impl.io.DefaultHttpRequestWriterFactory.<init>(DefaultHttpRequestWriterFactory.java:57)
at org.apache.http.impl.io.DefaultHttpRequestWriterFactory.<clinit>(DefaultHttpRequestWriterFactory.java:47)
at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<init>(ManagedHttpClientConnectionFactory.java:83)
at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<init>(ManagedHttpClientConnectionFactory.java:96)
at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<init>(ManagedHttpClientConnectionFactory.java:105)
at org.apache.http.impl.conn.ManagedHttpClientConnectionFactory.<clinit>(ManagedHttpClientConnectionFactory.java:63)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$InternalConnectionFactory.<init>(PoolingHttpClientConnectionManager.java:601)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:180)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:164)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:155)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.<init>(PoolingHttpClientConnectionManager.java:131)
at com.zimbra.common.util.ZimbraHttpConnectionManager.<init>(ZimbraHttpConnectionManager.java:206)
at com.zimbra.common.util.ZimbraHttpConnectionManager.<clinit>(ZimbraHttpConnectionManager.java:56)
at com.zimbra.common.soap.SoapHttpTransport.<init>(SoapHttpTransport.java:80)
at com.zimbra.cs.account.soap.SoapProvisioning.soapSetURI(SoapProvisioning.java:455)
at com.zimbra.cs.account.ProvUtil.initProvisioning(ProvUtil.java:1035)
at com.zimbra.cs.account.ProvUtil.main(ProvUtil.java:4156)


Any help I will appreciate

[paierh]

Hello!

I had the same issue after upgrading our dev server.
Looks like there are left-overs in your Java class-path which cause an old version of the apache http-client to be loaded before the correct one.

DISCLAIMER - It worked for me, that does not imply it will work for you.

I used the following to cleanup any old java files from previous installations:

Code: Select all

sudo mkdir /tmp/jars.bak
sudo find /opt/zimbra/lib /tmp/jars.bak -type f -name '*.jar' ! -newermt '6 month ago' -exec echo sudo mv {} /tmp/jars.bak \;

This will give you a list of mv commands which will move old jar files to a temp dir.

After moving those files I generated a list of stale symlinks to also remove:

Code: Select all

sudo find /opt/zimbra/lib -xtype l -exec echo sudo mv {} /tmp/jars.bak \;

After the class-path has been cleaned up zmprov worked again.

I also recommend to rebuild the mailboxd class files:

Code: Select all

mailboxdctl stop
cd /opt/zimbra/jetty/work/zimbra
rm -rf *
mailboxdctl start

Hope that helps!

Regards
Harald

[Zuser]

We had the same moving from 8.8.11 to 8.8.15, the reason was an old manual installation of ZxSuite Talk under an older version (8.8.6 IIRC) that didn't uninstall correctly.

Moving /opt/zimbra/lib/jars/zcs-lib-apache-httpcore4.jar and /opt/zimbra/lib/jars/zcs-lib-apache-httpclient4.jar already made both zmmailbox and zmprov work for us, deleting all "old" jars broke stuff, make sure you have a backup if moving these two by themselves doesn't work

Support suggested some other stuff like:
- removing all symlinks from /opt/zimbra/lib/jars/
- uninstalling biz_zcs_vnc_talk_zimlet and biz_vnc_admin_talk_zimlet zimlets
- removing all zcs-libs*.jar files from /opt/zimbra/lib/jars/ (these are apparently installed by the above zimlets)
- (re)moving /opt/zimbra/jetty_base/webapps/zimlet/WEB-INF/lib/ if it exists (probably cleaned by uninstalling said zimlets, didn't exist here)
but these were not necessary for the zmmailbox/zmprov solution.