Public bug reported:
>From logs:
chronyd[3443]: Could not change ownership of /run/chrony : Operation not
permitted
chronyd[3443]: Could not access /run/chrony : No such file or directory
chronyd[3443]: Disabled command socket /run/chrony/chronyd.sock
Not sure if this is critical, but it should be checked.
Per chronyc this is for:
There are two ways chronyc can access chronyd. One is the Internet Protocol
(IPv4 or IPv6) and the other is a Unix domain socket, which
is accessible locally by the root or chrony user. By default, chronyc first
tries to connect to the Unix domain socket. The compiled-in
default path is /run/chrony/chronyd.sock. If that fails (e.g. because chronyc
is running under a non-root user), it will try to connect
to 127.0.0.1 and then ::1.
Some commands are ONLY allowed via the socket connection OR if allowed per
"cmdallow" so this should be important.
** Affects: chrony (Ubuntu)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746444
Title:
/run/chrony missing?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746444/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
