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 dataskq
We 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.conf
By 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:
The 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. ]