I am posting this here to report something unusual which I saw this morning and I think I understand the reason for it. If other users have seen this, the following description may solve some mysteries.
This morning our Bacula server was taken down for maintenance for about an hour and then restarted. About 45 minutes later the evening's compliment of backup jobs started 7 hours ahead of schedule. I think I know why... Some time ago this machine developed an occasional problem when started where its hardware clock would come up with the wrong time. Rather than replace the machine for such a trivial problem we put a line of code into the initialization scripts that sets the system clock from our time server. This is what I think is happening: The OS's system clock is set to the bad hardware value at boot, then the Bacula director starts and sets up jobs that are scheduled to run in the next hour, then the startup script corrects the system time to be right. As time advances the director will start jobs at what it thought was the right time, but no longer is. I consider this to be hardware related and not a Bacula problem, but I thought I'd share it to potentially save someone some troubleshooting time. Karl Cunningham ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
