Re: [pfSense Support] setting time
Not sure if this is resolved, I was reminded today of the BIOS reports of the system status - especially the voltages, a failing power supply might also cause this problem, check the voltages from the boot BIOS. Do let us know the outcome. Kind regards David Hingston - Original Message - From: Vivek Khera [EMAIL PROTECTED] To: support@pfsense.com Sent: Tuesday, May 13, 2008 2:47 AM Subject: Re: [pfSense Support] setting time You likely have faulty hardware. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
On May 10, 2008, at 11:16 AM, Dean Larson wrote: computer kept near perfect time before under different o/s. this seems real strange. A long long time ago, in a galaxy far far away, I had a box that ran 100% fine with linux under load. under FreeBSD and BSD/OS it would lock up randomly, and the clock would drift several minutes per day.ap You likely have faulty hardware. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
On May 10, 2008, at 4:13 PM, Chris Buechler wrote: 3) ACPI issues - try disabling ACPI, sometimes it causes time keeping issues. You can also selectively disable the ACPI timer device without turning ACPI off entirely. Add the following to your /boot/loader.conf file: debug.acpi.disabled=timer You'll see a change at the beginning of your kernel boot messages like this: Timecounter i8254 frequency 1193182 Hz quality 0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 Timecounter HPET frequency 14318180 Hz quality 900 The ACPI-fast line will go away, and the kernel will then be forced to choose a different timekeeping method. You can verify your timekeeper with this command: sysctl sysctl kern.timecounter.hardware It will list one of the available Timecounter options, such as HPET or ACPI-fast. By default, it picks the highest quality timer. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] setting time
battery appears to be fine. i didn't put a volt meter on it, but when the computer has been off, the cmos info stayed current. i'll take it down on monday, and if it is low on voltage, i'll report back Date: Sun, 11 May 2008 16:29:39 +1200 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time Dean, have you checked the motherboard battery? (I think in theory this should only be relevant on powering off, but I wouldn't be sure in practice) Kind regards David Hingston - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
Curtis LaMasters wrote: What timezone are you in? If CST try Chicago instead of GMT -6. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com Yeah, for those of you who don't know. The GMT settings for FreeBSD and other OSsen are completely wrong. If you're trying to use a GMT time zone setting and its not right, use the Country/City settings instead. For the OP: on the command line, run: ntpdate us.pool.ntp.org As long as your time zones are set correctly, this should ensure your time is set correctly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] setting time
right now it is running about 10 minutes fast. i set it to chicago about 30 minutes ago... and time still moves on a head. am i missing something? is there some way of telling the time? what i have been doing is getting a command prompt on the machine and doing date. also i've caused a event to log -- and looked at the entry in the look -- ie: pass traffic to a server that the firewall will not let me do: ie: tcp port 40. dean Date: Fri, 9 May 2008 23:46:18 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time What timezone are you in? If CST try Chicago instead of GMT -6. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com _ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
Have you run: ntpdate pool.ntp.org from the command line? Dean Larson wrote: right now it is running about 10 minutes fast. i set it to chicago about 30 minutes ago... and time still moves on a head. am i missing something? is there some way of telling the time? what i have been doing is getting a command prompt on the machine and doing date. also i've caused a event to log -- and looked at the entry in the look -- ie: pass traffic to a server that the firewall will not let me do: ie: tcp port 40. dean Date: Fri, 9 May 2008 23:46:18 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time What timezone are you in? If CST try Chicago instead of GMT -6. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com _ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] setting time
i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s tick.usno.navy.mil i did the command you said ntpdate pool.ntp.org. and yes it sets the time, but it doesn't stay. for long. computer kept near perfect time before under different o/s. this seems real strange. Date: Sat, 10 May 2008 10:12:32 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time Have you run: ntpdate pool.ntp.org from the command line? Dean Larson wrote: right now it is running about 10 minutes fast. i set it to chicago about 30 minutes ago... and time still moves on a head. am i missing something? is there some way of telling the time? what i have been doing is getting a command prompt on the machine and doing date. also i've caused a event to log -- and looked at the entry in the look -- ie: pass traffic to a server that the firewall will not let me do: ie: tcp port 40. dean Date: Fri, 9 May 2008 23:46:18 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time What timezone are you in? If CST try Chicago instead of GMT -6. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com _ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Get Free (PRODUCT) RED™ Emoticons, Winks and Display Pics. http://joinred.spaces.live.com?ocid=TXT_HMTG_prodredemoticons_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
If pfsense has a proper (or somewhat reasonable) ntp running, instead of using tick.usno.navy.mil in your cron job, set use this server (tick.usno.navy.mil) as the ntp time server in System General Setup in the GUI (at least in the embedded version it is located there). You *may* have to run ntpdate from the command line one time only. NTP won't correct if your clock is off by more than +-500 ppm -- which may be the case for you. Perhaps the clock speed is set wrong. John On May 10, 2008, at 8:16 AM, Dean Larson wrote: i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s tick.usno.navy.mil i did the command you said ntpdate pool.ntp.org. and yes it sets the time, but it doesn't stay. for long. computer kept near perfect time before under different o/s. this seems real strange. Date: Sat, 10 May 2008 10:12:32 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time Have you run: ntpdate pool.ntp.org from the command line? Dean Larson wrote: right now it is running about 10 minutes fast. i set it to chicago about 30 minutes ago... and time still moves on a head. am i missing something? is there some way of telling the time? what i have been doing is getting a command prompt on the machine and doing date. also i've caused a event to log -- and looked at the entry in the look -- ie: pass traffic to a server that the firewall will not let me do: ie: tcp port 40. dean Date: Fri, 9 May 2008 23:46:18 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time What timezone are you in? If CST try Chicago instead of GMT -6. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com _ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Get Free (PRODUCT) RED™ Emoticons, Winks and Display Pics. http://joinred.spaces.live.com?ocid=TXT_HMTG_prodredemoticons_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
I have seen some older systems have an issue between the hardware clock being set to UTC or Localtime and the OS showing a completely different time. May want to recheck your BIOS Date/Time. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com
RE: [pfSense Support] setting time
i'll verify the clock on the hardware to verify they are both on the same page. :) Date: Sat, 10 May 2008 11:53:10 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time I have seen some older systems have an issue between the hardware clock being set to UTC or Localtime and the OS showing a completely different time. May want to recheck your BIOS Date/Time. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com _ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] setting time
bios has no timezone settings. it just has a time. i verified they are both at same time, noticed after reboot, the system time appeared to be set to gmt. so i changed the time zone for pfsense to gmt. no change. time still is off. in 5 minutes time was adjusted -172.599028 s Date: Sat, 10 May 2008 11:53:10 -0500 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time I have seen some older systems have an issue between the hardware clock being set to UTC or Localtime and the OS showing a completely different time. May want to recheck your BIOS Date/Time. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com _ Make Windows Vista more reliable and secure with Windows Vista Service Pack 1. http://www.windowsvista.com/SP1?WT.mc_id=hotmailvistasp1banner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
On Sat, May 10, 2008 at 11:16 AM, Dean Larson [EMAIL PROTECTED] wrote: i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s tick.usno.navy.mil i did the command you said ntpdate pool.ntp.org. and yes it sets the time, but it doesn't stay. for long. computer kept near perfect time before under different o/s. this seems real strange. Sounds familiar. I've seen and/or heard of this under 3 circumstances. 1) Buggy BIOS - I've redeployed older hardware that ran fine for years with Windows, but as soon as I redeployed with FreeBSD, it wouldn't keep time for anything. Updated to the latest BIOS and the problem was gone. It was several revisions out of date, one of which included a timekeeping fix that apparently didn't apply to Windows. I specifically saw this with Dell hardware, but it's possible with any hardware and have heard of others seeing the same with other hardware. 2) PNP OS turned on - if PNP OS is on in your BIOS, turn it off. 3) ACPI issues - try disabling ACPI, sometimes it causes time keeping issues. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] setting time
tried flashing the bios... didn't seem to help. i guess we have a strange computer -- old, but i should be happy it works. it is a msi computer with 350 processor. thank you for all your help. dean Date: Sat, 10 May 2008 16:13:11 -0400 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time On Sat, May 10, 2008 at 11:16 AM, Dean Larson wrote: i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s tick.usno.navy.mil i did the command you said ntpdate pool.ntp.org. and yes it sets the time, but it doesn't stay. for long. computer kept near perfect time before under different o/s. this seems real strange. Sounds familiar. I've seen and/or heard of this under 3 circumstances. 1) Buggy BIOS - I've redeployed older hardware that ran fine for years with Windows, but as soon as I redeployed with FreeBSD, it wouldn't keep time for anything. Updated to the latest BIOS and the problem was gone. It was several revisions out of date, one of which included a timekeeping fix that apparently didn't apply to Windows. I specifically saw this with Dell hardware, but it's possible with any hardware and have heard of others seeing the same with other hardware. 2) PNP OS turned on - if PNP OS is on in your BIOS, turn it off. 3) ACPI issues - try disabling ACPI, sometimes it causes time keeping issues. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Stay in touch when you're away with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
Hi Dean, You can see what FreeBSD (pfSense) is using to keep time with the following command: firewall:~# sysctl kern.timecounter.hardware kern.timecounter.hardware: TSC You can see what is available with the command: firewall:~# dmesg | grep Timecounter Timecounter i8254 frequency 1193182 Hz quality 0 Timecounter TSC frequency 499904486 Hz quality 800 Timecounters tick every 10.000 msec You can try one of your other options with this command (e.g., to try i8254): sysctl -w kern.timecounter.hardware=i8254 If it keeps better time, you can add a line to /etc/sysctl.conf (so a reboot will use your new choice): kern.timecounter.hardware=i8254 John On May 10, 2008, at 7:14 PM, Dean Larson wrote: tried flashing the bios... didn't seem to help. i guess we have a strange computer -- old, but i should be happy it works. it is a msi computer with 350 processor. thank you for all your help. dean Date: Sat, 10 May 2008 16:13:11 -0400 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time On Sat, May 10, 2008 at 11:16 AM, Dean Larson wrote: i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s tick.usno.navy.mil i did the command you said ntpdate pool.ntp.org. and yes it sets the time, but it doesn't stay. for long. computer kept near perfect time before under different o/s. this seems real strange. Sounds familiar. I've seen and/or heard of this under 3 circumstances. 1) Buggy BIOS - I've redeployed older hardware that ran fine for years with Windows, but as soon as I redeployed with FreeBSD, it wouldn't keep time for anything. Updated to the latest BIOS and the problem was gone. It was several revisions out of date, one of which included a timekeeping fix that apparently didn't apply to Windows. I specifically saw this with Dell hardware, but it's possible with any hardware and have heard of others seeing the same with other hardware. 2) PNP OS turned on - if PNP OS is on in your BIOS, turn it off. 3) ACPI issues - try disabling ACPI, sometimes it causes time keeping issues. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Stay in touch when you're away with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] setting time
thank you thank you. you all are wonderful. i did ysctl -w kern.timecounter.hardware=i8254 and after 33 minutes i was off .04 seconds. better than 250 seconds.:) again thank you all for your help. dean From: [EMAIL PROTECTED] To: support@pfsense.com Date: Sat, 10 May 2008 19:55:03 -0700 Subject: Re: [pfSense Support] setting time Hi Dean, You can see what FreeBSD (pfSense) is using to keep time with the following command: firewall:~# sysctl kern.timecounter.hardware kern.timecounter.hardware: TSC You can see what is available with the command: firewall:~# dmesg | grep Timecounter Timecounter i8254 frequency 1193182 Hz quality 0 Timecounter TSC frequency 499904486 Hz quality 800 Timecounters tick every 10.000 msec You can try one of your other options with this command (e.g., to try i8254): sysctl -w kern.timecounter.hardware=i8254 If it keeps better time, you can add a line to /etc/sysctl.conf (so a reboot will use your new choice): kern.timecounter.hardware=i8254 John On May 10, 2008, at 7:14 PM, Dean Larson wrote: tried flashing the bios... didn't seem to help. i guess we have a strange computer -- old, but i should be happy it works. it is a msi computer with 350 processor. thank you for all your help. dean Date: Sat, 10 May 2008 16:13:11 -0400 From: [EMAIL PROTECTED] To: support@pfsense.com Subject: Re: [pfSense Support] setting time On Sat, May 10, 2008 at 11:16 AM, Dean Larson wrote: i have a cron job of 15 * * * * /usr/sbin/ntpdate -u -s tick.usno.navy.mil i did the command you said ntpdate pool.ntp.org. and yes it sets the time, but it doesn't stay. for long. computer kept near perfect time before under different o/s. this seems real strange. Sounds familiar. I've seen and/or heard of this under 3 circumstances. 1) Buggy BIOS - I've redeployed older hardware that ran fine for years with Windows, but as soon as I redeployed with FreeBSD, it wouldn't keep time for anything. Updated to the latest BIOS and the problem was gone. It was several revisions out of date, one of which included a timekeeping fix that apparently didn't apply to Windows. I specifically saw this with Dell hardware, but it's possible with any hardware and have heard of others seeing the same with other hardware. 2) PNP OS turned on - if PNP OS is on in your BIOS, turn it off. 3) ACPI issues - try disabling ACPI, sometimes it causes time keeping issues. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Stay in touch when you're away with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Stay in touch when you're away with Windows Live Messenger. http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
Dean, have you checked the motherboard battery? (I think in theory this should only be relevant on powering off, but I wouldn't be sure in practice) Kind regards David Hingston - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
On Sun, May 11, 2008 at 12:19 AM, Dean Larson [EMAIL PROTECTED] wrote: i did ysctl -w kern.timecounter.hardware=i8254 and after 33 minutes i was off .04 seconds. better than 250 seconds.:) Good to know! Thanks for reporting back. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] setting time
What timezone are you in? If CST try Chicago instead of GMT -6. -- Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com
