Subdomain error

[vdvm]

Hi,

When my customer adds a subdomain it doesn't resolve. Not even after 30 minutes.
When i restart named it still doesn't. When i restart httpd it does work.

How can i fix this?
Thank you.

 

[jmstacey]

Make sure DirectAdmin's task queue is being run every minute and that named can be restarted from the command line.

 

[vdvm]

This is my directadmin_cron wich is located in cron_d:

* * * * * root /usr/local/directadmin/dataskq
2 0-23/6 * * * root echo 'action=vacation&value=all' >> /usr/local/directadmin/data/task.queue;
#5 5 * * 0 root /sbin/quotaoff -a; /sbin/quotacheck -augm; /sbin/quotaon -a;
10 0 * * * root echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue
20 4 1 * * root echo 'action=reset&value=all' >> /usr/local/directadmin/data/task.queue
0 4 * * * root echo 'action=check&value=license' >> /usr/local/directadmin/data/task.queue

I can restart named from the commandline with:

service named restart


What should i change?
Thank you!

 

[vod]

do you mean that you cant access your subdomian thru http://subdomain.mydomain.com/ ? what happen if you try http://mydomain.com/subdomain folder?

 

[vdvm]

subdomain.mydomain.tld doesn't work, www.mydomain.tld/subdomain does work... but it should work like subdomain.myetcetc

When i restart apache it does...

 

[nobaloney]

It appears that DA isn't restarting httpd after the creation of a subdomain.

I'll ask DA Support to take a look at it. Please let us know which OS distribution you're running.

Jeff

 

[DirectAdmin Support]

Hello,

Along the lines of what jmstacey was getting at.. Also make sure that crond (or cron on freebsd) is running:

ps -ax | grep cron

Make sure it does return something (other than the grep command).

Also check the /var/log/cron log. It should hold one entry every minute for the dataskq program.

Sometimes, I've also seen cron not like the file permissions of /etc/cron.d/directadmin_cron. Try setting them to 644 and restart crond

Check the /usr/local/directadmin/data/task.queue file.
At most, you'd likely see maybe 5 lines. If the file has more data than was added within the last minute, then the dataskq program isn't running. Again, the above checks should verify if it's being called. You can manually run it to make sure it's not segfaulting or something like that:

/usr/local/directadmin/dataskq

If all of the above checks out, then next, check the /var/log/directadmin/system.log. You should see a line that says "httpd restarted" if it was in fact called. If you do see an entry there, you might also wan't to scan the /var/log/directadmin/errortaskq.log to see if there are any httpd restart errors showing up. If a restart of httpd through the DA Services monitor already works, then the httpd boot script is likely fine.

Hope that helps narrow it down.

John