Reaching out to others! Free & Open Source Software, Kannada, L10n, L18n Data Science, Cloud Computing & more…

Vmware workstation 8.0.4/player 4.0.4 fix for linux kernel 3.5.0

Weltall‘s blog gives us a patch to fix for vmblock installation issue for VMWare Workstation. Though he updates his blog regularly, I didn’t find the fix for Ubuntu 12.10 which runs on Linux kernel 3.5.0. One of the comments gave an hint to perform a little trick on vmblock module source of vmware workstation to get this working.
Here is how I got this working :

VMWare workstation 8.0.4 and player 4.0.4 after modifying

filesystem.c inside /usr/lib/vmware/modules/source/vmblock.tar

to look like this (Line 528)

And editing the patch file downloaded from Weltall’s blog to match workstation and player versions.

Now apply the patch and run the workstation to see the modules installation getting completed successfully.


Fix: fixquota fails with journaled quota support: not available with vzaquota (disabled)

If you’re running cPanel server on a OpenVZ hardware node, you might face issues with quota for few reasons:

1. Secondary quota might not have been enabled on hardware node.

You can verify by checking for “DISK_QUOTA=yes” in /etc/vz/conf/vz.conf

Also, QUOTAUGIDLIMIT needs to be set for the VPS in  /etc/sysconfig/vz-scripts/CT_ID.conf (PS: CT_ID is the container id of the VPS)

2. You should have initialized the quota via WHM.

If you continue to face problem even after applying both fixes, re-initializing quota might help as per  Here is the excerpt:

WHM/Cpanel, a popular commercial web-based control panel for Linux, has a tendency to overwrite the special quota files in the VE context. I am referring to:

lrwxr-xr-x 1 root root 39 Jun 8 17:27 -> /proc/vz/vzaquota/00000073/
lrwxr-xr-x 1 root root 38 Jun 8 17:27 aquota.user -> /proc/vz/vzaquota/00000073/aquota.user

The result of these being overwritten will be WHM showing “unlimited” quota reports for all users in the system. An quick solution to this is to run these commands from within the VE as root:

rm -rf /aquota.user 2>/dev/null
rm -rf / 2>/dev/null
unlink /aquota.user 2>/dev/null
unlink / 2>/dev/null
for x in `find /proc/vz/vzaquota/ | tail -2 `; do ln -s $x / ; done

journled quota support warning didn’t get resolved even after this. Yet to check for the core reason for the same.


  I have been searching for the right alternative for managing my Xen VM’s and hosts. Its a pain to boot a Windows VM just for  accessing XenCenter. You can download OpenXenManager from or Install it on your Ubuntu machine using the following command:

#sudo apt-get install openxenmanager

PS: Running it from the source from link didn’t work for me on Ubuntu 12.04 but found it working after installing via apt-get.

Once installed, its very similar to working with the windows version of Citrix Xen Center.


Hope you too find it useful.


Nagios plugin to check DELL OpenManage (OMSA)

Those who doesn’t like configuring a long list of alert mechanism of on servers, here comes a savior – check_openmanage Nagios plugin. Making life easier.

More info on this plugin:
check_ checks the hardware health of Dell servers running Server Administrator (OMSA). The plugin can be used remotely with SNMP or locally with NRPE, check_by_ssh or similar, whichever suits your needs and particular taste. The plugin checks the health of the storage subsystem, power supplies, memory modules, temperature probes etc., and gives an alert if any of the components are faulty or operate outside normal parameters.

Here are some of its results:

dell-server01 ~$
OK – System: ‘PowerEdge R710′, SN: ‘XXXXXXX’, 72 GB ram (18 dimms), 1 logical drives, 2 physical drives

nagios-server ~$ check_openmanage -H dell-server02
Physical Disk 1:3 [Seagate ST3300007LC, 300GB] on ctrl 0 needs attention: Failure Predicted

It’s neat output and nagios ability to keep us alerted about server issues via email, sound alert through nagios plugins etc makes it feel good to keep a healthier RAID array running on servers.

Tags: , , ,

Fix: iptables: Unknown error 4294967295

Following error is noticed when you are running in the VM.

: Unknown error 4294967295

Main reason for this error iptables support missing in OpenVZ.

Here are the quick steps to resolve this issue permanently:

1. Define which iptables modules are available for VEs.

Edit /etc/sysconfig/iptables-config file on a OpenVZ hardware node:

IPTABLES_MODULES=”ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp”

Edit /etc/sysconfig/vz file on a OpenVZ hardware node:

ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp”

Note:– iptables modules list in IPTABLES and IPTABLES_MODULES parameters in /etc/sysconfig/vz and /etc/sysconfig/iptables-config files should be placed in one single line, no linebreaks is allowed in this parameter.

Restart OpenVZ server
# service vz restart

2. Increase ‘numiptent’ parameter for the VE you need to install APF into. This parameter limits the amount of iptables rules available for a VE. Default APF configuration requires ~400 rules. Lets set it to 400 in the example below for VE #101:

# vzctl set 101 --numiptent 400 --save

3. Start APF inside the VE:
# /etc/init.d/apf start

Tags: , ,