March 16, 201016 yr Anyone know why I got this time sync very very often ? One example.... Mar 16 18:33:39 Tower ntpd[1398]: synchronized to 192.121.13.5, stratum 2 Mar 16 18:43:22 Tower ntpd[1398]: time reset +1.801618 s Mar 16 18:44:14 Tower ntpd[1398]: synchronized to 192.121.13.5, stratum 2 Mar 16 18:58:04 Tower kernel: mdcmd (214): spindown 0 Mar 16 18:59:55 Tower kernel: mdcmd (231): spindown 1 Mar 16 18:59:56 Tower kernel: mdcmd (232): spindown 2 Mar 16 19:00:07 Tower kernel: mdcmd (234): spindown 3 Mar 16 19:00:09 Tower kernel: mdcmd (235): spindown 4 Mar 16 19:00:17 Tower ntpd[1398]: time reset +1.801960 s Mar 16 19:00:21 Tower kernel: mdcmd (237): spindown 5 Mar 16 19:00:22 Tower kernel: mdcmd (238): spindown 6 Mar 16 19:00:22 Tower kernel: mdcmd (239): spindown 7 Mar 16 19:01:29 Tower ntpd[1398]: synchronized to 192.121.13.5, stratum 2 Se my hardware below
March 16, 201016 yr Anyone know why I got this time sync very very often ? I'm not sure. Ntpd can vary its synch intervals greatly, down to even 10 min apart. But since ntpd is pretty much set it and forget it, I've disabled its logging into my syslog.
March 16, 201016 yr Anyone know why I got this time sync very very often ? But since ntpd is pretty much set it and forget it, I've disabled its logging into my syslog. How did you disable the logging to the syslog. I would LOVE to do that as my syslog tends to fill with the messages about syncing which I could care less about.
March 16, 201016 yr Anyone know why I got this time sync very very often ? But since ntpd is pretty much set it and forget it, I've disabled its logging into my syslog. How did you disable the logging to the syslog. I would LOVE to do that as my syslog tends to fill with the messages about syncing which I could care less about. Simple. Just add the following lines to your 'go' script: # Disable all the annoying messages from ntpd in syslog echo "logfile /dev/null" >> /etc/ntp.conf- /etc/rc.d/rc.ntpd restart ...and you'll never hear from it again.
March 16, 201016 yr Simple. Just add the following lines to your 'go' script: # Disable all the annoying messages from ntpd in syslog echo "logfile /dev/null" >> /etc/ntp.conf- /etc/rc.d/rc.ntpd restart ...and you'll never hear from it again. Thanks you much!! Bookmarked so I can "fix" mine when I get home.
March 16, 201016 yr Anyone know why I got this time sync very very often ? One example.... Mar 16 18:33:39 Tower ntpd[1398]: synchronized to 192.121.13.5, stratum 2 Mar 16 18:43:22 Tower ntpd[1398]: time reset +1.801618 s Mar 16 18:44:14 Tower ntpd[1398]: synchronized to 192.121.13.5, stratum 2 Mar 16 18:58:04 Tower kernel: mdcmd (214): spindown 0 Mar 16 18:59:55 Tower kernel: mdcmd (231): spindown 1 Mar 16 18:59:56 Tower kernel: mdcmd (232): spindown 2 Mar 16 19:00:07 Tower kernel: mdcmd (234): spindown 3 Mar 16 19:00:09 Tower kernel: mdcmd (235): spindown 4 Mar 16 19:00:17 Tower ntpd[1398]: time reset +1.801960 s Mar 16 19:00:21 Tower kernel: mdcmd (237): spindown 5 Mar 16 19:00:22 Tower kernel: mdcmd (238): spindown 6 Mar 16 19:00:22 Tower kernel: mdcmd (239): spindown 7 Mar 16 19:01:29 Tower ntpd[1398]: synchronized to 192.121.13.5, stratum 2 Se my hardware below Yes, the clock on your motherboard is constantly losing time. It looks like it lost 1.8 second in 15 minutes.
March 16, 201016 yr Author Yes, when googling it I found some issue in the kernel for my HW, but I'm not sure, but loot of people do have the same problem with the same MB I have:-( EDIT And remove the logs from the log file doesn't help to solve the problem
March 16, 201016 yr And remove the logs from the log file doesn't help to solve the problem A problem you don't see is not really a problem. On my box I once saw it synching like 10 minutes apart, then some time later, it was down to once a day. So as long it keeps the time correct -- and it does -- I don't really care about how it's doing it.
March 16, 201016 yr Author Yes you have a point perhaps I should disable all my loggs, and I should not have any problems at all Just kidding, so the time problem are not a issue then
March 16, 201016 yr so the time problem are not a issue then It would be an issue if you see an issue, for example if the time on your server was incorrect.
March 16, 201016 yr I honestly do not care about seeing the ntpd log entries to know that it is working. I have an issue with mine updating alot, even after I have replaced the motherboard battery. I just wanted a way to remove it so it would not fill my syslog with needless crap.
Archived
This topic is now archived and is closed to further replies.