Date: Sun, 10 Sep 2017 13:58:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 222197] sysutils/py-google-compute-engine starts google_clock_skew_daemon too early Message-ID: <bug-222197-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222197 Bug ID: 222197 Summary: sysutils/py-google-compute-engine starts google_clock_skew_daemon too early Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: vivek@khera.org CC: helen.koike@collabora.com CC: helen.koike@collabora.com Flags: maintainer-feedback?(helen.koike@collabora.com) The clock skew daemon interferes with ntpd upon startup. On boot, the following is observed: Starting sshd. Performing sanity check on sshd configuration. Starting google_network_setup. Starting google_ip_forwarding_daemon. Starting google_clock_skew_daemon. Starting google_accounts_daemon. ntpd is not running. No core dumps found. Clearing /tmp (X related). Updating motd:. Mounting late filesystems:. Starting ntpd. Sep 8 20:17:20 yertle ntpd[697]: unable to bind to wildcard address :: - another process may be running - EXITING What happens is that the clock skew daemon starts and does not see ntpd running. It then proceeds to set the time using ntpdate. By luck of timing,= it does so at the precise moment that ntpd wants to start, causing that to fai= l. Subsequently, since ntpd was not discovered by the daemon it is not restart= ed, and the system time drifts without ntpd to keep it in check. Once the system is running, if you stop the clock skew daemon, start ntpd, = then re-start the clock skew daemon, you will observe it stop and restart ntpd. = If you stop ntpd, and restart the clock skew daemon, you will observe the "ntp= d is not running." message, and ntpd is not started. It seems to me that ntpd should come before the clock skew daemon in the startup order. The documentation implies that the daemon only does work on startup or migrate, so it is necessary for migration and ntpd is necessary = for the rest of the time. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222197-13>