[Touch-packages] [Bug 1649729] Re: ntpd startup failures under xenial

2016-12-17 Thread Matt LaPlante
Removing ntpdate should remove the if-up script, so I imagine that would
"resolve" the bug by way of workaround.

The hosts in question were upgraded from prior LTS, so they would have
inherited ntpdate from there.  I wasn't aware of the changes to sunset
it in the current release.

-- 
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/1649729

Title:
  ntpd startup failures under xenial

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  I have a system running 16.04.1 with multiple interfaces configured
  via /etc/network/interfaces.  Following a restart, ntpd will often be
  found not running, despite being installed and configured.

  syslog suggests ntpd is being repeatedly stopped and restarted within
  seconds.

  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING

  My current assumption is that this is the work of /etc/network/if-
  up.d/ntpdate being run on several interfaces nearly simultaneously.
  The rapid stop/start cycle of the daemon appears to trip up the port
  binding, and eventually cause ntpd to become unhappy and wind up
  stopped.

  Manually restarting ntpd (or even running /etc/network/if-
  up.d/ntpdate) outside of interface up/down time properly brings up
  ntpd.  It doesn't appear to be a configuration issue as such.

  Further, running  /etc/network/if-up.d/ntpdate from bash several times
  in rapid succession also produces the 'missing ntpd' behavior, outside
  of the context of any interface activity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1649729/+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


[Touch-packages] [Bug 1649729] Re: ntpd startup failures under xenial

2016-12-14 Thread Matt LaPlante
I actually think I gave a fairly thorough description of the problem and
it has nothing to do with ntpd configuration.  I even said specifically
that I can manually start/stop ntpd and it works - configuration valid
and operational.

The problem is /etc/network/if-up.d/ntpdate starting and stopping the
daemon in rapid succession when multiple interfaces come up.  This
causes binding conflicts and often ntpd will wind up down as a result.

Reproduction is fairly easy: Just run /etc/network/if-up.d/ntpdate
several times in rapid succession and see what happens.

-- 
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/1649729

Title:
  ntpd startup failures under xenial

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  I have a system running 16.04.1 with multiple interfaces configured
  via /etc/network/interfaces.  Following a restart, ntpd will often be
  found not running, despite being installed and configured.

  syslog suggests ntpd is being repeatedly stopped and restarted within
  seconds.

  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING

  My current assumption is that this is the work of /etc/network/if-
  up.d/ntpdate being run on several interfaces nearly simultaneously.
  The rapid stop/start cycle of the daemon appears to trip up the port
  binding, and eventually cause ntpd to become unhappy and wind up
  stopped.

  Manually restarting ntpd (or even running /etc/network/if-
  up.d/ntpdate) outside of interface up/down time properly brings up
  ntpd.  It doesn't appear to be a configuration issue as such.

  Further, running  /etc/network/if-up.d/ntpdate from bash several times
  in rapid succession also produces the 'missing ntpd' behavior, outside
  of the context of any interface activity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1649729/+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


[Touch-packages] [Bug 1649729] [NEW] ntpd startup failures under xenial

2016-12-13 Thread Matt LaPlante
Public bug reported:

I have a system running 16.04.1 with multiple interfaces configured via
/etc/network/interfaces.  Following a restart, ntpd will often be found
not running, despite being installed and configured.

syslog suggests ntpd is being repeatedly stopped and restarted within
seconds.

Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 UTC 
2016 (1): Starting
Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 UTC 
2016 (1): Starting
Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 UTC 
2016 (1): Starting
Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 UTC 
2016 (1): Starting
Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING
Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING

My current assumption is that this is the work of /etc/network/if-
up.d/ntpdate being run on several interfaces nearly simultaneously.  The
rapid stop/start cycle of the daemon appears to trip up the port
binding, and eventually cause ntpd to become unhappy and wind up
stopped.

Manually restarting ntpd (or even running /etc/network/if-up.d/ntpdate)
outside of interface up/down time properly brings up ntpd.  It doesn't
appear to be a configuration issue as such.

Further, running  /etc/network/if-up.d/ntpdate from bash several times
in rapid succession also produces the 'missing ntpd' behavior, outside
of the context of any interface activity.

** Affects: ntp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1649729

Title:
  ntpd startup failures under xenial

Status in ntp package in Ubuntu:
  New

Bug description:
  I have a system running 16.04.1 with multiple interfaces configured
  via /etc/network/interfaces.  Following a restart, ntpd will often be
  found not running, despite being installed and configured.

  syslog suggests ntpd is being repeatedly stopped and restarted within
  seconds.

  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :