[Resolved] 4.0.14 Breaks cPanel HTTP bandwidth tracking

A

AndrewT

Well-Known Member
#1
#1
Since upgrading to 4.0.14 all of our cPanel servers have not been recording HTTP bandwidth usage. Our servers using Apache are not affected. Additionally, I reverted a couple to 4.0.13 and bandwidth usage was once again being recorded correctly. Under 4.0.14 running /scripts/runweblogs <user> results in a bunch of these warnings being displayed which may be related:

Code: 
warn [cpanellogd] http Bytes overflow /usr/local/apache/domlogs/<domain>-bytes_log.bkup: 9604820573581 -4294967296 .

warn [cpanellogd] http Bytes overflow /usr/local/apache/domlogs/<domain>-bytes_log.bkup: 10167461289357 -4294967296 .

warn [cpanellogd] http Bytes overflow /usr/local/apache/domlogs/<domain>-bytes_log.bkup: 3115124989325 -4294967296 .

warn [cpanellogd] http Bytes overflow /usr/local/apache/domlogs/<domain>-bytes_log.bkup: 12052951932301 -4294967296 .
Upon switching back to 4.0.13 these warnings also do not appear.
 
Last edited by a moderator:
A

AndrewT

Well-Known Member
#2
#2
Another side effect which prompted this investigation is incredible RAM usage by cpanellogd. I've seen it use over 2GB of RAM while running on an account that receives a lot of traffic. Seems like 4.0.14 is not logging the data correctly.
 
A

AndrewT

Well-Known Member
#4
#4
Seems like you should be able to reproduce this on your own given that this is occurring on every server that we have LiteSpeed 4.0.14 on. Here are some excerpts from a bytes log under 4.0.14:

Code: 
7749394709592 -4611723848499331072 .
7684970200447 -4611723848499331072 .
7706445037232 34359738368 .
7680675233752 -4611720687403401216 .
7693560135943 -4611723848499331072 .
7702150070831 -4611723848499331072 .
7659200398176 0 .
2651268531070 0 .
2694218204031 0 .
44024688493523 585762277077024768 .
Here are some from 4.0.13:

Code: 
1273707235 1776 .
1273707534 1780 .
1273707833 1786 .
1273708133 1797 .
1273708434 1771 .
1273708735 1775 .
1273709035 1794 .
1273709335 1787 .
1273709434 617 .
1273709436 627 .
There are so many things wrong there I don't even know where to begin. In regards to the 4.0.14, the first number certainly isn't a valid date/time and those outrageously large / negative bytes are simply not possible.
 
A

AndrewT

Well-Known Member
#5
#5
To be clear, this only affects the bandwidth reporting of cPanel/WHM itself. Alternative stats programs (like AWStats) which rely on the domain's log file directly (not the bytes log) work normally as these values are being written correctly.
 
You must log in or register to reply here.
Top