It's probably a bug where the success time is being displayed in CEST
(+2). The job was probably performed on time. Either that, or it was
performed 2 hours too late because it reads the configuration wrong.
In the second case you could easily fix it by changing it to 22:02.
On Jun 21, 6:13 pm, dj
to me it looks like it ran 2sec late, not 2hrs :/
On Jun 21, 6:57 pm, djidjadji wrote:
> This was for another job on the same day, and that was on time,
> sometimes they are a few minutes off but not 2 hours
> ---
> every day 00:00 (UTC)
> 2010/06/21 00:00:00 on time Success
> ---
Heh, good point :)
On Jun 21, 7:24 pm, Claude Vedovini wrote:
> to me it looks like it ran 2sec late, not 2hrs :/
>
> On Jun 21, 6:57 pm, djidjadji wrote:
>
>
>
> > This was for another job on the same day, and that was on time,
> > sometimes they are a few minutes off but not 2 hours
> > --
This was for another job on the same day, and that was on time,
sometimes they are a few minutes off but not 2 hours
---
every day 00:00 (UTC)
2010/06/21 00:00:00 on time Success
---
2010/6/21 Blixt :
> It's probably a bug where the success time is being displayed i
Oops. Yes looks like it finished 2 sec after 00:02:00.
Maybe the confusion was because you specify hh:mm and you get a result
time in hh:mm:ss.
And the times are only 0's and 2's.
Maybe the target time can be displayed on the cron page too as hh:mm:ss
2010/6/21 Blixt :
> Heh, good point :)
>
> O
