Bugzilla – Bug 15048
Uninitialized Linux date and time results in incorrect date/time in logs, wrong time displayed on connected players, failure to scrobble etc.
Last modified: 2010-04-08 17:25:56 UTC
Running with firmware 7.5.0 r8005. The date and time stamps in logs is off. For example: [69-12-31 21:05:13.6842] main::init (341) Starting Squeezebox Server (v7.5.0, r29151, Wed Nov 4 02:14:56 PST 2009) perl 5.010000 I think that's December 31 1969. That was an interesting year, but it's not correct!
This is normal and should get fixed when you connect to a server.
Mickey is this really happening in a 'normal' use case?
After playing the logs a little bit, it appears to correct itself. Don't know how or when. Reducing priority given this finding.
This is a P1: several features depend on the clock (screensaver, logging, Last.FM handshake etc.).
re. comment 1: I'm seeing this when connecting to tinysc...
We could TinySC have look the time up on mysb.com. Might need to expose that call to the web UI and make it part of the mysb.com handshaking or something.
s/web UI/web service/
The problem we'd like to solve here is setting the fab4's time when it's connected to itself (tinysc). In the other cases the server will tell fab4 the time. My suggestion is quite simple: the Slim::Networking::SqueezeNetwork->login() already receives a time stamp from mysb.com in its response ( "time" => "1259963741" ). We can read this value, send it to the "date" listeners, which in turn will set the system's clock. In order to keep the time accurate, S::U::OS::SqueezeOS could trigger that quick request on an hourly basis. Sounds a bit backwards, but imho the simplest solution with the least code changes required. Most of it is already in place. The remaining changes would only be implemented for SqueezeOS/TinySC, thus safe for the other systems. All this is assuming there's a good reason we don't use NTP. I don't know the history and backgrounds of this issue...
This sounds like a good solution. we should at least try it. We don't use ntp because the full implementation is too big - but the real issue is what servers to point it at. We do have msntp in the build but are not using it just yet. We could switch it it if we have to but let's see how your suggestion works first.
== Auto-comment from SVN commit #29555 to the slim repo by michael == == https://svn.slimdevices.com/slim?view=revision&revision=29555 == Bug: 15048 Description: if SBS is run on SqueezeOS it doesn't know about the current time. We have to ask mysb.com and let subscribers know about the real time. There's still a problem with the scanner being triggered when the time is adjusted.
== Auto-comment from SVN commit #29562 to the slim repo by michael == == https://svn.slimdevices.com/slim?view=revision&revision=29562 == Bug: 15048 Description: use cheaper and public /api/v1/time query instead of login request
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!