The server and this computer have a discrepancy in the current timestamp of around 281940 seconds. This may cause issues for HaikuDepot communicating with the server. Check your computer’s clock settings and correct the current time if necessary.
The time discrepancy has grown a day since yesterday, so it’s like one of us is stopped. My date looks OK to me. Is there something I need to take care of here?
is your CMOS battery dead? if not then try editing the time settings in haiku by going to preferences in the deskbar and clicking on time. from there change your date or time zone. use gmt (unix compatible) if local time (windows compatible) doesnt work
Synchronize at boot has always been “on”. Is the idea here, that there are multiple system times? One that I can see on the deskbar, UNIX date, etc., and another that HaikuDepot consults that could be days behind? Time and date has been fine here, all along.
If there’s a local problem, it wouldn’t the time per se, but something like some state in the package management client that wasn’t successfully updated.
It’s using real_time_clock() (here) to get the local clock and is using an API call back to the server to find out the server clock. You can see this in the class ServerRuntimeInformationVerifierProcess::_CheckAndNotifyExcessCurrentTimestampDelta. When I get this error message, the clock is visibly incorrect on the desktop display in the dock; I then sync it with the NTP server from the preferences and the problem goes away.