Unable to create subdomain

Aspegic

Verified User
Joined
Aug 4, 2005
Messages
282
I am unable to create a subdomain for one of the users on my server. I do not have this problem with any of the other users on the server.

When I try to create a subdomain for this user I get the follow error message:

Code:
Unable to create subdomain

Error creating /home/bccbox/domains/bccbox.com/public_html/test
Unknown error

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

Error creating /home/bccbox/domains/bccbox.com/private_html/test
Unknown error
(the first and third errors are the problem, the second is just the result of the first operation failing)

I have searched this forum and there are several threads dealing with "Unable to create subdomain" but only two of them deal with the "Unknow error" result, neither of which provided a solution.

I have tried backing up the user, deleting the user and restoring the user. That didn't help.
I've check all file and directory access rights, both in /home and in /usr/local/diradmin/data/users. They are all the same as other users in those folders.

After the error message, if I check the DNS record for that user, I can see that the A records for the subdomain have been added (but no directory for the subdomain was created in the home folder of that user and no virtualhost entry was created in httpd.conf).

Does anyone have any idea what else I could check?
 
Last edited:
Solved!

Today I spend all day trying to work out what the problem was. Finally I decided to open two explorer windows side by side, one with the faulty user and the other with a working user. Then I checked every single file and folders' user/group/accessrights and changing everything to the way they were set for in the working user. When I was finished I had changed a lot of user/group/accessrights. Then I tried to create a subdomain and it worked! :eek:

So it must have had something to do with user/group/accessrights somehow, somewhere.
Fortunately for me it now works. Unfortunately I don't know exactly which change caused it to work again. All I can say is, if someone finds this thread in the future looking for a solution to the same problem, make sure you check the user/group/accessrights.
 
Back
Top