Jonathan Struebel's picture

I've been getting the following error from cron for the last 24 hours whenever it tries to run the hubdns-update script. I checked in my Turnkey Hub console under the AWS Account Access and it is reporting "RequestExpired" for Route53. All other AWS services are "Passed". I checked my server date/time and it agrees with the NIST time which I'm assuming AWS is synced to as well. Can you please check on the time sync of Turnkey Hub? Let me know if there is anything else you need me to check to ensure my server is synced correctly.

error: FQDN update error: Request timestamp: Mon, 09 Jan 2017 03:17:55 GMT expired.  It must be within 300 secs/ of server time.
run-parts: /etc/cron.hourly/hubdns-update exited with return code 1


Jeremy Davis's picture

Thanks for the report Jonathan.

FWIW I have just had 2 similar reports (via support requests). I will forward the info to Alon and get him to look into it ASAP. AFAIK the Hub has a cron job to keep time in sync, but perhaps something has gone wrong with that?

[Update] I have spoken with Alon and he will be looking into this today (Israel time) as his priority. It will be back online ASAP. Hopefully within a few hours...

Alon Swartz's picture

One of our servers had a time drift, which I just fixed. We'll be investigating how that happened, and make sure it doesn't happen again. Sorry about that, and for the late response.
Jonathan Struebel's picture

Thank you for the quick response. In the future is this the best place to report things like this or should I use the support chat on the hub?
Jeremy Davis's picture

Either way is fine. Even though I don't post in the forums as often or as regularly as I'd like, I do monitor them regularly. Primarily that is to remove spam, but also to note any important issues that may need immediate action (like this one).

Add new comment