DA Reseller quota error - please help

D

danellison

Verified User
Joined
Jul 18, 2007
Messages
14
Location
southern Illinois
Greetings all. I have a reseller setup on my system with full unlimited services. I have 32 domains defined under the reseller. When I try to add a new domain to this reseller I now get a message as follows:

"You've hit your maximum disk quota and do not have enough space to create another domain"

My reseller privs:

Bandwidth (MB) 1523.9 0.000000 unlimited
Disk Space (MB) 585.78 0.000000 unlimited
# of Domains 32 0 unlimited
# of SubDomains 0 0 unlimited
POP Email Accounts 175 0 unlimited
Email Forwarders 130 0 unlimited
Mailing Lists 0 0 unlimited
AutoResponders 0 0 unlimited
# of MySQL DBs 0 0 unlimited
Domain Pointers 6 0 unlimited
Ftp Accounts 7 0 unlimited

single mount point / partition is 5% used with 125GB free and is correctly referenced in the directadmin configuration file.

Am I missing something? Any ideas how this could be happening?

Thanks in advance for your help.

Dan Ellison,
Concepte of Illinois
 
Last edited:
Hello,

DA will give you that error if it figures you're out of space. The way it does this test is by creating a temp file in /home/username/.testfile with a "1" in it. It then reads it back in. If it doesn't see a "1", then it assumes the quotas are full. This may not be the case.. it's possible that /home/username simply isn't chowned properly to allow DA to write the file while running as the user.

John
 
Hmmm. I checked the permissions and low and behold the home directory was not owned by the reseller. Changed and problem fixed. Many thanks DA Support!

Thanks!

Dan Ellison
Concepte of Illinois
 
permissions solved the problem

Solved!

Just for record's sake, changing the /home/user permissions for the reseller user solved it for me as well.

Thanks!
Dotan
 
Last edited:
I have this problem as well. I don't resell etc, so have no resellers and no users under resellers. When I list users under admin level, I have only one user: admin

/home/admin is owned by wcadmin:admin

when I change this to admin:admin, I get:

Unable to create directory /home/admin/domains/fleetco.com.au,
Parent directory does not allow write, or one of the directories didn't allow search (execution) permission

Error creating /home/admin/domains/fleetco.com.au/public_html
A directory component in /home/admin/domains/fleetco.com.au/public_html does not exist or is a dangling symbolic link

Error creating /home/admin/domains/fleetco.com.au/public_html/cgi-bin
A directory component in /home/admin/domains/fleetco.com.au/public_html/cgi-bin does not exist or is a dangling symbolic link

Error creating /home/admin/domains/fleetco.com.au/public_html/cgi-bin/.htaccess
Unable to open /home/admin/domains/fleetco.com.au/public_html/cgi-bin/.htaccess for writing

Unable to create directory /home/admin/domains/fleetco.com.au/public_ftp,
A directory component in /home/admin/domains/fleetco.com.au/public_ftp does not exist or is a dangling symbolic link

Unable to create directory /home/admin/domains/fleetco.com.au/public_ftp/incoming,
A directory component in /home/admin/domains/fleetco.com.au/public_ftp/incoming does not exist or is a dangling symbolic link

... so I guess my question is: What is the correct setting for the ownership of /home/admin ?

TIA
 
Thanks Jeff. I have this:

drwxr-x--x 7 admin admin 4096 Feb 8 21:26 admin

... but I looked at /home/admin/domains and noticed that was owned by wcadmin:admin. Changing this to admin:admin solved the problem for me.

I'm confused as to how this happened out of the blue - I can only assume that it has to do with it being a managed server, and someone who manages the server must have done something somehow.
 
You must log in or register to reply here.
Back
Top