The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @WietsedeBoer2: Als (grond)water zo schaars is, waarom krijgt dit bedrijf dan een vergunning voor oppompen van 500.000 m3 water? Ergens… 2 hours ago
    • RT @bitsoffreedom: Stel vragen! En belangrijker, dit is gewoon iets voor het kabinet om netjes te regelen, dat is beter voor de ondernemers… 2 hours ago
    • RT @Crash2411: This tweet was postmarked last month 2 hours ago
    • RT @Afelia: Mailadresse. Die politische Debatte über digitale Bildung hängt solide 15 Jahre hinterher. 3 hours ago
    • RT @TerliWetter: “Nahezu sein gesamter Maisbestand hat sich in Popcorn verwandelt. Schuld ist wohl die aktuelle Hitzewelle, die deutschland… 3 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,052 other followers

Force NTP Time Update on Linux | KrazyWorks

Posted by jpluimers on 2020/06/01

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:

–jeroen

SEC_ERROR_OCSP_FUTURE_RESPONSE

SEC_ERROR_OCSP_FUTURE_RESPONSE

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

 
%d bloggers like this: