Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Il giorno Mon, 11 Nov 2019 15:39:58 +0900 Maxim Cournoyer ha scritto: > Hello Matias, Hello! > [...] > > The most likely reason to see this message (and have a wrong system > date) is that your hardware clock is wrong. This shouldn't be an > issue anymore on recent Guix, but older Guix NTP service > configuration used to refuse to update your clock if there was a > discrepancy of more than 3600 s between your hardware clock and the > system clock (the one sync'd with the NTP server). > > So, either: > > 1. Update your hardware clock > 2. Use a recent Guix, and let some time for the NTP service to sync > your clock. > > As an alternative to 2, you could set the "allow-large-adjustment?" > field of your NTP configuration to #t manually (that's what Guix does > by default since commit 08b4a10fa6b). > > HTH! > > Maxim I confirm, as also Leo suggested, simply updating and reconfiguring the system with root, made the system fly back to present :). Thanks to all! Cheers, Matias pgpmjjQwmYMQb.pgp Description: Firma digitale OpenPGP
Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Hello Matias, Matias Jose Seco Baccanelli writes: > On Fri, 1 Nov 2019 22:13:11 +0100 > Matias Jose Seco Baccanelli wrote: > >> Benvenuti Guixers, >> i wanted to share a time riddle which i'm unable to solve. >> Actually my timezone is aligned to : >> (timezone "Europe/Rome") >> >> Yet, system time is 1h 20m behind the official one >> ~$ date >> ven 1 nov 2019, 21.49.30, CET >> (23.09 at the time of writing) >> >> My system was installed with the graphical installer, guix version >> 1.0.1, Mate DE. >> > [...] > > Salve! > In addition to previous information, i wanted to ask if it would be > possible to solve the time synchronization by installing further > software. > > Actually my scm declares ntp service through %desktop-service > variable. Should i add other properties ? > [...] The most likely reason to see this message (and have a wrong system date) is that your hardware clock is wrong. This shouldn't be an issue anymore on recent Guix, but older Guix NTP service configuration used to refuse to update your clock if there was a discrepancy of more than 3600 s between your hardware clock and the system clock (the one sync'd with the NTP server). So, either: 1. Update your hardware clock 2. Use a recent Guix, and let some time for the NTP service to sync your clock. As an alternative to 2, you could set the "allow-large-adjustment?" field of your NTP configuration to #t manually (that's what Guix does by default since commit 08b4a10fa6b). HTH! Maxim
Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Eccomi! On Sun, 3 Nov 2019 15:23:01 -0500 Leo Famulari wrote: > > Hm... I'm not sure but I have a guess. > > By default, ntpd will not change your clock if it is very wrong. If it > is only a couple minutes wrong, then ntpd will slowly adjust the time, > but if it is wrong by some large threshold, ntpd will simply give up. > > However, you can run ntpd with '-g, --panicgate', which will allow > ntpd to make big adjustments to your clock. In Guix, this is called > 'allow-large-adjustment?' and we made it the default in September > 2019. [1] I tried launching ntpd with root adding the specified options, but it actually returns the following issue: ntpd[1162]: Command line: ntpd -g --panicgate ntpd[1164]: proto: precision = 1.746 usec (-19) ntpd[1164]: getconfig: Couldn't open : No such file or directory ntpd[1164]: unable to bind to wildcard address :: - another process may be running - EXITING couldn't simply kill the running process since it would respawn instantly. > Maybe your system has not been updated since then? As root, can you > check with `guix describe` and let us know exactly what it says? Indeed i didn't update root's profile since this system's installation back on Jul 22! Generation 1Jul 22 2019 19:17:54 file name: /var/guix/profiles/system-1-link canonical file name: /gnu/store/8ls7mlpn7vx2szd7ayy8isryjnfkab3w-system label: GNU with Linux-Libre 5.1.2 bootloader: grub root device: UUID: 9b3e267c-cb01-4121-a7d1-9d5b60a2e5cf kernel: /gnu/store/mmnl20fg05w8gzzsp4d8dvagmdn1vjil-linux-libre-5.1.2/bzImage Generation 2Nov 04 2019 14:38:46(current) file name: /var/guix/profiles/system-2-link canonical file name: /gnu/store/l4xssjf25si0zkfwqmp3lir2a4x8zjh0-system label: GNU with Linux-Libre 5.3.8 bootloader: grub root device: UUID: 9b3e267c-cb01-4121-a7d1-9d5b60a2e5cf kernel: /gnu/store/9l8z8k5ya6g9vwzn1jcba9qdlfhf6xhd-linux-libre-5.3.8/bzImage I imagine reason why pull generations only shows the last one: Generation 1Nov 04 2019 10:17:44(current) guix d258d9c repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: d258d9c7d222e6b64531c14293f41bd8d62ea4f7 > If that's the root cause, try doing, as root, `guix pull && guix > system reconfigure [...] && reboot` to get the new NTP service. Or > you could try a more targeted fix by adding the > 'allow-large-adjustment? #t' flag to your config.scm. Please ask on > IRC #guix if you need help :) > > [1] > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=08b4a10fa6bc535cd99d65f0233dd027153878eb The new generation actually introduces two unexpected elements: a. At the login section it proposes both gnome and mate environment (which is correctly usable only the latter) b. Once i login on Mate's de, i'm unable to use any menu's application (suggests something similar to "unable to spawn proccess gio-launch-desktop - missing directory") I wonder if i actually performed corectly root's commands, by accessing it via "sudo su -", is it the right way? (i remember there was a better one but couldn't find it on the manual) As you suggest i'll bring this quest onto irc so i can solve it in shared mode Grazie mille! Matias Jose Seco Baccanelli pgp9y852QXpiD.pgp Description: OpenPGP digital signature
Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
On Fri, Nov 01, 2019 at 10:13:11PM +0100, Matias Jose Seco Baccanelli wrote: > Benvenuti Guixers, > i wanted to share a time riddle which i'm unable to solve. > Actually my timezone is aligned to : > (timezone "Europe/Rome") > > Yet, system time is 1h 20m behind the official one > ~$ date > ven 1 nov 2019, 21.49.30, CET > (23.09 at the time of writing) > > My system was installed with the graphical installer, guix version > 1.0.1, Mate DE. Hm... I'm not sure but I have a guess. By default, ntpd will not change your clock if it is very wrong. If it is only a couple minutes wrong, then ntpd will slowly adjust the time, but if it is wrong by some large threshold, ntpd will simply give up. However, you can run ntpd with '-g, --panicgate', which will allow ntpd to make big adjustments to your clock. In Guix, this is called 'allow-large-adjustment?' and we made it the default in September 2019. [1] Maybe your system has not been updated since then? As root, can you check with `guix describe` and let us know exactly what it says? If that's the root cause, try doing, as root, `guix pull && guix system reconfigure [...] && reboot` to get the new NTP service. Or you could try a more targeted fix by adding the 'allow-large-adjustment? #t' flag to your config.scm. Please ask on IRC #guix if you need help :) [1] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=08b4a10fa6bc535cd99d65f0233dd027153878eb signature.asc Description: PGP signature
Re: ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
On Fri, 1 Nov 2019 22:13:11 +0100 Matias Jose Seco Baccanelli wrote: > Benvenuti Guixers, > i wanted to share a time riddle which i'm unable to solve. > Actually my timezone is aligned to : > (timezone "Europe/Rome") > > Yet, system time is 1h 20m behind the official one > ~$ date > ven 1 nov 2019, 21.49.30, CET > (23.09 at the time of writing) > > My system was installed with the graphical installer, guix version > 1.0.1, Mate DE. > [...] Salve! In addition to previous information, i wanted to ask if it would be possible to solve the time synchronization by installing further software. Actually my scm declares ntp service through %desktop-service variable. Should i add other properties ? Consider that i'm a beginner for Guix, so i don't know if i'm classifying correctly all the technical elements ^^ Thanks, have a wonderful time, Matias pgpfhOAmMJwnL.pgp Description: OpenPGP digital signature
ntpd: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Benvenuti Guixers, i wanted to share a time riddle which i'm unable to solve. Actually my timezone is aligned to : (timezone "Europe/Rome") Yet, system time is 1h 20m behind the official one ~$ date ven 1 nov 2019, 21.49.30, CET (23.09 at the time of writing) My system was installed with the graphical installer, guix version 1.0.1, Mate DE. Looking at the machine symptoms, i've found found the following errors from log 'messages': shepherd[1]: Service ntpd has been started. ntpd[288]: ntpd 4.2.8p13@1.3847-o Mon Mar 18 23:20:45 UTC 2019 (1): Starting ntpd[288]: Commandline: /gnu/store/c7lsm0nkrdkp1rapg6qkrr6121d1g2nh-ntp-4.2.8p13/bin/ntpd -n -c /gnu/store/1l1yf5dss8r9pqxklaax32s6bkah09c6-ntpd.conf -u ntpd ntpd[288]: proto: precision = 1.676 usec (-19) ntpd[288]: baseday_set_day: invalid day (25556), UNIX epoch substituted ntpd[288]: basedate set to 1970-01-01 ntpd[288]: gps base set to 1980-01-05 (week 0) ntpd[288]: restrict default: KOD does nothing without LIMITED. ntpd[288]: restrict ::: KOD does nothing without LIMITED. ntpd[288]: Listen and drop on 0 v6wildcard [::]:123 ntpd[288]: Listen and drop on1 v4wildcard 0.0.0.0:123 ntpd[288]: Listen normally on 2 lo 127.0.0.1:123 ntpd[288]: Listen normally on 3 lo [::1]:123 ntpd[288]: Listening on routing socket on fd #20 for interface updates ntpd[288]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized ntpd[288]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized ntpd[288]: Listen normally on 4 wlp2s0 192.168.1.109:123 ntpd[288]: bind(24) AF_INET6 fe80::1037:b214:ca40:cfe4%3#123 flags 0x11 failed: Cannot assign requested address ntpd[288]: unable to create socket on wlp2s0 (5) for fe80::1037:b214:ca40:cfe4%3#123 ntpd[288]: failed to init interface for address fe80::1037:b214:ca40:cfe4%3 ntpd[288]: Listen normally on 6 wlp2s0 [fe80::1037:b214:ca40:cfe4%3]:123 Am i missing some additional configuration for time updating properly ? Thank you very much, fondly, Matias pgpr1cg7jB4Qe.pgp Description: OpenPGP digital signature