Disk Space Usage and bandwidth data (RRD)
In cPanel™ 11.25 the number of bandwidth data (RRD) files has increased. File names have also changed for clarity. There are now two files for each protocol and for the aggregate.
As noted above, the number of RRD files generated by the system increased with cPanel™ 11.25. With this comes an increase in the disk space used by /var/cpanel/bandwidth.
To prevent issues related to disk consumption by the RRD files, during the cPanel™ Update /usr/local/cpanel/bin/chk_bwrrd_space is used to examine the disk mount that contains /var/cpanel/bandwidth.
If insufficient disk space is detected then bandwidth generation is disabled.
Cpanel Bandwidth Statistics Generation
The bandwidth statistics system in cPanel™ uses RRDTool [http://oss.oetiker.ch/rrdtool/] to track the data and generate
resulting graphs and meters. In cPanel™ 11.24 and prior versions, the way the RRDTool data was interpreted by the sys-tem could vary according to which subsystem was examining the data. This often resulted in inconsistent interpretations of the data, as well as missing data.
For cPanel™ 11.25, every aspect of the product that handled RRDTool data was overhauled and consolidated into a single subsystem. The end result is a consistent system that generates reliable and accurate statistics and data.
Bandwidth is getting calculated higher than expected in Ensim Pro for Linux
For RHEL4, Cent OS 4.1, Cent OS 4.2, Cent OS 4.3:
http://download.swsoft.com/ensim/download/pro/linux/4.1.0/hotfix/bandwidth2/rhel4/webppliance-bandwidth-4.1.0-38.rhel.4ES.i386.rpm
Installation Procedure:
rpm -Uvh webppliance-bandwidth-4.1.0-38.[os version].i386.rpm
service webppliance restart
service bandwidth_manager restart
service [affected service] restart (where affected services are proftpd, sendmail, ssh)
Reference : http://parallels.com/
Reseller bandwidth usage not working in Ensim Control Panel
The problem can appears on the server with large amount of sites, where server is heavily loaded.
To fix the issue you have to increase some parameters in apache config file /usr/lib/ensim/frontend/httpd/conf/eplhttpd.conf.template
Add there env apache module:
LoadModule env_module modules/mod_env.so
and add there following values to proxy:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
Also increase Timeout value at the begining of this file, from 210 to 500 :
Restarting epld is necessary to apply changes.
Reference: http://parallels.com
Reducing DNS bandwidth
*Refresh - 86000 - This is time(in seconds) when the slave DNS server will refresh from the master. This value represents how often a secondary will poll the primary server to see if the serial number for the zone has increased (so it knows to request a new copy of the data for the zone). It can be written as “23h88M” indicating 23 hours and 88 minutes. If you have a regular Internet server, you can keep it between 6 to 24 hours.
There is constant bandwidth usage between primary and secondary(backup DNS) servers. This depends a lot on the Refresh value. If the refresh value is say 3 hours, your secondary server is polling your primary server every 3 hours and updating the cache. Lets assume you have a 1000 zone files, each with 3 hours refresh rate. You can imagine the bandwidth that must be getting used. This is especially true if the servers are on 2 separate physical servers.
An increase in the Refresh rate can effectively reduce bandwidth usage between the primary and secondary server.
BEWARE! Any name or label that appears on either the left or right-hand-side of a resource record that does not have a terminating full stop will have the origin added to the name/label. Missing full stops are one of the most common causes of error in DNS zone files.
