How quickly does "now" option begin creating a backup?

[waitek]

I'm running DirectAdmin on a new CentOS 6 minimal install server. When selecting the "now" option for an admin or system backup, I don't see that any backup file is being created--even after a few hours of waiting. If I manually run the same backup command from the command line, I get a backup file in a couple of minutes.

Seems like DirectAdmin should be running a "now" command fairly quickly. True? Or is there a delay before the queue items get run? There's nothing else in the queue file except for the backup item.

 

[zEitEr]

"Now" means within one minute by default. And it depends on how your crontask is set. Check if your crond is installed and running.

Check /etc/cron.d/directadmin_cron for /usr/local/directadmin/dataskq:

* * * * * root /usr/local/directadmin/dataskq

 

[waitek]

Thank you for the help!

OK, with the minimal install of CentOS 6, cron was missing. Installed it. Then I had to create the file /etc/cron.d/directadmin_cron and insert the entry listed above. Then I started cron and verified that it was running with service crond status. Then I tried to backup with "now" as the time option. Waited 15 minutes, but no backup file.

Worked through the steps at this link: http://help.directadmin.com/item.php?id=107.

Finally tried step 5 and ran this line manually:
/usr/local/directadmin/dataskq d

Here is the result:
Debug mode. Level 10
quota command: /usr/sbin/setquota admin 0 0 0 0 /

Not sure what to try next. dataskq is running every minute, according to the log file, but I'm not getting any backup files.

 

[zEitEr]

Did you copy /usr/local/directadmin/scripts/directadmin_cron to /etc/cron.d/directadmin_cron ? If not, then do it.

Set a task with "now", wait a minute or two and check

cat /var/log/directadmin/errortaskq.log

 

[waitek]

No I hadn't copied the file. That was the rest of the problem. Backup working now. Thank you much!