Hallo,
mit dem PVE Kernel 5.4.78-2 startet leider keine chronyd mehr, mit dem original Kernel hingegen schon. Meine OVM ist direkt auf Debian 10 aufgesetzt worden.
Process: 1241 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
Was kann ich hier tun?
hi, i appear to have a similar problem.
i have replicated this on two systems, one a supermicro x9 machine and one a proxmox VM, both in UEFI mode. both were installed from debian buster netinst in the last week or so.
reading though Fehler beim Speichern von NTP-Server benutzen - General - openmediavault it appears this shouldn't be a problem? but i can't run chrony on my systems. halp
# cat /proc/version
Linux version 5.4.106-1-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.106-1 (Fri, 19 Mar 2021 11:08:47 +0100)# systemctl status chrony.service
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2021-05-13 10:48:32 NZST; 37s ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 1737 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
May 13 10:48:32 openmediavault systemd[1]: Starting chrony, an NTP client/server...
May 13 10:48:32 openmediavault chronyd[1737]: Could not open any command socket
May 13 10:48:32 openmediavault systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE
May 13 10:48:32 openmediavault systemd[1]: chrony.service: Failed with result 'exit-code'.
May 13 10:48:32 openmediavault systemd[1]: Failed to start chrony, an NTP client/server.# cat/etc/chrony/chrony.conf
bash: cat/etc/chrony/chrony.conf: No such file or directory
root@openmediavault:~# cat /etc/chrony/chrony.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
server nz.pool.ntp.org iburst
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
# Uncomment the following line to turn logging on.
#log tracking measurements statistics
# Log files location.
logdir /var/log/chrony
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
# This directive tells 'chronyd' to parse the 'adjtime' file to find out if the
# real-time clock keeps local time or UTC. It overrides the 'rtconutc' directive.
hwclockfile /etc/adjtime
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3# apt list --installed | grep apparmor
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
apparmor/stable,now 2.13.2-10 amd64 [installed,automatic]
libapparmor1/stable,now 2.13.2-10 amd64 [installed]systemctl -f output while executing systemctl restart chrony
May 13 11:02:11 openmediavault systemd[1]: Starting chrony, an NTP client/server...
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.565:18): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.565:19): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.565:20): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="inet" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="inet6" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault audit[2647]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault chronyd[2639]: Could not open any command socket
May 13 11:02:11 openmediavault systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE
May 13 11:02:11 openmediavault systemd[1]: chrony.service: Failed with result 'exit-code'.
May 13 11:02:11 openmediavault systemd[1]: Failed to start chrony, an NTP client/server.
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.571:21): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="inet" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.571:22): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.571:23): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="inet6" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.571:24): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
May 13 11:02:11 openmediavault kernel: audit: type=1400 audit(1620860531.571:25): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=2647 comm="chronyd" family="unix" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=noneworking on the VM (which is my test machine)
i had some updates to run, ran those and rebooted. no change, chrony still fails with same errors
apt remove apparmor -y
reboot
chrony now starts. if i read the other article correctly omv doesn't install apparmor typically so maybe it should be removed as part of the OMV install script?
or maybe i messed up; during debian install i left "ssh server" and "standard system utilities" enabled on tasksel. perhaps apparmor is installed as part of standard system utilities, and that isn't what you mean on the OMV on debian page by a "minimal install"?
if i'm on the right track, what else might i have screwed up by leaving standard system utilities enabled? should i reinstall?
i wonder if disabling apparmor is better ala AppArmor/HowToUse - Debian Wiki
not sure there's any benefit to doing one vs the other...keen for advice, thanks!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!