You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trigger für man-db (2.9.4-2) werden verarbeitet ...
Trigger für dbus (1.12.20-2) werden verarbeitet ...
Packages installed!
Failed to set ntp: NTP not supported
Command which failed was: " timedatectl set-ntp yes". Please try to execute it manually and attach the output to the bug report in the forum thread.
Executing the command manually also results in "Failed to set ntp: NTP not supported".
(Debian 11 latest version)
The text was updated successfully, but these errors were encountered:
This little change has removed the above-mentioned installation problem of SinusBot for me (error).
# service ntp restart --> TODO
# timedatectl set-ntp yes --> TODO
My system had already activated the "NTP service" for timedatectl, but not with using of the ntp package, rather with the systemd-timesyncd daemon itself. This is also described in more detail here.
"[...] Also, if the system is not going to be used as a time server, the ntp daemon is not recommended in recent versions of Ubuntu. Instead, systemd-timesyncd daemon should be used. [...]"
server_root: timedatectl
Local time: Sat 2024-09-28 04:31:20 CEST
Universal time: Sat 2024-09-28 02:31:20 UTC
RTC time: Sat 2024-09-28 02:31:20
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
Trigger für man-db (2.9.4-2) werden verarbeitet ...
Trigger für dbus (1.12.20-2) werden verarbeitet ...
Packages installed!
Failed to set ntp: NTP not supported
Command which failed was: " timedatectl set-ntp yes". Please try to execute it manually and attach the output to the bug report in the forum thread.
Executing the command manually also results in "Failed to set ntp: NTP not supported".
(Debian 11 latest version)
The text was updated successfully, but these errors were encountered: