On Wed, Jun 13, 2007 at 02:31:42PM -0500, Daniel Bourque wrote:
I noticed that a large clock change tends to stop the hobbit client from sending status messages to the server. For example, if a system boots with the wrong time, I get cpu alerts, I go restart ntpd on it, then I won't get anymore status until I restart hobbit-client on that system...
This was reported a few days ago for hobbitlaunch on the Hobbit server, but yes - the same issue occurs on clients.
What happens is basically that hobbitlaunch remembers when it last ran one of the tasks, and then it will run it again when the time becomes (last_time_it_ran + interval). So if you set the current time back, it will stop running for some time.
Clocks just aren't supposed to jump backwards ...
There are a couple of ways to fix this. One is in the current snapshot, but I might do it differently.
Regards, Henrik