PDA

View Full Version : 6.3 Latest SVN Startup Problem



atlslim
2006-06-05, 19:58
Performed SVN checkout of latest 6.3 branch (rev 7758) tonight.

Command line startup hangs w/ the following message:

2006-06-05 22:48:57.7342 Loading device description failed with error: 500 Can't connect to 192.168.2.1:5678 (connect: Unknown error) at Slim/Utils/UPnPMediaServer.pm line 62

(W2K machine w/ ActiveState Perl)

andyg
2006-06-05, 20:35
On Jun 5, 2006, at 10:58 PM, atlslim wrote:

>
> Performed SVN checkout of latest 6.3 branch (rev 7758) tonight.
>
> Command line startup hangs w/ the following message:
>
> 2006-06-05 22:48:57.7342 Loading device description failed with error:
> 500 Can't connect to 192.168.2.1:5678 (connect: Unknown error) at
> Slim/Utils/UPnPMediaServer.pm line 62

What device is 192.168.2.1? I wonder if we have problems with other
UPnP devices on the network.

Dan Sully
2006-06-05, 20:44
* Andy Grundman shaped the electrons to say...

>>2006-06-05 22:48:57.7342 Loading device description failed with error:
>>500 Can't connect to 192.168.2.1:5678 (connect: Unknown error) at
>>Slim/Utils/UPnPMediaServer.pm line 62
>
>What device is 192.168.2.1? I wonder if we have problems with other
>UPnP devices on the network.

Many routers do UPnP, for automatic port-opening for things like iChat.

If something falsely advertises as a:

urn:schemas-upnp-org:device:MediaServer

there may be issues.

-D
--
<faisal> my life is collapsing to what will soon be NEGATIVE INTEGER degrees of separation.

atlslim
2006-06-06, 08:03
On Jun 5, 2006, at 10:58 PM, atlslim wrote:

>
> Performed SVN checkout of latest 6.3 branch (rev 7758) tonight.
>
> Command line startup hangs w/ the following message:
>
> 2006-06-05 22:48:57.7342 Loading device description failed with error:
> 500 Can't connect to 192.168.2.1:5678 (connect: Unknown error) at
> Slim/Utils/UPnPMediaServer.pm line 62

What device is 192.168.2.1? I wonder if we have problems with other
UPnP devices on the network.

Andy,

I'm not finding any device at this IP address. Do I need to troubleshoot my router (Linksys) settings?

andyg
2006-06-06, 08:06
On Jun 6, 2006, at 11:03 AM, atlslim wrote:

>
> andyg Wrote:
>> On Jun 5, 2006, at 10:58 PM, atlslim wrote:
>>
>>>
>>> Performed SVN checkout of latest 6.3 branch (rev 7758) tonight.
>>>
>>> Command line startup hangs w/ the following message:
>>>
>>> 2006-06-05 22:48:57.7342 Loading device description failed with
>> error:
>>> 500 Can't connect to 192.168.2.1:5678 (connect: Unknown error) at
>>> Slim/Utils/UPnPMediaServer.pm line 62
>>
>> What device is 192.168.2.1? I wonder if we have problems with other
>> UPnP devices on the network.
>
> Andy,
>
> I'm not finding any device at this IP address. Do I need to
> troubleshoot my router (Linksys) settings?

That's odd. Look around for any UPnP settings in your router and try
disabling them.

andyg
2006-06-08, 08:16
On Jun 5, 2006, at 10:58 PM, atlslim wrote:

>
> Performed SVN checkout of latest 6.3 branch (rev 7758) tonight.
>
> Command line startup hangs w/ the following message:
>
> 2006-06-05 22:48:57.7342 Loading device description failed with error:
> 500 Can't connect to 192.168.2.1:5678 (connect: Unknown error) at
> Slim/Utils/UPnPMediaServer.pm line 62

This bug has been fixed starting with the 6/8 nightly. 192.168.2.1
is likely a UPnP device on another subnet that is found by multicast
but can't be reached directly from the network SlimServer is on.

atlslim
2006-06-08, 10:10
Thanks Andy. Still haven't determined where the 'rogue' device is, but this gets me running w/ 6.3.

Just a point of clarification: is the expected behavior that the device is queried every 10 minutes or only once if it fails to be detected? I'm seeing the former and get a slight hiccup in streaming radio as the device is queried every 10 minutes.

andyg
2006-06-08, 10:18
On Jun 8, 2006, at 1:10 PM, atlslim wrote:

>
> Thanks Andy. Still haven't determined where the 'rogue' device is, but
> this gets me running w/ 6.3.
>
> Just a point of clarification: is the expected behavior that the
> device
> is queried every 10 minutes or only once if it fails to be
> detected? I'm
> seeing the former and get a slight hiccup in streaming radio as the
> device is queried every 10 minutes.

It does check every 10 minutes and has a timeout of 2 seconds. I
didn't want to blacklist a failed device completely because it may
just be down or not responding, and may come back up later. Are you
using an SB1? Ideally the check would use AsyncHTTP but the code is
in an external UPnP library and would need to be pulled into the Slim
namespace if we use our async HTTP code. Or we might be able to
reduce the timeout to 1.

atlslim
2006-06-08, 10:43
I'm currently at my PC (using Softsqueeze) so I'm not sure if the stream/buffer issues during the query are present on my wired boxes. I have both SB1 and SB3 so I can check later.

Thanks.

Dan Sully
2006-06-08, 10:45
* atlslim shaped the electrons to say...

>I'm currently at my PC (using Softsqueeze) so I'm not sure if the
>stream/buffer issues during the query are present on my wired boxes. I
>have both SB1 and SB3 so I can check later.

I had the device on a strange subnet problem come from VMWare Network
Adaptors on my Windows box.. you might want to check for things like that.

-D
--
You know, for kids.