Re: NTPD not keeping time
Just a follow up, Turned off NTPD and the clock is still drifting. I set the clock around 1200 on Dec 7th, and the time is reported as Dec 7th 22:20 PST 2006. Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NTPD not keeping time
After poking about vmware's web site I've done the following. Installed VMWare tools for FreeBSD and activated it. Also, from the toolbox I checked of sync clock. Not yet implemented: /boot/loader.conf and disabling APIC. I'll try this later. Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Peter A. Giessel [EMAIL PROTECTED] wrote: On 2006/12/01 8:56, Kris Anderson seems to have typed: --- Chuck Swiger [EMAIL PROTECTED] wrote: However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. Nope, not dual booting, see below. :| It could be that the virtual machine is giving FreeBSD the time in UTC, not your local timezone. Try changing the timezone options (you can use sysinstall - Configue - Time Zone and choosing yes) Peter, I'll give that a shot and see what happens. It certainly is mucking things up, that's for sure, poor cron. :( Although the host clock is correct so I just don't get it. Perhaps just not run ntpd and see what happens. I'll try that the next day. Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- John Webster [EMAIL PROTECTED] wrote: --On Friday, December 01, 2006 10:23:17 -0800 Chuck Swiger [EMAIL PROTECTED] wrote: On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote: Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. Sigh-- you're right, you should have mentioned this before. One should not attempt to change the clock from within a virtual machine at all, only in the parent or host OS. VMs depend on the host OS to provide the timekeeping, and it is known that systems running inside a VM may experience timing glitches as a result of running inside the machine emulation. http://ntp.isc.org/bin/view/Support/KnownOsIssues#Section_9.2.1. Having read that, my guess is that I should just disable ntp and reboot the system. Just so that all is well in the world. I'll give that a shot the next day. *sigh* Thanks. :) Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Nov 30, 2006, at 12:55 PM, Kris Anderson wrote: Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. Off by an hour? Let's see the date is November 30th, and 12:41pm, that's what Windows says. Meanwhile freebsd says - Thu Nov 30 00:22:07 PST 2006. Wouldn't that be...nearly 12 hours? I was judging the time-offset by the output of ntpq -p. Ah, okay. Thanks. :) However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. Nope, not dual booting, see below. :| It's entirely possible that doing a touch /etc/wall_cmos_clock will solve your issue. The file already exists, I have the timezone set to PST. :) [ ... ] If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. I'll give it a shot and see what happens, I did just that yesterday. Okay, changed my pool since it's to keep this computer's time correct. Thanks for your help. :) You are most welcome. -- -Chuck Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. The system it is runing on is Windows 2003, the time and all that system are correct. I turned on ntpd because for some strange reason the date and time were still not in keeping with the system time, or so I thought. I'ld have to re-investigate that to be sure. Over the weekend I'll stop the ntpd and see what happens to the time when Monday rolls around. Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On 2006/12/01 8:56, Kris Anderson seems to have typed: --- Chuck Swiger [EMAIL PROTECTED] wrote: However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. Nope, not dual booting, see below. :| It could be that the virtual machine is giving FreeBSD the time in UTC, not your local timezone. Try changing the timezone options (you can use sysinstall - Configue - Time Zone and choosing yes) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote: Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. Sigh-- you're right, you should have mentioned this before. One should not attempt to change the clock from within a virtual machine at all, only in the parent or host OS. VMs depend on the host OS to provide the timekeeping, and it is known that systems running inside a VM may experience timing glitches as a result of running inside the machine emulation. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--On Friday, December 01, 2006 10:23:17 -0800 Chuck Swiger [EMAIL PROTECTED] wrote: On Dec 1, 2006, at 9:56 AM, Kris Anderson wrote: Darn the system time strayed over night. One thing I failed to mention is that freebsd is running on a virtual machine. Sigh-- you're right, you should have mentioned this before. One should not attempt to change the clock from within a virtual machine at all, only in the parent or host OS. VMs depend on the host OS to provide the timekeeping, and it is known that systems running inside a VM may experience timing glitches as a result of running inside the machine emulation. http://ntp.isc.org/bin/view/Support/KnownOsIssues#Section_9.2.1. pgpMohInQAgxV.pgp Description: PGP signature
NTPD not keeping time
Hi folks, Having an issue with ntpd not keeping the correct time. I first ran ntpdate from /etc/rc.d/ntpdate and that set the date and time. Then I ran /etc/rc.d/ntpd and that started up fine. The followind day I find that the system still thinks it is the previous day and such. I thought the purpose of ntp was to keep the time correct, why would it be off? Here is my ntp.conf. logconfig =syncstatus +sysevents logfile /var/log/ntp.log server time-a.nist.gov prefer iburst server utcnist.colorado.edu iburst server lerc-dns.lerc.nasa.gov iburst driftfile /var/db/ntp.drift Contents of ntp.drift 0.000 ntp.log 29 Nov 23:08:39 ntpd[18856]: frequency initialized 0.000 PPM from /var/db/ntp.drift 29 Nov 23:08:39 ntpd[18856]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) ntpd.log 29 Nov 23:08:39 ntpd[18856]: logging to file /var/log/ntpd.log 29 Nov 23:08:39 ntpd[18856]: ntpd 4.2.0-a Mon Oct 30 10:00:24 PST 2006 (1) 29 Nov 23:08:39 ntpd[18856]: precision = 1.955 usec 29 Nov 23:08:39 ntpd[18856]: kernel time sync status 2040 Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Nov 30, 2006, at 11:16 AM, Kris Anderson wrote: I first ran ntpdate from /etc/rc.d/ntpdate and that set the date and time. Good. That should have gotten your clock reasonably sync'ed. Then I ran /etc/rc.d/ntpd and that started up fine. The followind day I find that the system still thinks it is the previous day and such. I thought the purpose of ntp was to keep the time correct, why would it be off? NTPd does a good job of keeping the clock synced if properly configured, so there is likely to be something wrong with your specific circumstances. What does ntpq -p show? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Nov 30, 2006, at 11:16 AM, Kris Anderson wrote: I first ran ntpdate from /etc/rc.d/ntpdate and that set the date and time. Good. That should have gotten your clock reasonably sync'ed. Then I ran /etc/rc.d/ntpd and that started up fine. The followind day I find that the system still thinks it is the previous day and such. I thought the purpose of ntp was to keep the time correct, why would it be off? NTPd does a good job of keeping the clock synced if properly configured, so there is likely to be something wrong with your specific circumstances. What does ntpq -p show? -- -Chuck Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 10240 0.0000.000 4000.00 Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Nov 30, 2006, at 12:16 PM, Kris Anderson wrote: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 10240 0.0000.000 4000.00 Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. You should also note that your third ntp server is not answering queries, so you should try finding some other ntp server to use. Are you providing time syncronization from this machine to other hosts, or are you only running as a standalone client? If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On 2006/11/30 11:16, Kris Anderson seems to have typed: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 10240 0.0000.000 4000.00 I take it this system was shutdown overnight? It looks like ntpd hasn't been running long at this point. Try starting ntpd with the -g flag On 2006/11/30 10:16, Kris Anderson seems to have typed: server time-a.nist.gov prefer iburst server utcnist.colorado.edu iburst server lerc-dns.lerc.nasa.gov iburst You might also want to consider using the pool instead of all stratum 1 servers, for most the pool is more than accurate enough, so: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org Unless you really need to be using statum 1 servers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On 2006/11/30 11:48, Peter A. Giessel seems to have typed: On 2006/11/30 11:16, Kris Anderson seems to have typed: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 102400.0000.000 4000.00 I take it this system was shutdown overnight? It looks like ntpd hasn't been running long at this point. Nevermind, I misread the reach column... Sorry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Nov 30, 2006, at 12:16 PM, Kris Anderson wrote: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 1024 0 0.0000.000 4000.00 Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. Off by an hour? Let's see the date is November 30th, and 12:41pm, that's what Windows says. Meanwhile freebsd says - Thu Nov 30 00:22:07 PST 2006. Wouldn't that be...nearly 12 hours? You should also note that your third ntp server is not answering queries, so you should try finding some other ntp server to use. Are you providing time syncronization from this machine to other hosts, or are you only running as a standalone client? If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. I'll give it a shot and see what happens, I did just that yesterday. Okay, changed my pool since it's to keep this computer's time correct. Thanks for your help. :) Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
--- Peter A. Giessel [EMAIL PROTECTED] wrote: On 2006/11/30 11:16, Kris Anderson seems to have typed: Here's the output from ntpq. webdev# ntpq -p remote refid st t when poll reach delay offset jitter == time-a.nist.gov .ACTS. 1 u 485 1024 377 78.454 4307608 923174. india.colorado. .ACTS. 1 u 491 1024 377 22.918 4307064 922326. lerc-dns.grc.na .INIT. 16 u- 1024 0 0.0000.000 4000.00 I take it this system was shutdown overnight? It looks like ntpd hasn't been running long at this point. Try starting ntpd with the -g flag Going to try and reset the clocks and such and see what happens the next day. :) On 2006/11/30 10:16, Kris Anderson seems to have typed: server time-a.nist.gov prefer iburst server utcnist.colorado.edu iburst server lerc-dns.lerc.nasa.gov iburst You might also want to consider using the pool instead of all stratum 1 servers, for most the pool is more than accurate enough, so: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org Unless you really need to be using statum 1 servers... Yep, going to add the ntp.org pool and see how that works. Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD not keeping time
On Nov 30, 2006, at 12:55 PM, Kris Anderson wrote: Your clock is off by a little over an hour; while ntpd can correct very large offsets, doing so takes a long time. Kill ntpd, re-run ntpdate -b, double-check that your clock is sane, and then re-start ntpd. Off by an hour? Let's see the date is November 30th, and 12:41pm, that's what Windows says. Meanwhile freebsd says - Thu Nov 30 00:22:07 PST 2006. Wouldn't that be...nearly 12 hours? I was judging the time-offset by the output of ntpq -p. However, if you are dual-booting between FreeBSD and Windows, you will also need to consider whether to keep the CMOS/BIOS clock running in UTC or in your local timezone; see man adjkerntz for details. It's entirely possible that doing a touch /etc/wall_cmos_clock will solve your issue. [ ... ] If you are not providing time sync to a large subnet, please consider using stratum-2 servers or the NTP pool, ie, pool.ntp.org, or more specific regional parts, such as 0.us.pool.ntp.org, 1.us.pool.ntp.org-- this is assuming from your IP that you are located in the US, otherwise choose the appropriate country code for where-ever you are. I'll give it a shot and see what happens, I did just that yesterday. Okay, changed my pool since it's to keep this computer's time correct. Thanks for your help. :) You are most welcome. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
