[Bug 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"

[Launchpad Bug Tracker]

This bug was fixed in the package ntp - 1:4.2.6.p5+dfsg-3ubuntu9

---------------
ntp (1:4.2.6.p5+dfsg-3ubuntu9) xenial; urgency=medium

  [ Cam Cope ]
  * Use a single lockfile again - instead unlock the file before starting the
    init script. The lock sho uld be shared - both services can't run at the
    same time. (LP: #1125726)

 -- Iain Lane <iain at orangesquash.org.uk>  Mon, 07 Dec 2015 13:38:16
+0000

** Changed in: ntp (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1125726

Title:
  boot-time race between /etc/network/if-up.d/ntpdate and
  "/etc/init.d/ntp start"

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  We're seeing a race between if-up.d/ntpdate and the ntp startup
  script.

  1) if-up.d/ntpdate starts.
  2) if-up.d/ntpdate acquires the lock "/var/lock/ntpdate-ifup".
  3) if-up.d/ntpdate stops the ntp service [which isn't running anyway].
  4) if-up.d/ntpdate starts running ntpdate, which bids UDP *.ntp
  5) /etc/init.d/rc 2 executes "/etc/rc2.d/S20ntp start"
  6) /etc/init.d/ntp acquires the lock "/var/lock/ntpdate".
  7) /etc/init.d/ntp starts the ntp daemon.
  8) The ntp daemon logs an error, complaining that it cannot bind UDP *.ntp.
  9) if-up.d/ntpdate now starts the ntp service.

  The result is a weird churn, though ntpd does end up running at the
  end.

  Should these not be using the same lock file?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+subscriptions