Time in backups

meto

Verified User
Joined
Sep 14, 2009
Messages
54
My backups are executing 8h behind schedule, f.e. I have backup set to run at 3 AM, and it started ad 11 AM. Directadmin is installed on CentOS VPS.

Some time info
date on vps:
Fri Oct 8 13:19:49 CEST 2010
date on host:
Fri Oct 8 13:20:19 CEST 2010
hwtime on host:
Fri 08 Oct 2010 01:20:41 PM CEST -0.311114 seconds

Any ideas?

PS.
time difference is from running them sequentially by hand ;)
 
How do you know it starts at 11am. What is in the cron log? What does your directadmin backup cron say?
 
How do you know it starts at 11am. What is in the cron log? What does your directadmin backup cron say?

I also didn't believe it but then I've set backup to run at 5.15 AM. and it executed at 13.15 (1.15 PM).
Code:
Oct  8 11:00:01 vm1 crond[16359]: (diradmin) CMD (echo -e "action=backup&id=2&owner=meto" >> /usr/local/directadmin/data/task.queue.da; /bin/chmod 600 /usr/local/directadmin/data/task.queue.da)

Code:
Oct  8 13:15:01 vm1 crond[19562]: (diradmin) CMD (echo -e "action=backup&id=3&owner=meto" >> /usr/local/directadmin/data/task.queue.da; /bin/chmod 600 /usr/local/directadmin/data/task.queue.da)

--edit
http://awesomescreenshot.com/0e626k5b1
 
Do you sync your time with ntpdate or ntpd?

You should verify the time is correct and on the right timezone for your area.

You could try restarting the cron daemon maybe.

Other than that you might need to get directadmin to look at your server.
 
Do you sync your time with ntpdate or ntpd?

You should verify the time is correct and on the right timezone for your area.

You could try restarting the cron daemon maybe.

Other than that you might need to get directadmin to look at your server.
Yes and Yes.

I'll maybe try rebooting it later...

It seams that's the DA which is having troubles. I added as a user a Cron job to run at 15.15 - date:
Fri Oct 8 15:15:01 CEST 2010

--edit
It seams that cron daemon restart helped.
Thanks m8 :)
 
Last edited:
Back
Top