A while ago, I had a problem that one of my Raspberry Pi machines hadn’t been turned on for a while, so after a reboot the clock was way off.
This resulted in errors like the below: SEC_ERROR_OCSP_FUTURE_RESPONSE errors indicating the TLS certificates being not yet valid (and numerous other TLS certificate issues).
The /etc/ntp.conf was OK, and rcntpd status indicated the service was running. Looking at /var/log/ntp.log I saw a few syncing issues:
11 Feb 20:04:15 ntpd[1419]: receive: Unexpected origin timestamp 0xde15bc7f.59622c55 does not match aorg 0000000000.00000000 from server@93.94.224.67 xmt 0xde2b122f.0d222048
11 Feb 20:04:15 ntpd[1419]: receive: Unexpected origin timestamp 0xde15bc7f.595fec0e does not match aorg 0000000000.00000000 from server@213.154.236.182 xmt 0xde2b122f.0dc06af7
11 Feb 20:04:15 ntpd[1419]: receive: Unexpected origin timestamp 0xde15bc7f.595d4584 does not match aorg 0000000000.00000000 from server@149.210.199.182 xmt 0xde2b122f.0df70400
My guess was that the time was so much of (more than a month) that syncing would not work, so a manual force was needed.
[Archive.is] Force NTP Time Update on Linux | KrazyWorks provides two solutions:
sntp -r pool.ntp.org
# or
ntpdate -u pool.ntp.org
Only the last one works; I’m not sure why yet:
daisy:/etc # ntpdate -u pool.ntp.org
15 Mar 19:20:59 ntpdate[2516]: step time server 131.211.8.244 offset 4140423.716209 sec
Further reading:
- [WayBack] sntp – Simple Network Time Protocol (SNTP) Client
- [WayBack] ntpdate – set the date and time via NTP
–jeroen
SEC_ERROR_OCSP_FUTURE_RESPONSE
