Fix Zimbra stats graph/cron jobs

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:

[root@zimbra crontabs]# cat crontab >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.ldap >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.logger >> crontab.zimbra
[root@zimbra crontabs]# cat crontab.mta >> crontab.zimbra
[root@zimbra crontabs]# cat >> crontab.zimbra

Finally,Load the crontab.zimbra file to crontab as follows:

[root@zimbra 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’.

Books on the shelf – March 2014

Books on the shelf – March 2014

At last Pavithra gets her copy of “Birds of the Indian Subcontinent” by Richard Grimmett, Carol Inskipp and Tim Inskipp.


And I bought John Berger’s “Understanding a Photograph”. Having read John Berger’s kannada translation of “ways of seeing” by H.A Anilkumar, I got interested by the title of this book. An another step to understand the art of painting with light “PHOTOGRAPHY”.

Vmware Workstation 10.x patch for Linux kernel 3.13

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 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 "compat_module.h"
#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
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);
+ transmit = (hooknum == VMW_NF_INET_POST_ROUTING);
+ transmit = (ops-&gt;hooknum == VMW_NF_INET_POST_ROUTING);

packetHeader = compat_skb_network_header(skb);
ip = (struct iphdr*)packetHeader;

Allow access to external git repositories

Many public git repositories have several alternate URLs; for instance, the 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.