Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Thursday, July 14, 2011 04:38 PM, Mark wrote: On 14/07/2011 11:54 a.m., Gary wrote: On Wed, Jul 13, 2011 at 1:04 PM, Mark wrote: The 500ppm ntp range limit is easy to exceed with virtual hardware, since it isn't real time orientated. The original poster, Chris Chan, is running it on bare metal hardware. Regardless, I've never had that issue with running NTP in guests hosted in VirtualBox or VMware. If that happened to me in a VM, however, I'd be filing a bug with the VM software vendor. If it is hardware, then check the bios setup for a Spread Spectrum clock setting and try disabling it if it is on. /me takes note. Thanks! ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On 14/07/2011 11:54 a.m., Gary wrote: On Wed, Jul 13, 2011 at 1:04 PM, Mark wrote: The 500ppm ntp range limit is easy to exceed with virtual hardware, since it isn't real time orientated. The original poster, Chris Chan, is running it on bare metal hardware. Regardless, I've never had that issue with running NTP in guests hosted in VirtualBox or VMware. If that happened to me in a VM, however, I'd be filing a bug with the VM software vendor. If it is hardware, then check the bios setup for a Spread Spectrum clock setting and try disabling it if it is on. Mark. -Gary ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
ntpdate once an hour/half hour in cron?, or grep for the message in a loop and ntpdate if it sees the message? but that's just the hacker in me ... On 13 July 2011 02:56, Christopher Chan christopher.c...@bradbury.edu.hk wrote: On Wednesday, July 13, 2011 09:54 AM, Christopher Chan wrote: On Wednesday, July 13, 2011 06:52 AM, Christopher Chan wrote: On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote: Sigh... ntpdate -u 192.168.9.1 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset 3317.946738 sec IIRC ntpd won't adjust the time if the difference is too big, measured between the system clock, inherited from the hardware clock, and the ntp servers. I've see this on VMs a few times on Linux - if the guest OS doesn't have a time source compatible, it'll usually drift a lot, possibly enough to make ntpd give up. But then, since you're running on iron (or silicon or something), adjusting the time on bootup with ntpdate should suffice :) I have switched from broadcastclient to specifying 5 time servers. That seems to have got it to behave properly. Spoke too soon...it's off by nine minutes after 12 hours Jul 13 07:42:44 bradsuper1 ntpd[414]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM Jul 13 08:02:27 bradsuper1 ntpd[414]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM What causes this?!?! The only thing that has changed is the fact we are in the summer break and we have blooming renovators/builders coming in but they don't start at 7:42am. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On 13/07/2011 8:37 p.m., Jonathan Adams wrote: ntpdate once an hour/half hour in cron?, or grep for the message in a loop and ntpdate if it sees the message? That is a fix I have used for Virtual Linux guests, and it works well, but don't run ntpd as well to avoid the port conflict. The 500ppm ntp range limit is easy to exceed with virtual hardware, since it isn't real time orientated. Mark. but that's just the hacker in me ... On 13 July 2011 02:56, Christopher Chan christopher.c...@bradbury.edu.hk wrote: On Wednesday, July 13, 2011 09:54 AM, Christopher Chan wrote: On Wednesday, July 13, 2011 06:52 AM, Christopher Chan wrote: On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote: Sigh... ntpdate -u 192.168.9.1 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset 3317.946738 sec IIRC ntpd won't adjust the time if the difference is too big, measured between the system clock, inherited from the hardware clock, and the ntp servers. I've see this on VMs a few times on Linux - if the guest OS doesn't have a time source compatible, it'll usually drift a lot, possibly enough to make ntpd give up. But then, since you're running on iron (or silicon or something), adjusting the time on bootup with ntpdate should suffice :) I have switched from broadcastclient to specifying 5 time servers. That seems to have got it to behave properly. Spoke too soon...it's off by nine minutes after 12 hours Jul 13 07:42:44 bradsuper1 ntpd[414]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM Jul 13 08:02:27 bradsuper1 ntpd[414]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM What causes this?!?! The only thing that has changed is the fact we are in the summer break and we have blooming renovators/builders coming in but they don't start at 7:42am. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Wed, Jul 13, 2011 at 1:04 PM, Mark wrote: The 500ppm ntp range limit is easy to exceed with virtual hardware, since it isn't real time orientated. The original poster, Chris Chan, is running it on bare metal hardware. Regardless, I've never had that issue with running NTP in guests hosted in VirtualBox or VMware. If that happened to me in a VM, however, I'd be filing a bug with the VM software vendor. -Gary ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
Sigh... ntpdate -u 192.168.9.1 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset 3317.946738 sec IIRC ntpd won't adjust the time if the difference is too big, measured between the system clock, inherited from the hardware clock, and the ntp servers. I've see this on VMs a few times on Linux - if the guest OS doesn't have a time source compatible, it'll usually drift a lot, possibly enough to make ntpd give up. But then, since you're running on iron (or silicon or something), adjusting the time on bootup with ntpdate should suffice :) Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote: Sigh... ntpdate -u 192.168.9.1 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset 3317.946738 sec IIRC ntpd won't adjust the time if the difference is too big, measured between the system clock, inherited from the hardware clock, and the ntp servers. I've see this on VMs a few times on Linux - if the guest OS doesn't have a time source compatible, it'll usually drift a lot, possibly enough to make ntpd give up. But then, since you're running on iron (or silicon or something), adjusting the time on bootup with ntpdate should suffice :) I have switched from broadcastclient to specifying 5 time servers. That seems to have got it to behave properly. cheers, Christopher ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Jul 12, 2011, at 3:52 PM, Christopher Chan wrote: I have switched from broadcastclient to specifying 5 time servers. That seems to have got it to behave properly. That isn't a default setting in OI, is it? If so, I'd strongly advise against it. In fact, I advise against using it at all since DHCP has options for NTP but IIRC not all clients will use them by default. -Gary ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Wednesday, July 13, 2011 09:13 AM, Gary Driggs wrote: On Jul 12, 2011, at 3:52 PM, Christopher Chan wrote: I have switched from broadcastclient to specifying 5 time servers. That seems to have got it to behave properly. That isn't a default setting in OI, is it? If so, I'd strongly advise against it. In fact, I advise against using it at all since DHCP has options for NTP but IIRC not all clients will use them by default. Nay, it uses multicastclient as a default (/etc/inet/ntp.client) but I did set it up to use the local time server I run after it started having issues (it had been using it just fine with broadcastclient) to no avail. Then I went for multiple external time servers. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Wednesday, July 13, 2011 09:54 AM, Christopher Chan wrote: On Wednesday, July 13, 2011 06:52 AM, Christopher Chan wrote: On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote: Sigh... ntpdate -u 192.168.9.1 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset 3317.946738 sec IIRC ntpd won't adjust the time if the difference is too big, measured between the system clock, inherited from the hardware clock, and the ntp servers. I've see this on VMs a few times on Linux - if the guest OS doesn't have a time source compatible, it'll usually drift a lot, possibly enough to make ntpd give up. But then, since you're running on iron (or silicon or something), adjusting the time on bootup with ntpdate should suffice :) I have switched from broadcastclient to specifying 5 time servers. That seems to have got it to behave properly. Spoke too soon...it's off by nine minutes after 12 hours Jul 13 07:42:44 bradsuper1 ntpd[414]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM Jul 13 08:02:27 bradsuper1 ntpd[414]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM What causes this?!?! The only thing that has changed is the fact we are in the summer break and we have blooming renovators/builders coming in but they don't start at 7:42am. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
I see those messages too, but the time stays accurate. -Original Message- From: Christopher Chan [mailto:christopher.c...@bradbury.edu.hk] Sent: Saturday, July 09, 2011 9:07 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] ntpd not keeping time in sync Hi all, Would flaky electricity cause the system clock to go 'haywire' and ntpd to generate logs such as: Jul 7 22:46:33 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM Jul 7 23:02:31 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM and lead to the system clock an hour behind after about 24 hours? Christopher ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Saturday, July 09, 2011 10:30 PM, Dan Swartzendruber wrote: I see those messages too, but the time stays accurate. Okay, so maybe flaky electricity does not affect ntpd...but would it mess up the system clock? -Original Message- From: Christopher Chan [mailto:christopher.c...@bradbury.edu.hk] Sent: Saturday, July 09, 2011 9:07 AM To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] ntpd not keeping time in sync Hi all, Would flaky electricity cause the system clock to go 'haywire' and ntpd to generate logs such as: Jul 7 22:46:33 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM Jul 7 23:02:31 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM and lead to the system clock an hour behind after about 24 hours? Christopher ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
-Original Message- From: Christopher Chan [mailto:christopher.c...@bradbury.edu.hk] Sent: Saturday, July 09, 2011 10:53 AM To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On Saturday, July 09, 2011 10:30 PM, Dan Swartzendruber wrote: I see those messages too, but the time stays accurate. Okay, so maybe flaky electricity does not affect ntpd...but would it mess up the system clock? I can't see how. I think we have two different things going on in your case. The 500ppm messages seem to be something with the solaris kernel time keeping mechanism. In my case it seems to be harmless. It's hard to believe that in your case, it screws up the time by an hour (although I could be wrong...) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
Hmmm, good question! -Original Message- From: Gary Gendel [mailto:g...@genashor.com] Sent: Saturday, July 09, 2011 11:49 AM To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync Christopher, A silly question... Is this on a dual-boot system? I had a problem on one machine where booting windows would change the bios clock so bringing up OpenIndiana would be an hour off. I suppose this could be true of a virtual machine resetting the time as well. Gary On 7/9/11 9:07 AM, Christopher Chan wrote: Hi all, Would flaky electricity cause the system clock to go 'haywire' and ntpd to generate logs such as: Jul 7 22:46:33 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM Jul 7 23:02:31 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice] frequency error 512 PPM exceeds tolerance 500 PPM and lead to the system clock an hour behind after about 24 hours? Christopher ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote: I suppose this could be true of a virtual machine resetting the time as well. A guest OS should never be allowed to adjust its hosts clock. Sometimes a failing motherboard battery can cause issues but NTP should be correcting them. Have you tried resarting or disabling/enabling the service? -Gary D ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
No, I think he meant resetting the time in the BIOS of the VM. -Original Message- From: Gary Driggs [mailto:gdri...@gmail.com] Sent: Saturday, July 09, 2011 1:42 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote: I suppose this could be true of a virtual machine resetting the time as well. A guest OS should never be allowed to adjust its hosts clock. Sometimes a failing motherboard battery can cause issues but NTP should be correcting them. Have you tried resarting or disabling/enabling the service? -Gary D ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On 10/07/2011 5:43 a.m., Dan Swartzendruber wrote: No, I think he meant resetting the time in the BIOS of the VM. -Original Message- From: Gary Driggs [mailto:gdri...@gmail.com] Sent: Saturday, July 09, 2011 1:42 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote: I suppose this could be true of a virtual machine resetting the time as well. A guest OS should never be allowed to adjust its hosts clock. Sometimes a failing motherboard battery can cause issues but NTP should be correcting them. Have you tried resarting or disabling/enabling the service? If this is a virtual server, then it is normal and the drift will depend on physical server load. The physical timers used by the kernel to keep accurate period counts used for local clock don't exist, and the virtual replacements don't offer much precision. The host server's cmos clock isn't referenced. This phenomenon is well documented by VMWare, and outcome varies from one OS to the next, depending on how they derive time. Mark. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
AFAIK, at least historically, the hardware battery clock time is expected (without some tweaks, to the extent that a given version allowed those) by Windows to be in local time. Operating systems that keep their internal time in something else (.e.g. Unix and related, where it's supposed to be in GMT, with the TZ environment variable providing an offset to local time as desired) already have to deal with that (and probably with the possibility of it running in GMT instead). It seems to me that a virtualization environment should simulate an RTC clock for the guest, and should simply keep track of the offset between that time and the host's internal time, to be used to supply an initial value when the guest is started. Both virtualization and dual boot get tricky if there are mixed assumptions as to the RTC being in local vs GMT, especially with the addition of daylight saving time, and most particularly if the guest or less common boot environment is active at start or end of DST. It takes some care on the part of all OS and virtualization product producers _and_ the person setting up such a system, to get the whole situation right. It would probably be helpful if the OP provided more details of whether dual boot or virtualization was involved in their situations; and also if someone would write up a good guide to cases where Solaris/OpenSolaris/OpenIndiana was host or guest or primary or alternate boot with various other common OSs, on how to successfully keep the time consistent (unless something other than consistency was intentional!) across all environments. AFAIK, for semi-modern versions of Windows, there are settings that can allow the RTC to run in GMT and still have the OS in local time (with or without DST). I think most other OSs should also be happy with that, or be easily able to be made happy with that. It's what I'd do if I had a multi-boot Intel box that was having issues with getting the time right on some of the OSs. On Jul 9, 2011, at 1:43 PM, Dan Swartzendruber wrote: No, I think he meant resetting the time in the BIOS of the VM. -Original Message- From: Gary Driggs [mailto:gdri...@gmail.com] Sent: Saturday, July 09, 2011 1:42 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote: I suppose this could be true of a virtual machine resetting the time as well. A guest OS should never be allowed to adjust its hosts clock. Sometimes a failing motherboard battery can cause issues but NTP should be correcting them. Have you tried resarting or disabling/enabling the service? -Gary D ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss -- The waitress asked, Do you want lemon or no lemon with that iced tea? Naturally, I said yes, and then burst out laughing, because there simply wasn't any other answer in Boolean logic. She didn't get it, but I got the lemon, which I wanted anyway. Later, I realized a quantum computer could have offered another answer: Schroedinger's Lemon! ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
-Original Message- From: Mark [mailto:mark0...@gmail.com] Sent: Saturday, July 09, 2011 4:51 PM To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On 10/07/2011 5:43 a.m., Dan Swartzendruber wrote: No, I think he meant resetting the time in the BIOS of the VM. -Original Message- From: Gary Driggs [mailto:gdri...@gmail.com] Sent: Saturday, July 09, 2011 1:42 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote: I suppose this could be true of a virtual machine resetting the time as well. A guest OS should never be allowed to adjust its hosts clock. Sometimes a failing motherboard battery can cause issues but NTP should be correcting them. Have you tried resarting or disabling/enabling the service? If this is a virtual server, then it is normal and the drift will depend on physical server load. The physical timers used by the kernel to keep accurate period counts used for local clock don't exist, and the virtual replacements don't offer much precision. The host server's cmos clock isn't referenced. This phenomenon is well documented by VMWare, and outcome varies from one OS to the next, depending on how they derive time. *** But he is talking about ntpd not being able to keep time to within one hour. I'm sorry, that is NOT normal. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On 10/07/2011 8:54 a.m., Richard L. Hamilton wrote: AFAIK, at least historically, the hardware battery clock time is expected (without some tweaks, to the extent that a given version allowed those) by Windows to be in local time. Operating systems that keep their internal time in something else (.e.g. Unix and related, where it's supposed to be in GMT, with the TZ environment variable providing an offset to local time as desired) already have to deal with that (and probably with the possibility of it running in GMT instead). It seems to me that a virtualization environment should simulate an RTC clock for the guest, and should simply keep track of the offset between that time and the host's internal time, to be used to supply an initial value when the guest is started. Both virtualization and dual boot get tricky if there are mixed assumptions as to the RTC being in local vs GMT, especially with the addition of daylight saving time, and most particularly if the guest or less common boot environment is active at start or end of DST. It takes some care on the part of all OS and virtualization product producers _and_ the person setting up such a system, to get the whole situation right. It would probably be helpful if the OP provided more details of whether dual boot or virtualization was involved in their situations; and also if someone would write up a good guide to cases where Solaris/OpenSolaris/OpenIndiana was host or guest or primary or alternate boot with various other common OSs, on how to successfully keep the time consistent (unless something other than consistency was intentional!) across all environments. AFAIK, for semi-modern versions of Windows, there are settings that can allow the RTC to run in GMT and still have the OS in local time (with or without DST). I think most other OSs should also be happy with that, or be easily able to be made happy with that. It's what I'd do if I had a multi-boot Intel box that was having issues with getting the time right on some of the OSs. On Jul 9, 2011, at 1:43 PM, Dan Swartzendruber wrote: No, I think he meant resetting the time in the BIOS of the VM. -Original Message- From: Gary Driggs [mailto:gdri...@gmail.com] Sent: Saturday, July 09, 2011 1:42 PM To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote: I suppose this could be true of a virtual machine resetting the time as well. A guest OS should never be allowed to adjust its hosts clock. Sometimes a failing motherboard battery can cause issues but NTP should be correcting them. Have you tried resarting or disabling/enabling the service? -Gary D ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss The hardware RTC is only read at boot and sets the initial date/time. The OS will adjust it's internal time from this initial reference and it's timezone, hence different times between cmos rtc and server e.g daylight time. Then the hardware time ticks are counted by the OS to maintain internal time. This is the sole time source until the next boot. The issue is drift of the internal time ticks against the ntp external reference. When this drift exceeds ntp's capture range, you get the error message. I have seen this with virtual (VMWare) Windows and Linux as well. VMware also throws in a few extra's at vm bootup, just to make life more interesting, but one running, it's up to the OS's method to maintain time. Mark. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
/listinfo/openindiana-discuss The hardware RTC is only read at boot and sets the initial date/time. The OS will adjust it's internal time from this initial reference and it's timezone, hence different times between cmos rtc and server e.g daylight time. Then the hardware time ticks are counted by the OS to maintain internal time. This is the sole time source until the next boot. The issue is drift of the internal time ticks against the ntp external reference. When this drift exceeds ntp's capture range, you get the error message. I have seen this with virtual (VMWare) Windows and Linux as well. VMware also throws in a few extra's at vm bootup, just to make life more interesting, but one running, it's up to the OS's method to maintain time. *** I had posted about a similar issue sometime ago and never got a useful answer. It seems to be harmless, so I dropped it. What puzzles me is that I have had 3 other vmware esxi clients (ubuntu, centos and freebsd) all running almost identical ntpd clients and don't get this message with them. The one hour thing, I have seen when dual booting between two different OS (don't remember offhand which - windows vs linux?) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
Negative and also negative for vm install.
This is the image on iron that I am talking about. I have not check the
time on the vbox guest though...
I have restarted ntpd too and set both broadcastclient and server
directives. Manually running ntpdate -u ${server} works and will
readjust time.
Christopher
On Saturday, July 09, 2011 11:48 PM, Gary Gendel wrote:
Christopher,
A silly question... Is this on a dual-boot system? I had a problem on
one machine where booting windows would change the bios clock so
bringing up OpenIndiana would be an hour off. I suppose this could be
true of a virtual machine resetting the time as well.
Gary
On 7/9/11 9:07 AM, Christopher Chan wrote:
Hi all,
Would flaky electricity cause the system clock to go 'haywire' and
ntpd to generate logs such as:
Jul 7 22:46:33 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice]
frequency error 512 PPM exceeds tolerance 500 PPM
Jul 7 23:02:31 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice]
frequency error 512 PPM exceeds tolerance 500 PPM
and lead to the system clock an hour behind after about 24 hours?
Christopher
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Sunday, July 10, 2011 09:00 AM, Christopher Chan wrote:
Negative and also negative for vm install.
This is the image on iron that I am talking about. I have not check the
time on the vbox guest though...
I have restarted ntpd too and set both broadcastclient and server
directives. Manually running ntpdate -u ${server} works and will
readjust time.
Christopher
Sigh...
ntpdate -u 192.168.9.1
10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset
3317.946738 sec
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
