Bugzilla – Bug 2438
SB2 stops working each night
Last modified: 2008-09-15 14:39:24 UTC
Since upgrading to 6.2. my SB2 stops working overnight - as an example, at 03:30 this morning, the time was displayed but at 06:00, there was no display and the alarm set for 06:30 has not worked. Pressing the power button on the remote gives the message 'waking up...' then the box connects back to the server and the alarm playlist starts. Settings for the SB2 are to display time & date under all three conditions (playing, not playing, powered off). The SB2 connects wirelesssly to an ADSL router while SlimServer runs on a Mac connnected by wire to the same router. All worked OK in the previous version of SlimServer.
is your mac shutting off as a power saver? "waking up..." message indicates a wake on lan packed being sent to the server.
No - I had thought that might have been the case because that's what happened the first day I had the SB so I went into Energy Saver settings on the Mac and changed the value of 'Put the computer to sleep when it is inactive for..' to 'Never'. I do, however, still have 'put the hard disks to sleep when possible' ticked - let me know if this is a problem. I only have default logging settings on and the only entry in the log which might be relevant is this: 2005-10-30 20:15:32.6453 Requesting web page to keep SlimServer unswapped, re-request interval is 30 minutes. which, understandably repeats every 30 mins. Not sure if this is relevant at all. Tonight's test has been to set the time forward to 03:30 and see if I can see when the SB display goes off. I'm wondering if there may be a connection with rescanning my music library....
That log messages is harmless. The refresh is there to keep the database active (mostly for mysql users). I'm still curious about the "waking up" message, as this would seem to indicate that the squeezebox has lost its connection to slimserver.
OK - How do we track whether the SB is losing its connection back to the Mac running Slimserver? Network in the house is really simple: Netgear DG834G ADSL router with 2 Macs connected via ethernet ports on the back. SB working wirelessly. All devices getting DHCP assigned addresses. Let me know what you want me to look at, logs to switch on etc. If we don't get the early morn ing issue sorted soon, it's going to affect my job continuity program ;-)
I'd advise contacting Slim Devices support as one option. Instinct is telling me this is a support problem as opposed to a bug. d_slimproto might shed some light on what the server is seeing. d_server option will also show any start/stop issues for the server itself. None of this will help debug wireless network issues, however, except maybe to show the result of reconnections.
I have contacted support on the issue and will pursue this course of action but still feel this is worth considering a bug because: (a) everything worked until the upgrade to 6.2 of Slimserver and (b) there appears to be a pattern around the time the device fails which is consistent. If it were simply inactivity causing the SB to lose connectivity with Slimserver, the same would happen during the day when I'm at work - there's an 8+ hour period during which it should (if it were a networking issue) fall off the network. Sorry to be such a stubborn cuss but can we continue to consider this a bug? I'll happily eat a large and very dry slice of humble pie if and when I'm proved wrong! In the meantime, I'll turn on the logging options you suggest.
you'll notice that I didn't close this report. As such, it is continued. It will be continued until you or someone at slimdevices confirms that a resolution is found, or some actual source is found that can be fixed with a patch. there is no need to presume that this is being dumped. It sounds like your server is running fine (since you can reconnect, and your mac seems to be staying on). it can even be that you have a neighbour who has recently taken up long phone calls on a new 2.4G phone at 3am. i write code, so without a specific code problem, there is little to be done here. Support can help debug networking issues, and isolate a source of the problem, whether it is hardware or outside interference. now, one other thing I forgot to check, have you tried the latest 6.2.1 build? If not, please do so.
Sorry for the delay in responding - I was doing the dance of smugness! Having changed the clock on my Mac to 03:30 earlier this evening, the SB switched off at somewhere between 05:48 and 06:15 in 'spoof' time. I can't get any more accurate than that as I wasn't in the room when it happened and I hadn't touched the Mac to turn on any of the debugging options as I wanted to see what would happen with complete inactivity on both Mac and SB. I've now turned debugging options on as suggested and am just downloading the latest nifghtly build of SlimServer. I have an early start tomorrow so there'll be a tetchy report if it still fails! Thanks for assistance and persistence on this one. Much appreciated.
so, then the question is what might you have scheduled at that time? rescan? a different alarm? check your settings before you end up missing another wake up.
Created attachment 979 [details] Log file showing SB2 crash
Log file attached showing SB2 crash with time set for alarm to go off at 06:30. Hope this helps a bit....
well, I can't ever make much sense of a slimproto log, but I dont see which point is the crash. There is a decoder startup which strikes me as odd. I don't know why a Squeezebox would request stream.mp3. That is usually an http client thing. (or so I thought). so essentially, still hunting the real bug behind all of this. did the alarm actually trigger properly then freeze?
Sorry the log didn't make much sense but, yes, the alarm did trigger properly. After it had played for some minutes, the sound went dead and the screen blanked. Stupidly, I didn't grab the log at that minute so I can't tell you what the relevant entry was. Development this morning is that the SB stayed working all night and the alarm worked. Changes made have been as follows: loaded 6.2.1 release, loaded Mac OS X latest software update, removed alarm plugin, reboted Mac. I'll let you know if all works well for the next couple of days.
Created attachment 982 [details] Log file showing latest SB2 failure This looks like I can now see when the SB2 goes AWOL - although it is now 18:55, last log is 18:30 amd the Squeezebox is dead. I hope this helps narrow down where the problem lies.
Is the CPU usage very high at this point? What state are you leaving the player in: idle, or off? What screensavers do you have set for that mode.
CPU usage average to low - mac is idle SB2 is left off - not playing Screensaver for this state is just time - HH:MM Hope this helps
darn. all three not what I was hoping to see :) I'm afraid I have no theories left here. Lets see what support has to say. You can always have kevin drop comments in here if progress is made.
Yes - and the slimproto logs aren't the best thing to be looking at. Kevin - have you talked to Jon?
OK - It's hands up time. I *think* I may have found the culprit and I don't *think* that it is the Squeezebox/SlimServer. In addition to upgrading to the latest nightly build earlier in the week and applying Apple's latest Mac OS X update, I also decided to look at the networking issue in a lot more detail. Although I am using a recent netgear ADSL router, I took the opportunity to turn on logging just to see if there was anything strange going on. I noticed that I had another problem on the SB and looked at the log on the router. The entry read: Sun, 2002-09-08 12:00:22 - Initialize LCP. Sun, 2002-09-08 12:00:22 - LCP is allowed to come up. Sun, 2002-09-08 12:00:27 - CHAP authentication success Sun, 2002-09-08 12:00:33 - Send out NTP request to time-g.netgear.com Wed, 2005-11-02 21:07:42 - Receive NTP Reply from time-g.netgear.com Which coincided pretty much exactly with the Squeezebox problem. Looking at the router, I found it was running really out of date firmware and upgraded it. Since then, I have run without problems for over 48 hours. In that time, I have also not seen the message in the router logs again so can only assume that the two might have been related. What can I say - I'm really sorry if I have had you chasing ghosts on this one. I really do hope that it was a networking issue and am now happy for you to close the issue as you see fit. My apologies if I wasted your time - I'll try and do more checking next time round.
great to hear that its working for you. I wont close this (I believe you can close yoru own reported bugs yourself). Give it some time if you want and you shoudl be able to close this off yourself when you are satisfied the issue really is gone.
Changing status to FIXED although, with recent investigations of ADSL router/switch, I am no longer convinced that this was either a bug with SlimServer or Squeezebox so a better status might be FALSE ALARM! Regardlesss, as it has now not repeated for several days, I think it is probably safe to consider the issue closed. Thanks to those who offered help/advice on this one - hope I didn't waste too much of peoples' time...