Bugzilla – Bug 9699
Controller loses music sources
Last modified: 2008-10-31 13:15:47 UTC
This may or may not be related to 7153. Unlike that bug, both components ping. I have a Duet that has been working fine, unless I do this: While it is running, use SqueezeCenter to change the music source from Squeeze Network to my computer. Then, use SqueezeCenter to change the music source back to SqueezeNetwork. Then, shut down the computer. Now the home menu of the controller displays only "Settings" and "Music Source". The name of the receiver is not displayed. "Music Source" contains only the entry "Other Server." The Duet is working fine from SqueezeCenter but the controller is useless. How can I get this working again? This happened once before, and I fixed it by factory resetting the controller. That is highly undesirable, as it loses all settings on the controller, including favorite radio stations. It was also only a temporary cure, as I now have the same problem again. How can this be fixed? I am using the latest SqueezeCenter dowload (don't know how to get the version number) on Windows XP + SP3. It displays this about the receiver: Name: Viburnum Model: receiver Firmware: 47 The IP address for this player is: 192.168.10.151:40555 The Ethernet MAC address for this player is: 00:04:20:16:22:21 Wireless Signal Strength: 90 The controller says it is connected to my network (settings/advanced/wireless network). I can ping both the receiver and the controller. The receiver pings in 0 ms, and the controller in 47 ms. The controller reports that it needs updating to an unknown firmware version (I doubt it). If I start the update, it says it can't do it. I am using a ZyXEL M-550 wireless router with latest firmware. The log file includes the following, which may be relevant: [08-10-11 09:43:51.7010] Slim::Networking::SqueezeNetwork::Players::_players_error (146) Unable to get players from SN: Connect timed out: Bad file descriptor, retrying in 300 seconds [08-10-11 09:43:51.7030] Slim::Networking::SqueezeNetwork::PrefSync::_syncDown_error (359) Sync Down failed: Connect timed out: Bad file descriptor, will retry in 43253 [08-10-11 09:44:03.0053] Slim::Networking::Discovery::Players::_players_error (140) Unable to get players: Connect timed out: Bad file descriptor This issue has taken a lot of the joy out of my purchase. Please help!
I forgot to say, I have tried power-cycling the receiver and the controller (separately and togther), and that has not resolved this. MHP
Ross to investigate
I can add more information. I got the Controller working again by resetting it to factory defaults. Regarding that: (1) I don't view it as a real solution, as it is a pain and it does lose settings -- though not the favorite radio stations, as I had feared. (2) It was not straightforward. In repeated attempts, the controller reported failure to obtain an IP address, although the ZyXEL router showed that a DHCP address had been assigned to it. Suddenly, and for no obvious reason, everything started working again. When working, the ping time (PC to Controller) is 1ms, rather than the ~47ms reported when the Controller had lost contact with the Receiver. None of that helps ME understand what is happening, but I hope it helps Logitech.
BUG 7153 may be related. Try tuning off Power Savings in the Controller.
Further information. The device was working fine last night. It was in the charging station for ~20 hr, and the symptoms have recurred. "Home," not player name, is shown on the Controller's menu. The home menu has only "Settings" and "Music Source." "Settings" says the controller IS connected to my home network, and it and can be pinged (see bottom of message), but it does not see the Receiver. I understand I might solve this by replacing the ZyXEL router with a Netgear unit. ((((Comments, please on that as a possible solution.)))) However, I hate to do that, as it's an added expense, and the ZyXEL works fine with everything else. If I can send any additional information that will help resolve this, please contact me. In the meantime, I will reset the Controller and turn off power saving to see if that helps. Pinging 192.168.10.106 with 32 bytes of data: Reply from 192.168.10.106: bytes=32 time=92ms TTL=64 Reply from 192.168.10.106: bytes=32 time=115ms TTL=64 Reply from 192.168.10.106: bytes=32 time=37ms TTL=64 Reply from 192.168.10.106: bytes=32 time=61ms TTL=64 Reply from 192.168.10.106: bytes=32 time=85ms TTL=64 Reply from 192.168.10.106: bytes=32 time=109ms TTL=64 Reply from 192.168.10.106: bytes=32 time=118ms TTL=64 Reply from 192.168.10.106: bytes=32 time=40ms TTL=64 Reply from 192.168.10.106: bytes=32 time=64ms TTL=64 Reply from 192.168.10.106: bytes=32 time=88ms TTL=64 Reply from 192.168.10.106: bytes=32 time=112ms TTL=64 Reply from 192.168.10.106: bytes=32 time=35ms TTL=64 Reply from 192.168.10.106: bytes=32 time=59ms TTL=64 Reply from 192.168.10.106: bytes=32 time=85ms TTL=64 Reply from 192.168.10.106: bytes=32 time=107ms TTL=64 Reply from 192.168.10.106: bytes=32 time=29ms TTL=64 Ping statistics for 192.168.10.106: Packets: Sent = 16, Received = 16, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 118ms, Average = 77ms
(In reply to comment #5) ((((Comments, please on that as a possible solution.)))) Mike, please see bug 7153. We have a known issue with Zyxel routers and our power management, did you try disabling it as James mentioned? Settings - Advanced - Factory Test - Power Management - disable wireless power save.
(In reply to comment #6) > > Mike, please see bug 7153. We have a known issue with Zyxel routers and our > power management, did you try disabling it as James mentioned? I have done it now. Is it also necessary, or desirable, to disable suspend?
If you'd like, you may. I have reproduced some issues with suspend that I was not able to reproduce without, that may not say much though. I'm curious, Mike when you see this issue what color is the wireless icon on your Controller?
(In reply to comment #8) > I'm curious, Mike when you see this issue what color is the wireless icon on > your Controller? Ross, the icon remains white. (I have seen it turn red a few times when the unit was working perfectly, but not lately.)
I turned off suspend and wireless power save about 48 hrs ago. No problems have occurred since (except quick battery discharge). As well as the issue reported here, this seems to have resolved a tendency of the unit to stop playing music after a short time for no obvious reason -- it MAY have been associated with screen-saver startup. After a few more days, I'll re-enable suspend and file a new bug ((or add to this one??? please advise)) if that causes a problem. Thanks to all for the help. Looking at reviews of wireless routers, I see that the ZyXEL M-550 has received far better customer reviews than most. Mine has given excellent throughput and not required resetting or adjustment in the 18 months I've had it. I very much hope that Logitech and ZyXEL will do what it takes to overcome the compatibility issues.
Based on your last comment this makes me think you're actually encountering bug 7153. I'm tempted to resolve this bug as nobody is seeing it any more, and it is confusingly similar to bug 8159. Mike, please let us know what you find with screen savers here in this bug. I will close this after 7.2.1 is live if nothing is discovered by then.
(In reply to comment #11) Ross, I've enabled "suspend" to check stopping problem & will report in a few days. I agree, this probably = 7153, though some symptoms differ. It differs from 8159, which requires just a reboot of the Controller, as here a factory reset is needed. Also, the Controller is always within wireless range. I hope that by "resolving" the bug you mean only as a duplicate, and that the compatibility w/ ZyXEL routers will be improved.
(In reply to comment #12) > I agree, this probably = 7153, though some symptoms differ. It differs from > 8159, which requires just a reboot of the Controller, as here a factory reset > is needed. Also, the Controller is always within wireless range. You may be onto something, however I think it is only different symptoms of bug 8159. My reproducible case is not the only case that will result in blue icon troubles, simply a reliable means of reproducing the symptom. > I hope that by "resolving" the bug you mean only as a duplicate, and that the > compatibility w/ ZyXEL routers will be improved. Exactly. There should be only one instance within bugzilla per each actual bug; I'm only trying to reduce clutter and confusion by resolving this bug. Bug 7153 is targeted for 7.3 and while I'm not sure Richard will have time to repair it in time, it will not be forgotten. You're not the only ZyXEL user affected. Please do keep us posted on your screen saver testing here in this bug.
(In reply to comment #13) > Please do keep us posted on your screen saver testing here in this bug. Enabling "suspend" appears to bring on a milder form of the bug. When I took the Controller out of its charger, the Home menu read "Home" rather than the player name, and it was shortened to only "Settings" and "Music Source". However, after several unsuccessful attempts, the Controller was able to bring contact the SqueezeNetwork and the player, whereupon the player name appeared and the menu expanded -- i.e., normal operation resumed. So I have disabled "suspend" again. I am happy to say that the screen savers have not triggered any problems when power management is off.
Two weeks later, the Duet is still working perfectly -- with power saving and suspend turned OFF. Battery life is only ~3 hrs, though ... way too short. Based on Ross's comments, I'll expect this bug to be rolled into 7153. I am willing to serve as beta tester if that will expedite a solution, particularly if the proposed solution has been tested with an M-550 in the lab.
Thanks Mike for reporting back, and thanks for hanging in there with us. *** This bug has been marked as a duplicate of bug 7153 ***