Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to set ntp: NTP not supported #91

Open
bnt4 opened this issue May 26, 2022 · 1 comment
Open

Failed to set ntp: NTP not supported #91

bnt4 opened this issue May 26, 2022 · 1 comment

Comments

@bnt4
Copy link

bnt4 commented May 26, 2022

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)

@RedstoneFuture
Copy link

RedstoneFuture commented Sep 28, 2024

Hello.

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

Tested with Debian 12.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants