Zimbra desktop installation on my system was prompting me to upgrade the installation to the latest 7.2.7 version. I downloaded the installer (zdesktop_7_2_7_ga_b12059_20150629062326_linux_i686.tgz) from Zimbra and found that it was not working. For couple of weeks there was no discussion around this on zimbra forums too.
Looking at the logs displayed the following error:
STARTED Jetty ಸೋ ಆ 3 23:03:55 IST 2015
Error: This Java instance does not support a 32-bit JVM.
Please install the desired version.
STOPPED ಸೋ ಆ 3 23:03:55 IST 2015
This forced me to change the default java version that I’m using on my desktop to and i386 version.
$ sudo update-alternatives –config java
There are 4 choices for the alternative java (providing /usr/bin/java).
Selection Path Priority Status
0 /usr/lib/jvm/java-8-oracle/jre/bin/java 1077 auto mode
1 /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java 1071 manual mode
* 2 /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java 1070 manual mode
3 /usr/lib/jvm/java-8-oracle/jre/bin/java 1077 manual mode
4 /usr/lib/jvm/java-9-oracle/bin/java 1076 manual mode
Press enter to keep the current choice[*], or type selection number:
This sorted the issue with Zimbra desktop quickly.
Zimbra desktop installation on a brand new installation of Ubuntu/Linux mint 64 bit release always fails (Tried on Ubuntu 14.04/14.10/Linux Mint 17 etc) due to the lack of 32 bit architecture support.
I confirmed it by running Zimbra desktop with ia32-libs added to the distribution and manually running zdclient as follows:
$ /opt/zimbra/zdesktop/linux/prism/zdclient -webapp “/home/techfiz/zdesktop/zdesktop.webapp” -override “/home/techfiz/zdesktop/zdesktop.webapp/override.ini” -profile “/home/techfiz/zdesktop/profile”
Couldn’t load XPCOM.
This is mainly because the way 32 architecture support used to be enabled on the distro’s. Earlier installing ia32-libs package was quire easier via apt-get. Now the best way to install 32 bit architecture support is as follows:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs
Now try opening Zimbra desktop, it works like a charm.
If your zimbra scheduled tasks are not running or if you don’t see your stats graphs on admin panel, the first thing that you should check if zimbra’s cronjobs. When you reinstall/move your zimbra installation we normally tend to miss cron job setups required for zimbra.
To fix this, find the Zimbra crontabs directory at /opt/zimbra/zimbramon/crontabs
Now, lets put alwal the cronjob’s to a single file (just to make your job easier) as follows:
[[email protected] crontabs]# cat crontab >> crontab.zimbra
[[email protected] crontabs]# cat crontab.ldap >> crontab.zimbra
[[email protected] crontabs]# cat crontab.logger >> crontab.zimbra
[[email protected] crontabs]# cat crontab.mta >> crontab.zimbra
[[email protected] crontabs]# cat crontab.store >> crontab.zimbra
Finally,Load the crontab.zimbra file to crontab as follows:
[[email protected] crontabs]# crontab crontab.zimbra
Voila, that’s it. Wait for few minutes to start seeings the graphs. You can also verify the cornjobs by using ‘crontab -l’.
If you’re trying to work on Zimbra migration etc, you might require to know the Zimbra LDAP master URL. Generally it should work as ldap:domainname:389, if it doesn’t then use the following command as zimbra to get the right ldap master url.
#su – zimbra
$zmlocalconfig -s zimbra_ldap_password ldap_master_url
The same command might reveal the admin password too.
You can also use the following commands to retrieve the ldap admin password:
$zmlocalconfig -s | grep ldap_amavis_password
$zmlocalconfig -s | grep ldap_nginx_password
$zmlocalconfig -s | grep ldap_postfix_password
$zmlocalconfig -s | grep ldap_replication_password
$zmlocalconfig -s | grep ldap_root_password
$zmlocalconfig -s | grep zimbra_ldap_password
Reference: Set the password in the LDAP database
If you want Zimbra to work on both port 80 and 443, You can use the following commands:
su zimbra –
After this, restart zimbra and you will be able to login to Zimbra on port 80 as well.
PS: Running Zimbra on port 80 is not secure.
If you’re changing your system and trying to reconfigure your zimbra, you might have to use the following commands:
su – zimbra
The above commands come very handy when you might have mistakenly typed a wrong hostname and configured zimbra to continue using it.
Before making changes to the zimbra server name, ensure the hostname and the DNS is configured fine.
For more info refer to: https://wiki.zimbra.com/index.php?title=Zmsetservername
Self-Signed Certificate on your Zimbra server is expired? Follow the instructions given below, and you will be back online asap.
1. Begin by generating a new Certificate Authority (CA).
/opt/zimbra/bin/zmcertmgr createca -new
2. Then generate a certificate signed by the CA that expires in 365 days.
/opt/zimbra/bin/zmcertmgr createcrt -new -days 365
3. Next deploy the certificate.
/opt/zimbra/bin/zmcertmgr deploycrt self
4. Next deploy the CA.
5. To finish, verify the certificate was deployed to all the services.
Resetart your zimbra and you will be good.
I have this tested against Zimbra 8.
Login to Your Zimbra Server with root login and password .
Type following commands :-
[[email protected]]# su – zimbra
This Command will change the Console name to
[[email protected] ~]$
Then Type Following command.
[zimbr[email protected] ~]$ zmprov -l renamedomain olddomain.com newdomain.com
This has been tested against Zimbra 6, 7 and 8.