My Almalinux VM runs on Virtualbox, and works like a charm. The hardware I’m using is a Thinkbook with awesome gaming specs. I don’t want to deal with games that don’t run on Linux, so I choose Windows.
I woke up with Chrony issues on Alma today, so I wasn’t able to browse the net (Read this):
$ systemctl status chronyd
● chronyd.service – NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-04-06 23:47:31 CEST; 13h ago
Docs: man:chronyd(8)
man:chrony.conf(5)
Main PID: 837 (chronyd)
Tasks: 1 (limit: 67703)
Memory: 3.7M
CPU: 168ms
CGroup: /system.slice/chronyd.service
└─837 /usr/sbin/chronyd -F 2
Apr 06 23:47:40 10.0.2.15 chronyd[837]: System clock was stepped by 1.798667 seconds
Apr 06 23:47:40 10.0.2.15 chronyd[837]: System clock TAI offset set to 37 seconds
Apr 07 01:16:24 10.0.2.15 chronyd[837]: Selected source 185.216.161.42 (2.almalinux.pool.ntp.org)
Apr 07 01:17:29 10.0.2.15 chronyd[837]: Source 83.137.149.135 replaced with 164.92.216.152 (2.almalinux.pool.ntp.org)
Apr 07 01:23:31 10.0.2.15 chronyd[837]: Selected source 164.92.216.152 (2.almalinux.pool.ntp.org)
Apr 07 01:23:31 10.0.2.15 chronyd[837]: System clock wrong by 40468.187955 seconds
But fixed it with $ sudo chronyc -a makestep
Leave a Reply