[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
No, I never saw this again.
The very next day after filing this bug I had another monitoring warning
about a stale ntpd pidfile, but this time there was no second ntpd
process running, and journalctl showed a simple conflict with ntpdate
during startup.
I apt-get removed ntpdate and never saw any
Yeah this is just using a generated sytsemd unit for the sysv init file.
Never the less I wasn't able to trigger that throughout some ntp upgrades in
containers.
The bug was already inactive for very long, but I think the reason is
currently that it isn#t really actionable.
@Marius - was that a
Unfortunately there were more unattended upgrades that require a reboot
since I filed this bug, so systemd-analyze can't see what happened any
more.
As for systemd service files, I believe ntp has none. systemctl status
ntp says
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
wh
Thank you for filing this bug, it does look like a race.
We probably will need to see the systemd service files for ntp, at
least. I wonder if any of the `systemd-analyze` subcommands might be
helpful here to determine why ntpd is started twice.
** Changed in: ntp (Ubuntu)
Status: New => T
5 matches
Mail list logo
