Package with BWLIMIT=1048576 changing alone
Hi..
Our client created several packages, where he changed only the Disk Space Quota, but left the Monthly Bandwidth Limit at the default value of 1048576.
root@server112 [~]# egrep BWLIMIT /var/cpanel/packages/host50*
/var/cpanel/packages/host50_exemplo_full_pacote:BWLIMIT=1048576
/var/cpanel/packages/host50_Plano G:BWLIMIT=1048576
/var/cpanel/packages/host50_Plano M:BWLIMIT=1048576
/var/cpanel/packages/host50_Plano P:BWLIMIT=1048576
root@server112 [~]#
As soon as you finish creating an account, when listing in whm the account that shows it was created correctly with the selected package, appears in another default package created by root
root@server112 [~]# egrep BWLIMIT /var/cpanel/packages/Reseller\ Example
BWLIMIT=10000
root@server112 [~]#
In /usr/local/cpanel/logs/error_log this is shown:
[2024-01-11 18:23:44 -0300] info [xml-api] Failed to load package “host50_Plano P”: No such file or directory
[2024-01-11 18:36:27 -0300] info [xml-api] Failed to load package “host50_Plano M”: No such file or directory
[2024-01-11 18:38:47 -0300] info [xml-api] Failed to load package “host50_Plano G”: No such file or directory
This value of 1048576 is what WHM reports in Home -> Account Functions -> Limit Bandwidth Usage
I set this option to Unlimited for the reseller, but the behavior of changing the package for customers continued to occur.
Under Home / Resellers / Edit Nameservers and Reseller Privileges, the Maximum Allowed Bandwidth value is 9999999999
When you click to create an account, it appears as follows:
Any explanation for this to happen?
Thanks.
-
Hey there! I would focus on the error portion where it can't load the packages properly first. Can you make some other minor edit to the package through WHM to see if it takes care of that error?
0 -
Yes, the error stops appearing when decreasing the bandwidth value configured in the package.
0 -
The problem only occurs with the value of 1048576. I entered 999000 and the error did not occur. (Error of changing the package by yourself)
The error in the log no longer occurs.
0 -
Thanks for the additional details. I wasn't able to reproduce this problem on a machine with a package where the bandwidth limit was set to our recommended value of 1048576. It would likely be best to create a ticket, either with us or with your host, so we can check this out and see the problem in action on your machine.
0
Please sign in to leave a comment.
Comments
4 comments