Bugzilla – Bug 4115
Rhapsody UPnP server doesn't always show up
Last modified: 2008-12-18 11:12:53 UTC
I've noticed that nearly 1/3 of the time I open Rhapsody, my SlimServer either running on the same computer, or another computer on the network (or sometimes both) will not 'see' the Rhapsody server. I've found that reloading the browser doesn't help, and restarting Rhapsody often doesn't help. However if I start/stop the UPnP server within Rhapsody sometimes then it will show up in SlimServer, if that doesn't work then I try stopping UPnP server, renaming it, and then starting it again. This works most of the time, however there are still times (like right now) that the Rhapsody server still doesn't show up in SlimServer.
If Rhapsody doesn't get detected right after signing in, try waiting a few (maybe 10) minutes. It should send out notify messages every few minutes, and so it may get picked up later. It's possible the initial packets are being lost. When I was first working on the UPnP stuff, I was sending out a lot of malformed UPnP packets. Whenever Rhapsody saw these, the UPnP service would die, the UPnP service button would change to Stopped, and I would have to restart Rhapsody before it worked again. If there is something on the network sending out a bad UPnP packet, it could cause this problem. Nothing we can do about this at the moment. My step-daughter has a Rhapsody account and at least once a day she has to restart Rhapsody because it just goes away in SlimServer. I have another instance running on the same network and it doesn't experience this problem. So who knows, the Rhap app is just not the most stable piece of software.
One other thing, try running with --d_upnp, this will report notification messages from UPnP services on the network. As soon are you start SlimServer (if Rhapsody is already running), or as soon as you sign in to Rhapsody, it should be detected.
Thanks for working with me on this one Andy, I know we've talked about this before. Here's what I'm doing, I have a mac and a PC both running 6.5b3, then I open Rhapsody on the PC obviously. Most often the Rhapsody server will only show up in one or the other, rarely both. For instance this morning I opened Rhapsody, and immediatly SlimServer on the PC sees the Rhapsody server, but the mac does not. I waited 15 minutes, SS on the mac still doesn't see Rhapsody.
Are they on different subnets maybe? Try running tcpdump on the Mac and look for any SSDP packets from the Rhapsody PC.
There are indeed some SSDP packets from the PC, many that say "NOTIFY * HTTP/1.1[Packet size limited during capture] Both computers are on the same subnet. I'm now noticing that the Rhapsody is showing up in both SlimServers, here about 2 hours later.
When you get a chance, Ross, I'd like for you to try to reproduce this downstream of one of my routers on your own tiny network, to see if that has an effect.
Just assigning this to you for when you get a chance, Ross. Also I don't think it's serious enough to hold up the 6.5.1 release.
I have nothing definitive to add other than to say I've experimented with this at home, and here at work by creating in a small closed network with just my PC and a Squeezebox, and then Rhapsody's UPnP server shows up MUCH more consistently. At home there are a few other UPnP devices on the network, primarily for the Xbox 360's music share plugin, and there I notice that Rhapsody's UPnP server shows up more consistently than here at work, but less consistently than on my mini network. In other words with just one computer and a Squeezebox its nearly bullet proof. A network with a few other UPnP 'things' then Rhapsody doesn't show up consistently. Here at work, with our network of who knows what... it seems to be 50/50. While this may be an issue, I see no reason to keep this bug open. Andy or anyone who disagrees please go ahead and reopen this bug.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.