ClearOS Bug Tracker

Main | My View | View Issues | Change Log | Roadmap | Repositories
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001378ClearOSapp-ntp - NTP Serverpublic2013-10-15 17:592013-12-03 09:17
Reporterbchambers 
Assigned Tobchambers 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version6.5.0 Beta 2 
Target Version6.5.0 Beta 2Fixed in Version6.5.0 Beta 2 
Summary0001378: Server clock drifts
DescriptionWith NTP service running (as per webconfig NTP page), server clock was off by 10 minutes.

Running 'timesync' manually, shows in system log:

Oct 15 19:46:55 chambers timesync: synchronizing skipped (NTP server running)
Oct 15 19:46:55 chambers timesync: synchronizing hardware clock

Stopping NTP service and running 'timesync' again, shows this in 'messages' log:

Oct 15 19:42:55 chambers ntpd[29106]: ntpd 4.2.4p8@1.1612-o Thu Feb 21 21:12:26 UTC 2013 (1)
Oct 15 19:42:55 chambers ntpd[29106]: precision = 0.125 usec
Oct 15 19:42:55 chambers ntpd[29106]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Oct 15 19:42:55 chambers ntpd[29106]: Listening on interface 0000001 wildcard, ::#123 Disabled
Oct 15 19:42:55 chambers ntpd[29106]: Listening on interface 0000002 lo, 127.0.0.1#123 Enabled
Oct 15 19:42:55 chambers ntpd[29106]: Listening on interface 0000003 eth1, 192.168.71.1#123 Enabled
Oct 15 19:42:55 chambers ntpd[29106]: Listening on interface 0000004 tun0, 10.8.0.1#123 Enabled
Oct 15 19:42:55 chambers ntpd[29106]: Listening on interface 0000005 ppp0, 67.55.9.17#123 Enabled
Oct 15 19:42:55 chambers ntpd[29106]: Listening on routing socket on fd 0000022 for interface updates
Oct 15 19:42:55 chambers ntpd[29106]: kernel time sync status 2040
Oct 15 19:42:55 chambers ntpd[29106]: frequency initialized 0.000 PPM from /var/lib/ntp/drift
Oct 15 19:43:15 chambers ntpd[29106]: no reply; clock not set

Running 'date' show clock is still 10 minutes off.

WTF?

TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0001043)
dloper (administrator)
2013-10-15 18:17

 As with DNS, ClearOS is best suited to be a caching server. We cannot reliably state that all user hardware will have sufficient clocks. As an NTP server, the ClearOS server should also reference a trusted upstream server. This can be any regular NTP server and MUST be the AD server in the case of the Active Directory Connector.
(0001044)
user2
2013-10-15 18:29

 > Oct 15 19:43:15 chambers ntpd[29106]: no reply; clock not set

The time server can't contact the upstream time servers (time1/2/3/4.clearsdn.com). Network? DNS?
(0001046)
bchambers (administrator)
2013-10-16 11:01

 Fix explained here:

http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,28/func,view/id,2738/limit,10/limitstart,30/#56602 [^]
(0001062)
bchambers (administrator)
2013-10-23 19:16

 Source Code Changelog
---------------------------------------------------
- Added req'd firewall rule [fixed tracker 0001378]

File Changes
---------------------------------------------------
Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=6606 [^]
U webconfig/apps/ntp/trunk/deploy/info.php
A webconfig/apps/ntp/trunk/packaging/10-ntp
U webconfig/apps/ntp/trunk/packaging/app-ntp.spec

- Issue History
Date Modified Username Field Change
2013-10-15 17:59 bchambers New Issue
2013-10-15 18:17 dloper Note Added: 0001043
2013-10-15 18:29 user2 Note Added: 0001044
2013-10-16 11:01 bchambers Note Added: 0001046
2013-10-16 11:01 bchambers Assigned To => bchambers
2013-10-16 11:01 bchambers Status new => assigned
2013-10-23 19:16 bchambers Checkin
2013-10-23 19:16 bchambers Note Added: 0001062
2013-10-23 19:16 bchambers Status assigned => resolved
2013-10-23 19:16 bchambers Resolution open => fixed
2013-12-03 09:16 user2 Category app-date - Date and Time => app-ntp - NTP Server
2013-12-03 09:17 user2 Status resolved => closed
2013-12-03 09:17 user2 Fixed in Version => 6.5.0 Beta 2