![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2022-08-20 06:28, Charlie Chan wrote:
Hello,
This little weird problem has confused me for some time, but I can't find any related situation from Google.
Since quite some time ago when I boot up, the system time is never correct at first. It shows the date which is a month or two before, and the time is always 8am. But after 3-4 mins the system time becomes normal and accurate again. So every time when I logged into the system and opened a browser window immediately, the browsers would give a NET::ERR_CERT_DATE_INVALID complaint.
It looks like it's something related to the NTP daemon. I am using Network manager under Plasma desktop with WiFi enabled. I'm not sure if only after Network Manager starts up my wifi then the NTP daemon begins to sync time, which in turn causes this problem? But this set up is quite common and I couldn't find any similar cases from other users, so maybe there's another reason?
Thanks in advance.
The problem is the CMOS clock that keeps the time while the machine is switched off; yours must be a month off. Now this is a bit strange, because with a dead battery it would be years off. And if the battery is OK, it should be adjusted to the correct time when ntp syncs. So check the battery with a meter if you have it. Or: sensors | grep -i bat (if that doesn't work, run first "sensors-detect") On my desktop machine: cer@Telcontar:~> sensors | grep -i bat Vbat: +3.31 V (min = +2.70 V, max = +3.63 V) cer@Telcontar:~> Then try these commands in sequence to reset the cmos clock: rm /etc/adjtime (or rename) hwclock --utc --systohc hwclock date On next reboot, time should be Ok. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)