Are you facing the error, DirectAdmin: User too large, delete on background?
This guide will help you.
Originally, if the sum of the disk usage of any user being deleted in DirectAdmin exceeds a certain threshold, the account will be deleted by a background process.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to resolve DirectAdmin related queries.
In this context, we shall look into steps to fix this DirectAdmin error.
Nature of the error, DirectAdmin: User too large, delete on background ?
In the process of deleting excessively large accounts, we may come across time-outs in the browser.
To prevent this, DirectAdmin executes the deletion by adding the command to the background's task queue, instead of performing it in the foreground.
Once DirectAdmin assigns this task to a background process, we will receive the following message:
user too large, delete on background
The process will actually just be the dataskqWe can change the configuration by modifying the value of the "get_background_delete_size" in the directadmin.conf settings file.
In order to do this, we connect to the server via SSH using root access.
Then we go to DirectAdmin’s installed directory:
# cd /usr/local/directadmin/conf/Then we edit the directadmin.conf file in the directory:
# vi directadmin.confBy default, if the variable “get_background_delete_size” value exists in the directadmin.conf file, it will be 10 GB.
On the other hand, If we cannot find the variable in the file, simply add it in.
We can change the value of 10240 to a value we wish.
For example, to set the get_background_delete_size to 20 gigabytes, we modify the value to:
get_background_delete_size=20480The 20480 means we've set a 20 GB. We can also disable the feature by setting the value to 0.
[Couldn't fix this DirectAdmin error? We are here for you. ]
Conclusion
This article covers method to fix the error, DirectAdmin: User too large delete on background. Basically, this error occurs when the sum of the disk usage of any user exceeds a certain threshold.
To prevent time-outs in your browser when deleting excessively large accounts, DirectAdmin will execute the deletion by adding the command to the background’s task.queue, instead of performing the execution on the foreground.
To fix DirectAdmin: User too large delete on background error, you can connect to the server through SSH using root access, then go to DirectAdmin's installed directory as below:
cd /usr/local/directadmin/conf/
Then edit the directadmin.conf file in the directory by running
vi directadmin.conf
If the variable "get_background_delete_size" value exists in the directadmin.conf file, it will be set to 10 GB by default (get_background_delete_size=10240).
If the variable cannot be found in the file, simply add it in.
You can modify the value of 10240 to define the value that you wish to set.
This article covers method to fix the error, DirectAdmin: User too large delete on background. Basically, this error occurs when the sum of the disk usage of any user exceeds a certain threshold.
To prevent time-outs in your browser when deleting excessively large accounts, DirectAdmin will execute the deletion by adding the command to the background’s task.queue, instead of performing the execution on the foreground.
To fix DirectAdmin: User too large delete on background error, you can connect to the server through SSH using root access, then go to DirectAdmin's installed directory as below:
cd /usr/local/directadmin/conf/
Then edit the directadmin.conf file in the directory by running
vi directadmin.conf
If the variable "get_background_delete_size" value exists in the directadmin.conf file, it will be set to 10 GB by default (get_background_delete_size=10240).
If the variable cannot be found in the file, simply add it in.
You can modify the value of 10240 to define the value that you wish to set.
