[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ntp (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1632575

Title:
  systemd starts two copies of ntp at boot time

Status in ntp package in Ubuntu:
  Expired

Bug description:
  My system monitoring check noticed a stale /var/run/ntpd.pid pidfile
  on a xenial machine that rebooted at 2 AM after unattended upgrades.
  ntpd itself was running, but with a different pid.

  Digging through journalctl I can see

      Oct 12 02:00:11 xenial64 ntp[681]:  * Starting NTP server ntpd
      Oct 12 02:00:11 xenial64 systemd[1]: Started Getty on tty1.
      Oct 12 02:00:11 xenial64 systemd[1]: Reached target Login Prompts.
      Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
      Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
      Oct 12 02:00:11 xenial64 run-parts[760]: run-parts: executing 
/etc/redis/redis-server.post-up.d/00_example
      Oct 12 02:00:11 xenial64 systemd[1]: Starting LSB: Start NTP daemon...
      Oct 12 02:00:11 xenial64 ntpd[719]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
      Oct 12 02:00:11 xenial64 ntpd[719]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
      Oct 12 02:00:11 xenial64 ntp[770]:  * Starting NTP server ntpd
      Oct 12 02:00:11 xenial64 ntpd[778]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
      Oct 12 02:00:11 xenial64 ntpd[778]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
      Oct 12 02:00:11 xenial64 ntp[770]:    ...done.
      Oct 12 02:00:11 xenial64 systemd[1]: Started LSB: Start NTP daemon.
      Oct 12 02:00:11 xenial64 systemd[1]: Started Advanced key-value store.
      Oct 12 02:00:11 xenial64 ntpd[773]: proto: precision = 0.077 usec (-24)
      Oct 12 02:00:11 xenial64 ntpd[780]: proto: precision = 0.076 usec (-24)
      Oct 12 02:00:11 xenial64 ntpd[780]: unable to bind to wildcard address :: 
- another process may be running - EXITING
      Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 0 v6wildcard 
[::]:123
      Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 1 v4wildcard 
0.0.0.0:123

  As you can see, for some reason systemd starts ntpd twice, so there's
  a race to take over the socket, and a race to take over the pidfile.
  ntpd[773] gets the socket, ntpd[780] gets the pidfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 12 06:18:29 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
         Users in the 'systemd-journal' group can see all messages. Pass -q to
         turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to