BUG: Delete domain timeout with lots of content

[zylon]

Description:
On some websites, deleting the content takes longer than the timeout of directadmin interface. Happens with latest v1.32.2.

It will work if you refresh a few times, but this is very confusing for the user and looks like a broken system.

How to reproduce:
1. Create a domain with many, many files in the documentroot (few hundred thousand in my case).
2. Try to delete domain via webinterface and get error:
---
Your connection has timed out


*Details*

Either your request was invalid or the program hasn't completed your
request.
Please notify the server admin
---
3. Then the server is left with this domain as 'error' in the list. Once all files are gone you can delete it again, but you get some errors:

Domain Deletion Results


*Details*

*Error deleting example.com*

*Error removing site from IP file*
example.com's config files have been removed
*Unable to write user's httpd.conf* *Unable to read
example2.com.conf file*
*Unable to read example3.com file*
*Unable to read example2.com.conf file*
*Unable to read example3.com file*

 

[zylon]

4. I just noticed that (probably) because of the timeouts canceling the request it sometimes leaves some data of the websites on the server.

 

[DirectAdmin Support]

Hello,

That sounds about right.

The only real solution is to increase the timeout value in Admin Level -> Admin Settings.

DirectAdmin cannot delete files any faster than the system allows.
Once the timeout hits, it's assumed that something was wrong (since that's what a timeout is for) and the process stops.

Deleting again would be the correct solution, as long as everything is cleaned up once it's all done.

John