Cpanel 6.0?

[jmorby]

Resetting Bandwidth Counters

I've got the same problem here ... overnight a customer has gone from 732Mb to 134Gb of data transferred ... when I know for a fact he's not done anywhere near that. (the whole machine didn't ship that much data in the last 48 hours so ....

Anyway, how do we reset the counters?

(I got auto-updated to 6.0E48 last night, and reverted to 5.3.0 R117 when I realised)

 

[dgbaker]

Running 6.0.0-E49 and our bandwidth usage reports are dead on. Well as dead on as cpanel ever has

 

[bdraco]

The problem is caused by cpanellogd not being restarted during the install on some systems (it seems to be random which systems it happens on). cPanel 5's bandwidth system does not understand data written by cPanel 6's bandwidth sysem. ( cPanel 6 logs the time the traffic is done. cPanel 5 will view the times as bandwidth usage. ) If your cpanellogd did not restart, please put in a support ticket (http://support.cpanel.net/) so we can reset the affected domains. Please do not downgrade to cPanel 5 as it will not solve the problem unless you reset /var/cpanel/bandwidth and /usr/local/apache/domlogs/*bytes_log.

E53 also kills cpanellogd 4 times to ensure that it actually dies. This is not a bug in bandwidth tracking system so people who are already using cpanel 6 shouldn't start having any problems.

If you have experienced the problem, do not downgrade to cpanel5. Please run the following:

/scripts/updatenow;/scripts/cleanbw;echo &CPANEL=edge& && /etc/cpupdate.conf;/scripts/upcp

or contact [email protected] to have them run it for you.

 

[mesranet]

Hi,

I still got an error message as below when the exim trying to send any email, this problem still happen after i upgrade to EDGE 53:

Error in message_filter file: failed to expand &${perl{amavis_filter_scan}{$message_id}{$sender_address}{$recipients}}& in filter file: Undefined subroutine &main::amavis_filter_scan called.\n

Please help

 

[hormigo]

remove amavis filter from exim conf

 

[anand]

[quote:0497950d1f][i:0497950d1f]Originally posted by hormigo[/i:0497950d1f]

remove amavis filter from exim conf[/quote:0497950d1f]

Thx for the advise.

Don't people think its kinda ridiculous that first we install the antivirus and then we need to disable because the new exim won't work with it ?? I just happened to login on my server after 1 day and found over 5000 messages in queue and then tried to manually deliver the mails and the same error message struck me. Coming to these forums sorted the probs but the antivirus is out now. What happening.

Any possible solutions to run amavis back ??

regards,

Anand

 

[mesranet]

Dont tell us to remove it but please find the solutions to run amavis back

 

[anand]

[quote:df76ce4be6][i:df76ce4be6]Originally posted by mesranet[/i:df76ce4be6]

Dont tell us to remove it but please find the solutions to run amavis back [/quote:df76ce4be6]

absolutely correct i agree.

we need a solution here guys!

regards,

Anand

 

[googleme]

So does anyone have a fix for the chilisoft problem? Is there anyway to downgrade from glibc 2.2.5 to 2.2.4?

-g

 

[kwimberl]

To fix amavis:

/scripts/patcheximconf

 

[JustinK]

Originally posted by bdraco
The problem is caused by cpanellogd not being restarted during the install on some systems (it seems to be random which systems it happens on). cPanel 5's bandwidth system does not understand data written by cPanel 6's bandwidth sysem. ( cPanel 6 logs the time the traffic is done. cPanel 5 will view the times as bandwidth usage. ) If your cpanellogd did not restart, please put in a support ticket (http://support.cpanel.net/) so we can reset the affected domains. Please do not downgrade to cPanel 5 as it will not solve the problem unless you reset /var/cpanel/bandwidth and /usr/local/apache/domlogs/*bytes_log.

E53 also kills cpanellogd 4 times to ensure that it actually dies. This is not a bug in bandwidth tracking system so people who are already using cpanel 6 shouldn't start having any problems.

If you have experienced the problem, do not downgrade to cpanel5. Please run the following:

/scripts/updatenow;/scripts/cleanbw;echo &CPANEL=edge& && /etc/cpupdate.conf;/scripts/upcp

or contact [email protected] to have them run it for you.

So that basically resets february's bandwidth to 0? Any chance you could change the script to use the current month instead of february (since it's now march and this could be handy in the future)?

 

[Dathorn_ADT]

I am having the same problem. Still some accounts' bandwidth usage will grow insanely high. It is very random but it still needs to be fixed

 

[anand]

does amavis work with cpanel6 now properly ???

regards,

Anand