On (23/10/06 08:08), Ed Curtis wrote: > On Mon, 23 Oct 2006, Clive Menzies wrote: > > On (23/10/06 07:24), Ed Curtis wrote: > > > Just wondering if anyone can shed some light on this for me. Our system's > > > time has been off by about 30 minutes for the last month or so. When I run > > > ntpdate and set the time we would get some wierd things happening on the > > > system (i.e. Service unavailable in apache, etc.) I would have to move the > > > time forward at least the 30 minutes again to have the system act > > > normally. > > > > > > This morning at 5:31 I shutdown the server to look at the bios time and > > > date. It showed the correct date but the time was 10:04. I set it to the > > > correct time of 5:31 and rebooted. When I checked the server time after > > > the reboot it said 1:04 am with the correct date. I used ntpdate to update > > > and everything is running normally. > > > > > > Can anyone shed some light on to why the system/bios time would differ > > > like that or why running ntpdate and setting the correct time would > > > affect the server as mentioned above? > > > > Have you run tzconfig to check if your time zone is set correctly? > > > > Yes. It is correctly set for America/New York.
I've only seen this problem on dual boot machines where on installation you set the time to the hardware clock but switching between systems does strange things. This doesn't apply here but you could try rerunning base-config and see if that helps .... I use ntpdate and I've never seen this but other people recommend chrony.. could be worth a try. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
