Hi Majal,
hrm if this is a fresh chrony install then something is really odd.
The service is expected to be started on install and that failed.
It is reported as:
Loaded: loaded (/lib/systemd/system/chrony.service; disabled; vendor preset:
enabled)
I tried in a container and a VM for me it starts fine and is not masked.
ntp/chrony/open-ntp are mutually exclusive, and systemd-timesyncd should step
back if a real ntp server is installed.
Never the less have you configured/experimented with any of the above on your
system?
Furthermore if you start the service on your own, does it work then.
$ systemctl restart chrony
If it does not is there anything in "journalctl -xef" while you do so that
might explain it?
I don't expect the above to help too much, the real puzzle is why it is
"disabled" that would be enabled on install. I even tried to disable my
service manually, then deinstall and reinstall - still working. So if
you have any extra info why it might have ended up this way in your
scenario please let me know.
** Changed in: chrony (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771101
Title:
package chrony 3.2-4ubuntu4 failed to install/upgrade: installed
chrony package post-installation script subprocess returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1771101/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
