Centos 7 - I can't fix the datetime

michaelk · 04-04-2022, 10:51 AM

I thought that chronyd started similarly to ntp and would force a time update. Try:

systemctl stop chronyd

chronyd -q 'pool es.pool.ntp.org iburst'

SPiKeGoD · 04-04-2022, 10:59 AM

Quote:

Originally Posted by michaelk

I thought that chronyd started similarly to ntp and would force a time update. Try:

systemctl stop chronyd

chronyd -q 'pool es.pool.ntp.org iburst'

Code:

[root@localhost ~]# systemctl stop chronyd
[root@localhost ~]# chronyd -q 'pool es.pool.ntp.org iburst'
2022-04-04T22:54:04Z chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
2022-04-04T22:54:04Z Initial frequency -50.037 ppm
2022-04-04T22:54:09Z System clock wrong by -24929.716105 seconds (step)
2022-04-04T15:58:39Z chronyd exiting

The time is the same

Code:

[root@localhost ~]# date
Tue Apr  5 00:54:13 CEST 2022

Code:

[root@localhost ~]# timedatectl
      Local time: Tue 2022-04-05 00:54:17 CEST
  Universal time: Mon 2022-04-04 22:54:17 UTC
        RTC time: Mon 2022-04-04 15:58:49
       Time zone: Europe/Madrid (CEST, +0200)
     NTP enabled: no
NTP synchronized: no
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2022-03-27 01:59:59 CET
                  Sun 2022-03-27 03:00:00 CEST
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2022-10-30 02:59:59 CEST
                  Sun 2022-10-30 02:00:00 CET

michaelk · 04-04-2022, 11:25 AM

I am confused.

Code:

2022-04-04T22:54:09Z System clock wrong by -24929.716105 seconds (step)
2022-04-04T15:58:39Z chronyd exiting

This looks like the time was updated from 22:54:09Z to 15:58:39Z which was the UTC at the time of posting.
Yet the output of the timedatectl did not change.

michaelk · 04-04-2022, 11:31 AM

With chronyd stopped can you manually set time using the date command?

SPiKeGoD · 04-04-2022, 11:37 AM

Quote:

Originally Posted by michaelk

With chronyd stopped can you manually set time using the date command?

The command doesn't do anything

Code:

[root@localhost ~]# systemctl stop chronyd
[root@localhost ~]# date -s "2022-04-04 18:37:30"
Mon Apr  4 18:37:30 CEST 2022
[root@localhost ~]# date
Tue Apr  5 01:32:49 CEST 2022

Code:

[root@localhost ~]# timedatectl
      Local time: Tue 2022-04-05 01:33:45 CEST
  Universal time: Mon 2022-04-04 23:33:45 UTC
        RTC time: Mon 2022-04-04 16:38:17
       Time zone: Europe/Madrid (CEST, +0200)
     NTP enabled: no
NTP synchronized: no
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2022-03-27 01:59:59 CET
                  Sun 2022-03-27 03:00:00 CEST
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2022-10-30 02:59:59 CEST
                  Sun 2022-10-30 02:00:00 CET

SPiKeGoD · 04-04-2022, 02:39 PM

@michaelk do you know any more things that i can check? Thanks you very much

michaelk · 04-04-2022, 03:41 PM

ntpdate should be install by default try:

ntpdate es.pool.ntp.org

SPiKeGoD · 04-05-2022, 01:16 AM

Quote:

Originally Posted by michaelk

ntpdate should be install by default try:

ntpdate es.pool.ntp.org

The command is working, but now also there are difference with de minutes not only in hours

Code:

[root@localhost ~]# ntpdate es.pool.ntp.org
 5 Apr 08:14:49 ntpdate[24116]: step time server 185.179.104.12 offset -24929.708733 sec

Code:

[root@localhost ~]# date
Tue Apr  5 15:10:21 CEST 2022

Code:

[root@localhost ~]# timedatectl
      Local time: Tue 2022-04-05 15:10:30 CEST
  Universal time: Tue 2022-04-05 13:10:30 UTC
        RTC time: Tue 2022-04-05 06:14:59
       Time zone: Europe/Madrid (CEST, +0200)
     NTP enabled: no
NTP synchronized: no
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2022-03-27 01:59:59 CET
                  Sun 2022-03-27 03:00:00 CEST
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2022-10-30 02:59:59 CEST
                  Sun 2022-10-30 02:00:00 CET

michaelk · 04-05-2022, 10:09 AM

Is this a physical or virtual machine?

Have you tried syncing the system clock to the hardware clock?

hwclock --hctosys

SPiKeGoD · 04-05-2022, 10:16 AM

Quote:

Originally Posted by michaelk

Is this a physical or virtual machine?

Have you tried syncing the system clock to the hardware clock?

hwclock --hctosys

I have tried a lot of things, and rebooted the machine and now it seems that it is OK:

Code:

[root@localhost ~]# date
Tue Apr  5 17:13:20 CEST 2022

Code:

[root@localhost ~]# timedatectl
      Local time: Tue 2022-04-05 17:13:25 CEST
  Universal time: Tue 2022-04-05 15:13:25 UTC
        RTC time: Tue 2022-04-05 15:13:25
       Time zone: Europe/Madrid (CEST, +0200)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2022-03-27 01:59:59 CET
                  Sun 2022-03-27 03:00:00 CEST
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2022-10-30 02:59:59 CEST
                  Sun 2022-10-30 02:00:00 CET

Code:

[root@localhost ~]# systemctl status chronyd
● chronyd.service - NTP client/server
   Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2022-04-05 13:27:27 CEST; 3h 46min ago
     Docs: man:chronyd(8)
           man:chrony.conf(5)
  Process: 780 ExecStartPost=/usr/libexec/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
  Process: 740 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 754 (chronyd)
   CGroup: /system.slice/chronyd.service
           └─754 /usr/sbin/chronyd

Apr 05 13:27:27 localhost.localdomain chronyd[754]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
Apr 05 13:27:27 localhost.localdomain chronyd[754]: Frequency -50.276 +/- 0.407 ppm read from /var/lib/chrony/drift
Apr 05 13:27:38 localhost.localdomain chronyd[754]: Selected source 178.32.88.247
Apr 05 13:28:44 localhost.localdomain chronyd[754]: Selected source 178.62.18.76

Better i don't go to use the "hwclock --hctosys", i was suffering a lot to fix it hehe

Thanks you very much for helping me