We don't have a clear reproducer for the issue, and we don't know what
makes the boot ordering different on your system. So even though you
provided the requested information, the bug is still incomplete because
we don't have enough information to act on it, and we don't know at this
time what
Do you have any kind of override file for timesyncd and/or chrony (it
could be named anything with a .conf extension) in the directories under
/etc/systemd/system? If yes, could you please show its contents?
--
You received this bug notification because you are a member of Ubuntu
Server, which
For reference,
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1764357 has a lot
of history behind these decisions
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
https://bugs.launchpad.net/bugs/1779621
Title:
Yeah, it looks fine. I don't know what is going on. Our chrony expert is
on holidays and will be back only in a week or so, maybe he can look at
it the. Unless I can reproduce this problem, I cannot make progress at
this time I'm afraid.
--
You received this bug notification because you are a
Ok, could you please attach these files:
/lib/systemd/system/chrony.service
/lib/systemd/system/systemd-timesyncd.service
And if there are equivalent ones in /etc/systemd, those too. They could
be overriding settings from the ones in /lib.
You might want to run this to find them:
find
[79657.110021] coulson chronyd[23591]: chronyd version 3.2 starting
(+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND
+ASYNCDNS +IPV6 -DEBUG)
if 79657 is seconds since reboot, how come it is so high if you just
rebooted? Didn't you mean to use | tail instead of head?
--
You
After a reboot where chrony isn't running, can you run these commands
and show their outputs:
sudo systemd-analyze critical-path
sudo journalctl -o short-monotonic -u systemd-timesyncd.service -u
chrony.service
I'll do the same in my vm where chrony is working and let's compare
notes.
--
You
I believe so.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
https://bugs.launchpad.net/bugs/1779621
Title:
chrony exits unexpectedly
To manage notifications about this bug go to:
My previous statement was incorrect when I said that chrony would be
disabled if timesyncd was installed, sorry. I seem to have
misinterpreted the conflicts line.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
Well, that is what happens actually, at least in my vm.
When I don't have chrony installed, timesyncd is running:
root@bionic-chrony:~# systemctl status systemd-timesyncd chronyd
Unit chronyd.service could not be found.
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded
But then it should happen at every reboot, unrelated to your suspends.
Is that the case?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
https://bugs.launchpad.net/bugs/1779621
Title:
chrony exits unexpectedly
To
Note it will not start if any of these other services are there:
Conflicts=systemd-timesyncd.service openntpd.service ntp.service
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
https://bugs.launchpad.net/bugs/1779621
I did an experiment with a bionic VM, where I installed chronyd and
removed the "makestep" line. I then paused the VM and let it be for a
while. About an hour later I unpaused it, and the clock was of course
off. I rebooted it, and it came back up just fine with chronyd running
and the clock
Can you show the resulting /etc/chrony/chrony.conf file?
Also, my puppet-foo is rusty, but doesn't this mean all 3 packages will
be installed alongside chrony:
package {"chrony":
ensure => present,
require => Package['openntpd', 'ntpdate', 'ntp'],
}
--
You received this bug
If you have disabled stepping, maybe chrony gives up trying to adjust
the clock when you come back from suspend and the clock is incorrect.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
While I try to reproduce this, could you please attach the custom config
you said you have for chronyd, and where it is located exactly? systemd
overrides, config file, etc
** Changed in: chrony (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
16 matches
Mail list logo
