Opened 5 years ago

Last modified 4 years ago

#13741 reopened defect

ntpd cannot start as ntpclient remains active

Reported by: mds-openwrt@… Owned by:
Priority: normal Milestone: Chaos Calmer 15.05
Component: luci Version: Trunk
Keywords: ntp, ntpclient, ntpd Cc:


Using Razvi's June 6 build of r36828 on ASUS RT-N16.

In LuCI, System/System[Time Synchronization], there is a checkbox to 'Enable NTP Client', and a contingent checkbox to 'Provide NTP server'. I checked both, as serving time is a useful thing. Separately, in LuCI:System/Startup, at priority 98 sysntpd is shown to be on. However, no ntpd process was actually running or contactable, even after a reboot. Un-checking LuCI:System/System[Time Synchronization]'Enable NTP Client' hides the 'Provide NTP server' checkbox completely, which is odd and, it transpires, unhelpful.

Evidently, in the normal course of a boot-up, ntpclient runs from ./hotplug.d/iface/20-ntpclient using parameters set through LuCI:System/Time Synchronization. (NB: this is not the same page as the above checkboxes). These parameters, as set by default, mean that ntpclient is still running when ntpd attempts to start, and, I believe, this prevents the ntpd starting (port clash?).

Currently then, after boot-up, if you want NTP as a service ntpclient has to be manually stopped and ntpd manually (re)started. This does work, but one has to remember to do it, or make alterations to the scripts in-situ, either way, working around what appears to be a bug.

I think the LuCI interfaces to ntpd/ntp-client could be usefully gathered into one page, and be more logically constructed, and that the underlying config and script-logic could be more clearly rendered as either ntpclient or ntpd, or ntpclient explicitly run, stopped and then followed by ntpd.

Attachments (0)

Change History (2)

comment:1 Changed 5 years ago by jow

  • Resolution set to wontfix
  • Status changed from new to closed

Don't use any ntpclient package, it will conflict with the builtin ntpd.

comment:2 Changed 4 years ago by anonymous

  • Resolution wontfix deleted
  • Status changed from closed to reopened

same problem but i don't wanan use any ntp client. sysntpd disabled in startup and ntpclient starts either way after restart. only way to stop it is kill the process manually each time.

basically it woulnd't be a problem if it would update once per day but it keeps connecting all the time just as described here

Add Comment

Modify Ticket

as reopened .

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

Note: See TracTickets for help on using tickets.