Sep 23 13:58:24 raspberrypi systemd: Starting Network Time Synchronization. Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)ĭrop-In: /usr/lib/systemd/system/Īctive: active (running) since Thu 13:58:24 CEST 1h 22min agoĬGroup: /system.slice/rvice Inet6 fe80::f2d5:f228:3c7b:86aa/64 scope linkģ: wlan0: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 Poll interval: 1min 4s (min: 32s max 34min 8s)ġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 Running timedatectl timesync-status gives me the following result: Or maybe some overaching reasons they can't sync? Is there an alley which I have not yet tried. None of these things can get the synchronization to work.
Installed ntp and ntpdate and tried forcing the sync. Installed and enabled chrony and tried it that way (when this didn't work I purged it from the system)
Specifying the same time server that all other machines sync to within our network as the NTP server
Turning on the ntp within timedatectl with sudo timedatectl set-ntp true after which I have restarted the systemd-timedated and systemd-timesyncd services. Which is kind of crucial or this to work. However I noticed that the clocks on all of them cannot be synchronized with an NTP server. 2 raspberry pi 4 model b 4gb (due to chip shortage 2gb were no longer available)Īll of these are running the default Pi OS.I have bought three raspberry pi's with the intention of using them as temperature sensors throughout the building.
0 kommentar(er)
