This bug was fixed in the package chrony - 4.5-1ubuntu4
---
chrony (4.5-1ubuntu4) noble; urgency=medium
* d/usr.sbin.chronyd: Fix failure to start timemaster due to lack
of rw permissions on chrony socket.
(LP: #2032805)
* d/usr.sbin.chronyd: Allow the default UNIX domain
This bug was fixed in the package linuxptp - 4.0-1ubuntu1
---
linuxptp (4.0-1ubuntu1) noble; urgency=medium
* d/timemaster.conf: Fix path to chrony.conf.
(LP: #2032805)
-- Bryce Harrington Mon, 01 Apr 2024 18:42:08
-0700
** Changed in: linuxptp (Ubuntu)
Status: In
Hi Patrik, thanks for the quick response on the testing!
I've proceeded with uploading these fixes to both chrony and linuxptp
for noble. They're in the unapproved queue currently, as things are
frozen for beta release, but hopefully should go in post-beta and be
included in the final LTS
Bryce, your fixes work fine in my VM. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open socket /var/run/timemaster/chrony.SOCK0
To manage notifications about this
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open socket /var/run/timemaster/chrony.SOCK0
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/linuxptp/+git/linuxptp/+merge/463460
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/chrony/+git/chrony/+merge/463455
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open socket
Hi Patrik,
I've packaged up the fixes Christian suggested and posted to this PPA:
https://launchpad.net/~bryce/+archive/ubuntu/chrony-fix-lp2032805
Once the packages have finished building, I would appreciate it if you
could verify this fixes the issues you've encountered, if you're able to
** Changed in: chrony (Ubuntu)
Status: Triaged => In Progress
** Changed in: linuxptp (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Agreed with Christian's suggested changes to fix in noble, and worth
prioritizing for getting in before final freeze.
It sounds like an SRU at least for mantic would be appropriate, however
I wonder if the fix should be limited to just what is directly
reproducible for this specific issue. But
I corrected /etc/chrony/chrony.conf in timemaster.conf years ago but
forgot to file a bug. It is still needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open socket
While the above is needed to change chrony, I further found that
timemaster also has an issue in the default config.
debian/timemaster.conf:14:[chrony.conf]
debian/timemaster.conf:15:include /etc/chrony.conf
That causes the default to behave like:
Mar 22 07:03:49 n chronyd[50428]: Fatal error :
Thanks for the ping on this @ahresse !
Yes, this should be very similar to thew old fix in bug 1771028
It is essentially yet another "chrony works with something else" use case.
There is a section for that in the chrony apparmor rules and we should indeed
add the known default paths (like this)
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032805
Title:
Could not open socket /var/run/timemaster/chrony.SOCK0
To
14 matches
Mail list logo
