2022-08-24T09:24:13Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG) 2022-08-24T09:24:17Z System clock wrong by -58.289906 seconds (step) 2022-08-24T09:23:19Z chronyd exiting...
2021-05-25T01:59:42Z System clock wrong by -0.006248 seconds (step) 2021-05-25T01:59:42Z chronyd exiting 1. 2. 3. 4. 5. 从上面的输出中可以看到,chrony已校正了系统时间。 Start 和 Enable chronyd 服务 运行以下命令以启用chronyd服务: [root@server1 ~]# systemctl enable chronyd [root@...
Apr 28 05:33:10 localhost chronyd[1216]: Can't synchronise: no selectable sources Apr 28 05:36:24 localhost chronyd[1216]: Selected source x.x.x.x Apr 28 05:36:24 localhost chronyd[1216]: System clock wrong by -3444.493726 seconds, adjustment started Apr 28 05:42:01 localhost chrony...
Apr 28 05:33:10 localhost chronyd[1216]: Can't synchronise: no selectable sources Apr 28 05:36:24 localhost chronyd[1216]: Selected source x.x.x.x Apr 28 05:36:24 localhost chronyd[1216]: System clock wrong by -3444.493726 seconds, adjustment started Apr 28 05:42:01 localhost chrony...
$ docker logs -f ntps [...] 2021-05-25T18:41:40Z System clock wrong by -2.535004 seconds 2021-05-25T18:41:40Z Could not step system clock 2021-05-25T18:42:47Z System clock wrong by -2.541034 seconds 2021-05-25T18:42:47Z Could not step system clock ...
The clock does not need to be synchronised, but another time source is needed to complete the PPS samples. Note that some PTP clocks cannot be configured to timestamp only assert or clear events, and it is necessary to use the width option to filter wrong PPS samples. pin=index This ...
$ docker logs -f ntps [...] 2021-05-25T18:41:40Z System clock wrong by -2.535004 seconds 2021-05-25T18:41:40Z Could not step system clock 2021-05-25T18:42:47Z System clock wrong by -2.541034 seconds 2021-05-25T18:42:47Z Could not step system clock Good question! Since ...
$ docker logs -f ntps [...] 2021-05-25T18:41:40Z System clock wrong by -2.535004 seconds 2021-05-25T18:41:40Z Could not step system clock 2021-05-25T18:42:47Z System clock wrong by -2.541034 seconds 2021-05-25T18:42:47Z Could not step system clock ...