I posted logs and comment here: http://forums.slimdevices.com/showthread.php?t=56079

This appears to be the correct thread: http://forums.slimdevices.com/showthread.php?t=56226 :)

Changing target to next release

Please don't preset the Target on bugs, that will get done during bug review

slimproto log might be interesting

Any chance this is related to the controller time stuck problem I reported in bug 10498?

(In reply to comment #6)
> Any chance this is related to the controller time stuck problem I reported in
> bug 10498?
> 

It could be, since SC drives the clock function for both players.

Can you attach a log file?

*** Bug 10498 has been marked as a duplicate of this bug. ***

Here's a log, with proto activated as requested in the Beta forum.

http://pastebin.com/f679a8124

Server was put to standby in the morning, turned back on at 22.31, clock remained stuck.

This happened by waking up the server with the power button on the case, not by WOL.

I am experiencing the same kind of problem with my SB 2, firmware 121. It started when I installed 7.3.1

I reported 10498 on the controller.  I haven't seen it again.  However, I do not use WOL - my SC runs 24/7.  So whatever caused my problem, it is NOT WOL.

Looking at this bug now, attempting to reproduce and generate logs.  Target will be changed once we understand the cause of the bug.

I have the same problem randomly on my boom and on squeezebox2 and squeezebox3 when waking up the server from Windows standby mode (running SC 7.3.2).

Everyone with this error - please list what 3rd party plug ins you are using.

I have YET to reproduce this issue.

It would also be helpful to have step - by - step instructions on a reproducible case, as well as LOG files.

Please turn the following logs to DEBUG, reop the error, then attach the logs to this bug:

network.protocol
network.protocol.slimp3
network.protocol.slimproto

I have only LazySearch, latest version.
As far as the logs you ask for, I'll activate them and report back once the error happens again.

James, here's the new log with the settings you asked for:

http://pastebin.com/f3fc4793e

The server woke up at 11.09 and the clock remained stuck to 11.09 until I stopped the service and copied the log to pastebin.

I hope this will help.
Cheers!

I also have this problem, no with WOL but waking the computer from standby with Windows Tasks.

I have the following plugins installed:
SuperDateTime ScreenSaver 5.8.2
Music Information Screen 4.3.6

Thanks!

Is there some interaction between the players getting powered off and the server waking up?  Like, is the player power disconnected, then the server sleeps, then the player is powered up and the WOL is sent?

Another possibility, could you have a windows clock display up when the server is rebooted?  Is the overall windows clock incorrect after the WOL?

If you just leave it alone for a long time, does it eventually correct itself?

OK, this is the situation for me:

I put my computer in standby during night (the computer which runs SqueezeCenter). In the morning I power it on. Then the display gets stuck. I am not really sure, but I think it is on the time when I powered on my computer. It stays this way for at least several hours. The only way I have found which sets time correctly is to power cycle the Squeezebox...

I am not running any special plugins at all.

>Is there some interaction between the players getting powered off and the
server waking up?  Like, is the player power disconnected, then the server
sleeps, then the player is powered up and the WOL is sent?

No. Only the server is put in stand by. The player is never turned off.

>Another possibility, could you have a windows clock display up when the server
is rebooted?  Is the overall windows clock incorrect after the WOL?

The windows clock is correct.

>If you just leave it alone for a long time, does it eventually correct itself?
It does not correct itself, unless you turn the player on.

It seems that when the server turns on again (actually it was never turn off exactly, it is put into stand by, so the server isn't started again, it just resumes from where it was before), it sends some message to the player, and this makes the players clock freeze. Or else the server is always sending the the same time to the player, not increasing the minutes or seconds.

Yes, the time that gets stuck is the time the computer turns on again. From then on, the computer's time continues normally, but the player's is never updated.

In my case the server was not rebooted but only in Windows standby mode. I have set the server to go in standby mode after 45 min idle time. I have turned off my squeezebox using the remote and then the server went into standby mode after some time (this could be much later than 45 min after having turned of the squeezebox since there is a further computer which sometimes has a connection to the server which prevents standby mode of the server).

But finally the server was in standby mode which could be seen on the blank (black) display of the squeezebox. I then pressed the power button on the remote which does not directly turn on the squeezebox (since the server is in standby) but which brings the server back from standby mode. After that the squeezebox was still powered off but now displayed the correct current time which was however  freezed immediately (the seconds were not running). When I then again pressed the power button on the remote the squeezebox turned finally on and shows the normal menu. I then turned power off again to display the time and now it was correctly running.

do all of you "power off" (using the remote button) the SB before the computer
goes to sleep?

Sometimes, sometimes not - does not seem to make any difference.


(In reply to comment #23)
> do all of you "power off" (using the remote button) the SB before the computer
> goes to sleep?
> 

I also saw this error this morning again.

Setup:

WHS running a 7.3.2 build of squeezecenter.
Server goes to hibernation mode using the server power control plugin after 30
minutes of inactivity.
Usually two squeezeboxes are connected.
One Boom and one Classic. (all connected through WLAN).
All players where powered off before the server went into hibernation.
(Power Save plugin powers off all players after 15 minutes idle and the server
power control plugin will also power off players before going to standby).

In the morning the server wakes at 6:20. (programmed in the server)
The boom had an alarm scheduled at 6:45 which worked as expected.
At about 7:00 I had a look at the classic which was still showing 6:20 on the
display.

(In reply to comment #23)
> do all of you "power off" (using the remote button) the SB before the computer
> goes to sleep?
> 

Yup, even if the SB is powered off the bug occurs just the same.

Here's my tuppence worth:

I've only seen this happen once so far with the Date and Time screensaver but I did see it a few times over Christmas with the Snow screensaver activated.  The falling snowflakes just froze in place leading me to think my Squeezebox 3 had crashed or something.  Turning the squeezebox on and off again with the remote cleared it.

When it happened with the Date and Time screensaver I was already aware of this bug (courtesy of the forum) so I ignored it.  When I looked a few hours later it had indeed sorted itself out.  I'm afraid I can't say whether this was as a result of something I did with my PC or if it just unstuck itself.

All the above happened while I wasn't using the Squeezebox so it was permanently in Standby (apart from the aforementioned time I switched it on and off again to clear it).

I just thought it was worth mentioning that this appears to be an issue with screensavers, rather than specifically a clock display problem.

(In reply to comment #23)
> do all of you "power off" (using the remote button) the SB before the computer
> goes to sleep?
> 

Yepp...

I only want to mention that I haven't had this error since my last report (January 12, 2009). Since then I have several upgraded to nightly releases (presently 7.3.2). Could it be that this bug has been fixed by chance or can anybody still recognize this bug with a current version of SqueezeCenter?

I also had this bug when using 7.3.2, it used to always happen.

Now upgraded to a nightly 7.4 (7.4 - 24762) and no more sticky clock. Perhaps it has been fixed??

Well, I just updated to latest nightly and today my players time stuck again. So the bug is still there for me...

Yeah, i am on the lastest 7.4 and i still see thgis.

However, the behaviour seems slightly different now - it will stay stuck for a while (after reconnecting to the server), then it will revert to the correct time, keep the correct time for a while then free again, even if the server had not slept/woke during that time.

I have seen this on an SB now.

SB in standby
SC server set to sleep after 1 hour
System attempts to sleep, but gets woken up (bug 10810)
At some point the server can no longer connect to the player (player count = 0), at which point the clock on the player will get 'stuck'

Also note, that when this happens, SC Web UI does not see any players attached.

Restarting SC will reconnect the player
Power Cycle player will reconnect to the server
==================================================
[09-02-02 07:13:45.4533] Slim::Web::Cometd::sendHTTPResponse (669) Sending Cometd chunk:
[{"data":{"other player count":"20","info total albums":"4257","player count":"0","version":"7.2.1","sn player count":"0","info total artists":"1368","info total songs":"43934","info total genres":"123","other_players_loop":
==================================================
The player that was attached to the server in question, was not found in the player_loop list

QA to get a wireshark log of the packets

Update on my previous comment. I'm still getting this bug on 7.4.

I'm seeing this on Boom after the server wakes up from sleep to run a scheduled task.  The Boom local clock shows the corrrect time whilst the server is sleeping, but gets stuck one minute before the server wakes up on its schedule.

My clock is stuck right now; I have the SqueezeCenter (7.3.2) web interface open and it shows my Squeezebox attached.  If I turn the Squeezebox on and off via the web interface the clock starts running again.

We are now planning to make a 7.3.3 release.  Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future.

Thanks!

With Version: 7.3.3 - 25463 @ Wed Mar 11 03:05:39 PDT 2009 I had a stuck clock on my Squeezbox Boom some days ago.

I have this bug also on my SB3 on Win XP Mediacenter Edition with SqC 7.3.2. I have been in contact with Logitech customer support and after weeks of trying out different solutions (re-installing Squeezecenter software, reprogramming SB3's xilinx chip, reflashing firmware, reset to factory defaults) to no avail, I was pointed to this bug.

Here is some text copied from my support ticket giving some diagnostic information:

* if my mediacenter PC comes out of standby on its own, that is to
record a show, the clock is frozen on the standby time.
* if in this situation I manually put my PC in standby by pressing the
power button and wake it up again by pressing the power button, the
clock updates ONCE, showing the right time, but then its time is frozen
again.
* when the squeezebox time is frozen and I push a button on the remote
it awakes properely, if I then use the SB's remote's power button to
"shut it down" again, actually putting it in stanby, the clock shows again and its running ok
* when in that case I push the PC power button to put it on standby and
rewake it again, the clock DOES run and show the right time.

Note the most curious thing: IF the clock is frozen and you cycle the PC to standby and resume, the clock updates ONCE to the right time but is still frozen.

This bug has been bothering me for 3 months.

I try to use the Boom as my alarm clock in the morning, but it is very unreliable. Some mornings the clock gets stuck. Some mornings it doesn't.

Unfortunately I haven't found a pattern to reproduce this bug consistently, but the bug is there for sure.

Some times I find that the clock gets stuck even when the computer and Boom are turned on.

*** Bug 11560 has been marked as a duplicate of this bug. ***

Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out.  If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it.

Thanks.

For some reason Bugzilla did not change the target when I did this yesterday.  Or maybe it was me.  In either case, I'm trying it again.

Does this bug really need to get pushed forward again? It's a pretty common bug and not having the correct time it quite a big deal for some people. I think it needs greater priority and im very surprised it has not been properly addressed yet TBH.

I'd also like to see this get the proper attention.
I see this bug on one of my Squeezboxes every morning and it really annoys me to see it display the wrong time.

Well, this is starting to get really embarrassing. Four months without any real attention from SD. And now pushed again. Well, it seems like my outstanding Booxbox purchase will be on hold indefinitly. I have been using SB2 for about four years without major hickups. all the small details have been taken care of. But now something major hits me (yeah, for me a not working clokc is major) and SD totally ignores it. With proper attention it cannot be that hard to find a bug introduced in a certain firmware update. I am disappointed...

I second that.

Please fix this bug.

Yes me too please fix this soon!!!! I use the clock in my living room. When you take a glance at the time and do not notice its not running, you can imagine the irritation later on when you discover you are too late for something.

Could everybody please update to the latest 7.3.3 nightly build, disable all 3rd party plugins and try again?

I still can't reproduce this issue.

> I still can't reproduce this issue.

As I sent this and went back to my test-installation, there it was: updating once, then again after about 90 seconds, but definitely not correctly.

It's not in the date/time screensaver, but the underlying screensaver code. The line mode isn't called any more. Investigating.

Created attachment 5063 [details]
--debug server.timers=info

For whatever reasons S::B::Common:_periodicUpdate is triggered after the wakeup (17:35), but either doesn't set a new timer, or it fails in some other way. 

Can anybody confirm this behaviour? Set server.timers=info, go to standby, wait 5-10 minutes (or more) and wake up. Check the lot around the time you woke your machine up.

change 25873 - only adjust timers when the server travelled back in time, as the queue isn't influenced when travelling forward (eg. waking from suspend mode)

Would this patch not be better just removing the forward check?  (I think this is how it used to be)

However have we reviewed why the forward check was added as I don't think it was there originally?  (perhaps review with Max as he had problems with the alarm stuff at one stage)

The check had been added to update boom's RTC - which is still needed. We could rearrange the code a bit, but performance wise it seems good the way it is now.

My Boom clock freezes nearly every night since i sent my macmini to sleep at night. The Boom clock freezes exactly in the minute, the mini is waken up by its RTC-event.

SC-version: 7.3.2 on mac os x

Please see comment #53 - this issue is fixed in 7.3.3.

SqueezeCenter 7.3.3 appears to address this issue.  Would everyone please try that version, then report in the bug if your issue is resolved.

Please download 7.3.3 from here:  http://downloads.slimdevices.com/nightly/?ver=7.3

I used to see this problem every day, but haven't seen it since updating to SC 7.3.3 - 26488 for 3 days ago.

Same here, I have not seen this bug appear since I installed 7.3.3. Thank you!

This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html 

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

This happens on a QNAP 809 Pro as well, have the issue right now using the latest version available on the web 7.3.3

Thanks

This happens on a QNAP 809 Pro as well, have the issue right now using the latest version available on the web 7.3.3

Thanks