Plesk 10 bug when quota is exceeded

[faris]

I just came across a nasty bug which caused havoc today.

A client exceeded their hard quota (the FTP one, as opposed to the soft one for everything).

They then attempted to remove some subdomains
The subdomains were removed from Plesk's list, but the website files remained AND SO DID the includes to the conf files which were removed.

This caused Plesk to be unable to reconfigure apache
I had to solve this via http://kb.parallels.com/116412 which was no fun because it didn't seem to work initially - it took some minutes for it to come into effect, allowing httpdmnrg --reconfigure-all to run without errors.


Next, they tried adding a new subdomain. And this is where it gets interesting.
The subdomain structure was created, but due to the quota thing, the files could not be chowned to the ftpuser.psaserv ownership by Plesk, which left them as root:root!! Nor could it set the permissions on the files correctly, some of which were 000! Big mess.
I solved this by changing the quota, manually setting ownership and permissions, removing the newly created subdomains and then re-creating them.

Hope this helps someone in the future. I've been at this for four hours now. Whew!