Many applications which look for 32bit packages on your Debian/Ubuntu/Mint packages would need ia32-libs packages. Earlier it was possible to get this package installed and later on it has been removed from all distributions. The best way to get back the 32bit package support is to add the architecture to dpkg as follows:
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install ia32-libs
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’.
Vmware Workstation breaks if you try using upcoming Linux kernel release’s and at the same time, VMWare community moves fast to push a quick patches to applied for those who dare to use cutting edge beta OS on their machines.
WoodyZ on https://communities.vmware.com provides a patch which just works for Linux Kernel 3.13.
Here is the patch provided from WoodyZ for your quick reference.
Apply the patch to /usr/lib/vmware/modules/source/vmnet.tar (Extract, apply the patch using patch command, compress the files back to vmnet.tar) and run vmware workstation again.
--- vmnet-only/filter.c 2013-10-18 15:11:55.000000000 -0400
+++ vmnet-only/filter.c 2013-12-21 20:15:15.000000000 -0500
@@ -27,6 +27,7 @@
#include <linux/mutex.h> #include <linux/netdevice.h> +#include <linux/version.h> #if COMPAT_LINUX_VERSION_CHECK_LT(3, 2, 0)
# include <linux/module.h> #else
@@ -203,7 +204,11 @@
static unsigned int
+#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 13, 0)
VNetFilterHookFn(unsigned int hooknum, // IN:
+VNetFilterHookFn(const struct nf_hook_ops *ops, // IN:
struct sk_buff *skb, // IN:
@@ -252,7 +257,12 @@
/* When the host transmits, hooknum is VMW_NF_INET_POST_ROUTING. */
/* When the host receives, hooknum is VMW_NF_INET_LOCAL_IN. */
- transmit = (hooknum == VMW_NF_INET_POST_ROUTING);
+#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 13, 0)
+ transmit = (hooknum == VMW_NF_INET_POST_ROUTING);
+ transmit = (ops->hooknum == VMW_NF_INET_POST_ROUTING);
packetHeader = compat_skb_network_header(skb);
ip = (struct iphdr*)packetHeader;
Many public git repositories have several alternate URLs; for instance, the kernel.org repositories have git://, http://, and https:// URLs.
The common URL schemes for git repositories are:
ssh:// – default port 22
git:// – default port 9418
http:// – default port 80
https:// – default port 443
Above list gives you the respective ports which needs to be kept open on the firewall to be able use your Git repositories.
The git:// protocol uses port 9418, so you should make sure your firewall allows outbound connections to this port.
If you use csf ensure this port is enabled in TCP_IN and TCP_OUT.
To test if the git:// is working you can try the following command on the server
netstat -ntpl|grep -i 9418
To test it externally you can telnet to the port for the respective server’s ip.
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: http://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.