Hi,

My customer just asked why his cpanel shows 700MB and his webalizer only shows 480MB? Anybody knows why?

TIA

muppie,

The answer is mod_gzip ... Read my report/post here (http://www.webhostingtalk.com/showthread.php?threadid=25282)

cheers,
:beer:

Second, I was also able to verify what causes the mysterious problems that most host have been asking, the difference between CPanel's bandwith monitoring (bandmin) and webalizer's. With mod_gzip turned on, I got about a factor of up to 3 times between bandmin and webalizer, but after turning it off, I realized that bandin and webalizer are withing 0.5%-1% of each other! I guess/believe that any host having a huge differences between webalizer and bandmin will have this mod_gzip intalled!


Dektong,

Please tell me if any of these is wrong:

1. cpanel / bandmin is counting the bw prior to being gzipped by mod_gzip
2. whereas webalizer counts the bw after being gzipped

That's why webalizer shows smaller amount than cpanel, right? So far am I right?

Now, from what I know, the customers are being limited on the WHM which uses bandmin as well, so say I limit one customer to 5 GB, the minute his bandmin reports 5GB he'll be suspended. However, his actual transfer using gzip is less than that, and it's only fair if we give him the benefit of gzip as well.

Could you tell me how to solve this problem?

Thanks

how to start/stop mod_gzip ??



Thanks

Originally posted by muppie
1. cpanel / bandmin is counting the bw prior to being gzipped by mod_gzip
2. whereas webalizer counts the bw after being gzipped

That's why webalizer shows smaller amount than cpanel, right? So far am I right?


Webalizer reports data transfer based on httpd log, and hence mod_gzip really does have affect on webalizer. Bandmin (and mod_watch) claim to record data transfer directly from the eth0, so I heard people argue bandmin (and mod_watch) will report actual data transfer truthfully. However, my finding was different. So I guess you are right. Somehow mod_watch and bandmin records data transfer prior to mod_gzip compression. I even saw bandmin reporting the same amount of data transfer as webalizer (withing few KB differences) after I turn off mod_gzip.

I still wonder: If bandmin/mod_watch records bandwith directly from the eth0, how come they are different than MRTG? My MRTG jumps up after I disabled mod_gzip yet mod_watch/bandmin stays the same!

Could you tell me how to solve this problem?


Turn of mod_gzip ;) The host will actually get more money by charging bandwith overusage. Why save bandwith on behalf of our clients? :D

cheers,
:beer:

Originally posted by mercury
how to start/stop mod_gzip ??
[/B]

Stop apache, go to your httpd.conf, comment out/remove all lines corresponding to mod_gzip. Restart apache, and this should disable mod_gzip.

cheers,
:beer:

hi all,

i really can't found anything about mod_gzip in httpd.conf :(

Is there a way to install it (turn it ON ) ??


Thanks

So should I tell my customer that I actually compressed his bandwidth but he is getting charged the normal bandwidth (pre-compression) ? Somehow I think they're not going to like that explanation....

muppie, I will just tell him that you (for now, until the investigation is clear) will bill him based on webalizer .... Then turn off mod_gzip to see how the two bandwith reporting now compare to each other.

cheers,
:beer:

Originally posted by mercury
Is there a way to install it (turn it ON ) ??


I learnt how to install mod_gzip here (http://i4net.tv/marticle/get.php?action=getarticle&articleid=21). So all credit should go to eva2000 :)

disclaimer: although it's pretty easy/safe to install mod_gzip, do this at your own risk ;)

cheers,
:beer: