This message is usually related to the hardware clock not synced with the systems clock. You can check this by running:
Code:
Prompt>hwclock;date
The hwclock will show you what time the hardware clock thinks it is, and the date will show you what time the system thinks it is. If this is off by a lot you may get those log errors.
Set your system time with:
Code:
Prompt>date --set="Tue Jun 25 00:00:00"
Or type:
To learn to set the clock with date.
Of Course use the correct time.
If using NTP:
Code:
Prompt>ntpdate -u time.nist.gov
Once your system time is correct you can run "hwclock --systohc" which will set your hardware clock to the same time as system.
This is as always is an attempt at resolving your issue. Nixcraft recently helped me setup a NTP server for both of my LANS. So this clock business can be tricky. Good Luck
HTH,
Jaysunn