Fehler beim Speichern von NTP-Server benutzen

strike · 21. September 2020

Hallo,

Neuinstallation von aktueller Debian Buster Netinstall mit nachträglich installiertem OMV5.

Wenn ich den NTP-Server über die WebGui speichern will bekomme ich folgende Fehlermeldung:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run chrony 2>&1' with exit code '1': OMV-Debian.fritz.box: ---------- ID: configure_chrony Function: file.managed Name: /etc/chrony/chrony.conf Result: True Comment: File /etc/chrony/chrony.conf is in the correct state Started: 22:35:33.935779 Duration: 32.21 ms Changes: ---------- ID: start_chrony_service Function: service.running Name: chrony Result: False Comment: Job for chrony.service failed because the control process exited with error code. See "systemctl status chrony.service" and "journalctl -xe" for details. Started: 22:35:33.976302 Duration: 57.598 ms Changes: Summary for OMV-Debian.fritz.box ------------ Succeeded: 1 Failed: 1 ------------ Total states run: 2 Total run time: 89.808 ms

Details:

Code

Fehler #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run chrony 2>&1' with exit code '1': OMV-Debian.fritz.box:
----------
          ID: configure_chrony
    Function: file.managed
        Name: /etc/chrony/chrony.conf
      Result: True
     Comment: File /etc/chrony/chrony.conf is in the correct state
     Started: 22:35:33.935779
    Duration: 32.21 ms
     Changes:
----------
          ID: start_chrony_service
    Function: service.running
        Name: chrony
      Result: False
     Comment: Job for chrony.service failed because the control process exited with error code.
              See "systemctl status chrony.service" and "journalctl -xe" for details.
     Started: 22:35:33.976302
    Duration: 57.598 ms
     Changes:

Summary for OMV-Debian.fritz.box
------------
Succeeded: 1
Failed:    1
------------
Total states run:     2
Total run time:  89.808 ms in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuskV...', '/tmp/bgoutput34...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Alles anzeigen

systemctl status chrony.service

Code

# systemctl status chrony.service
â chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-09-21 22:35:34 CEST; 15min ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 27303 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)

Sep 21 22:35:34 OMV-Debian.fritz.box systemd[1]: Starting chrony, an NTP client/server...
Sep 21 22:35:34 OMV-Debian.fritz.box chronyd[27303]: Could not open any command socket
Sep 21 22:35:34 OMV-Debian.fritz.box systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE
Sep 21 22:35:34 OMV-Debian.fritz.box systemd[1]: chrony.service: Failed with result 'exit-code'.
Sep 21 22:35:34 OMV-Debian.fritz.box systemd[1]: Failed to start chrony, an NTP client/server.

Alles anzeigen

Ansonsten läuft das System ohne Probleme.

Gruß,

strike

votdev · 22. September 2020

Was steht denn in der Datei /etc/chrony/chrony.conf?

strike · 22. September 2020

/etc/chrony/chrony.conf

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

server 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

Alles anzeigen

votdev · 22. September 2020

Die Konfiguration sieht gut aus. Steht sonst noch etwas im syslog? Kann leider mit Google nichts finden was den Fehler Could not open any command socket betrifft.

Kannst Du mal folgende Befehle in unterschiedlichen Terminals laufen lassen?

journalctl -f
systemctl restart chrony

strike · 22. September 2020

hier die Ausgabe von journalctl -f ab dem restart von chrony

Code

Sep 22 13:29:37 OMV-Debian.fritz.box systemd[1]: Starting chrony, an NTP client/server...
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" sock_type="dgram" protocol=0 request                                                                                                                          ed_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" sock_type="stream" protocol=0 reques                                                                                                                          ted_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" sock_type="stream" protocol=0 reques                                                                                                                          ted_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.723:16): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" soc                                                                                                                          k_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.723:17): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" soc                                                                                                                          k_type="stream" protocol=0 requested_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.723:18): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" soc                                                                                                                          k_type="stream" protocol=0 requested_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.726:19): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="inet" soc                                                                                                                          k_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.726:20): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" soc                                                                                                                          k_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.726:21): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="inet6" so                                                                                                                          ck_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.726:22): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" soc                                                                                                                          k_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box kernel: audit: type=1400 audit(1600774177.726:23): apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" soc                                                                                                                          k_type="dgram" protocol=0 requested_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="inet" sock_type="dgram" protocol=0 request                                                                                                                          ed_mask="create" denied_mask="create"
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" sock_type="dgram" protocol=0 request                                                                                                                          ed_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="inet6" sock_type="dgram" protocol=0 reques                                                                                                                          ted_mask="create" denied_mask="create"
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" sock_type="dgram" protocol=0 request                                                                                                                          ed_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box audit[25384]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/chronyd" pid=25384 comm="chronyd" family="unix" sock_type="dgram" protocol=0 request                                                                                                                          ed_mask="create" denied_mask="create" addr=none
Sep 22 13:29:37 OMV-Debian.fritz.box chronyd[25364]: Could not open any command socket
Sep 22 13:29:37 OMV-Debian.fritz.box systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE
Sep 22 13:29:37 OMV-Debian.fritz.box systemd[1]: chrony.service: Failed with result 'exit-code'.
Sep 22 13:29:37 OMV-Debian.fritz.box systemd[1]: Failed to start chrony, an NTP client/server.
Sep 22 13:29:41 OMV-Debian.fritz.box monit[609]: Filesystem '/srv/dev-disk-by-label-JD2' not mounted
Sep 22 13:29:41 OMV-Debian.fritz.box monit[609]: 'filesystem_srv_dev-disk-by-label-JD2' unable to read filesystem '/srv/dev-disk-by-label-JD2' state
Sep 22 13:29:41 OMV-Debian.fritz.box monit[609]: 'filesystem_srv_dev-disk-by-label-JD2' trying to restart
Sep 22 13:29:41 OMV-Debian.fritz.box monit[609]: 'mountpoint_srv_dev-disk-by-label-JD2' status failed (1) -- mountpoint: /srv/dev-disk-by-label-JD2: Datei oder Verzeichnis nicht gefunden
Sep 22 13:30:01 OMV-Debian.fritz.box CRON[25730]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 22 13:30:01 OMV-Debian.fritz.box CRON[25731]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 22 13:30:01 OMV-Debian.fritz.box CRON[25732]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Sep 22 13:30:01 OMV-Debian.fritz.box CRON[25733]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
Sep 22 13:30:01 OMV-Debian.fritz.box CRON[25731]: pam_unix(cron:session): session closed for user root
Sep 22 13:30:02 OMV-Debian.fritz.box CRON[25730]: pam_unix(cron:session): session closed for user root
Sep 22 13:30:11 OMV-Debian.fritz.box monit[609]: Filesystem '/srv/dev-disk-by-label-JD2' not mounted
Sep 22 13:30:11 OMV-Debian.fritz.box monit[609]: 'filesystem_srv_dev-disk-by-label-JD2' unable to read filesystem '/srv/dev-disk-by-label-JD2' state
Sep 22 13:30:11 OMV-Debian.fritz.box monit[609]: 'filesystem_srv_dev-disk-by-label-JD2' trying to restart
Sep 22 13:30:11 OMV-Debian.fritz.box monit[609]: 'mountpoint_srv_dev-disk-by-label-JD2' status failed (1) -- mountpoint: /srv/dev-disk-by-label-JD2: Datei oder Verzeichnis nicht gefunden

Alles anzeigen

strike · 22. September 2020

hier noch die Ausgabe von journalctl -f ab dem restart von chrony auf einem zweitem System. Hier ist alles IO.

Code

Sep 22 14:30:53 OMV5-Buster chronyd[580]: chronyd exiting
Sep 22 14:30:53 OMV5-Buster systemd[1]: Stopping chrony, an NTP client/server...
Sep 22 14:30:53 OMV5-Buster systemd[1]: chrony.service: Succeeded.
Sep 22 14:30:53 OMV5-Buster systemd[1]: Stopped chrony, an NTP client/server.
Sep 22 14:30:53 OMV5-Buster systemd[1]: Starting chrony, an NTP client/server...
Sep 22 14:30:53 OMV5-Buster chronyd[12030]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)
Sep 22 14:30:53 OMV5-Buster chronyd[12030]: Frequency -4.727 +/- 0.074 ppm read from /var/lib/chrony/chrony.drift
Sep 22 14:30:53 OMV5-Buster chronyd[12030]: Loaded seccomp filter
Sep 22 14:30:53 OMV5-Buster systemd[1]: Started chrony, an NTP client/server.
Sep 22 14:30:57 OMV5-Buster chronyd[12030]: Selected source 131.188.3.220

Das erste System habe ich mit Debian on Top installiert. Bei diesem funktioniert chrony nicht.

uname -a

Linux OMV-Debian.fritz.box 5.4.60-1-pve #1 SMP PVE 5.4.60-2 (Fri, 04 Sep 2020 10:24:50 +0200) x86_64 GNU/Linux

Das zweite System habe ich mit dem ISO installiert. Bei diesem ist alles IO.

uname -a

Linux OMV5-Buster 5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) x86_64 GNU/Linux

Wieso werden hier unterschiedliche Kernel verwendet?

Wobei, das dürfte aber nichts mit dem chrony Problem haben.

votdev · 22. September 2020

Das Problem ist AppAmor auf einem original Debian, OMV installiert dieses Paket nicht. Du solltest mal https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888038 anschauen. Wenn Du es ans laufen gebracht hast wäre es nett dies hier zu posten damit wir es in OMV einbauen können.

strike · 22. September 2020

Sytem 1 Debian onTop:

Code

 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  [Installiert,automatisch]
libapparmor1/stable,now 2.13.2-10 amd64  [installiert]

System 2 OMV5 vom ISO

Code

apt list --installed | grep apparmor

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libapparmor1/stable,now 2.13.2-10 amd64  [installiert]

Es ist demnach auf beiden Systeme die gleiche Version von Apparmor installiert.

Wenn ich diesem Link folge, ist demnach der Bug seit Oct. 2018 behoben.

Debian Bug report logs - #871441

Code

Date: Sun, 21 Oct 2018 10:19:30 +0000

Source: apparmor
Source-Version: 2.13.1-1

We believe that the bug you reported is fixed in the latest version of
apparmor, which is due to be installed in the Debian FTP archive.

votdev · 22. September 2020

OMV installiert durch Abhängigkeiten nur die AppArmor Libraries, nicht aber den Service. Dass der Bug behoben ist hab ich auch gesehen, dennoch scheint mit der AppArmor Konfiguration für chrony etwas nicht zu stimmen. Mir scheint das Problem aber nur auf Dein System bezogen zu sein, da hier ansonsten öfters und schon vor langer Zeit solche Fehlermeldungen gemeldet gemeldet worden wären.

strike · 22. September 2020

Zitat

Mir scheint das Problem aber nur auf Dein System bezogen zu sein, da hier ansonsten öfters und schon vor langer Zeit solche Fehlermeldungen gemeldet gemeldet worden wären.

Genau, das denke ich auch. Sonst wären schon mehrere Fehlermeldungen in letzter Zeit gemeldet worden.

Ich werde ggf. noch mal neu aufsetzen, Geht ja relativ flott.

Danke noch mal.

techtom · 23. Januar 2022

habe das gleich Problem nach upgrade von OMV 4 auf 5

Debian GNU/Linux, mit Linux 5.4.162-1-pve und ZFS

gleiches Problem wie hier

ist ein Upgrade auf 6.x sinnvoll ?

Jetzt mitmachen!