Opened 9 years ago

Closed 8 years ago

#19 closed defect (fixed)

NTP daemon fail in sync time

Reported by: linux571 Owned by: amain
Priority: minor Milestone: milestone:
Component: debian/rootfs Version: 2.0
Severity: severity 4 Keywords: ntp time


When system boot NTP daemon start but the time is not synced at all.

I need to stop ntp daemon and run manually "ntpdate".

At this time I run "ntpdate" with S02 priority (NOTE: before S23ntp) in rc2.d but this is a bad workaround.
This "solution" won't work if you use DHCP to get internet connection.

Attachments (0)

Change History (5)

comment:1 Changed 9 years ago by amain

  • Status changed from new to accepted

comment:2 Changed 9 years ago by amain

ntpd will refuse to update the time, if the difference between sync time and local clock time is to big. It will then slowly start to sync the time. Not a once. So before ntpd is start, we should do an ntpdate <ip>.

comment:3 Changed 9 years ago by stappers


in the proper startup file, wild guess: /etc/rc1.d/S15becauseNOhardwareClock

comment:4 Changed 8 years ago by amain

  • Severity set to severity 4

At least in Debian squeeze (6.0.3) ntpdate if called whenever a network interface comes up (see /etc/network/if-up.d/ntpdate).

When using openntp instead of default ntp the daemon is started by DebWrt with an option(/etc/default/openntpd) which sets the time regardless of the difference between ntp time and system clock time. Openntp is available in sqeeze backports.

ntp is run using -g allowing any difference between ntp time and system clock time.

Tested on RSPro and as soon as WAN connection comes up, the clock is set from 1970 to current time.

I can imagine that the Debian way of syncing is not covering all situations. In these situation unfortunately manual intervention will be needed.

comment:5 Changed 8 years ago by amain

  • Resolution set to fixed
  • Status changed from accepted to closed

Add Comment

Modify Ticket

as closed The owner will remain amain.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.