spinbot Posted October 26, 2009 Author Share Posted October 26, 2009 If she looked like that, I wouldn't be online playing with my computer! For reference, she is Commander T'Pol in Star Trek: Enterprise (played by Jolene Blalock ) She's on "My list" Looks like I have 15 hours of re-building to wait for I'm sorta laughing about the issue I had with it. When I was buying new drives, I was undecided between staying with Seagates or giving WD Green a chance . I ended up getting one of each, although I used my Seagate for parity ( as I still trust them more, even with their bad firmware release ). I hope this is just a "glitch" that will disappear now, but.... if not, I think I will be firm in my decision to stay with Seagates. I do have a spare 1.5TB Seagate drive not installed in my array yet ( I removed it from my Popcorn Hour ). I'll need to add it soon as I the copying of my library to the drives is eating up the space pretty fast. The last few days I've re-done my Popcorn Hour with a YAMJ and a new skin and have to say I am glad I undertook this UnRaid project as the ending result is very impressive. Too bad I don't have any friends to show it off too! hehe Link to comment
Joe L. Posted October 26, 2009 Share Posted October 26, 2009 Done. While you are being me for the night, do you think I should break up with my girlfriend or let things go a little long to see if a future does exist for us? My wife would frown highly if I were to have a girlfriend. You are on your own there... If the two of you have common interests, it could last. How is she at wiring a LAN? My wife and I took up Ballroom Dancing about 4 years ago. Fun, social, exercise, something else to do together (lessons, social dinner dances), and a lot to learn together. Oh yes, we also watch a lot of movies together, from our server... In fact, a few years ago she requested the LAN connection in our bedroom, so we could use media player there to watch movies and play music from the unRAID server... Who knows, if you two find some common interests, you might make a go of it like we have. (Married 35+ years) Joe L. Link to comment
Joe L. Posted October 26, 2009 Share Posted October 26, 2009 Looks like I have 15 hours of re-building to wait for If you spent a tiny bit of that 15 hours with your girl-friend, or used some of it to make some friends, you might not be so lonely. Only kidding... Link to comment
spinbot Posted October 26, 2009 Author Share Posted October 26, 2009 She's got the flu , so I'm keeping my space from her and her kids right now. I'll get my immunity to the flu the old fashion way ..... FLU SHOT I find it easier to have few friends in life. I don't have to worry about birthday presents or Christmas presents then. I think I'm just getting selfish with my time as I get older ( almost 40 now ). I like my quiet, alone time. Not sure I am ready to share a home with a woman and kids again, on a full time basis ( not sure I ever was, thus the reason I never married or had kids of my own ). My health has always been questionable ( Chrohn's Disease ), so I try to keep a slower paced life, less responsibility as it just seems to work best for me. Ok...back on topic..... 8 hours of rebuilding to go. Once the rebuild is completed, should I do anything else ( ie. test anything ) to make sure everything is back in working order? More screen shots from the Smart features like before and an updated copy of the syslog? Could anything I had done caused this problem in the first place? Here's a few things I did today, all through Windows Explorer: - added some .nfo files in the folders of some of the DVDs - renamed the odd folder and ISO so YAMJ would read it properly - deleted a duplicate copy of an .ISO I had - added some image files to some of the folders - ran YAMJ multiple times to build my Jukebox folder and index.html file ( this output was all stored on my Popcorn Hour ) - added a few smaller files to my network share /media by dragging and dropping ( .avi and .mkv ) - shuffled a few files around to group like items in the same folder. Ex. from: /media/Stargate.S3.D1/disc1.iso /media/Stargate.S3.D2/disc2.iso /media/Stargate.S3.D3/disc3.iso to: /media/Stargate.S3/disc1.iso /media/Stargate.S3/disc2.iso /media/Stargate.S3/disc3.iso Link to comment
spinbot Posted October 26, 2009 Author Share Posted October 26, 2009 Re-Build has completed. From the mail screen, all has green lights Status: STARTED, 5 disks in array. Parity is Valid:. Last parity check < 1 day ago with no sync errors. Here's some details, for your expert analysis HDParm Info for /dev/sdb WDC_WD15EADS-00P8B0_WD-WMAVU0072618 /dev/sdb: ATA device, with non-removable media Model Number: WDC WD15EADS-00P8B0 Serial Number: WD-WMAVU0072618 Firmware Revision: 01.00A01 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5 Standards: Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 2930277168 device size with M = 1024*1024: 1430799 MBytes device size with M = 1000*1000: 1500301 MBytes (1500 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * SATA-I signaling speed (1.5Gb/s) * SATA-II signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * unknown 76[12] DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 334min for SECURITY ERASE UNIT. 334min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee017dfab1 NAA : 5 IEEE OUI : 14ee Unique ID : 017dfab1 Checksum: correct Statistics for /dev/sdb WDC_WD15EADS-00P8B0_WD-WMAVU0072618 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EADS-00P8B0 Serial Number: WD-WMAVU0072618 Firmware Version: 01.00A01 User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Oct 26 09:21:09 2009 GMT+5 SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (32760) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 200 179 021 Pre-fail Always - 4975 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 121 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 685 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 58 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 44 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3425 194 Temperature_Celsius 0x0022 123 115 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Syslog is attached. Nothing in RED ( thankfully ). Although it does seem to want to repeat a few lines over and over again: Oct 26 08:24:19 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 08:40:24 Tower ntpd[1295]: time reset +2.597765 s Oct 26 08:45:18 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 08:53:48 Tower ntpd[1295]: no servers reachable Oct 26 09:05:41 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:05:41 Tower ntpd[1295]: time reset +3.902682 s Oct 26 09:06:00 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:14:28 Tower ntpd[1295]: no servers reachable Oct 26 09:16:37 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:17:41 Tower ntpd[1295]: no servers reachable Oct 26 09:19:47 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:21:57 Tower ntpd[1295]: time reset +2.507568 s Oct 26 09:22:34 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:31:05 Tower ntpd[1295]: no servers reachable Link to comment
prostuff1 Posted October 26, 2009 Share Posted October 26, 2009 Oct 26 08:24:19 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 08:40:24 Tower ntpd[1295]: time reset +2.597765 s Oct 26 08:45:18 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 08:53:48 Tower ntpd[1295]: no servers reachable Oct 26 09:05:41 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:05:41 Tower ntpd[1295]: time reset +3.902682 s Oct 26 09:06:00 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:14:28 Tower ntpd[1295]: no servers reachable Oct 26 09:16:37 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:17:41 Tower ntpd[1295]: no servers reachable Oct 26 09:19:47 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:21:57 Tower ntpd[1295]: time reset +2.507568 s Oct 26 09:22:34 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:31:05 Tower ntpd[1295]: no servers reachable This is happening to me lately on my machine and I am not quite sure why. I assume it is because the ntp can't find a server to update from. if you need more info on NTP take a look here. Link to comment
Joe L. Posted October 26, 2009 Share Posted October 26, 2009 Oct 26 08:24:19 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 08:40:24 Tower ntpd[1295]: time reset +2.597765 s Oct 26 08:45:18 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 08:53:48 Tower ntpd[1295]: no servers reachable Oct 26 09:05:41 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:05:41 Tower ntpd[1295]: time reset +3.902682 s Oct 26 09:06:00 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:14:28 Tower ntpd[1295]: no servers reachable Oct 26 09:16:37 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:17:41 Tower ntpd[1295]: no servers reachable Oct 26 09:19:47 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:21:57 Tower ntpd[1295]: time reset +2.507568 s Oct 26 09:22:34 Tower ntpd[1295]: synchronized to 216.221.90.121, stratum 3 Oct 26 09:31:05 Tower ntpd[1295]: no servers reachable This is happening to me lately on my machine and I am not quite sure why. I assume it is because the ntp can't find a server to update from. if you need more info on NTP take a look here. Not sure what part of the world you are in, but I use us.pool.ntp.org as my NTP time server, and do not get similar messages. You need to have a DNS nameserver defined in your unRAID settings, but in many cases, it can be the IP address of your router. Link to comment
spinbot Posted October 26, 2009 Author Share Posted October 26, 2009 Not sure what part of the world you are in, but I use us.pool.ntp.org as my NTP time server, and do not get similar messages. You need to have a DNS nameserver defined in your unRAID settings, but in many cases, it can be the IP address of your router. I'm in Canada (-5 GMT). If that works for you, then I guess maybe we should use it too? Is this something simple that can be changed? Secondly, can you take a peak at the end of Page 2 Joe, as I output my results after rebuilding the array over night. I'd like your trained eye to skim it over and let me know if everything looks ok right now. Then I can proceed to move some files into the array again. Thanks! Link to comment
Joe L. Posted October 26, 2009 Share Posted October 26, 2009 Not sure what part of the world you are in, but I use us.pool.ntp.org as my NTP time server, and do not get similar messages. You need to have a DNS nameserver defined in your unRAID settings, but in many cases, it can be the IP address of your router. I'm in Canada (-5 GMT). If that works for you, then I guess maybe we should use it too? Is this something simple that can be changed? It is in your settings page in the unRAID management web-interface. You will need to fill in the "Gateway" (usually your router's IP will do there) and the DNS Server (again, usually the router's IP will do) and then under date and time fill in the NTP Server 1 with us.pool.ntp.org I'm curious, what do you have there now as the NTP server? Secondly, can you take a peak at the end of Page 2 Joe, as I output my results after rebuilding the array over night. I'd like your trained eye to skim it over and let me know if everything looks ok right now. Then I can proceed to move some files into the array again. Thanks! Looked good. Keep an eye on the array. If the loose connection still exists it will take the drive off-line again. Unless you watch for the DISK_DSBL status, you might not notice anything odd with getting to the "virtual" disk that is simulated by parity and the other data drives. Joe L. Link to comment
spinbot Posted October 26, 2009 Author Share Posted October 26, 2009 You will need to fill in the "Gateway" (usually your router's IP will do there) and the DNS Server (again, usually the router's IP will do) and then under date and time fill in the NTP Server 1 with us.pool.ntp.org I'm curious, what do you have there now as the NTP server? Secondly, can you take a peak at the end of Page 2 Joe, as I output my results after rebuilding the array over night. I'd like your trained eye to skim it over and let me know if everything looks ok right now. Then I can proceed to move some files into the array again. Thanks! My current settings are: Gateway: 172.16.0.1 ( this is from the UnRaid setup screen ) and is listed on my Linksys router as my Local IP Address, under the setup screen On my Linkysys Router Status screen, I get: Default Gateway: 206.248.154.122 DNS Servers ( are the same as I get in my router's info page) NTP Server 1: pool.ntp.org Link to comment
Joe L. Posted October 26, 2009 Share Posted October 26, 2009 You will need to fill in the "Gateway" (usually your router's IP will do there) and the DNS Server (again, usually the router's IP will do) and then under date and time fill in the NTP Server 1 with us.pool.ntp.org I'm curious, what do you have there now as the NTP server? Secondly, can you take a peak at the end of Page 2 Joe, as I output my results after rebuilding the array over night. I'd like your trained eye to skim it over and let me know if everything looks ok right now. Then I can proceed to move some files into the array again. Thanks! My current settings are: Gateway: 172.16.0.1 ( this is from the UnRaid setup screen ) and is listed on my Linksys router as my Local IP Address, under the setup screen On my Linkysys Router Status screen, I get: Default Gateway: 206.248.154.122 DNS Servers ( are the same as I get in my router's info page) NTP Server 1: pool.ntp.org That all looks good too... must just have been a point in time where the ntp pool was not reachable from your router. What do you get when you try pinging it from a login prompt? ping -c 5 pool.ntp.org Link to comment
spinbot Posted October 26, 2009 Author Share Posted October 26, 2009 Looks good, from the prompt: Tower login: root Linux 2.6.29.1-unRAID. root@Tower:~# ping -c 5 pool.ntp.org PING pool.ntp.org (199.60.16.218) 56(84) bytes of data. 64 bytes from csss.cs.sfu.ca (199.60.16.218): icmp_seq=1 ttl=49 time=117 ms 64 bytes from csss.cs.sfu.ca (199.60.16.218): icmp_seq=2 ttl=49 time=72.6 ms 64 bytes from csss.cs.sfu.ca (199.60.16.218): icmp_seq=3 ttl=49 time=71.0 ms 64 bytes from csss.cs.sfu.ca (199.60.16.218): icmp_seq=4 ttl=49 time=72.6 ms 64 bytes from csss.cs.sfu.ca (199.60.16.218): icmp_seq=5 ttl=49 time=72.5 ms --- pool.ntp.org ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4038ms rtt min/avg/max/mdev = 71.032/81.282/117.602/18.172 ms root@Tower:~# How often does this check take place, to make sure the time is correct? I have issues with my DSL dropping periodically, so this may be part of the problem if it checks a lot. Link to comment
RobJ Posted October 28, 2009 Share Posted October 28, 2009 If you are losing Internet access periodically, then that would explain the unreachable servers. Otherwise, I recommend adding additional time servers, see the following new FAQ entry for 2 links that can help. How do I keep accurate time on my server? NTP seems to be very intelligently designed. Initially, it will check the time very often, and build up its own knowledge base about your own machine's timekeeping abilities, as well as the time server(s) you assign to it. Once it has determined an accurate drift factor for your machine, and possibly an idea of how consistently your machine drifts, then it will greatly lengthen the checking interval. It then uses this calculated drift value to periodically update your clock. If it does find a problem later, such as a TSC error, then it will start checking more frequently again. Link to comment
spinbot Posted October 28, 2009 Author Share Posted October 28, 2009 Call me old fashion, but I set my clock once and leave it be! Does it really need to check that often? Maybe a re-sync every week or month seem reasonable to me. I will try what you said when I get home this evening. Link to comment
BRiT Posted October 28, 2009 Share Posted October 28, 2009 That all depends, do you want the correct time or something that's in the general area of plus or minus a couple of minutes? I've seen systems with clock skews of several minutes daily. Link to comment
spinbot Posted October 29, 2009 Author Share Posted October 29, 2009 System time is more useful to me than the server ( as I really don't use the clock on it ), nonetheless I made a change and listed 3 Canadian NTP servers. Lets see if my syslog stabilizes or gets loaded with errors still Link to comment
RobJ Posted October 29, 2009 Share Posted October 29, 2009 That reminds me, and I forgot to tell you, but those time reset messages in your syslog indicate the need to constantly and significantly correct your system clock. It looks to me as if it is about 9 seconds per hour, which extrapolates to about 220 seconds per day. That is more than 3 and a half minutes each day! You will see a lot of time corrections and time server checks for a few days, until it is confident about how much correction is needed, then it will use its own calculated number (the drift value) to periodically correct your clock, with only a very occasional external check of the other time servers. Link to comment
Joe L. Posted October 29, 2009 Share Posted October 29, 2009 Call me old fashion, but I set my clock once and leave it be! Does it really need to check that often? Maybe a re-sync every week or month seem reasonable to me. The time sync is very important to be nearly identical across a network of PCs on the same LAN if you are doing any kind of automated backups between them. Most of the programs use the file modification times to detect a change. If the server clock drifts it might do more (or less) than it needs to if it thinks the time-stamp on the backup copy is older/newer than the source. Joe L. Link to comment
spinbot Posted October 29, 2009 Author Share Posted October 29, 2009 Changing the NTP last night didn't really help, as look at my syslog since only noon today: Oct 29 12:00:41 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:11:37 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 12:12:30 Tower ntpd[10746]: no servers reachable Oct 29 12:19:09 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:19:09 Tower ntpd[10746]: time reset +3.506298 s Oct 29 12:19:55 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:22:50 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:26:15 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:27:09 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:29:30 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:32:30 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:35:59 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:35:59 Tower ntpd[10746]: time reset +2.427581 s Oct 29 12:36:48 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:40:18 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 12:46:36 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:48:57 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 12:51:34 Tower ntpd[10746]: no servers reachable Oct 29 12:52:13 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:52:13 Tower ntpd[10746]: time reset +2.490606 s Oct 29 12:52:29 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 12:56:33 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:08:39 Tower ntpd[10746]: time reset +2.463528 s Oct 29 13:08:59 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:16:37 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:16:53 Tower ntpd[10746]: no servers reachable Oct 29 13:27:01 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:27:01 Tower ntpd[10746]: time reset +2.739769 s Oct 29 13:27:37 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:31:38 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:35:24 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:38:13 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:38:36 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:39:15 Tower ntpd[10746]: no servers reachable Oct 29 13:39:19 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:43:58 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:43:58 Tower ntpd[10746]: time reset +2.466030 s Oct 29 13:44:11 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:49:27 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 13:51:22 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 13:51:34 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 13:52:40 Tower ntpd[10746]: no servers reachable Oct 29 13:53:45 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 13:59:08 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 14:00:15 Tower ntpd[10746]: time reset +2.498497 s Oct 29 14:00:32 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 14:04:20 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:05:26 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 14:08:52 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:17:17 Tower ntpd[10746]: time reset +2.414158 s Oct 29 14:17:56 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 14:20:45 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:22:13 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 14:26:12 Tower ntpd[10746]: no servers reachable Oct 29 14:29:16 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 14:30:21 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:31:54 Tower ntpd[10746]: no servers reachable Oct 29 14:32:43 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 14:32:43 Tower ntpd[10746]: time reset +2.420543 s Oct 29 14:32:59 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 14:37:11 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:37:30 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 14:40:16 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:48:19 Tower ntpd[10746]: time reset +2.295961 s Oct 29 14:48:48 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 14:59:18 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 15:03:54 Tower ntpd[10746]: time reset +2.345694 s Oct 29 15:04:15 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 15:12:35 Tower ntpd[10746]: no servers reachable Oct 29 15:16:26 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 15:19:41 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 15:19:41 Tower ntpd[10746]: time reset +2.364253 s Oct 29 15:20:38 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 15:23:36 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 15:26:51 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 15:35:32 Tower ntpd[10746]: time reset +2.247270 s Oct 29 15:35:54 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 15:41:04 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 15:41:06 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 15:49:37 Tower ntpd[10746]: no servers reachable Oct 29 15:50:49 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 15:54:01 Tower ntpd[10746]: no servers reachable Oct 29 15:57:10 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 15:57:13 Tower ntpd[10746]: time reset +3.285615 s Oct 29 15:57:46 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 16:00:45 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 16:05:46 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 16:12:35 Tower ntpd[10746]: no servers reachable Oct 29 16:13:18 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 16:13:18 Tower ntpd[10746]: time reset +2.391443 s Oct 29 16:14:01 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 16:15:11 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 16:23:39 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 16:26:38 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 16:29:03 Tower ntpd[10746]: time reset +2.297740 s Oct 29 16:29:20 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 16:32:32 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 16:40:41 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 16:44:23 Tower ntpd[10746]: time reset +2.325069 s Oct 29 16:45:02 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 16:47:37 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:00:06 Tower ntpd[10746]: time reset +2.344087 s Oct 29 17:00:56 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 17:03:31 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:15:54 Tower ntpd[10746]: time reset +2.356962 s Oct 29 17:16:44 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:20:51 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 17:24:04 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:29:25 Tower ntpd[10746]: no servers reachable Oct 29 17:30:29 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:33:44 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 17:33:44 Tower ntpd[10746]: time reset +2.535942 s Oct 29 17:34:07 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:43:23 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 17:44:46 Tower ntpd[10746]: no servers reachable Oct 29 17:46:54 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Oct 29 17:47:58 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 17:48:50 Tower ntpd[10746]: time reset +2.351398 s Oct 29 17:49:27 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Oct 29 17:52:32 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Oct 29 18:05:45 Tower ntpd[10746]: time reset +2.520399 s Oct 29 18:05:53 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Link to comment
BRiT Posted October 29, 2009 Share Posted October 29, 2009 Wow, drifting 2.5 seconds every 15 minutes is quite a bit. That may be a sign of a weak/drained battery on the motherboard or a timing crystal out of sync. Link to comment
RobJ Posted October 30, 2009 Share Posted October 30, 2009 Changing the NTP last night didn't really help, as look at my syslog since only noon today: As I said, give it a few days, and I think even your crazy clock will settle down! It is still in a learning mode. Link to comment
spinbot Posted November 2, 2009 Author Share Posted November 2, 2009 The "crazy clock" hasn't settled down. Here is just a snip from my syslog in the past 11 hours ( note that I did make a change to the timezone as we just had daylight savings time this weekend ) : Nov 1 22:14:13 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 1 22:18:30 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 22:23:45 Tower ntpd[10746]: time reset +2.246433 s Nov 1 22:23:56 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 22:39:56 Tower ntpd[10746]: time reset +2.318980 s Nov 1 22:40:23 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 1 22:43:45 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 22:55:43 Tower ntpd[10746]: time reset +2.235072 s Nov 1 22:56:25 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:11:09 Tower ntpd[10746]: time reset +2.172664 s Nov 1 23:11:45 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 1 23:14:51 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:26:54 Tower ntpd[10746]: time reset +2.235231 s Nov 1 23:27:10 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 1 23:31:36 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:34:24 Tower ntpd[10746]: no servers reachable Nov 1 23:34:49 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:35:52 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 1 23:43:59 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:44:25 Tower ntpd[10746]: no servers reachable Nov 1 23:46:36 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:46:36 Tower ntpd[10746]: time reset +2.800913 s Nov 1 23:47:04 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 1 23:53:13 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 1 23:55:39 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 00:02:58 Tower ntpd[10746]: time reset +2.267831 s Nov 2 00:03:09 Tower emhttp: Spinning up all drives... Nov 2 00:03:22 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 00:18:18 Tower ntpd[10746]: time reset +2.184479 s Nov 2 00:19:08 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 00:22:14 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 00:34:20 Tower ntpd[10746]: time reset +2.302826 s Nov 2 00:34:54 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 00:37:55 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 00:49:49 Tower ntpd[10746]: time reset +2.207635 s Nov 2 00:50:13 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 01:03:19 Tower emhttp: shcmd (226): /usr/sbin/hdparm -y /dev/sde >/dev/null Nov 2 01:03:19 Tower emhttp: shcmd (227): /usr/sbin/hdparm -y /dev/sdb >/dev/null Nov 2 01:03:20 Tower emhttp: shcmd (228): /usr/sbin/hdparm -y /dev/sda >/dev/null Nov 2 01:03:20 Tower emhttp: shcmd (229): /usr/sbin/hdparm -y /dev/sdc >/dev/null Nov 2 01:06:03 Tower ntpd[10746]: time reset +2.240976 s Nov 2 01:06:19 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 01:22:09 Tower ntpd[10746]: time reset +2.317161 s Nov 2 01:22:38 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 01:25:44 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 01:37:57 Tower ntpd[10746]: time reset +2.228115 s Nov 2 01:38:54 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 01:41:33 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 01:54:59 Tower ntpd[10746]: no servers reachable Nov 2 01:56:12 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 01:56:12 Tower ntpd[10746]: time reset +2.606567 s Nov 2 01:56:54 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 01:59:56 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 02:03:09 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 02:06:25 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 02:07:54 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 02:07:56 Tower ntpd[10746]: no servers reachable Nov 2 02:10:04 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 02:13:18 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 02:13:18 Tower ntpd[10746]: time reset +2.285876 s Nov 2 02:14:02 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 02:16:32 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 02:29:04 Tower ntpd[10746]: time reset +2.318568 s Nov 2 02:29:46 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 02:45:38 Tower ntpd[10746]: time reset +2.230570 s Nov 2 02:46:14 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 02:49:04 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 02:49:29 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 02:56:33 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 02:59:09 Tower ntpd[10746]: no servers reachable Nov 2 02:59:44 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 03:00:49 Tower ntpd[10746]: time reset +2.297098 s Nov 2 03:01:29 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 03:04:58 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 03:10:41 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 03:11:21 Tower emhttp: shcmd (230): /usr/sbin/hdparm -y /dev/sda >/dev/null Nov 2 03:11:21 Tower emhttp: shcmd (231): /usr/sbin/hdparm -y /dev/sdc >/dev/null Nov 2 03:11:21 Tower emhttp: shcmd (232): /usr/sbin/hdparm -y /dev/sdd >/dev/null Nov 2 03:14:08 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 03:17:11 Tower ntpd[10746]: time reset +2.261237 s Nov 2 03:17:59 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 03:23:15 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 03:27:49 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 03:31:32 Tower ntpd[10746]: no servers reachable Nov 2 03:32:35 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 03:33:43 Tower ntpd[10746]: time reset +2.353650 s Nov 2 03:34:09 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 03:37:09 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 03:50:23 Tower ntpd[10746]: time reset +2.299079 s Nov 2 03:51:12 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 03:54:11 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 04:04:10 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 04:05:30 Tower ntpd[10746]: no servers reachable Nov 2 04:07:04 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 04:07:07 Tower ntpd[10746]: time reset +2.436850 s Nov 2 04:08:09 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 04:12:00 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 04:16:43 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 04:17:05 Tower ntpd[10746]: no servers reachable Nov 2 04:17:22 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 04:22:45 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 04:23:11 Tower ntpd[10746]: time reset +2.240712 s Nov 2 04:23:27 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 04:28:26 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 04:38:20 Tower ntpd[10746]: time reset +2.072527 s Nov 2 04:38:51 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 04:49:10 Tower ntpd[10746]: no servers reachable Nov 2 04:50:27 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 04:53:41 Tower ntpd[10746]: no servers reachable Nov 2 04:55:37 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 04:55:40 Tower ntpd[10746]: time reset +2.610044 s Nov 2 04:56:19 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:01:08 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 05:03:56 Tower ntpd[10746]: no servers reachable Nov 2 05:08:16 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 05:09:11 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:10:46 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 05:13:39 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:13:39 Tower ntpd[10746]: time reset +2.496086 s Nov 2 05:13:59 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:17:56 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 05:21:22 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:24:26 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 05:26:47 Tower ntpd[10746]: no servers reachable Nov 2 05:29:43 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 05:29:43 Tower ntpd[10746]: time reset +2.314056 s Nov 2 05:30:29 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:41:34 Tower ntpd[10746]: no servers reachable Nov 2 05:42:01 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 05:46:24 Tower ntpd[10746]: time reset +2.224653 s Nov 2 05:46:42 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 05:50:11 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 06:01:59 Tower ntpd[10746]: time reset +2.394065 s Nov 2 06:02:55 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 06:12:58 Tower ntpd[10746]: no servers reachable Nov 2 06:19:03 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 06:19:03 Tower ntpd[10746]: time reset +2.377665 s Nov 2 06:19:22 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 06:22:35 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 06:34:31 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 06:34:31 Tower ntpd[10746]: time reset +2.181498 s Nov 2 06:34:46 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 06:38:35 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 06:50:37 Tower ntpd[10746]: time reset +2.303166 s Nov 2 06:51:25 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 07:06:05 Tower ntpd[10746]: time reset +2.177686 s Nov 2 07:06:10 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 07:07:11 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 07:21:51 Tower ntpd[10746]: time reset +2.163732 s Nov 2 07:22:29 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 07:24:25 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 07:37:43 Tower ntpd[10746]: time reset +2.452872 s Nov 2 07:38:27 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 07:44:55 Tower ntpd[10746]: no servers reachable Nov 2 07:45:47 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 07:54:22 Tower ntpd[10746]: time reset +2.282435 s Nov 2 07:54:41 Tower ntpd[10746]: synchronized to 207.61.229.70, stratum 3 Nov 2 07:59:23 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 07:59:45 Tower dhcpcd[1287]: sending DHCP_REQUEST for 172.16.0.103 to 172.16.0.1 Nov 2 07:59:45 Tower dhcpcd[1287]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Nov 2 07:59:45 Tower dhcpcd[1287]: DHCP_ACK received from (172.16.0.1) Nov 2 08:03:19 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 08:10:06 Tower ntpd[10746]: time reset +2.173703 s Nov 2 08:10:49 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 08:25:34 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 08:25:47 Tower ntpd[10746]: time reset +2.277037 s Nov 2 08:26:06 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 08:31:11 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 08:34:16 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 08:38:38 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 08:41:54 Tower ntpd[10746]: time reset +2.280083 s Nov 2 08:42:33 Tower ntpd[10746]: synchronized to 216.234.161.11, stratum 2 Nov 2 08:47:26 Tower ntpd[10746]: synchronized to 129.128.5.210, stratum 1 Nov 2 08:52:32 Tower emhttp: shcmd (233): ln -sf /usr/share/zoneinfo/Etc/GMT+5 /etc/localtime-copied-from Nov 2 08:52:32 Tower emhttp: shcmd (234): cp /etc/localtime-copied-from /etc/localtime Nov 2 07:52:32 Tower emhttp: shcmd (235): /etc/rc.d/rc.ntpd restart >/dev/null 2>&1 Nov 2 07:52:32 Tower ntpd[10746]: ntpd exiting on signal 15 Nov 2 07:52:34 Tower ntpd[14845]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1) Nov 2 07:52:34 Tower ntpd[14846]: precision = 1.000 usec Nov 2 07:52:34 Tower ntpd[14846]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Nov 2 07:52:34 Tower ntpd[14846]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Nov 2 07:52:34 Tower ntpd[14846]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Nov 2 07:52:34 Tower ntpd[14846]: Listening on interface #2 eth0, 172.16.0.103#123 Enabled Nov 2 07:52:34 Tower ntpd[14846]: kernel time sync status 0040 Nov 2 07:52:34 Tower ntpd[14846]: frequency initialized 37.967 PPM from /etc/ntp/drift Nov 2 07:52:43 Tower ntpd[14846]: synchronized to 208.83.212.8, stratum 3 Nov 2 07:52:45 Tower ntpd[14846]: time reset +1.528360 s Nov 2 07:59:07 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:02:20 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 08:09:03 Tower ntpd[14846]: time reset +2.221214 s Nov 2 08:09:38 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:12:39 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 08:21:23 Tower ntpd[14846]: no servers reachable Nov 2 08:23:31 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 08:25:40 Tower ntpd[14846]: no servers reachable Nov 2 08:27:35 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:27:35 Tower ntpd[14846]: time reset +2.859115 s Nov 2 08:28:12 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 08:36:32 Tower ntpd[14846]: synchronized to 208.83.212.8, stratum 3 Nov 2 08:37:45 Tower ntpd[14846]: no servers reachable Nov 2 08:37:54 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 08:38:40 Tower ntpd[14846]: no servers reachable Nov 2 08:40:05 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:41:10 Tower ntpd[14846]: synchronized to 208.83.212.8, stratum 3 Nov 2 08:46:25 Tower ntpd[14846]: no servers reachable Nov 2 08:50:56 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:50:56 Tower ntpd[14846]: time reset +3.291020 s Nov 2 08:51:31 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:58:14 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 08:58:16 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 08:59:17 Tower ntpd[14846]: no servers reachable Nov 2 08:59:50 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 09:06:50 Tower ntpd[14846]: time reset +2.242826 s Nov 2 09:07:20 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 09:10:16 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:12:40 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 09:17:46 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:18:00 Tower ntpd[14846]: no servers reachable Nov 2 09:19:02 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:24:34 Tower ntpd[14846]: time reset +2.546777 s Nov 2 09:25:14 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 09:33:30 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:34:59 Tower ntpd[14846]: no servers reachable Nov 2 09:37:51 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 09:41:07 Tower ntpd[14846]: no servers reachable Nov 2 09:42:36 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:42:36 Tower ntpd[14846]: time reset +2.560501 s Nov 2 09:43:18 Tower ntpd[14846]: synchronized to 208.83.212.8, stratum 3 Nov 2 09:46:07 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 09:51:50 Tower ntpd[14846]: no servers reachable Nov 2 09:51:56 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:53:01 Tower ntpd[14846]: no servers reachable Nov 2 09:56:16 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 09:58:27 Tower ntpd[14846]: time reset +2.304690 s Nov 2 09:58:42 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 10:02:52 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 10:05:02 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 10:06:03 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 10:09:22 Tower ntpd[14846]: no servers reachable Nov 2 10:15:50 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 10:15:50 Tower ntpd[14846]: time reset +2.502035 s Nov 2 10:16:17 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 10:25:35 Tower ntpd[14846]: no servers reachable Nov 2 10:27:04 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 10:32:08 Tower ntpd[14846]: time reset +2.249098 s Nov 2 10:32:24 Tower ntpd[14846]: synchronized to 208.83.212.8, stratum 3 Nov 2 10:35:59 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Nov 2 10:36:37 Tower ntpd[14846]: synchronized to 207.61.229.70, stratum 3 Nov 2 10:38:09 Tower ntpd[14846]: synchronized to 209.139.209.82, stratum 2 Link to comment
lionelhutz Posted November 2, 2009 Share Posted November 2, 2009 Your motherboard clock does seem to be drifting well over 2 seconds every 5 minutes so it probably won't get any better. You could try just one time server though and see if anything changes or if it at least does fewer updates. Peter Link to comment
spinbot Posted November 2, 2009 Author Share Posted November 2, 2009 OK.. i removed the other 2 and left just: 0.ca.pool.ntp.org I'll see how that works out over the next day or so. Link to comment
purko Posted November 3, 2009 Share Posted November 3, 2009 To me it looked like one time server was out of wack with respect to the other time servers. Changing your setting to a narrower pool of servers like 0.ca.pool.ntp.org rather than pool.ntp.org is a good idea. I bet this will do it. But if it doesn't, then just try a different (narrow) pool, like 2.us.pool.ntp.org or something. Purko Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.